Search Results chv_authorizations_v




Overview
Explore in AI Chat

Overview

CHV_AUTHORIZATIONS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, classified under the CHV – Supplier Scheduling product family. In the ETRM metadata for 12.2.2 the object is marked VALID and carries the description "- Retrofitted," indicating that the view was re-created or preserved unchanged during the upgrade path from 12.1.1 to 12.2.2 and forms part of the compatibility surface used by Supplier Scheduling and its dependent integrations. The view presents supplier schedule authorization records in a denormalized, presentation-ready form by joining the authorizations table to the purchasing lookup codes view so that the authorization code is accompanied by its human-readable name.

The view is read-only by construction and is intended to support reporting, concurrent-program extraction, and interface queries rather than transactional maintenance. Because the authorization name is resolved at query time from PO_LOOKUP_CODES, the view automatically reflects lookup code maintenance performed in Purchasing without requiring a data migration step.

Underlying Base Objects

The documented base objects referenced by CHV_AUTHORIZATIONS_V are:

  • CHV_AUTHORIZATIONS (referenced in metadata as a SYNONYM over the underlying authorization table)
  • PO_LOOKUP_CODES (VIEW), the Purchasing lookup view
  • FND_GLOBAL (PACKAGE), the standard Oracle Applications global context package

The defining query joins CHV_AUTHORIZATIONS (aliased CAU) to PO_LOOKUP_CODES (aliased PLC) with two predicates: CAU.REFERENCE_TYPE must equal the literal 'SCHEDULE_ITEMS', and CAU.AUTHORIZATION_CODE must equal PLC.LOOKUP_CODE, with PLC.LOOKUP_TYPE constrained to the literal 'AUTHORIZATION_TYPE'. In the source text published in the ETRM record, the lookup-type predicate is expressed in the form 'AUTHORIZATION_TYPE' = PLC.LOOKUP_TYPE. The effect is a one-to-many collapse risk if duplicate lookup codes exist within that lookup type, so consumers should assume the lookup table is unique on (LOOKUP_TYPE, LOOKUP_CODE), which is the functional expectation in a standard EBS installation.

Note that the view's select list in the documented source text references CAU.REFERENCE_ID, whereas the column listing exposes SCHEDULE_ITEM_ID. In practice the reference identifier is the schedule item identifier for rows where REFERENCE_TYPE is 'SCHEDULE_ITEMS', and the semantic meaning is identical.

Key Columns

Common Use Cases and Queries

Typical uses include reporting release authorizations against supplier schedules, auditing time fence and cutoff dates, and supplying extract files for supplier portals. A representative query listing authorizations for a given schedule item and ordering them by sequence:

SELECT schedule_item_id,
       authorization_sequence,
       authorization_code,
       authorization_name,
       schedule_quantity,
       primary_unit_of_measure,
       cutoff_date,
       timefence_days
FROM   apps.chv_authorizations_v
WHERE  schedule_item_id = :p_schedule_item_id
ORDER BY authorization_sequence;

Because the view already resolves the lookup description, it is convenient for value-set or LOV-style reads that need the authorization name without an additional join to PO_LOOKUP_CODES. Reports keyed on creation or update dates can filter on CREATION_DATE and LAST_UPDATE_DATE directly, and concurrent-program lineage can be traced through REQUEST_ID and PROGRAM_ID. When only coded values are required, querying CHV_AUTHORIZATIONS directly avoids the lookup join entirely.