Search Results authorization_name

Overview

POS_CHV_AUTHORIZATIONS_V is a reporting view owned by the APPS schema within the Oracle E-Business Suite Purchasing (PO) module. Its status is documented as VALID in ETRM 12.2.2. The view exposes authorization records associated with purchasing schedule items, presenting the authorization code alongside its descriptive lookup name and the associated schedule line attributes such as quantity, unit of measure, and cutoff date.

The view functions primarily as a denormalized read layer. Instead of requiring report developers and integration interfaces to join the authorization table to the lookup table manually, POS_CHV_AUTHORIZATIONS_V performs that join internally, returning the human-readable authorization name (via the DISPLAYED_FIELD column) in the same result set as the code and quantity data. The name "POS_CHV" reflects its lineage in the Purchasing scheduling and cumulative history functionality, where authorization sequences and cutoff dates govern how supplier schedule quantities are processed and confirmed.

Underlying Base Objects

The documented base objects for this view are CHV_AUTHORIZATIONS (exposed through a synonym), FND_GLOBAL (a package), and PO_LOOKUP_CODES (itself a view). The view text joins CHV_AUTHORIZATIONS (aliased CAU) to PO_LOOKUP_CODES (aliased PLC) on the condition that CAU.AUTHORIZATION_CODE equals PLC.LOOKUP_CODE and the lookup type is 'AUTHORIZATION_TYPE'. A fixed filter restricts CAU.REFERENCE_TYPE to 'SCHEDULE_ITEMS', meaning the view returns only authorizations tied to schedule item references.

Because FND_GLOBAL is referenced, the view inherits standard EBS multi-org and session context behavior used throughout the applications schema. The join to PO_LOOKUP_CODES supplies the descriptive authorization name (returned as DISPLAYED_FIELD) that maps the stored authorization code to its displayed meaning.

Key Columns

The view exposes a comprehensive set of columns. The most significant include:

• AUTHORIZATION_CODE — the code identifying the type of authorization applied to the schedule item, joined to LOOKUP_CODE in PO_LOOKUP_CODES.
• AUTHORIZATION_NAME — the descriptive lookup value (derived from DISPLAYED_FIELD) corresponding to the authorization code.
• SCHEDULE_ITEM_ID / REFERENCE_ID — the identifier linking the authorization to its purchasing schedule item.
• AUTHORIZATION_SEQUENCE — the ordering sequence of authorizations applied.
• SCHEDULE_QUANTITY and SCHEDULE_QUANTITY_PRIMARY — the schedule quantity in purchasing and primary units of measure respectively.
• PRIMARY_UNIT_OF_MEASURE and PURCHASING_UNIT_OF_MEASURE — the units associated with each quantity.
• TIMEFENCE_DAYS — the number of days defining the authorization time fence.
• CUTOFF_DATE — the date beyond which the authorization no longer applies.
• Standard audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE, supporting concurrent program tracking and change auditing.
• Fifteen ATTRIBUTE columns (ATTRIBUTE_CATEGORY through ATTRIBUTE15) providing the standard EBS extensibility descriptors.

Common Use Cases and Queries

Typical usage centers on reporting schedule item authorizations with readable names, reconciling quantity and cutoff information, and feeding downstream integrations. A common query retrieves authorizations for a given schedule item, displaying code and name:

• SELECT authorization_code, authorization_name, schedule_quantity, cutoff_date FROM pos_chv_authorizations_v WHERE schedule_item_id = :p_schedule_item_id ORDER BY authorization_sequence;
• SELECT authorization_code, COUNT(*) FROM pos_chv_authorizations_v GROUP BY authorization_code;
• SELECT schedule_item_id, authorization_name, timefence_days, cutoff_date FROM pos_chv_authorizations_v WHERE cutoff_date >= SYSDATE;

Because the view already resolves the lookup join, developers avoid re-implementing the AUTHORIZATION_TYPE lookup logic. Queries filtering by AUTHORIZATION_CODE are the most frequent, as the code is the primary search key for this object.