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.

Saturday, November 19, 2011

R12 Payables

Supplier

In Release 12, Suppliers are defined as Trading Community Architecture (TCA) parties.
During the upgrade, TCA party records are created and updated for all suppliers, they
are linked back to their records in the supplier entities and the payment and banking
details are migrated into the Oracle Payments data model. The supplier, supplier site,
and supplier contacts tables are obsolete and replaced with views that join information
from the old tables with information in TCA.

Also during the upgrade, Oracle Payables reviews the supplier sites and determines
duplicates, based on the supplier, address, city, county, province, state, country, zip and
language. Oracle Payables then creates only one Party Site for each distinct supplier site
address.

INVOICE LINE
Invoice Lines are introduced as an entity between the invoice header and invoice
distributions in order to better match the structure of real world invoice documents and
improve the flow of information in the Oracle E-Business Suite. 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. In
prior releases, a charge allocation table managed the allocations, but this entity is
obsolete in Release 12.

BANK

In Release 12, the ownership of internal banks and bank accounts will move to Oracle Cash Management for all products in the E-Business Suite. All internal banks and bank
Accounts you had defined for your operations will be migrated from the Payables entities to the central Cash Management entities. A Legal Entity now owns the bank accounts and their payment documents, rather than being owned by an Operating Unit as in prior releases.

TAX

If you choose to use the features of E-Business Tax, you can make the transition at your own pace, incrementally adding
E-Business Tax rules to meet your requirements. Release 12, there are new fields added to the supplier, invoice, and related entities that track tax attributes used by E-Business Tax.

MULTI ORG

Multiple Organizations Access Control is an enhancement to the Multiple Organizations feature of Oracle Applications. Multiple Organizations Access Control allows a user to access data from one or many Operating Units while within a give
responsibility. Data security is maintained using the Multiple Organizations Security Profile, defined in Oracle HRMS, which specifies a list of operating units and Profile, defined in Oracle HRMS, which specifies a list of operating units and determines the data access privileges for a use. If you want to use Multiple Organizations Access Control, you will first need to define security profiles, then link them to responsibilities or users.

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