10-15-2010, 06:40 AM
1. Revise the Organization Structure.
2. Define Sets of Books (optional).
3. Define Locations.
4. Define Organizations.
5. Define Relationships.
6. Define Responsibilities.
7. Set Profile Options for Each Responsibility linked to the new Operating Unit.
8. Run the Replicate Seed Data concurrent program.
9. Set profile options specific to operating units.
10. Define Inventory Organization Security (optional).
11. Implement the Application Products.
12. Secure Balancing Segment Values (optional).
13. Run the Setup Validation Report (recommended).
14. Implement Document Sequencing (optional).
15. Define Intercompany Relations (optional).
16. Set the top reporting level (optional).
17. Set up conflict domains (optional).
The trick with adding a new operating unit to the existing configurations was to figure out which configurations were operating unit specific. The attached three documents capture those steps for a typical installation of Oracle Projects and Financials.
Another dilema we had was how many operating units to define in the same set of books. We started with the “best practice” approach to have one set of books for all operating units with the same 3 Cs (Chart of Accounts, Calendar and Currency). The challenge with this approach was how to manage some financial operations, including closing the periods, securing journals by operating unit, or defining default accounting rules. And because we needed to completely separate three legal entities, we ended up with multiple sets of books - one for operating unit. There are several improvements to the multi-organization structures in the release 12