Results for “object_id”

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

Overview

ICX_PO_ACTION_HISTORY_PK_V is an Oracle E-Business Suite view owned by the APPS schema and classified under the ICX product family, which corresponds to Oracle iProcurement. As documented in the ETRM metadata for release 12.2.2, the object is described as the Requisition Action History View. Its purpose within iProcurement is to expose the requisition action history in a shape suitable for the iProcurement user interface and for reporting or integration consumers that require a lightweight projection of the underlying history data.

The view is marked VALID in the data dictionary, indicating that it compiles successfully against the referenced objects. It is documented as a thin wrapper: the view text is defined as SELECT NULL, NULL FROM PO_ACTION_HISTORY_V, and it exposes only two columns, OBJECT_ID and OBJECT_SUB_TYPE_CODE. This structure gives the view a narrowly scoped contract — it is not a general-purpose replacement for PO_ACTION_HISTORY_V, but a deliberate two-column projection used by callers in the iProcurement flow.

Underlying Base Objects

The documented dependency list for this view includes PO_ACTION_HISTORY_V (a view), FND_GLOBAL (a package), and PO_EMPLOYEES_SV (a package). The primary data source is PO_ACTION_HISTORY_V, which in turn is built on the PO_ACTION_HISTORY base table and related Purchasing entities. The view text explicitly selects from PO_ACTION_HISTORY_V, so any row-level filtering, join behavior, or security predicates defined inside that view cascade through to ICX_PO_ACTION_HISTORY_PK_V.

The presence of FND_GLOBAL and PO_EMPLOYEES_SV in the dependency chain reflects standard EBS design patterns. FND_GLOBAL supplies session context such as user identifier, responsibility, and application. PO_EMPLOYEES_SV is a security/employee view used to resolve and restrict employee-related data. Together these dependencies imply that the underlying view applies context-sensitive access rules, meaning the rows a caller sees may vary by login session and responsibility.

Key Columns

• OBJECT_ID — Identifier for the document or object whose action history is being represented. In the iProcurement requisition context this typically corresponds to the requisition header or line identifier used by the caller to correlate history entries.
• OBJECT_SUB_TYPE_CODE — A classification code distinguishing the sub-type of the object or action being recorded. This column is frequently the target of filtering, since consumers commonly search on object_sub_type_code to isolate a specific class of history entry.

Because the view projects only these two columns, it should be treated as a narrow lookup surface rather than a full history record. Attributes such as action code, action date, performer, and notes are not exposed here and must be retrieved from PO_ACTION_HISTORY_V or PO_ACTION_HISTORY when needed.

Common Use Cases and Queries

Typical usage centers on identifying the object identifiers and sub-type classifications associated with requisition action history. A representative query is:

SELECT object_id, object_sub_type_code
FROM apps.icx_po_action_history_pk_v
WHERE object_sub_type_code = :p_sub_type_code;

Another common pattern joins the projected OBJECT_ID back to requisition or purchasing tables to enrich the result set with header details. Report developers use this view when performance and minimal column breadth are preferred over the fuller PO_ACTION_HISTORY_V. Integration developers may use it to validate that a given object participates in action history before calling deeper APIs. All access should be performed through the APPS schema, respecting the session context supplied by FND_GLOBAL.