Search Results contractor_status




Overview
Explore in AI Chat

Overview

POBV_REQUISITIONS is a read-only Oracle EBS view owned by the APPS schema within the PO – Purchasing product family. Its name follows the Oracle "business view" (BV) convention, and it serves as a simplified, flattened reporting layer over purchasing requisition data for use by Oracle iProcurement, Purchasing, and related self-service modules. The view is documented in ETRM as a retrofitted object, meaning it was introduced or reworked to support multi-org architecture and Oracle E-Business Suite 12.1.1 and 12.2.2 release levels.

The view exposes requisition header information in a form suitable for forms-based validation and reporting, including several columns whose names are actually Lookup Attribute (LA) definitions (for example, _LA:REQUISITION_TYPE and _LA:AUTHORIZATION_STATUS). These descriptors drive list-of-values and displayed-field behavior inside Oracle Applications. Because the view is defined WITH READ ONLY, it supports query access only and is not intended for direct DML.

For users investigating contractor_status, the view is directly relevant: it carries both CONTRACTOR_STATUS and CONTRACTOR_REQUISITION_FLAG, which together indicate whether a requisition originated as a contractor requisition and its current contractor-related state.

Underlying Base Objects

According to the documented ETRM metadata, POBV_REQUISITIONS is defined over exactly two referenced base objects, both referenced through APPS synonyms:

  • PO_REQUISITION_HEADERS_ALL – the core requisition header table, aliased RH. This supplies requisition identity, operating unit, document number, status flags, contractor columns, and audit columns.
  • HR_ALL_ORGANIZATION_UNITS – the organization/operating-unit definition table, aliased OP. It supplies the operating unit name.

The join is RH.ORG_ID = OP.ORGANIZATION_ID, and the view enforces multi-org security by requiring '_SEC:RH.ORG_ID' IS NOT NULL, which applies the current operating unit security profile to the result set. Because PO_REQUISITION_HEADERS_ALL is an _ALL table, the join effectively restricts rows to organizations visible under the active security context.

Key Columns

Common Use Cases and Queries

Typical uses include reporting on requisition status by operating unit, feeding iProcurement display logic, and auditing contractor requisitions. The view is commonly joined to requisition lines, distributions, or approval history using REQUISITION_ID.

Example – contractor requisitions for the current operating unit:

  • SELECT document_number, operating_unit_name, contractor_status, contractor_requisition_flag, approved_date FROM apps.pobv_requisitions WHERE contractor_requisition_flag = 'Y';

Example – pending requisitions by authorization status:

  • SELECT document_number, "_LA:AUTHORIZATION_STATUS", preparer_id FROM apps.pobv_requisitions WHERE "_LA:AUTHORIZATION_STATUS" = 'IN PROCESS';

Because the view is secured by operating unit and read-only, queries automatically honor the active organization security profile, making it a reliable source for multi-org-aware reporting and integration extraction.