Join the OracleApps88 Telegram group @OracleApps88to get more information on Oracle EBS R12/Oracle Fusion applications.

If you are facing any issues while copying the Code/Script or any issues with Posts, Please send a mail to OracleApp88@Yahoo.com or message me at @apps88 or +91 905 957 4321 in telegram.

Tuesday, September 8, 2015

Oracle Payables Standard Features Differences between 11i and R12

Sl
Standard Features
11i
R12
1
Few Features like invoice Lines, Line level approvals, Matching to a PO shipment or receipt, Suppliers in TCA makes a complete new look.
• Suppliers defined in AP.
• Supplier contacts replicated for each supplier site.
• Supplier becomes as TCA Party.
• Suppliers Sites as TCA Party Site for each distinct address.
• Contacts for each supplier/address , it means Single supplier address and contact can be leveraged by multiple sites, for each OU
o A single change to an address can be seen instantly by all OUs
o No longer need to manually 'push' updates across OUs.This can be best understood by the figure below
2
Invoice
• Had only distributions line.
• Allocation of freight and special charges are captured at the distribution level only
• Tax and payment and Project accounting Payment was captured through global Descriptive Flexfields.
Invoice Lines as a new additional line accommodated in Invoice data model
Because of introduction of invoice line there is significant improvement of data flow with n other oracle modules like
• Fixed Asset - Asset Tracking
• Business Tax - Tax line
• Payment - Payment
• SubLedger Accounting - Accounting
Allocate freight and special charges are captured to the lines on the invoice
Invoice distributions created at the maximum level of detail similar to 11i.
Core functionality
3
Internal Bank Accounts
In 11i we have seen internal Banks defined in AP and that is shared by AP/AR/CE, Payroll and Treasury and they are bank accounts often replicated in multiple Ous
Where as in R12,
• Bank and Branch become part of TCA Parties.
Internal Bank Account in Cash Management which is owned by a Legal Entity. Here the Operating units have granted usage rights
4
Suppliers Bank Accounts
• Banks/Branches defined in AP
• Bank accounts often replicated in multiple OUs Before
• Suppliers, Banks and Branches are defined as Parties in TCA
• Supplier (party's) payment information and all payment instruments (Bank Accounts, Credit Cards) moved into Oracle Payments.
5
Integration with Oracle E-Business Tax
• Oracle standard functionality was based out of User which determines tax by assigning Tax Codes at line level of invoice and Tax rules was controlled at underline code.
• There was global descriptive flex fields were captured for country-specific tax attributes.
• More important most of the setup performed at OU level
• A new module eBusinessTax determines tax based on facts about each transaction, this is reason why Oracle has introduced additional line information at invoice level.
• The module "ebusiness Tax" set and configure Tax rules which can be viewed
• Tax attributes collected in fields on key entities
• Configure tax rules once per regime and share with your legal entities
6
Replace Supplier Bank Accounts on Invoices

In today’s business environment, it is a common practice to change bank accounts. If suppliers change their bank accounts, Oracle Payables can now automatically update all unpaid and partially paid invoices with the new bank account information. When users end date an existing supplier bank account and provide a new active bank account, Oracle Payables will automatically update the remit-to bank account information on unpaid and partially paid invoices. This streamlines transaction processing and prevents the need to update each invoice manually.
7
Business Intelligence Publisher Support for Selected Payables Reports

The following Oracle Payables reports have been re-written utilizing the Business Intelligence Publisher (BIP) tool. BIP based reports offer greater flexibility to end users in changing report layouts and formats:
• Withholding Tax by Invoice Report
• Bills Payable Maturity Date Report
• Discounts Available Report
• Payment Audit by Voucher Number
• Prepayments Status Report
8
Third Party Payments

Suppliers can specify a related trading partner to be paid on their behalf. The payments made on behalf of suppliers to other trading partners are termed as third party payments.
Oracle Payables has been enhanced to record third party relationships and to process third party payments. Withholding and 1099 processing continue to occur for invoicing suppliers.
9
Supplier Dispute Processing

Supplier invoices may be short paid to expedite dispute settlements. The Payables Invoice Workbench has been enhanced to capture the invoice amount originally claimed by the supplier and the reason for short payment.
10
Discount Calculation Enhancements

Suppliers offer discounts for early payment. Early payment discounts can be fixed monetary amounts or calculated on a percentage basis.
In prior releases, discounts could be defined in percentage terms only. Oracle Payables now allows discounts to be specified in monetary amounts. When a percentage as well as an amount is available, the higher or lower of the two can be specified for application.

No comments:

Post a Comment

If you are facing any issues while copying the Code/Script or any issues with Posts, Please send a mail to OracleApp88@Yahoo.com or message me at @apps88 or +91 905 957 4321 in telegram.
Best Blogger TipsGet Flower Effect