Search Results po_requisitions_interface

Overview

PO_IMPORT_SOURCES_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, residing in the Purchasing (PO) product module. In ETRM 12.1.1 and 12.2.2 the object carries a status of VALID and is documented under the Purchasing product with the description "Requisition Import." The view presents a distilled list of the distinct interface source codes and operating unit identifiers that currently exist within the Requisition Import interface table. Rather than exposing transactional requisition rows, it answers a single, narrow question: which interface sources have been loaded into the requisition interface for a given organization.

This makes the view a lightweight reference and control object. It is typically consumed by reporting, validation, and lookup logic that needs to confirm whether a particular interface source (for example, a named external feeder system or a legacy conversion load) has populated the interface table before the Requisition Import concurrent program is run. Because the view is defined with a GROUP BY, it returns only one row per unique combination of source code and organization, keeping the result set small and inexpensive to query.

Underlying Base Objects

Per the documented ETRM metadata, the view is defined exclusively over PO_REQUISITIONS_INTERFACE, referenced through a synonym in the APPS schema. The underlying interface table stores staged requisition data awaiting import into the production purchasing tables. The view text is:

SELECT INTERFACE_SOURCE_CODE, ORG_ID
FROM PO_REQUISITIONS_INTERFACE
GROUP BY INTERFACE_SOURCE_CODE, ORG_ID

Consequently, the view presents no data of its own; it is a purely derived projection of the base interface table. Row count in the base table directly affects the distinct-value results, and any purge or truncation of the interface table changes the view output. Because it aggregates rather than joining to production tables, the view does not reflect validated or successfully imported requisitions — only the staging records present at query time.

Key Columns

• INTERFACE_SOURCE_CODE — A short identifier indicating the origin of requisition interface records, such as a named external system, conversion load, or other feeder process. This is the primary filtering attribute and typically drives the values passed to the Requisition Import process parameters.
• ORG_ID — The operating unit (organization) identifier under which the interface records were staged. It aligns the source code to a specific business entity and is commonly joined to HR_OPERATING_UNITS or resolved through the ORG_ID naming convention for reporting.

The view exposes only these two columns. There is no status, date, or quantity column, so it serves exclusively as a distinct-value lookup rather than a transactional report source.

Common Use Cases and Queries

Typical scenarios include confirming valid source codes before submitting Requisition Import, building a value set or list of values for the import concurrent program parameter, and auditing which operating units have pending interface data.

Listing all available sources and their organizations:

SELECT INTERFACE_SOURCE_CODE, ORG_ID
FROM   APPS.PO_IMPORT_SOURCES_V
ORDER BY ORG_ID, INTERFACE_SOURCE_CODE;

Restricting to a single operating unit:

SELECT INTERFACE_SOURCE_CODE
FROM   APPS.PO_IMPORT_SOURCES_V
WHERE  ORG_ID = :p_org_id;

Joining to resolve the operating unit name:

SELECT s.INTERFACE_SOURCE_CODE, hou.NAME
FROM   APPS.PO_IMPORT_SOURCES_V s,
       APPS.HR_OPERATING_UNITS hou
WHERE  hou.ORGANIZATION_ID = s.ORG_ID;

Because the view depends entirely on staged rows, it is best used as a pre-import readiness check rather than as a historical or reconciliation report.