Results for “sy_cmpy_mst”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

SY_CMPY_MST is a table owned by the GMA schema within the Process Manufacturing Systems product family in Oracle E-Business Suite. Its documented purpose is to store organization definitions at a single level. In the ETRM 12.2.2 physical schema, the table contains six columns and is classified as a valid, persistent base table that anchors organization-level company records used throughout the Process Manufacturing (OPM) application stack.

From a dimensional modeling perspective, the heuristic Data Vault classification derived from its foreign key structure is link. This classification is a modeling suggestion drawn from the FK topology rather than an Oracle-imposed constraint. The table sits between the master organization definitions represented in SY_ORGN_MST and SY_ORGN_MST_B, and it carries a distinguishing column (CO_CODE) that participates in those relationships. Treating SY_CMPY_MST as a link reflects its role in connecting company-level identity to the broader organization hierarchy rather than acting as a pure descriptive satellite.

Key Information Stored

The documented column set for SY_CMPY_MST is compact, comprising six columns. The most important are:

• CO_CODE — The company code, which serves as the primary key column in the unique index SY_CMPY_MST_PK and simultaneously functions as the foreign key column referencing SY_ORGN_MST_B and SY_ORGN_MST. This single column is the business-key candidate and the join backbone of the table.
• CREATED_BY — The application user identifier that created the company record.
• CREATION_DATE — The timestamp at which the record was inserted.
• LAST_UPDATED_BY — The application user who most recently modified the record.
• LAST_UPDATE_DATE — The timestamp of the most recent modification.
• LAST_UPDATE_LOGIN — The login/session context associated with the most recent change.

Because CO_CODE is both the unique index component and the sole FK column, it is the only true business-key candidate documented; the WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) provide standard auditing attribution rather than business meaning.

Common Use Cases and Queries

SY_CMPY_MST is typically queried to resolve company definitions and to validate that a company code exists before joining it to organization-level data. A common reporting pattern joins the table to its master counterparts on CO_CODE:

• Company lookup validation: SELECT co_code FROM gma.sy_cmpy_mst WHERE co_code = :p_co_code;
• Organization enrichment: SELECT c.co_code, o.organization_name FROM gma.sy_cmpy_mst c, gma.sy_orgn_mst o WHERE c.co_code = o.co_code;
• Audit reporting: selecting CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, and LAST_UPDATE_DATE to track when company definitions were introduced or changed.

Typical consumers include OPM setup reports, access-control listings that map users to companies, and migration or interface scripts that must confirm company codes exist before loading downstream transactions. Because the table is small and keyed on a single column, joins are inexpensive and it is frequently used as a conformed dimension in OPM reporting models.

Related Objects

The FK and PK metadata identify the following significant related objects:

• SY_ORGN_MST_B — Referenced by SY_CMPY_MST.CO_CODE. This is the base-table counterpart of the organization master.
• SY_ORGN_MST — Also referenced by SY_CMPY_MST.CO_CODE. This is the translated/view layer of the organization master.
• SY_CMPY_MST_PK — The unique index enforcing uniqueness on CO_CODE and serving as the primary key.

Applications and reports that resolve OPM company context generally traverse SY_CMPY_MST together with SY_ORGN_MST and SY_ORGN_MST_B using CO_CODE as the common join column. The single-column link structure means any object that depends on company identity within GMA can be joined through CO_CODE without additional key resolution.