Search Results authorizer_note




Overview

APPS.POFV_REQUISITIONS is a Business Intelligence System (BIS) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is registered under FND Design Data as PO.POFV_REQUISITIONS and holds a VALID status. The view presents internal requests for goods or services, capturing requisitions that may originate from an employee or from another source such as inventory or manufacturing. Because it is a BIS-style view, it is intended primarily for reporting, ad hoc querying, and downstream integration rather than for transactional data entry. In practice it serves as a denormalized, read-only projection of purchasing requisition header information, joining requisition data to people, organization, and procurement card context so that requisition activity can be reported without navigating multiple base tables directly.

Underlying Base Objects

Per the documented 12.2.2 metadata, POFV_REQUISITIONS is defined over the following referenced objects:

The view therefore combines purchasing requisition headers with HR person and organization data plus procurement card detail, applying HR security logic so that results respect the querying user's organization access.

Key Columns

The view exposes both raw identifiers and translated (_LA:) descriptive columns. Notable columns include:

Common Use Cases and Queries

Typical uses include requisition approval audits, reporting on approver comments, temp labor tracking, and procurement card analysis. The authorizer_note column is frequently queried to retrieve approval comments. For example, to list requisitions with authorizer notes:

  • SELECT document_number, preparer_name, _LA:AUTHORIZATION_STATUS, authorizer_note FROM apps.pofv_requisitions WHERE authorizer_note IS NOT NULL;

To report temp labor requisitions by operating unit:

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

To audit approvals within a date range:

  • SELECT document_number, preparer_name, approved_date FROM apps.pofv_requisitions WHERE approved_date BETWEEN :from_date AND :to_date ORDER BY approved_date;

Because the view enforces HR security and includes multiple synonyms and packages, queries should be run against the APPS schema and results filtered as needed for performance.