Search Results gmd_activities_b

Overview

The PM_OPRN_DTL table is a core data object within the Oracle E-Business Suite (EBS) Process Manufacturing (GME) module, specifically for Process Execution. It serves as the detailed transactional repository for batch operations. While a batch routing defines the master sequence of steps, this table stores the granular execution details for each operation or activity performed within a batch step. Its primary role is to capture the actual resource usage, activity performance, and associated costs during the manufacturing process, enabling precise tracking, costing, and analysis of production batches. The table's existence is critical for bridging the planned process defined in the formula and routing with the actual execution events recorded on the shop floor.

Key Information Stored

The table's structure is designed to link execution details to specific batch steps and their constituent lines. Its primary key (PM_OPRN_DTL_PK) uniquely identifies a record using the combination of BATCH_ID, BATCHSTEP_NO, RESOURCES, ACTIVITY, and BATCHSTEPLINE_ID. This composite key underscores its granular nature. Important columns include BATCH_ID and BATCHSTEP_NO, which anchor the detail to a specific step in a specific batch. The RESOURCES and ACTIVITY columns identify the specific resource (e.g., a reactor, labor crew) and the activity (e.g., charge, heat, clean) performed. The BATCHSTEPLINE_ID links to the material or resource line being acted upon. Other significant columns include USAGE_UM (the unit of measure for the resource usage), COST_ANALYSIS_CODE, COST_CMPNTCLS_ID for costing integration, and TEXT_CODE for attaching descriptive notes.

Common Use Cases and Queries

This table is central to operational reporting and cost analysis in Process Manufacturing. Common use cases include generating detailed batch operation reports for shop floor review, calculating actual resource consumption (like machine hours or labor time) for variance analysis against standards, and providing the transaction source for WIP and cost accounting. A typical query might join PM_OPRN_DTL to batch header (GME_BATCH_HEADER) and resource master (CR_RSRC_MST) tables to report all operations for a completed batch. For cost roll-up, queries often join through COST_CMPNTCLS_ID to cost component tables (CM_CMPT_MST). Analysts frequently use this table to investigate production delays by analyzing activity durations or to audit material usage by correlating operations with material transactions.

Related Objects

PM_OPRN_DTL maintains extensive foreign key relationships, integrating execution data with master and transactional data across modules. Key documented relationships include:

• PM_ROUT_DTL: Linked via BATCH_ID and BATCHSTEP_NO. This is a fundamental relationship to the batch step definition.
• CR_RSRC_MST / GMD_ACTIVITIES_B / FM_ACTV_MST: Reference tables for valid RESOURCES and ACTIVITY codes, respectively.
• CM_ALYS_MST and CM_CMPT_MST: Links for cost analysis and cost component classification, crucial for Process Costing.
• FM_OPRN_DTL: Linked via OPRN_LINE_ID, connecting execution details back to the master routing operation definition.
• SY_UOMS_MST: For the unit of measure (USAGE_UM) validation.
• PM_TEXT_HDR: For attaching descriptive text notes to an operation detail line.

These relationships ensure data integrity and enable comprehensive joins for reporting and process traceability.