Results for “overrided_protected_ind”

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

Overview

PC_TRAN_PND is a transaction table owned by the GME schema in Oracle E-Business Suite, belonging to the Process Manufacturing Process Execution (POC) module. The object name reflects its purpose: POC (Process Operations Control) Transaction Pending. It serves as a staging and holding area for transaction records generated during process manufacturing execution before they are completed, posted, or interfaced to downstream systems such as inventory, costing, or the process execution history tables.

Within the GME product family, PC_TRAN_PND functions as the operational repository for resource consumption, transaction activity, and event linkage associated with process batches and production runs. Records are written as process operations are performed and subsequently updated as transactions progress through completion, posting, and reconciliation stages, as indicated by status columns such as COMPLETED_IND and POSTED_IND.

From a data-modeling perspective, the ETRM metadata classifies PC_TRAN_PND heuristically as a link table. This classification is derived from its heavy foreign-key structure, which connects organizational units, documents, resources, reason codes, units of measure, and process history records. In a Data Vault model, PC_TRAN_PND would naturally resolve into a link entity capturing the relationships between these business hubs across each transaction event, rather than a hub or satellite.

Key Information Stored

The table contains 59 documented columns. The most operationally significant columns include:

• POC_TRANS_ID — the surrogate primary key defined by the constraint PC_TRAN_PND_PK, uniquely identifying each pending process transaction.
• ORGN_CODE — the organization code, a foreign key to both SY_ORGN_MST_B and SY_ORGN_MST, identifying the operating unit or warehouse context.
• DOC_TYPE and DOC_ID — the document type (FK to SY_DOCS_MST) and document identity linking the transaction to its source production or inventory document.
• LINE_TYPE and LINE_ID — identify the specific line within the originating document, enabling line-level transaction tracking.
• RESOURCES and RESOURCE_USAGE — capture the resource consumed and the quantity or usage amount associated with the transaction.
• TRANS_UM — the unit of measure for the transaction, FK to SY_UOMS_MST.
• TRANS_DATE, START_DATE, and END_DATE — transaction timestamp and the start/end of the activity window.
• EVENT_ID — foreign key to PM_HIST_HDR, tying the pending transaction to its process history header record.
• COMPLETED_IND and POSTED_IND — status flags indicating whether the transaction has completed and posted downstream.
• REASON_CODE — FK to SY_REAS_CDS_B and SY_REAS_CDS, identifying the reason for variance or adjustment.
• TEXT_CODE — FK to PC_TEXT_HDR, linking to associated text notes.
• OVERRIDED_PROTECTED_IND — flag indicating whether a protected value was overridden.
• DELETE_MARK — logical deletion indicator.
• Standard audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY) and the WHO-style request columns (PROGRAM_ID, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE).
• The thirty ATTRIBUTE1 through ATTRIBUTE30 columns plus ATTRIBUTE_CATEGORY, providing the standard DFF extension mechanism.

POC_TRANS_ID is the documented surrogate key. No alternate unique business key is specified in the metadata; DOC_TYPE plus DOC_ID plus LINE_ID plus RESOURCES plus an effective date would be a plausible natural candidate for de-duplication.

Common Use Cases and Queries

PC_TRAN_PND is most frequently queried for pending-transaction monitoring, resource-consumption reporting, and troubleshooting incomplete process execution records. Typical patterns include:

• Pending transaction backlog — identify transactions that have not yet posted: SELECT poc_trans_id, orgn_code, doc_id, resources, resource_usage FROM gme.pc_tran_pnd WHERE posted_ind = 'N' AND delete_mark = 0;
• Resource usage by organization and date range — aggregate RESOURCE_USAGE grouped by ORGN_CODE and TRANS_DATE for process costing or yield analysis.
• Completion reconciliation — compare COMPLETED_IND against POSTED_IND to detect records stuck between process execution and inventory posting, commonly audited by production support teams.
• Reason-code analysis — join to SY_REAS_CDS to classify variance transactions by reason for quality or scrap reporting.
• Event traceability — join EVENT_ID to PM_HIST_HDR to correlate pending transactions with their process history record for end-to-end batch genealogy.

Related Objects

The following objects are directly referenced through documented foreign-key or PK relationships:

• PM_HIST_HDR — joined on EVENT_ID = PM_HIST_HDR.EVENT_ID; provides process history detail for each transaction event.
• SY_DOCS_MST — joined on DOC_TYPE; resolves the transaction document type.
• SY_ORGN_MST_B and SY_ORGN_MST — joined on ORGN_CODE; supply organization and operating-unit definitions.
• SY_REAS_CDS_B and SY_REAS_CDS — joined on REASON_CODE; resolve reason-code descriptions.
• SY_UOMS_MST — joined on TRANS_UM; resolves the unit of measure.
• PC_TEXT_HDR — joined on TEXT_CODE; supplies associated text headers.

Additional GME consumers, such as process execution concurrent programs and interface routines that read completed and posted pending transactions, populate downstream inventory and costing tables, but these are not enumerated as FK relationships in the documented metadata.