Results for “pm_oprn_dtl”

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

Overview

PM_OPRN_DTL is a GME (Process Manufacturing Process Execution) table in the Oracle EBS 12.1.1 / 12.2.2 schema, owned by GME and holding batch operation detail records. In process manufacturing, once a batch is created and routed through a recipe, each routing step is exploded into the specific operations, resources, and activities that must be executed. PM_OPRN_DTL stores that exploded view: one row per batch, per batch step, per resource, and per activity. It links a batch step to the resource consumed or produced, to the activity performed, and to cost components and cost analysis codes used in batch costing. As the physical detail layer beneath batch routing and execution, it is fundamental to resource consumption tracking, actual-versus-plan variance analysis, and batch cost rollups.

The heuristic Data Vault classification derived from the foreign-key structure is link. This suggests the object principally models associations between business entities — batch steps, resources, activities, and costing components — rather than serving as a standalone reference hub or a purely descriptive satellite. When modeling this data, treat PM_OPRN_DTL as a connecting structure whose grain is defined by the batch step-to-resource-to-activity relationship.

Key Information Stored

The documented physical schema contains 61 columns. The most significant include:

• BATCH_ID, BATCHSTEP_NO, RESOURCES, ACTIVITY, BATCHSTEPLINE_ID — the composite primary key PM_OPRN_DTL_PK, identifying each batch operation detail row.
• BATCHSTEPLINE_ID — also defined as the alternate unique index PM_OPRN_DTL_U1; this is the strongest business-key candidate, as it uniquely identifies the operation line independently of the composite key.
• OPRN_LINE_ID — links to the operation line (FM_OPRN_DTL), tying the detail back to the routing operation.
• COST_ANALYSIS_CODE, COST_CMPNTCLS_ID — costing classification of the resource or activity consumed.
• PRIM_RSRC_IND — indicates whether the resource is the primary resource for the operation.
• PLAN_RSRC_COUNT, PLAN_RSRC_QTY, PLAN_RSRC_USAGE — planned resource quantities and usage.
• ACTUAL_RSRC_COUNT, ACTUAL_RSRC_QTY, ACTUAL_RSRC_USAGE — actual consumption recorded during execution.
• USAGE_UM — unit of measure for usage, referencing SY_UOMS_MST.
• PLAN_START_DATE, PLAN_CMPLT_DATE, ACTUAL_START_DATE, ACTUAL_CMPLT_DATE — scheduled and actual operation timing.
• SCALE_TYPE — indicates how the operation scales with batch size.

Standard EBS audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, DELETE_MARK) and 30 ATTRIBUTE columns are also present, supporting extensibility and multi-org auditing conventions.

Common Use Cases and Queries

Typical usage includes batch execution reporting, resource consumption and yield analysis, and batch costing. A common query lists operations for a given batch with planned versus actual usage:

• Reporting planned-versus-actual resource usage per batch step by joining PLAN_RSRC_USAGE and ACTUAL_RSRC_USAGE filtered by BATCH_ID.
• Batch cost analysis by grouping rows by COST_ANALYSIS_CODE and COST_CMPNTCLS_ID.
• Resource-level tracing joining RESOURCES to CR_RSRC_MST to obtain resource names and descriptions.
• Timeline reporting using PLAN_START_DATE/ACTUAL_START_DATE to detect schedule slippage on batch operations.
• Identifying primary resources via PRIM_RSRC_IND to distinguish essential from ancillary resource usage.

Related Objects

PM_OPRN_DTL participates in a rich foreign-key web. The most significant related objects and join columns are:

• PM_ROUT_DTL (via BATCH_ID, BATCHSTEP_NO) — the routing detail defining the batch step.
• FM_OPRN_DTL (via OPRN_LINE_ID, and self-referenced by DEP_OPRN_LINE_ID) — the operation line master.
• CR_RSRC_MST (via RESOURCES) — the resource master.
• FM_ACTV_MST and GMD_ACTIVITIES_B (via ACTIVITY) — activity definitions.
• CM_ALYS_MST (via COST_ANALYSIS_CODE) — cost analysis master.
• CM_CMPT_MST (via COST_CMPNTCLS_ID) — cost component class master.
• SY_UOMS_MST (via USAGE_UM) — unit-of-measure definitions.
• PM_TEXT_HDR (via TEXT_CODE) — text and notes headers attached to the operation.

These relationships make PM_OPRN_DTL a central junction for batch execution, resource management, and process costing transactions within GME.