Results for “object_id2”

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

Overview

PON_ACTION_HISTORY is a Sourcing module table owned by the PON schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It functions as the audit and approval log for sourcing documents, recording each approval, rejection, signature, or workflow action taken against a sourcing object during its lifecycle. Records are retained for compliance, audit trail, and notification purposes, and are consumed by procurement user interfaces that render approval history to buyers and approvers.

The documented ETRM metadata classifies the object heuristically as standalone in Data Vault terms. Because no foreign keys to parent entities are declared, the object is best modeled as a self-contained satellite-style table that accumulates event rows keyed by the sourcing entity, action type, and sequence number, rather than as a hub or link joining multiple business entities. Practitioners modeling this data for a warehouse should treat it as an action-event satellite keyed by the composite primary key.

Key Information Stored

• OBJECT_ID, OBJECT_ID2, OBJECT_TYPE_CODE, SEQUENCE_NUM, ACTION_TYPE — the composite primary key (PON_ACTION_HISTORY_PK). OBJECT_ID identifies the sourcing document, OBJECT_TYPE_CODE distinguishes the document class, SEQUENCE_NUM orders actions within a document, and ACTION_TYPE names the action performed. These five columns together form the business key of the record.
• ACTION_DATE — timestamp of the approval or workflow action.
• ACTION_USER_ID — the user who performed the action; USER_NAME preserves the display name at the time of the event.
• ACTION_NOTE — free-text remarks entered by the approver or initiator.
• ACTION_REASON_CODE — coded reason for a rejection, return, or other disposition.
• FILE_ID — reference to an attached document or signature file associated with the action.
• REQUESTED_FOR_TPC_ID — identifier of the trading partner contact or party for whom the action was requested.
• SIGNED_DATE — date a signature was applied, aligned with the approval history audit trail.

Common Use Cases and Queries

Typical reporting includes reconstructing the approval chain for a sourcing document, measuring approval cycle times, and auditing who signed or rejected a document and under what reason code. A representative query joins the history table to the sourcing header on the object identifier and object type, ordering by sequence number:

• SELECT h.object_id, h.sequence_num, h.action_type, h.action_date, h.user_name, h.action_reason_code FROM pon_action_history h WHERE h.object_type_code = :object_type AND h.object_id = :object_id ORDER BY h.sequence_num;
• Cycle-time analysis: compute MAX(action_date) - MIN(action_date) grouped by document to quantify approval latency.
• Rejection audit: filter ACTION_REASON_CODE IS NOT NULL to surface negative dispositions.
• Signature tracking: filter SIGNED_DATE IS NOT NULL to report documents with executed signatures.

Because the table is append-only in normal operation, it supports point-in-time reconstruction of approval state and is a reliable source for SLA dashboards and audit extracts.

Related Objects

• PON_AUCTION_HEADERS / PON_BIDDINGS and other PON sourcing headers link via OBJECT_ID and OBJECT_TYPE_CODE to the sourcing document being approved.
• PO_ACTION_HISTORY — the procurement counterpart storing approval history for purchasing documents; same design pattern may be used for cross-module reporting.
• FND_USER — resolves ACTION_USER_ID to the application user account and complements the stored USER_NAME.
• FND_ATTACHED_DOCUMENTS / FND_LOBS — resolve FILE_ID to the attached artifact.
• WF_NOTIFICATIONS / WF_ITEM_ACTIVITY_STATUSES — workflow engine records correlated with approval steps.

Sourcing document headers, workflow notification tables, and the FND user and attachment entities form the principal dependency set for reporting against PON_ACTION_HISTORY.