Sei sulla pagina 1di 3

R12 Enhancements

R12: Legal Entity (LE)

Legal entity is created as a party of party type ORGANIZATION or PERSON An establishment is created as a party of party type ORGANIZATION. TCA creates a new classification category called Business Function. It is used mainly to model what business functions a party can perform in E-Business Suite For modeling legal entities and establishments in TCA, classification code Legal Entity and Establishment are created under the Business Function class category. An establishment is created as a party and always link to a party that is classified as a legal entity through the relationship model

R12: TCA (Trading Community Architecture): What is TCA?

Oracle Trading Community Architecture (TCA) is a data model that allows you to manage complex information about the parties, or customers. The Trading Community Manager Responsibility, allows users to create a setup or update data sharing and security Oracle Introduced a brand new HTML UI built using OA Frame works leveraging TCA that can be used to manage Customers, Accounts, etc.

Before TCA:

There are multiple customer definitions across the enterprise. It was very difficult to track current and historical information about the customers.

There was a lack of support for mixed business. It was quite tough to understand relationships between customers and others (suppliers, partners, competitors) After TCA: Create a central repository for the entire E-Business Suite to store information relating to all members of a trading community versus separate tables for each member-Prospects, Customers, Contacts, Employees, Partners, Distributors, Suppliers, Banks, etc.

Record complex business relationships between Trading entities (including 3rd party relationships). Support all business models, industries, and geographies.

R12: Bank Account Model

Oracle-R-12 MOAC-Concept: Multi-Org or multiple organization access Control (MOAC) is basically the ability to access multiple operating units from a single application responsibility. In Release 11i, when one had to enter or process data for multiple operating units, one had to login to different responsibilities because each responsibility could only access one operating unit. In Release 12, one would create a Security Profile and assign as many operating units as you required. One can tie that security profile to a single responsibility. In R12

The Set of Books evolved into Ledgers and Ledger Sets. The philosophy of Multiple Organization Access Control (MOAC) introduced in R12, ensured that the same user could perform multiple tasks across operating units without changing responsibilities. The use of Security Profiles was extended beyond HR to make MOAC possible. In 11i

In 11i, a user working with a specific responsibility, under a given operating unit, would need to switch responsibilities, if he/she were to access a sales order that was created from a different operating unit. For this to happen, the user had to be assigned a second responsibility that was linked to the second operating unit.

The Multi Org Access Control (MOAC) feature in R12 retains the data security aspect between organizations and users. However, it also brings with it a certain degree of user friendliness in navigating between different operating units.