Search Results sy_orgn_mst

Overview

The SY_ORGN_MST table serves as the central organization code master within the Oracle E-Business Suite Process Manufacturing (GMA) module. It functions as a foundational data repository that defines and stores the hierarchical and operational structure of business entities, such as companies, plants, warehouses, and departments. Its primary role is to provide a normalized reference for organizational units across the manufacturing and financial suites, ensuring data integrity and enabling transactional processing, cost accounting, and reporting to be correctly scoped and attributed to the appropriate legal or operational entity. The table's critical importance is evidenced by its extensive foreign key relationships with numerous transactional and control tables across the GMA, Inventory (INV), Cost Management (CM), and General Ledger (GL) applications.

Key Information Stored

While the full column list is not detailed in the provided metadata, the primary and foreign key structures reveal the core data elements. The table is uniquely identified by two primary keys: ORGN_CODE (a legacy or application-specific identifier) and ORGANIZATION_ID (typically aligning with the standard Oracle Inventory ORG_ORGANIZATION_DEFINITIONS table). Essential relational attributes include CO_CODE for the owning company, PARENT_ORGN_CODE for defining organizational hierarchies, and ADDR_ID for physical location linkage. Additional descriptive and control data is referenced via foreign keys to TEXT_CODE (SY_TEXT_HDR) for notes and TAXLOC_CODE (TX_TLOC_CDS) for tax jurisdiction.

Common Use Cases and Queries

This table is central to organization-centric reporting and data validation. Common operational scenarios include validating transaction postings, generating organizational hierarchy reports, and ensuring setup completeness for new entities. Sample SQL patterns often involve joining to transactional tables or resolving organization descriptions.

• Hierarchy Resolution: A recursive query or CONNECT BY statement using PARENT_ORGN_CODE to list all child organizations under a specific company (CO_CODE).
• Transaction Validation: Joining SY_ORGN_MST to a transactional table like IC_TRAN_PND to verify that the ORGN_CODE on a pending transaction is valid and active.
• Setup Reporting: A left outer join from SY_ORGN_MST to key setup tables (e.g., GL_PLCY_MST on CO_CODE) to identify organizations missing critical configuration.

Related Objects

SY_ORGN_MST has a vast network of dependencies, as shown in the foreign key metadata. Key relationships are categorized below:

• Master Data References: SY_ADDR_MST (address), SY_TEXT_HDR (descriptive text), SY_DOCS_SEQ (document sequencing).
• Self-Referential Hierarchy: SY_ORGN_MST itself, via CO_CODE and PARENT_ORGN_CODE.
• Core Manufacturing & Costing: CM_CLDR_HDR (calendar), CM_RSRC_DTL (resources), FM_FORM_EFF (formula efficacy), GMP_FORM_EFF (process manufacturing plant data).
• Inventory Management: IC_CLDR_HDR (inventory calendar), IC_TRAN_PND (pending transactions), IC_PLNT_INV (plant inventory), IC_JRNL_MST (journals).
• Financial Integration: GL_PLCY_MST (accounting policies), GL_ACCT_MAP (account mapping), GL_ITEM_CST (item costs).

The specific relationship to the user's searched object, IC_CLDR_HDR, is explicitly documented: SY_ORGN_MST.ORGN_CODE is referenced by IC_CLDR_HDR.ORGN_CODE, linking an inventory calendar to its governing organization.