This release introduces Oracle Sub ledger Accounting, E-Business Tax, Ledgers, Banks, and
other common data model components that are used by Oracle Payable.
Suppliers in Trading Community Architecture
· Suppliers are now defined as TCA Parties. During the upgrade, TCA Party records are
created / updated for all suppliers, they are linked to their records in the existing supplier
entities, and the payment and banking details are migrated into the Oracle Payments
data model. Although the underlying data model has changed, you still enter and
manage suppliers in the Suppliers windows.
· Oracle Payables introduces invoice lines as an entity between the invoice header and
invoice distributions. With the new model, the invoice header remains unchanged, and
continues to store information about the supplier who sent the invoice, the invoice
attributes, and remittance information.
· Invoice lines represent the goods (direct or indirect materials), service(s), and/or
associated tax/freight/miscellaneous charges invoiced. Invoice distributions store the
accounting, allocation and other detail information that makes up the invoice line. The
charge allocation table used in prior releases to manage accounting allocations is
· During the upgrade, Oracle Payables creates invoice lines for all existing invoices,
creating one line for every distribution available in the Release 11i distributions table,
except in the case of reversal pairs. In those cases, Payables creates one line with a
Centralized Banks and Bank Accounts Definitions
· All internal banks and bank accounts that you had defined in Release 11i are
automatically migrated to the central Cash Management entities. The bank accounts and
their payment documents are owned by a legal entity rather than by an operating unit.
See Cash Management in this appendix for more information.
· Also, the banks and bank branches are centralized in Cash Management entities as
described in the preceding paragraph. However, the bank accounts you had defined for
your suppliers are migrated from the Payables entities to the central Payments entities.
Payments centralize and secure all payment instrument data, including external bank
accounts, credit cards, and debit cards. See Payments in this appendix for more
Payment Document Sequencing
· If you used document sequencing for payment documents in Release 11i, your
document sequence category is migrated from the payment document, which is
associated with a bank account and, hence a legal entity, to the bank account uses
entity. This change preserves the option of having document sequence categories vary
across operating units.
· Integration with Payments for Funds Disbursements
· Oracle Payments can be used by Oracle Payables for processing invoice payments. See
Payments in this appendix for more information.
· Payment Features Controlled by Global Descriptive Flexfields
· Many European payment features that were implemented using global descriptive
flexfields in Release 11i are migrated to the Oracle Payables, Oracle Payments, and
Oracle Cash Management data models.
Integration with Subledger Accounting (SLA)
· This release introduces Oracle Subledger Accounting (SLA) to manage accounting
across subledger transactions. Payables no longer create any accounting entries. During
the upgrade, accounting options and their settings, and the existing accounting entries in
the Payables data model, are moved to the new SLA accounting data model to ensure a
continuous business operation between the two releases.
· During the upgrade, all accounting events, headers, and lines from the Release 11i data
model are upgraded to the new Subledger Accounting events, headers, and lines data
model, regardless of the period range you set for the upgrade.
Integration with E-Business Tax
· Oracle E-Business Tax manages tax across the E-Business Suite. In prior releases, the
setup, defaulting, and calculation of tax for Payables was managed within Payables
using tax codes, their associated rates, and a hierarchy of defaulting options. This
method is still available in this release. During the upgrade, E-Business Tax migrates the
tax codes as appropriate within E-Business Tax so that your tax processing can work the
same way after the upgrade as it did before.
· New fields are added to the supplier, invoice, and invoice lines entities to track tax
attributes used by E-Business Tax. Many of these attributes were implemented with
global descriptive flexfields in prior releases and are upgraded to regular fields on these