Search Results gmd_operations_b_u1

Overview

GMD_OPERATIONS_B is the operations base table within the Oracle EBS Process Manufacturing Product Development (GMD) module. It stores the master definition of process manufacturing operations — the discrete activities or processing steps that, when combined with routing and recipe information, form the basis of a production process. Each row represents one version of an operation, holding both operating parameters and descriptive attributes used throughout recipe, routing, and production execution flows.

The object is documented as owned by the GMD schema and classified VALID in release 12.1.1 and 12.2.2. Its documented physical schema contains 54 columns and two unique indexes: GMD_OPERATIONS_B_PK on OPRN_ID and GMD_OPERATIONS_B_U1 on (OPRN_NO, OPRN_VERS). The ETRM metadata assigns this table a heuristic Data Vault classification of "standalone," meaning it was mined as having no foreign key dependencies on other tables within the classified model. Modeled as a Data Vault construct, this suggests the table behaves as a hub-like entity where OPRN_ID is the surrogate identifier and the natural/business key (OPRN_NO, OPRN_VERS) is a candidate for a business key. The _B suffix indicates a base table, typically paired with a corresponding _TL translation table in EBS multilanguage schema conventions.

Key Information Stored

The most significant columns fall into identifier, classification, status, and control groups:

• OPRN_ID — surrogate primary key (GMD_OPERATIONS_B_PK) that uniquely identifies an operation record and is the value referenced by downstream recipe, routing, and transaction tables.
• OPRN_NO — user-facing operation number; together with version it forms the unique business-key candidate (GMD_OPERATIONS_B_U1).
• OPRN_VERS — version number of the operation definition, enabling multiple revisions to coexist.
• OPRN_DESC#1 — operation description.
• OPRN_CLASS — class or category that determines how the operation is used or grouped.
• POC_CTL_CLASS — process operation control class, governing control behavior during execution.
• OPERATION_STATUS and INACTIVE_IND — lifecycle and active/inactive state indicators.
• IN_USE and DELETE_MARK — usage and soft-delete flags controlling whether the record is referenced or logically removed.
• PROCESS_QTY_UOM / PROCESS_QTY_UM — unit of measure for the process quantity.
• MINIMUM_TRANSFER_QTY — minimum quantity permitted to be transferred from the operation.
• OWNER_ORGN_CODE / OWNER_ORGANIZATION_ID — owning organization for multi-org security and data partitioning.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — date-range validity of the operation version.
• TEXT_CODE — reference to extended descriptive text.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–30 — the standard EBS DFF/descriptive-flexfield column set for customer-defined extensions.
• Standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) provide audit tracking.

Common Use Cases and Queries

Operations are typically queried to list all versioned operations available for recipe and routing design, to validate an operation is active before it is attached to a routing, or to populate reports and interfaces for process manufacturing planning. A frequent pattern joins the base table to its translation table to retrieve language-specific descriptions, filtering by organization and status:

• Retrieve the current version of an operation by number via OPRN_NO and OPRN_VERS, using the unique index GMD_OPERATIONS_B_U1 for efficient access.
• List active operations (INACTIVE_IND = 'N' AND DELETE_MARK = 0) within an owner organization (OWNER_ORGANIZATION_ID).
• Filter by effectivity (EFFECTIVE_START_DATE / EFFECTIVE_END_DATE) to find operations valid as of a given date.
• Resolve an operation's surrogate key OPRN_ID from a business operation number to support downstream lookups in routing and recipe tables.
• Report on operations by OPRN_CLASS or POC_CTL_CLASS to analyze control classifications across a plant.

Because the table carries a DELETE_MARK flag and the WHO audit columns, all reporting should generally include DELETE_MARK = 0 to exclude logically deleted rows.

Related Objects

Although the heuristic Data Vault classification marks this table as standalone (no mined foreign keys), in practice GMD_OPERATIONS_B is referenced by dependent objects through OPRN_ID and identified by its business key OPRN_NO/OPRN_VERS:

• GMD_OPERATIONS_TL — translation table keyed by OPRN_ID, supplying language-specific operation descriptions.
• GMD_OPERATION_ROUTINGS and routing/recipe operation tables — reference OPRN_ID to place operations within a routing.
• GMD_RECIPE_OPERATIONS — associates recipes to operations by OPRN_ID.
• GMD_OPERATION_ACTIVITIES / operation activity tables — hold the sub-steps belonging to an operation via OPRN_ID.
• GMD_OPERATION_RESOURCES — resource requirements attached to an operation.
• Process execution and transaction tables in the GML/process modules that consume operation definitions at run time.

Joins are consistently performed on OPRN_ID for internal references and on OPRN_NO plus OPRN_VERS when reconciling against user-entered operation numbers. The two documented unique indexes — GMD_OPERATIONS_B_PK and GMD_OPERATIONS_B_U1 — enforce the integrity of these relationships.