Search Results pc_tran_pnd




Overview
Explore in AI Chat

Overview

The PC_TRAN_PND table is a core transactional data object within the Oracle E-Business Suite Process Manufacturing (GME) module, specifically for Process Execution. It serves as the primary staging or pending transaction table for Point of Consumption (POC) transactions. In the context of process manufacturing, POC transactions are critical for recording the consumption of ingredients, resources, and by-products against a batch or process order in real-time. The table's role is to hold transaction data before it is fully processed, validated, and potentially posted to permanent inventory and costing tables, ensuring data integrity and supporting complex manufacturing execution workflows in versions 12.1.1 and 12.2.2.

Key Information Stored

The table's primary key is POC_TRANS_ID, which uniquely identifies each pending transaction record. Based on the documented foreign key relationships, the table stores several key pieces of information that contextualize the transaction. This includes organizational data (ORGN_CODE linked to SY_ORGN_MST), the unit of measure for the transaction (TRANS_UM linked to SY_UOMS_MST), and reason codes (REASON_CODE linked to SY_REAS_CDS) for audit and analysis. It also links to quality or process events (EVENT_ID linked to PM_HIST_HDR), document types (DOC_TYPE linked to SY_DOCS_MST), and descriptive text (TEXT_CODE linked to PC_TEXT_HDR). These relationships indicate the table captures a comprehensive set of attributes necessary for a complete manufacturing transaction record.

Common Use Cases and Queries

A primary use case is investigating pending transactions that have not yet completed processing, which may indicate a system stall or require manual intervention. A common query would join to organization and item tables to list pending consumptions for a specific batch. For example: SELECT pnd.poc_trans_id, pnd.orgn_code, gbh.batch_no, msib.segment1 item
FROM gme.pc_tran_pnd pnd,
gme.gme_batch_header gbh,
inv.mtl_system_items_b msib
WHERE pnd.batch_id = gbh.batch_id
AND pnd.inventory_item_id = msib.inventory_item_id
AND pnd.organization_id = msib.organization_id
AND pnd.transaction_status = 'PENDING'; Reporting use cases include analyzing consumption reasons, correlating transactions with process events for yield analysis, and auditing material movements prior to final cost posting. Integration points often involve the GME transaction manager and cost processor, which read from and clear this table.

Related Objects

As defined by its foreign keys, PC_TRAN_PND has direct relationships with several foundational and module-specific tables. Key related objects include:

  • PC_TEXT_HDR: For descriptive text associated with the transaction.
  • PM_HIST_HDR: For linking to process or quality management history events.
  • SY_DOCS_MST, SY_ORGN_MST, SY_UOMS_MST, SY_REAS_CDS: For document types, organization, unit of measure, and reason code master data, respectively.
This table is a feeder for permanent inventory transaction tables (e.g., MTL_MATERIAL_TRANSACTIONS) and likely interfaces with GME transaction processing packages. Its "PND" (pending) suffix suggests the existence of a corresponding processed history table, such as PC_TRAN_HDR or PC_TRAN_DTL, to which records are moved upon completion.