Results for “transfer_step_no”

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

Overview

PM_OPRN_WIP is a Process Manufacturing Process Execution (GME) transaction table owned by the GME schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented description is "Completed incoming/output WIP transactions," indicating that it stores material movements completed against work-in-process operations in process manufacturing batches. Each row records a discrete quantity transfer — typically a batch step receiving input or producing output — together with its unit of measure, transaction date, routing context, and a set of descriptive and DFF attributes.

The table is central to reconciling batch yield, step consumption, and transfer quantities within process execution. Its primary key is PM_OPRN_WIP_PK, defined on the WIP_TRANS_ID column. The ETRM relational metadata classifies this object heuristically as a link in a Data Vault model, since it references multiple parent entities (text headers, routing detail, and units of measure) rather than behaving as a standalone hub or a descriptive satellite. This classification should be treated as a modeling suggestion derived from the foreign-key structure, not as a formal Oracle designation.

Key Information Stored

The documented physical schema contains 46 columns. The most significant are:

• WIP_TRANS_ID — surrogate primary key (PM_OPRN_WIP_PK) uniquely identifying each completed WIP transaction.
• BATCH_ID — the batch (recipe/routing instance) against which the transaction was completed; a business-key candidate when combined with step and transaction context.
• BATCHSTEP_NO — the batch step at which the material movement occurred.
• TRANSFER_STEP_NO — the counterpart step for transfers, distinguishing source and destination operations.
• LINE_TYPE — classifies the transaction line (for example, incoming versus output semantics).
• TRANS_QTY — the quantity transferred or completed.
• TRANS_UM — unit of measure for TRANS_QTY, validated against SY_UOMS_MST.
• TRANS_DATE — effective date of the completed transaction.
• TEXT_CODE — reference to a text header (PC_TEXT_HDR) supplying free-form notes.
• DELETE_MARK — logical deletion flag; active rows are typically filtered on DELETE_MARK = 0.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE30 — the standard Oracle descriptive flexfield columns for customer-defined extensions.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit and concurrency columns.

The surrogate key is WIP_TRANS_ID; the natural business key is composed of BATCH_ID together with BATCHSTEP_NO, TRANSFER_STEP_NO, and TRANS_DATE for a given execution context.

Common Use Cases and Queries

Typical reporting uses include batch yield analysis, step-level consumption reconciliation, and audit of completed WIP movements for a given date range. A representative query retrieving completed transactions with their unit-of-measure description is:

• SELECT w.WIP_TRANS_ID, w.BATCH_ID, w.BATCHSTEP_NO, w.TRANSFER_STEP_NO, w.TRANS_QTY, w.TRANS_UM, w.TRANS_DATE FROM GME.PM_OPRN_WIP w WHERE w.DELETE_MARK = 0 AND w.TRANS_DATE BETWEEN :start_date AND :end_date ORDER BY w.BATCH_ID, w.BATCHSTEP_NO;
• Joining to SY_UOMS_MST on TRANS_UM to resolve the unit of measure name for reporting.
• Aggregating TRANS_QTY by BATCH_ID and BATCHSTEP_NO to produce a completed-step yield summary.
• Filtering by LINE_TYPE to separate incoming input transactions from output completion transactions.

Because the table carries forty-six columns including a thirty-segment DFF, deployments that use descriptive flexfields should aggregate ATTRIBUTE_CATEGORY and the relevant ATTRIBUTE columns explicitly in extract queries.

Related Objects

The documented foreign keys establish the following principal relationships:

• PM_ROUT_DTL — referenced twice via BATCH_ID, once for BATCHSTEP_NO and once for TRANSFER_STEP_NO. This links each transaction to the routing detail row defining the step.
• PC_TEXT_HDR — referenced through TEXT_CODE, providing textual annotations attached to the transaction.
• SY_UOMS_MST — referenced through TRANS_UM, supplying the unit-of-measure definition.

In practice these parent tables form the standard join path for batch transaction reporting: PM_OPRN_WIP to PM_ROUT_DTL for step context, to PC_TEXT_HDR for notes, and to SY_UOMS_MST for measurement text. Downstream reporting and extract programs in the GME module query PM_OPRN_WIP as the authoritative record of completed incoming and output WIP transactions, and reconcile it with batch and routing definitions when validating yields for Oracle EBS 12.1.1 and 12.2.2.