Results for “sequence_num”

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

Overview

PO_ACTION_HISTORY_V is an APPS-owned database view in the Oracle E-Business Suite Purchasing (PO) module, reported with a VALID status in ETRM 12.2.2 and documented identically for 12.1.1. The view is flagged as "10SC ONLY," indicating that it is intended exclusively for the Oracle Advanced Supply Chain Planning / Supply Chain Management context rather than for general-purpose transactional reporting. Its function is to denormalize approval and control workflow actions recorded against purchasing documents, translating internal action codes into user-facing display text and resolving the performing employee's name.

In reporting and integration terms, the view presents a readable audit trail of approvals, rejections, notifications, and control actions taken on purchase orders, releases, RFQs, quotations, and related objects. Because it enriches coded values with descriptive display fields, it is well suited to operational audit extracts, workflow monitoring dashboards, and interfaces that must present human-readable approval histories without joining lookup tables directly.

Underlying Base Objects

The view is defined over the following documented base objects:

• PO_ACTION_HISTORY (SYNONYM) — the primary driving table, supplying all transactional, audit, and who-columns.
• PO_EMPLOYEES_SV (PACKAGE) — a server-side package whose GET_EMP_NAME function resolves EMPLOYEE_ID to an employee name.
• PO_LOOKUP_CODES (VIEW) — joined twice, with outer joins, to translate ACTION_CODE into a displayed field.
• FND_GLOBAL (PACKAGE) — the standard Oracle Applications context package referenced by the definition.

The join on PO_LOOKUP_CODES uses two aliases with the (+) outer-join operator. POLC1 matches ACTION_CODE against LOOKUP_TYPE 'APPROVER ACTIONS'; POLC2 matches ACTION_CODE against LOOKUP_TYPE 'CONTROL ACTIONS'. The select list applies NVL(POLC1.DISPLAYED_FIELD, POLC2.DISPLAYED_FIELD), so approver-action descriptions take precedence and control-action descriptions serve as the fallback. This mechanism ensures that a single ACTION_CODE is rendered meaningfully regardless of which lookup category defines it.

Key Columns

The view exposes the full column set of PO_ACTION_HISTORY plus two derived columns:

• ROW_ID — the row identifier of the underlying PO_ACTION_HISTORY record, often used as a pseudo key.
• OBJECT_ID, OBJECT_TYPE_CODE, OBJECT_SUB_TYPE_CODE — identify the specific purchasing document and its class to which the action applies.
• ACTION_CODE / ACTION_CODE_DSP — the stored action code and its resolved, displayable description.
• ACTION_DATE, SEQUENCE_NUM — chronology of the action and its ordering within a document's history.
• EMPLOYEE_ID / EMPLOYEE_NAME — the performer identifier and the name resolved through PO_EMPLOYEES_SV.GET_EMP_NAME.
• APPROVAL_PATH_ID — links the action to the approval path/route used.
• NOTE, OFFLINE_CODE, OBJECT_REVISION_NUM — free-text annotations, offline processing indicator, and object version.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE, PROGRAM_DATE — standard Oracle Applications audit and concurrent-program columns.

Common Use Cases and Queries

Typical scenarios include reconstructing the approval audit trail for a purchase order, auditing who approved which document and when, and feeding approval data into planning or analytics extracts. A representative query filters by document:

• SELECT object_id, action_code_dsp, action_date, employee_name, note FROM apps.po_action_history_v WHERE object_type_code = 'PO' AND object_id = :p_po_header_id ORDER BY sequence_num, action_date;

Because the view is designated "10SC ONLY," it should be treated as a specialized object: confirm its applicability in the target environment and prefer it over direct lookups to PO_ACTION_HISTORY when display-ready action descriptions and employee names are required.