Results for “requisition_total”
36 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
PO_HISTORY_REQUISITIONS_ALL is an Oracle Purchasing (PO) module table owned by the PO schema. Its documented description is "Purged requisitions," indicating that it functions as an archival store for requisition header records that have been removed from the operational purchasing tables, typically through the Purge Purchasing Documents concurrent program or the Requisition Purge process. In Oracle EBS 12.1.1 and 12.2.2, this table preserves a minimum set of identifying and audit attributes so that historical requisition activity remains retrievable after the live transaction has been purged from PO_REQUISITION_HEADERS_ALL.
From a Data Vault modeling perspective, the documented structure suggests a satellite-leaning classification. The table carries a narrow column set anchored to a segment identifier and an operating unit, with no downstream child references of its own. It therefore behaves less like a hub (which would normally hold a stable business key without descriptive attributes) and more like a historical satellite that records the state of a requisition at the point of purge.
Key Information Stored
The table is defined with 12 documented columns. The most significant are:
- SEGMENT1 — The requisition number, serving as the primary key column of PO_HISTORY_REQUISITIONS_PK. It is the core business identifier of the purged requisition.
- ORG_ID — The operating unit identifier. Together with SEGMENT1, it forms the unique index PO_HISTORY_REQUISITIONS_U1, marking (SEGMENT1, ORG_ID) as the true business-key candidate in a multi-org context.
- TYPE_LOOKUP_CODE — The requisition type classification drawn from the lookup codes used by the live requisition header.
- DOCUMENT_SUBTYPE — The document subtype, distinguishing categories such as purchase requisitions versus internal requisitions.
- CREATION_DATE — The date the requisition was originally created, retained to preserve the historical timeline.
- REQUISITION_TOTAL — The monetary value of the requisition at the time of purge, useful for historical spend reconstruction.
- PREPARER_NAME — The name of the person who prepared the requisition.
- PURGE_NAME — The identifier or name associated with the purge execution that moved the record into this table.
- REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID — The concurrent request and program context under which the purge ran, providing a full audit trail of when and by which process the record was archived.
- PROGRAM_UPDATE_DATE — The date the purge program last updated the record.
The surrogate primary key is PO_HISTORY_REQUISITIONS_PK on SEGMENT1, while PO_HISTORY_REQUISITIONS_U1 on (SEGMENT1, ORG_ID) acts as the business-key uniqueness constraint.
Common Use Cases and Queries
Typical usage centers on historical reporting and audit reconciliation when live requisitions are no longer available. A common pattern joins the history table back to the surviving headers to confirm the purge boundary:
- Purge audit trail: SELECT SEGMENT1, ORG_ID, PURGE_NAME, PROGRAM_UPDATE_DATE FROM PO_HISTORY_REQUISITIONS_ALL WHERE PROGRAM_ID = :program_id; This isolates records archived by a specific purge run.
- Historical requisition lookup: SELECT SEGMENT1, REQUISITION_TOTAL, CREATION_DATE, PREPARER_NAME FROM PO_HISTORY_REQUISITIONS_ALL WHERE SEGMENT1 = :req_number AND ORG_ID = :org_id; Using both key columns honors the U1 unique index.
- Multi-org spend reconstruction: Aggregate REQUISITION_TOTAL by ORG_ID and DOCUMENT_SUBTYPE to reconstruct requisition volume across operating units.
- Compliance and retention reporting: Filter by CREATION_DATE ranges to demonstrate retained historical documents for audit or regulatory retention requirements.
Related Objects
The principal documented relationship is a foreign key from PO_HISTORY_REQUISITIONS_ALL.SEGMENT1 to PO_REQUISITION_HEADERS_ALL. Note that this FK uses SEGMENT1 rather than an internal surrogate, so joins are performed on the human-readable requisition number. The most significant related objects include:
- PO_REQUISITION_HEADERS_ALL — The operational requisition header table; the foreign key target for SEGMENT1 and the source from which history rows are derived.
- PO_REQUISITION_LINES_ALL — The line-level operational table, relevant for reconstructing detail that may no longer be present after purge.
- PO_REQUISITION_DISTRIBUTIONS_ALL — Distribution-level detail supporting accounting reconstruction.
- PO_HEADERS_ALL and PO_LINES_ALL — Downstream purchasing documents that may have originated from the purged requisition.
- FND_CONCURRENT_REQUESTS — Joined via REQUEST_ID to identify the purge program instance.
- FND_APPLICATION and FND_PROGRAM — Joined via PROGRAM_APPLICATION_ID and PROGRAM_ID to resolve the purge process definition.
Together these objects allow analysts to bridge the gap between live purchasing activity and the historical archive represented by PO_HISTORY_REQUISITIONS_ALL.
-
Purged requisitions
-
This view is obsolete.
APPS.POR_APPROVAL_STATUS_HEADER_V·↳ DUAL·Explore ICX module →
-
This view is obsolete.
APPS.POR_APPROVAL_STATUS_HEADER_V·↳ DUAL·Explore ICX module →
-
Purged requisitions
-
View: POR_VIEW_HEADER_ALL_V 12.1.1
View Requsition Header view
APPS.POR_VIEW_HEADER_ALL_V·↳ AP_CARDS_ALL·↳ FINANCIALS_SYSTEM_PARAMS_ALL·↳ FND_CURRENCY·Explore ICX module →
-
View: POR_VIEW_HEADER_V 12.1.1
View Requisition Header
APPS.POR_VIEW_HEADER_V·↳ AP_CARDS·↳ FINANCIALS_SYSTEM_PARAMETERS·↳ FND_CURRENCY·Explore ICX module →
-
View: POR_VIEW_HEADER_V 12.2.2
View Requisition Header
APPS.POR_VIEW_HEADER_V·↳ AP_CARDS·↳ FINANCIALS_SYSTEM_PARAMETERS·↳ FND_CURRENCY·Explore ICX module →
-
View: POR_VIEW_HEADER_ALL_V 12.2.2
View Requsition Header view
APPS.POR_VIEW_HEADER_ALL_V·↳ AP_CARDS_ALL·↳ FINANCIALS_SYSTEM_PARAMS_ALL·↳ FND_CURRENCY·Explore ICX module →
-
VIEW: APPS.POR_VIEW_HEADER_V 12.1.1
-
VIEW: APPS.POR_VIEW_HEADER_V 12.2.2
-
eTRM - ICX Tables and Views 12.2.2
-
eTRM - ICX Tables and Views 12.1.1
-
eTRM - PO Tables and Views 12.1.1
Temporary table for tracking a receiving upgrade from Release 9 to Release 10
-
eTRM - PO Tables and Views 12.2.2
Temporary table for tracking a receiving upgrade from Release 9 to Release 10