This action might not be possible to undo. Are you sure you want to continue?
Definition: Business Group Legal Entity Operating Unit
or an operation company and has no accounting impact. Oracle Modules: HRMS Payroll . a major division. The Business Group partitions Human Resources information and the Purchasing Approval Hierarchy.Architecture Organization Model – Release 12 Business Group This is an Organization that represents the consolidated enterprise.
You assign tax identifiers and other legal entity information to these types of organizations. Future enhancements will include greater functionality at this organization level. Oracle Modules: GL FA .Architecture Organization Model – Release 12 Organization Definition: Legal Entity A legal entity represents a legal company for which you prepare fiscal or tax reports.
The Operating Unit has to be assigned to a Legal Entity and a Set of Books.Architecture Organization Model – Release 12 Organization Definition: Operating Unit Oracle Modules: The Operating Unit is an organization that uses Oracle. PO Payables Payments AR Cash Management . a division or a department. The operating unit may be a sales office. Oracle Payables. Cash Management. Oracle Purchasing and Oracle Receivables. Order Management and Shipping Execution.
What is TCA and its Background • A Trading Community is… – The participants in a community and their relationship to one another Competitor Competitor of Partner of Partner Customer / Organization Employee Employee of Supplier of Supplier .
DQM. D&B Integration. AR GL.• • TCA = Trading Community Architecture Provides a single. APIs TCA Data Model HZ Schema . universal definition of trading partners across applications and job function • TCA is an Data Model – it is not a Module Oracle E-Business Suite Application Families* What is TCA and its Background Sales / Service Marketing Financials – Financials – AP. FA. PO HR 3rd Party Systems TCA Enabling Infrastructure Common Party UI.
What is TCA and its Background TCA (Trading Community Architecture) Party Definition TCA Central Data Model Supplier Representation New Bank Model .
etc Recieva bles Party Informatio n Payable Purchasi s ng Suppliers Cash Manageme nt Banks and Branches Trading Trading Community Community Architecture Architecture Oracle ERP CRM r d 3rd Party . “Geographies”. Authorities.TCA in R12: Leveraging centralized data model Global Tax Governments.
Payables use the same employee records in TCA • New supplier maintenance are done using UI in TCA components (DQM) • Terms of doing business with the supplier are in Purchasing / Payables . contact. address. phone. email etc.• • TCA in R12: Supplier Representation Suppliers are organizations in TCA Supplier organization. are all in TCA • Employees are already in TCA.
bank accounts are owned by Legal Entities with the option to grant account use to Operating Unit (Payables. Legal Entity (Treasury).TCA in R12 New Bank Account Model • Central place to define internal bank accounts – Keep track of all bank accounts in one place – Explicitly grant account access to multiple operating units/functions and users • Multi-Org Access – In the new model. Receivables). Business Group (Payroll) .
TCA in R12: Bank Account Model Pay invoices from different OUs with 1 instruction OU A • New Payments Module • New Bank Module • New Bank & Credit Card Features OU B Payments OU C Single Payment Instruction Bank Invoices Sub Ledger Accounti ng .
MOAC: Multi-Org Access Control Role based access to Operating Units Define Security Profile MOAC Usage .
Invoice creation.. Consolidated reports can be run for those with multiple organizational access Month-end operations Done once per month in each module To be done multiple times – once per organization per month in each module. Visibility of master data e. assigned to each organization e.g. The other data needs to be etc.: only Vendor header level data is shared while vendor-site level data needs to be assigned separately in each organization. Payment processing etc Running Reports in Sub-ledger Single Organizations Multiple Organizations Potentially executed once for all three business functions combined Executed multiple times – once for each organization Potentially executed once for all three business functions combined Depending on security and access typically executed multiple times – once for each organization. Visible for all business functions within Only master data is shared between the Vendors (Suppliers). This is handled through a centralized access screen .Area of Impact Impact on Business Processes Day-to-day business processes e. However R12 allows users to close multiple organizations at once in order to streamline efficiency.g. Customers the same organization organizations.g.
. there is a higher likelihood of custom extensions to support these differences. significantly. As a result. Configuration is required for each organization (more effort). There will also be an issue to segregate the FAO HQ and Field report data. Reporting Report development could be complex Reporting will be less of a challenge with particularly if the reporting requirements separation by organization and will not have between the three areas differ the complexity of a single organization. However.Area of Impact Single Organizations Multiple Organizations Impact on Project (Implementation Effort) Application configuration Configuration is required for one organization (less effort). Need for custom extensions The FAO HQ and Field share similar Custom extensions are less likely (less effort) business processes but their focus differs. the complexity of configuration may increase (more effort). However. (more effort) This is particularly true with respect to the FAO HQ requirements. it offers more flexibility to meet requirements of each business function.
The training process and learning curve will be similar regardless of the number of organizations. if the future business processes vary significantly. configuring separate organizations is less of an effort with R12. The training process and learning curve will be similar regardless of the number of organizations. one organization is used.Area of Impact Single Organizations Multiple Organizations Testing With all of the FAO’s business processes Testing effort will be higher as the testing needs sharing the same organization. Training . The difference will be user access as some users may have access to multiple legal entities. Configuration Migration Final configuration will need to be migrated Configuration needs to migrated for each only once per organization per applications organization environment (more effort). Since all of the FAO HQ business processes would be contained in one organization. future testing complexity is increased. which could involve a shorter testing cycle. Oracle code) may be required. environment setup However. even though. Future Oracle patches could increase IT effort (testing and planning). The difference will be user access as some users may have access to multiple legal entities. Data segregation is a standard feature. Data restriction and security is not an issue with multiple organizations. However. This data restriction might be more of an issue with only one organization. only one organization would require testing. the potential will have to ensure each Field & FAO HQ are in for intrusive customizations (changes to place.
This could impact the Support. code) may be required. by nature. This would primarily be due to ensuring mock data segregation and to meet reporting requirements. . Future Oracle patches could increase IT effort (testing and planning). the potential for intrusive Therefore. impact to the FAO’s patching customizations (changes to Oracle strategy and upgrades could be reduced. as mentioned With Multiple organizations. effectiveness of Oracle Support as intrusive customizations. organization. intrusive processes sharing the same customizations will likely not be required.Area of Impact Single Organizations Multiple Organizations IT Efforts With all of the FAO HQ & Field business With Multiple organizations. requirement for intrusive In this scenario. there should be little customizations (changes to Oracle impact to the effectiveness of Oracle code). there is a potential for the customizations will likely not be required. are not supported by Oracle. intrusive above. there is always a risk of invaliding areas of support from Oracle. With custom code. Oracle Support With one organization.
Purchase Orders Receiving & Drop Ship Supplier Invoices Payments Customer Data Management Accounting Setup .MOAC: Multi-Org Access Control Role based access to Operating Units Perform multiple tasks across operating units without changing responsibilities HQ Legal Entity Mozambiq ue FAO HQ Operating Unit Congo Operating Unit Operating Unit Single Responsibility Responsibility Responsibility Responsibility Functional Tasks Requisition.
Usage Typical Screen in daily use Invoice Entry Quick Invoices PO Entry Receiving Supplier Sites Customer Sites OU Specific Set Ups OU Specific Reports .MOAC .
Q U E S T I O N SN S W E R S A & .
t FAO MOAC – Definitions & Implications MOAC Demo’s .Oracle Architecture / TCA / MOAC FAO Architecture Components of TCA TCA and its implications w.r.
Purchasing – Part 1 Buyers Workbench Personalization of Buyers Workbench PO Types Line Types PO Requisitions Standard PO’s. Global PO’s Service Orders. Goods . Contract Agreements.
Part 2 PO on the Field Receiving Pay on Receipt 6 Different Scenarios iProcurement .Purchasing .
Payables Quick Invoices Invoice Import Centralized Shared Services Invoice Workbench .
Payments New Payment Process Centralized Payments Quick Payments .
Old Model AR (Customer) John.org AP/PO (Supplier) John. XYZ Inc TCA Model Party: ABC Co. XYZ Inc. XYZ Inc Organization s (Organizatio n) fao. . Customer of Supplier of * Party: John.
Ship to SITE . Ship to Bill to.TCA Data Model: Visualization PARTY SITE Bill to Ship to Division Of PARTY PARTY Bill to Ship to SITE Bill to Ship to Account Acct Site Account Acct Site Account Acct Site Bill to. Ship to Bill to.
This action might not be possible to undo. Are you sure you want to continue?
We've moved you to where you read on your other device.
Get the full title to continue reading from where you left off, or restart the preview.