Results for “po_reqs_in_transit_all_v”

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

Overview

PO_REQS_IN_TRANSIT_ALL_V is an APPS-owned database view in the Oracle E-Business Suite Purchasing (PO) module. Its documented description identifies it as "10SC ONLY - Retrofitted," indicating that the object was introduced to support a specific 10SC (ten-step or business-specific) configuration and subsequently retrofitted into the standard EBS 12.1.1 and 12.2.2 data model. The view presents requisition header information for requisition lines that are in transit — that is, lines that have been placed on a receipt or shipment and are expected to arrive at a destination organization. Because it joins requisition data directly to RCV_SHIPMENT_LINES, it is positioned for reporting on outstanding inbound requisition demand rather than on completed procurement.

As a reporting and integration artifact, the view eliminates the need for custom SQL that reconstructs requisition, employee, document type, and receiving shipment relationships. Its MULTI-ORG nature is expressed through the ORG_ID column, and its use of USERENV('LANG') in the translation join indicates that displayed document-type text is language-sensitive.

Underlying Base Objects

The view is defined over the following documented base objects:

• PO_REQUISITION_HEADERS (SYNONYM) — requisition header header rows, aliased PRH.
• PO_REQUISITION_LINES_ALL (SYNONYM) — requisition lines, aliased PRL.
• HR_EMPLOYEES (VIEW) — employee records, aliased HRE.
• PO_DOCUMENT_TYPES_ALL_B (SYNONYM) — base document type setup, aliased PODB.
• PO_DOCUMENT_TYPES_ALL_TL (SYNONYM) — translated document type text, aliased PODT.
• PO_LOOKUP_CODES (VIEW) — lookup values for authorization status, aliased POLC.
• RCV_SHIPMENT_LINES (SYNONYM) — receiving shipment lines, aliased RSL.

Package and infrastructure references include FND_GLOBAL, FND_PROFILE, HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY. These supply localization, security, and naming context; notably, HR_SECURITY may restrict which preparers or to-persons are visible depending on the user's HR security profile, and FND_PROFILE resolves organization and language context. The join path is: requisition header to line on REQUISITION_HEADER_ID; line to shipment on REQUISITION_LINE_ID; line to employee on TO_PERSON_ID = EMPLOYEE_ID; and document type setup to header on DOCUMENT_SUBTYPE = TYPE_LOOKUP_CODE and matching ORG_ID.

Key Columns

• SEGMENT1 — the requisition number from the header.
• REQUISITION_HEADER_ID — the unique primary key of the requisition header.
• TYPE_LOOKUP_CODE — requisition type (document subtype).
• PREPARER_ID — the employee ID of the requisitioner.
• FULL_NAME — the full name of the to-person or preparer resolved from HR.
• DISPLAYED_FIELD — the display text for the authorization status lookup.
• DESCRIPTION — the requisition header description.
• SECURITY_LEVEL_CODE — the document security level derived from the document type setup (PO_DOCUMENT_TYPES_ALL_B). This is the column users most frequently reference when searching on security level filtering.
• ORG_ID — the operating unit that owns the requisition; essential for multi-org reporting.

The DISTINCT keyword in the view text suppresses duplicate rows resulting from the multiple joins.

Common Use Cases and Queries

Typical uses include monitoring requisitions with in-transit shipments, auditing preparer activity, and filtering by document type security level. A representative query:

SELECT SEGMENT1, REQUISITION_HEADER_ID, TYPE_LOOKUP_CODE,
       FULL_NAME, DISPLAYED_FIELD, SECURITY_LEVEL_CODE, ORG_ID
FROM   APPS.PO_REQS_IN_TRANSIT_ALL_V
WHERE  ORG_ID = :p_org_id
AND    SECURITY_LEVEL_CODE = :p_security_level;

Because the view is a join of transactional and setup data, report consumers should apply operating unit and security-level predicates to keep result sets relevant and to respect HR security constraints applied through the underlying objects.