Understanding Shared Product & Data

Posted on August 26th, 2007 by Sanjit Anand | Print This Post | Email This Post

The idea of having 'DEPENDENT' OR "SHARED" PRODUCTS or DATA in Oracle application is because of tight integration within the other area.

As Oracle application is tightly integrated.

• Each Application depends on components from other products,called dependent or "shared" products, for full functionality.
  • For example, Oracle Payables uses components in Oracle General Ledger, Oracle Purchasing, and Oracle Personnel.
  • Components always differ: 60-80% of all Applications files are needed by two or more products.
• When you install a product, you install the database components of all Oracle Applications products.
  • This only applies to the database portion of Oracle Applications.
    • You will not install the filesystem component of all Oracle Applications products.
  • Shared products are mostly transparent to the user.

If you take a case, to understand the sharing data concept in oracle application, you can find lot many nodes , but after all that's beauty of Oracle application.

1. Integration with Oracle Purchasing – Shared Data Flow
2. Understanding Multi-Organization Structure in EBS(Technical) – Part II
3. Understanding data flow for “Internal Orders”
4. Understanding data flow for “Standard Order”
5. Understanding Multi-Organization Structure in EBS – Part 1