Search Results qty_rcv_tolerance




Overview
Explore in AI Chat

Overview

APPS.PO_SGD_LINELOCS_V is a reporting and integration view in Oracle E-Business Suite Purchasing that exposes the shipment- and location-level attributes of purchase order lines in a normalized, name/value (entity-attribute-value) format. The view serves the Oracle "SGD" (Secured Generic Data / supplementary data) framework used by the ETRM and related tooling to present descriptive, editable, and auditable attributes of purchasing documents without requiring a dedicated column-to-attribute mapping in the consuming application. Rather than returning a conventional row-per-shipment result set, PO_SGD_LINELOCS_V projects each shipment attribute as an individual row consisting of a set of entity key columns and a paired column name and value.

This design allows generic consumers—such as the ETRM comparison, audit, and approval engines—to treat line-location fields uniformly, irrespective of their underlying data types. Numeric, date, and coded values are cast to character strings, and coded lookups can be resolved to their translated descriptions within the same view via inline scalar subqueries.

Underlying Base Objects

The ETRM metadata for this view documents the following referenced base objects:

  • PO_LINE_LOCATIONS_ALL (synonym) — the primary transactional source of confirmed purchase order shipment and distribution scheduling information.
  • PO_LINE_LOCATIONS_DRAFT_ALL (synonym) — holds draft (unapproved) line-location records; the view reconciles the draft and non-draft sources and defaults a null draft identifier to -1.
  • MTL_UNITS_OF_MEASURE_TL (synonym) — provides the translated unit-of-measure description for the UNIT_MEAS_LOOKUP_CODE attribute.
  • PO_GEN_DIFF_PKG (package) — the Purchasing package underpinning the generic attribute (SGD) extraction and formatting logic.

Because both the confirmed and draft line-location tables are referenced, the view supports attribute inspection for documents in progress as well as those already approved. The entity key columns derived from these objects (PO_HEADER_ID, DRAFT_ID, PO_LINE_ID, LINE_LOCATION_ID) preserve the document hierarchy: header, line, and shipment.

Key Columns

The view exposes a fixed set of entity key columns plus a generic attribute pair:

  • PK1_VALUE (PO_HEADER_ID), PK2_VALUE (DRAFT_ID), PK3_VALUE (PO_LINE_ID), PK4_VALUE (LINE_LOCATION_ID) — the composite identifier locating the attribute within the purchasing document hierarchy. PK5_VALUE is reserved and returned as null.
  • COL_NAME — the name of the shipment attribute being returned (for example, RECEIVING_ROUTING_ID, NEED_BY_DATE, QUANTITY, RECEIVE_CLOSE_TOLERANCE).
  • COL_VALUE — the attribute value as a character string; numeric and date attributes are converted using TO_CHAR.
  • COL_DESC — an optional decoded description. It is populated only for UNIT_MEAS_LOOKUP_CODE, where the unit of measure is translated via MTL_UNITS_OF_MEASURE_TL filtered by USERENV('LANG').

Attributes surfaced from the line-location source include shipment number, ship-to location, need-by and promised dates, receiving routing ID, receiving and invoice tolerances, receipt and quantity exception codes, substitute receipt and accrual flags, match option, and the full set of quantity and amount measures (ordered, received, accepted, rejected, billed, cancelled, shipped).

Common Use Cases and Queries

The principal use case is retrieving a specific shipment attribute for a known line location, most commonly RECEIVING_ROUTING_ID, which governs the routing applied during receipt of the shipment.

SELECT pk1_value po_header_id,
       pk3_value po_line_id,
       pk4_value line_location_id,
       col_name,
       col_value
FROM   apps.po_sgd_linelocs_v
WHERE  col_name = 'RECEIVING_ROUTING_ID'
AND    pk4_value = :line_location_id;

To obtain every attribute for a shipment in a pivoted, human-readable form, consumers aggregate COL_NAME/COL_VALUE pairs. A typical query pattern is to filter by header and line to compare draft against approved shipments:

SELECT col_name, col_value
FROM   apps.po_sgd_linelocs_v
WHERE  pk1_value = :po_header_id
AND    pk2_value = -1
ORDER  BY col_name;

Because the view returns translated descriptions where applicable, it is also well suited to reporting and audit extracts in which coded values must be presented in the user's language. Analysts should note that all values are returned as text, so numeric or date filtering must be performed on the base tables or with explicit conversions.