Académique Documents
Professionnel Documents
Culture Documents
Supplier
Where as in R12
Country and address line1 are required, this is because creation of suppliers in Party in
TCA data model would requires Country and address information, but it also understood
if there is no country or address line 1 specified for a supplier site in cases when upgrades
takes place, Payables derives the country based on the most frequently used operating
unit of the Supplier’s historical transactions.
3. Employee as suppliers: address NOT migrated to party site in TCA remains in Oracle
HR for data security reasons.
As we know in 11i employees are part of internal supplier’s record in order for Oracle
Payables to create payments for their expense reports. Employees defined in Oracle
Human Resources and associated with an Oracle Payables supplier record have existing
party information. During the upgrade, Oracle Payables updates the existing party
information to have a party usage of supplier but it does not migrate the employee
address to the party site in TCA, they remain in Oracle Human Resources for data
security reasons.
4. Utilize TCA Party relationships for franchise or subsidiary and its parent company.
Invoice
But in R12,
2. Allocate freight and special charges are captured to the lines on the invoice
3. Invoice distributions created at the maximum level of detail similar to 11i.
4. Core functionality
That’s means functional testing is more required while upgrade takes place.
Now a days corporate treasury role has been greatly enhanced thus picking up a global
bank as partner for all banking need is demand of time in global working model. The
recent couple of years have seen drastic increase in acquisition and merger of company
thus global working as well as global instance get popularity in ERP arena, and this is
one of reason of the reason bank data model has been significant changes from 11 to 11i
and 11i to R12.
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,
• Banks/Branches defined in AP
• Bank accounts often replicated in multiple OUs Before
R12
• a. Bank Number
b. Institution type
c. Country
d. Bank admin email
e. Bank name alt
f. Tax payer ID
g. Tax reference number
h. Description, Effective dates
3. Bank accounts, bank account uses are migrated into cash management.
4. Transactions are stamped with the bank account uses identifiers as part of the upgrade
In 11i
• 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 is most of the setup performed at OU level.
In R12
Impact of Upgrade
1. Payables Tax setup, Tax Code defaulting rules defined per OU are migrated to
eBusiness Tax.
2. OUs migrated to tax content owner in R12
3. Tax information in tax codes are transformed to Regime-Rate flow.
4. E-Business Tax takes information from the AP invoice lines and creates summary and
detail tax lines in the E-Business Tax repository.
This feature enables user to access data from one or many Operating Units while within a
set given responsibility. Due to this change, all processing and some Reporting in Oracle
Payables is available across Operating Units from a single Applications responsibility.
Hence you can isolate your transaction data by Operating unit for security and local level
compliance while still enabling shared Service centre processing. Data security is
maintained using the Multiple Organizations Security Profile, defined in Oracle HRMS,
which specifies a list of operating units and determines the data access privileges for a
user.
Impact of Upgrade
R12 Upgrade does not automatically create security profiles, thus is important if any one
want to use Multiple Organizations Access Control, the first things is to define security
profiles, then link them to respective responsibilities or users.
Reference: Details can be found more on R12 RCD documents, from Oracle site.