Search Results process_enabled_ind

Overview

SY_ORGN_MST_B is the organization code master base table in the Oracle EBS Process Manufacturing (OPM) schema GMA. It functions as the central registry of organizational units within the process manufacturing application family, storing the plant, company, warehouse, and regulatory organization definitions that drive inventory, costing, planning, quality, and manufacturing transactions. The table carries 63 documented columns in the ETRM 12.2.2 physical schema, is flagged VALID, and is owned by GMA.

The table plays a dual role: it is both a container for organization attributes and a hierarchical node structure, achieved through the self-referencing PARENT_ORGN_CODE and CO_CODE columns. This self-referential design allows organizations to be arranged into reporting or consolidation trees (for example, a plant rolling up to a company, and a company rolling up to a parent company).

In Data Vault modeling terms, the heuristic classification of SY_ORGN_MST_B is a hub. The ORGN_CODE column serves as the natural business key and is the anchor of the hub, while the descriptive attributes (names, indicators, addresses, and audit columns) behave as satellite content. The strong FK fan-in from transactional and master tables throughout GMA confirms this hub role.

Key Information Stored

The primary key of SY_ORGN_MST_B is the unique index SY_ORGN_MST_B_PK on ORGN_CODE; a secondary unique index SY_ORGN_MST_B_U1 covers ORGANIZATION_ID. ORGN_CODE is therefore the business-key candidate that ties the process manufacturing organization to the rest of the OPM application. The 10-15 most significant columns are:

• ORGN_CODE — The unique organization code and primary business key; the column referenced by nearly every FK in the relationship data.
• ORGANIZATION_ID — The stored organization identifier covered by the secondary unique index, generally aligned with the EBS HR organization identifier.
• ORGN_NAME — The descriptive name of the organization used in reports and LOVs.
• PARENT_ORGN_CODE — Self-referencing FK establishing the reporting or consolidation hierarchy.
• CO_CODE — Self-referencing FK identifying the company organization that owns the unit.
• PLANT_IND — Indicates whether the organization behaves as a plant.
• INVENTORY_ORG_IND — Indicates whether the organization is an inventory-owning organization.
• MASTER_ORGANIZATION_ID and TEMPLATE_ORGANIZATION_ID — Link the organization to its master or template definition.
• ADDR_ID — FK to SY_ADDR_MST, holding the organization's address.
• TAXLOC_CODE — FK to TX_TLOC_CDS, the tax location for the organization.
• TEXT_CODE — FK to SY_TEXT_HDR for free-form descriptive text.
• MFG_CALENDAR_ID — The manufacturing calendar associated with the organization.
• ACTIVE_IND, DELETE_MARK, and MIGRATED_IND — Status and lifecycle flags controlling visibility and transition state.
• PROCESS_ENABLED_IND and REGULATORY_ORG_IND — Flags enabling process manufacturing and regulatory behavior.
• RESOURCE_WHSE_CODE — Default warehouse code used for resource transactions.

The remaining columns are twenty-nine generic ATTRIBUTE1 through ATTRIBUTE30 slots plus ATTRIBUTE_CATEGORY, and standard audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN). These support customer extensions and should not be treated as semantically fixed across implementations.

Common Use Cases and Queries

The most common reporting pattern is to resolve an organization code to its attributes, or to join a transactional table back to this hub. For example, inventory transaction journal rows in IC_ADJS_JNL can be enriched with organization names:

• SELECT j.ORGN_CODE, o.ORGN_NAME, j.TRANS_CNT, j.CO_CODE FROM IC_ADJS_JNL j JOIN SY_ORGN_MST_B o ON j.ORGN_CODE = o.ORGN_CODE WHERE j.ORGN_CODE = :orgn_code;
• Identify all inventory-owning or plant organizations: SELECT ORGN_CODE, ORGN_NAME FROM SY_ORGN_MST_B WHERE INVENTORY_ORG_IND = 'Y' AND ACTIVE_IND = 'Y';
• Walk the organization hierarchy using the self-join on PARENT_ORGN_CODE and CO_CODE, or use CONNECT BY PRIOR ORGN_CODE = PARENT_ORGN_CODE to produce a rollup tree.
• Resolve the plant organization linked to a batch: SELECT b.BATCH_NO, o.ORGN_NAME FROM PM_BTCH_HDR b JOIN SY_ORGN_MST_B o ON b.PLANT_CODE = o.ORGN_CODE;

Because ORGN_CODE is referenced by hundreds of transactional tables (inventory, purchasing, order processing, quality, forecasting, and costing), the table is a standard dimension in OPM data warehouse extractions and in EBS Discoverer or BI Publisher reports. A recurring validation query is to find orphan transactional rows whose ORGN_CODE does not exist in SY_ORGN_MST_B, which typically indicates setup or migration gaps. Filtering on ACTIVE_IND and DELETE_MARK is advisable in operational queries so that inactive organizations do not distort results.

Related Objects

SY_ORGN_MST_B participates in an extensive web of foreign keys. The most significant related objects are:

• IC_PLNT_INV — References SY_ORGN_MST_B.ORGN_CODE and defines plant inventory parameters; this is the object most relevant to the "ic_plnt_inv" search.
• SY_CMPY_MST — Company master; SY_ORGN_MST_B.CO_CODE is conceptually aligned with the company definition.
• SY_ADDR_MST — Address master joined via ADDR_ID.
• SY_TEXT_HDR — Text header joined via TEXT_CODE for descriptive notes.
• TX_TLOC_CDS — Tax location codes joined via TAXLOC_CODE.
• IC_ADJS_JNL, IC_TRAN_PND, IC_TRAN_CMP, IC_XFER_MST, and IC_WHSE_MST — Inventory and warehouse transaction tables joined on ORGN_CODE and/or CO_CODE.
• GL_ACCT_MAP, GL_ITEM_CST, and GL_PLCY_MST — Costing and accounting mapping tables that reference the organization or company code.
• GMD_RECIPE_PROCESS_PARAMETERS, GMP_FORM_EFF, GMP_ITEM_APS, and PM_BTCH_HDR — Recipe, formula, item, and batch objects that use ORGN_CODE or PLANT_CODE.
• SY_ORGN_USR — Maps users to organizations and references SY_ORGN_MST_B.ORGN_CODE.
• SY_DOCS_SEQ — Document sequencing table referencing ORGN_CODE in multiple columns.

Additionally, the table self-references through CO_CODE and PARENT_ORGN_CODE, which is what enables the organization hierarchy to be reconstructed directly from this single base table.