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:
- PO_REQUISITION_HEADERS_ALL (SYNONYM) — the primary transactional source of requisition header rows.
- PER_PEOPLE_F (VIEW) — supplies preparer and person-related attributes.
- HR_ALL_ORGANIZATION_UNITS (SYNONYM) — provides the operating unit name associated with the requisition.
- AP_CARDS_ALL (SYNONYM) — supplies procurement card identifiers and numbers.
- HR_GENERAL (PACKAGE), HR_PERSON_NAME (PACKAGE), HR_SECURITY (PACKAGE) — used for name formatting and organization security enforcement.
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:
- REQUISITION_ID and DOCUMENT_NUMBER — the internal key and the user-visible requisition number.
- OPERATING_UNIT_ID and OPERATING_UNIT_NAME — the requesting operating unit.
- _LA:REQUISITION_TYPE, _LA:AUTHORIZATION_STATUS, _LA:CLOSURE_STATUS, _LA:CANCEL_FLAG, _LA:CHANGE_PENDING_FLAG — translated lookup descriptions for type, approval, closure, and status flags.
- AUTHORIZER_NOTE — a VARCHAR2(4000) free-text field carrying the note recorded by the approver/authorizer during the requisition approval process.
- DESCRIPTION, EMERGENCY_PO_NUMBER, USSGL_TRANSACTION_CODE — descriptive and accounting reference fields.
- PREPARER_ID and PREPARER_NAME — the preparer of the requisition.
- CREATED_DATE, CREATED_BY, LAST_UPDATED_DATE, LAST_UPDATED_BY — standard WHO audit columns.
- PCARD_ID and PCARD_NUMBER — procurement card association.
- CONTRACTOR_STATUS and CONTRACTOR_REQUISITION_FLAG — status of the resource finalization process for temp labor requisitions and an indicator distinguishing regular requisitions from temp labor requisitions.
- APPROVED_DATE and CBC_ACCOUNTING_DATE — approval and accounting dates.
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.
-
VIEW: APPS.POFV_REQUISITIONS
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:PO.POFV_REQUISITIONS, object_name:POFV_REQUISITIONS, status:VALID,
-
VIEW: APPS.POBV_REQUISITIONS
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:PO.POBV_REQUISITIONS, object_name:POBV_REQUISITIONS, status:VALID,
-
VIEW: APPS.POBV_REQUISITIONS
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:PO.POBV_REQUISITIONS, object_name:POBV_REQUISITIONS, status:VALID,
-
View: POFV_REQUISITIONS
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:PO.POFV_REQUISITIONS, object_name:POFV_REQUISITIONS, status:VALID, product: PO - Purchasing , description: - Retrofitted , implementation_dba_data: APPS.POFV_REQUISITIONS ,
-
VIEW: APPS.POFV_REQUISITIONS
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:PO.POFV_REQUISITIONS, object_name:POFV_REQUISITIONS, status:VALID,
-
View: POBV_REQUISITIONS
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:PO.POBV_REQUISITIONS, object_name:POBV_REQUISITIONS, status:VALID, product: PO - Purchasing , description: - Retrofitted , implementation_dba_data: APPS.POBV_REQUISITIONS ,
-
View: POBV_REQUISITIONS
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:PO.POBV_REQUISITIONS, object_name:POBV_REQUISITIONS, status:VALID, product: PO - Purchasing , description: - Retrofitted , implementation_dba_data: APPS.POBV_REQUISITIONS ,
-
View: POFV_REQUISITIONS
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:PO.POFV_REQUISITIONS, object_name:POFV_REQUISITIONS, status:VALID, product: PO - Purchasing , description: - Retrofitted , implementation_dba_data: APPS.POFV_REQUISITIONS ,
-
eTRM - PO Tables and Views
12.1.1
description: Temporary table for tracking a receiving upgrade from Release 9 to Release 10 ,
-
eTRM - PO Tables and Views
12.2.2
description: Temporary table for tracking a receiving upgrade from Release 9 to Release 10 ,