Search Results lead_time_unit




Overview
Explore in AI Chat

Overview

PO_RFQ_LINE_LOCATIONS_PRINT is an APPS-owned database view in the Oracle E-Business Suite Purchasing (PO) module that provides a flattened, print-oriented projection of Request for Quotation (RFQ) line location data. Rather than exposing the raw transactional structure of the purchasing tables, the view consolidates shipment scheduling, pricing, freight, terms, tax, ship-to address, and descriptive flexfield information into a single denormalized result set suitable for report layouts, concurrent program output, and printed RFQ documents. The view is documented as VALID and is defined over several base tables and supporting lookups, joining them with outer joins so that RFQ lines do not disappear when optional reference data is missing. It is registered in ETRM for release 12.2.2 (and remains applicable to 12.1.1), owned by the APPS schema, and is typically referenced by Purchasing RFQ printing and inquiry programs. Users searching for lead_time_unit should note that this attribute is exposed directly as the LEAD_TIME_UNIT column, carried forward from the underlying PO_LINE_LOCATIONS record alongside the related LEAD_TIME column.

Underlying Base Objects

The view is defined over the following documented base objects:

  • PO_LINE_LOCATIONS (alias PLL) — the driving table, supplying shipment-level attributes such as shipment number, type, quantity, price override, lead time, lead time unit, discount, and the key identifiers PO_HEADER_ID, PO_LINE_ID, LINE_LOCATION_ID, SHIP_TO_LOCATION_ID, and ORG_ID.
  • PO_HEADERS_ALL (alias POH) — joined on PO_HEADER_ID; the WHERE clause restricts rows to documents whose TYPE_LOOKUP_CODE is 'RFQ', and PLL.SHIPMENT_TYPE must also be 'RFQ'.
  • HR_LOCATIONS (alias HRL) — outer-joined on SHIP_TO_LOCATION_ID to supply address components.
  • AP_TERMS (alias APT) — outer-joined on TERMS_ID to supply the payment terms name.
  • PO_LOOKUP_CODES (aliases PLC1, PLC2) — outer-joined for FOB and FREIGHT TERMS displayed field values.
  • ORG_FREIGHT (alias OFC) — outer-joined on freight code and organization ID to resolve the ship-via value, with NVL falling back to the stored lookup code.

Additional referenced objects in the metadata include FND_GLOBAL and HR_GENERAL packages and a synonym to AP_TERMS. The pervasive use of outer joins (denoted by the (+) operator) ensures the print output remains complete even when optional address, terms, or freight data is absent.

Key Columns

  • SHIPMENT_NUM, SHIPMENT_TYPE — identify the RFQ shipment line; SHIPMENT_TYPE is constrained to 'RFQ'.
  • QUANTITY_ORDERED / QUANTITY — the requested quantity for the shipment.
  • PRICE_OVERRIDE, DISCOUNT — pricing adjustments carried from the line location.
  • LEAD_TIME, LEAD_TIME_UNIT — the negotiated lead time value and its unit of measure; directly relevant to the lead_time_unit search term.
  • START_DATE, END_DATE — effective date range for the shipment.
  • SHIP_VIA, FOB, FREIGHT_TERMS — resolved freight and FOB descriptive fields via ORG_FREIGHT and PO_LOOKUP_CODES.
  • PAYMENT_TERMS — the AP_TERMS name.
  • SHIP_ADDRESS_LINE1..SHIP_STATE_PROVINCE, SHIP_POSTAL_CODE, SHIP_COUNTRY — ship-to address fields from HR_LOCATIONS, with state resolved via NVL(HRL.REGION_2, HRL.REGION_1).
  • TAXABLE_FLAG — indicates taxability of the shipment.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield context and segments.
  • PO_HEADER_ID, PO_LINE_ID, LINE_LOCATION_ID, SHIP_TO_LOCATION_ID, ORG_ID — key identifiers enabling downstream joins and reporting.

Common Use Cases and Queries

The view is most commonly consumed by RFQ print programs and custom reports requiring a self-contained row per RFQ shipment. A typical query retrieving lead time details is:

  • SELECT shipment_num, quantity, lead_time, lead_time_unit, ship_via, payment_terms FROM po_rfq_line_locations_print WHERE po_header_id = :header_id;
  • SELECT shipment_num, ship_via, ship_city, ship_country, lead_time, lead_time_unit FROM po_rfq_line_locations_print WHERE org_id = :org_id ORDER BY shipment_num;
  • SELECT shipment_num, lead_time, lead_time_unit FROM po_rfq_line_locations_print WHERE lead_time_unit = :unit AND shipment_type = 'RFQ';

Because the view is restricted to RFQ shipment types, callers need not add document-type filters. It supports printed quotation comparisons, supplier response review, and integrations that extract RFQ shipment schedules including lead time and freight terms.