Results for “new_status”

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

Overview

PM_HIST_HDR is a production history header table owned by the GME (Process Manufacturing Process Execution) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It records header-level production history events generated as batches move through the process manufacturing lifecycle, capturing status transitions and warehouse reassignments. In practice, PM_HIST_HDR functions as a transactional history ledger that preserves a record of what changed on a batch, when, and under which concurrent program or request. Data Vault modeling suggests classifying this table as satellite-leaning, with its primary key (EVENT_ID) behaving as a link to production history detail rather than a true business hub key.

Key Information Stored

The table contains 16 documented columns. The most significant are listed below.

• EVENT_ID — Surrogate primary key (PM_HIST_HDR_PK). Identifies each history event uniquely and is the join key to dependent tables such as PC_TRAN_PND.
• BATCH_ID — Foreign key to PM_BTCH_HDR. Links the history record to the originating batch.
• ORIG_STATUS — The batch status before the recorded event.
• NEW_STATUS — The batch status after the recorded event, enabling before/after status tracking.
• ORIG_WIP_WHSE — Foreign key to IC_WHSE_MST; the original work-in-process warehouse.
• NEW_WIP_WHSE — Foreign key to IC_WHSE_MST; the new work-in-process warehouse after the event.
• GL_POSTED_IND — Indicates whether the associated transaction has been posted to the General Ledger.
• CREATION_DATE and LAST_UPDATE_DATE — Standard audit timestamps for record creation and last modification.
• CREATED_BY and LAST_UPDATED_BY — Audit columns capturing the user IDs responsible for the record.
• PROGRAM_ID, PROGRAM_APPLICATION_ID, REQUEST_ID, and PROGRAM_UPDATE_DATE — Concurrent program context identifying the process that wrote the history row.

The documented primary key is EVENT_ID. The metadata does not identify a separate unique business-key index, so BATCH_ID combined with status and audit attributes serves as the practical business identifier.

Common Use Cases and Queries

Typical uses include batch status transition audits, WIP warehouse movement reporting, GL posting reconciliation, and concurrent program traceability.

• Batch status history: SELECT h.BATCH_ID, h.ORIG_STATUS, h.NEW_STATUS, h.CREATION_DATE FROM GME.PM_HIST_HDR h WHERE h.BATCH_ID = :batch_id ORDER BY h.CREATION_DATE;
• Warehouse movement analysis: join ORIG_WIP_WHSE and NEW_WIP_WHSE to IC_WHSE_MST to describe warehouse transfers.
• Unposted GL transactions: SELECT * FROM GME.PM_HIST_HDR WHERE GL_POSTED_IND = 'N';
• Concurrent program audit: filter on REQUEST_ID, PROGRAM_ID, or PROGRAM_APPLICATION_ID to trace which job produced each history row.

Related Objects

• PM_BTCH_HDR — Joined on PM_HIST_HDR.BATCH_ID = PM_BTCH_HDR.BATCH_ID; the parent batch header.
• IC_WHSE_MST — Joined twice, via ORIG_WIP_WHSE and NEW_WIP_WHSE, for warehouse lookups.
• PC_TRAN_PND — References PM_HIST_HDR via EVENT_ID (PC_TRAN_PND.EVENT_ID → PM_HIST_HDR.EVENT_ID), linking pending transactions to history events.

Together these relationships position PM_HIST_HDR as the central header record for production history events within Process Manufacturing Process Execution.