Results for “address_line”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The APPS.PO_CXML_DELIVERTO_ARCH_V view is a Purchasing (PO) module reporting object in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes archived deliver-to address information for purchase order distributions in a denormalized, XML-friendly format intended to support Oracle Procurement's cXML (commerce XML) punchout and document exchange capabilities, as well as general reporting on historical purchasing shipment destinations. The view joins archived PO distribution records to HR location and person data so that fully resolved address and requestor details can be retrieved in a single query without requiring the caller to perform the underlying joins directly. The view is documented with a status of VALID and is owned by the APPS schema, which is consistent with standard Oracle seed reporting views.

The most frequent entry point for users is the po_line_loc_id column, which the view exposes as an alias for the LINE_LOCATION_ID of the archived distribution. This makes the view useful when reconstructing shipment-level detail for a purchase line location after the corresponding transactional records have been archived.

Underlying Base Objects

The view is defined over three base objects, all referenced through public synonyms in the APPS schema:

• PO_DISTRIBUTIONS_ARCHIVE_ALL — the archived distributions table, aliased PDAA, which supplies the primary keys, quantities, destination type, and deliver-to identifiers.
• HR_LOCATIONS_ALL — aliased HLA, joined on DELIVER_TO_LOCATION_ID = LOCATION_ID to supply the street address, city, region, postal code, and country.
• PER_ALL_PEOPLE_F — aliased PAPF, joined on DELIVER_TO_PERSON_ID = PERSON_ID using an outer join, filtered by NVL(EFFECTIVE_END_DATE, SYSDATE) >= SYSDATE so that only the currently effective person record is returned as the requestor.

Key Columns

The view projects the following columns, most of which are direct references to archived distribution attributes:

• REVISION_NUM, PO_RELEASE_ID, PO_HEADER_ID, PO_LINE_ID — identification of the archived document, release, header, and line.
• PO_DISTRIBUTION_ID, DISTRIBUTION_NUM — the distribution identity and its sequence number.
• PO_LINE_LOC_ID — aliased from LINE_LOCATION_ID and the field most often used to link back to the shipment or line location.
• DELIVER_TO_LOCATION_ID — foreign key to the HR location used in the address join.
• QUANTITY — computed as QUANTITY_ORDERED minus QUANTITY_CANCELLED, presenting the net ordered quantity.
• REQUESTOR — the full name of the effective person record associated with DELIVER_TO_PERSON_ID.
• DESTINATION_TYPE — the destination type code of the distribution.
• LOCATION_CODE, ADDRESS_LINE, COUNTRY, POSTAL_CODE, TOWN_OR_CITY, STATE — the resolved deliver-to address components from HR_LOCATIONS_ALL.

Common Use Cases and Queries

The view is typically queried to retrieve a shipment address block for an archived distribution, or to find all archived distributions shipped to a given location. A representative query retrieving address and requestor detail for a specific line location would select PO_LINE_LOC_ID, DELIVER_TO_LOCATION_ID, ADDRESS_LINE, TOWN_OR_CITY, STATE, POSTAL_CODE, COUNTRY, REQUESTOR, and QUANTITY from PO_CXML_DELIVERTO_ARCH_V where PO_LINE_LOC_ID equals the sought value.

A second common pattern joins the view back to PO_HEADERS_ALL or PO_LINES_ALL on PO_HEADER_ID or PO_LINE_ID to enrich archived address data with current header attributes. Because the view already resolves the effective-dated person and the HR location, it is also suited to cXML ship-to payload generation and to reconciliation reports comparing ordered, cancelled, and net distributed quantities.