Results for “formula_id”

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

Overview

GMP_FORM_EFF is the Formula Effectivity Mapping Table within the Oracle EBS Process Manufacturing Process Planning module (GMP). It resides in the GMP schema and serves as the central association object that binds a formula definition to the specific effectivity context under which it is valid — plant, warehouse, and routing. In Oracle Process Manufacturing, formulas (FM_FORM_MST) define the bill of materials for a product, while routings define the sequence of operations. Before a formula can be used for production planning or scheduling, it must be declared effective for a given organization and routing. GMP_FORM_EFF provides that declaration layer, allowing the same formula to be reused across multiple plants, warehouses, and routing combinations with distinct effectivity records.

From a dimensional modeling perspective, the documented foreign-key structure suggests this table behaves as a link entity in a Data Vault classification (heuristic, mined from the FK topology). Its APS_FMEFF_ID primary key is a pure surrogate, and the surrounding FK columns reference multiple independent hubs — formula, routing, warehouse, and organization — making it a natural many-to-many resolution table rather than a descriptive satellite.

Key Information Stored

The documented schema contains twelve columns. The most significant are:

• APS_FMEFF_ID — Surrogate primary key defined by the GMP_FORM_EFF_PK unique index. This is the only documented unique business-key candidate.
• FMEFF_ID — Foreign key to FM_FORM_EFF, linking to the formula effectivity definition record.
• FORMULA_ID — Foreign key to FM_FORM_MST identifying the formula being made effective.
• ROUTING_ID — Foreign key referencing both GMD_ROUTINGS_B and FM_ROUT_HDR, tying effectivity to a routing header.
• WHSE_CODE — Foreign key to IC_WHSE_MST, scoping effectivity to a warehouse.
• PLANT_CODE — Foreign key to SY_ORGN_MST_B and SY_ORGN_MST, scoping effectivity to an organization/plant.
• ORGANIZATION_ID — Multi-org partitioning column used by EBS security (MOAC).
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit trail columns.

Common Use Cases and Queries

Typical reporting scenarios include identifying which formulas are effective for a given plant before running MRP or production scheduling, and confirming that a routing is properly associated with a formula. A representative query joining the formula master and plant organization is:

• SELECT fe.FORMULA_ID, fm.FORMULA_NO, fe.ROUTING_ID, fe.PLANT_CODE, fe.WHSE_CODE FROM GMP.GMP_FORM_EFF fe, GMP.FM_FORM_MST fm WHERE fe.FORMULA_ID = fm.FORMULA_ID AND fe.ORGANIZATION_ID = :org_id;
• Effectivity gap analysis — detecting formulas defined in FM_FORM_MST but with no corresponding row in GMP_FORM_EFF for a given plant.
• Routing-to-formula audit — joining to GMD_ROUTINGS_B to list all effective combinations per routing.
• Multi-org compliance reporting — filtering by ORGANIZATION_ID to isolate records owned by a specific operating unit.

Related Objects

The documented foreign keys establish the following dependencies:

• FM_FORM_EFF — joined via GMP_FORM_EFF.FMEFF_ID; the parent effectivity definition.
• FM_FORM_MST — joined via FORMULA_ID; the formula master.
• FM_ROUT_HDR and GMD_ROUTINGS_B — joined via ROUTING_ID; routing headers.
• IC_WHSE_MST — joined via WHSE_CODE; warehouse master.
• SY_ORGN_MST_B and SY_ORGN_MST — joined via PLANT_CODE; organization definitions.

These relationships make GMP_FORM_EFF a focal junction for formula, routing, warehouse, and organization data in Process Planning.