When you use an E-business suite, you need to engineer it to suit your business requirements. In this topic, you learn about the principles that form the basis of the business architecture of oracle 11i/R12 E-Business Suite.
Read the basics of multi-org structure @
www.oracleug.com/user-guide/oracle-basics/multiple-organizations-overview-r12
Step 1: Develop the Organization Structure
A successful implementation of Multiple Organization support in Oracle Applications depends primarily on defining your organizational structure in the multi-level hierarchy used by Oracle Applications. The levels are:
• Business groups
• Primary ledgers (as defined in Accounting Setup Manager)
• Legal entities
• Operating units
• Inventory organizations
For details checck http://www.oracleug.com/user-guide/oracle-basics/multiple-organizations-overview-r12
Step 2: Define Accounting Setups
Use the Accounting Setup Manager in Oracle General Ledger to define accounting setups that include the following common financial components:
One or more legal entities (optional)
Primary ledger
• Reporting Currencies (optional)
• Balancing segment value assignments (optional)
• Subledger Accounting Options
Operating Units (available if legal entities are assigned)
• Intercompany Accounts (available if legal entities are assigned)
• Intracompany Balancing Rules (optional)
Sequencing (optional)
Secondary Ledger (optional)
To use multiple organizations, you must define an accounting setup with at least one legal entity, a primary ledger that will record the accounting for the legal entity, and an operating unit that is assigned to the primary ledger and a default legal context (legal entity). It is also recommended that balancing segment values be assigned to the legal entity to help you identify legal entity transactions during transaction processing and reporting and to take advantage of Intercompany Accounting.
Note: If your enterprise structure requires that you define a business group, you should define accounting setups before business groups.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Installation step 1.1 - Create legal entity
Once the installation of R12 is complete, log into the system with user id and password as sysadmin/sysadmin and create the user who 'll handel the Accounting part. Assign Grants Accounting Super User to the user
An Oracle Applications Release 12 system utilizes components from many Oracle products. These product files are stored below a number of key top-level directories on the database and application server machines.
Note: No Applications files are installed on desktop client machines, although JAR files and their supporting utilities are downloaded as required.
Depending on how you chose to install Applications, these product directories may be located on a single machine (the simplest case) or on multiple machines (the most common type of deployment). Operating system environment settings indicate the location of the various files in the file systems of the database and application server machines. This chapter discusses the association between these environment settings and the corresponding files and directories.
Shared entities can be referenced by multiple products. These entities allow you to define broad-level structures that help you to include members when implementing the E-business suite. Which business unit will own specific data in a shared entity is at the discretion of the compnay. Employee data is always owned by human resources, provided the E-business suite is installed.
A methodology is a set of guidelines or principles that can be tailored and applied to a specific situation. In a project environment, these guidelines might be a list of things to do. A methodology could also be a specific approach, templates, forms, and even checklists used over the project life cycle. Therefore that was the driving factor for bringing AIM’s as methodology which was initially used by Oracle consulting , which is now most acceptable methodology for oracle application roll out.
So then what oracle application methodology in short AIM’s based out of
