Search Results lookup_code




Overview
Explore in AI Chat

Overview

PO_LINE_LOCATIONS_CHANGE_PRINT is an APPS-owned database view in the Oracle E-Business Suite Purchasing (PO) module. It exposes shipment and schedule-level purchasing data drawn from the archived copy of purchase order line locations, joined to header, ship-to location, territory, and lookup metadata. The view is marked "Retrofitted," indicating it was migrated forward to support Oracle EBS 12.1.1 and 12.2.2 compatibility. Its name and column set suggest it is used primarily for change-order printing and audit reporting: it presents the shipment attributes (number, revision, type, promised date, quantities, price overrides, cancellation details, and descriptive flexfield context) needed to render a printed record of changes to a purchase order shipment.

Because the view filters on NVL(PLL.LATEST_EXTERNAL_FLAG, 'N') = 'Y', it reports only the latest externally visible version of each archived shipment, which is the appropriate scope for supplier-facing or change-notification output.

Underlying Base Objects

Per the documented ETRM 12.2.2 metadata, the view is defined over the following objects:

  • PO_LINE_LOCATIONS_ARCHIVE (synonym) — the driving table, aliased PLL, supplying shipment quantities, dates, flags, amounts, and DFF attributes.
  • PO_HEADERS_ALL (synonym) — aliased POH, joined on PO_HEADER_ID to confirm the header context.
  • PO_HR_LOCATIONS (view) — aliased HRL, supplying ship-to address components; outer-joined on LOCATION_ID = SHIP_TO_LOCATION_ID.
  • FND_TERRITORIES_TL (synonym) — aliased FTE, resolving the country to a translated territory short name, language-matched to USERENV('LANG').
  • FND_LOOKUP_VALUES (synonym, referenced three times as FCL1, FCL2, FCL3) — resolving province/region codes using lookup types such as <country>_PROVINCE.
  • FND_GLOBAL (package) and HR_GENERAL (package) — invoked for lookup security group resolution and related session context.

Key Columns

Common Use Cases and Queries

The view supports change-order print programs, shipment audit extracts, and reporting that requires resolved ship-to address and region text rather than raw lookup codes. Because the user searched for lookup_code, note that the region resolution depends on FCL.LOOKUP_CODE in the underlying join; the view exposes the resolved meaning rather than the raw code, so a query needing the code itself must look to FND_LOOKUP_VALUES directly. A typical query:

  • SELECT shipment_num, revision_num, quantity, nvl(promised_date, need_by_date) eff_date, town_or_city, region, territory_short_name
  • FROM apps.po_line_locations_change_print
  • WHERE org_id = :org_id AND po_header_id = :header_id;

Analysts auditing cancellations often filter on cancel_flag = 'Y' and aggregate quantity_cancelled by header. For address validation, the outer joins mean shipments without a valid ship-to still return, with address columns null.