Search Results quantity_accepted




Overview
Explore in AI Chat

Overview

APPS.PO_SGD_MOD_LINELOCS_V is a PL/SQL-based reporting view in Oracle E-Business Suite Purchasing that exposes draft-modified purchasing document line-location (shipment/schedule) attribute changes. The suffix "SGD" denotes the Shipment/Goods-Delivery change data set, and the view is designed to present, in a normalized key/value form, the differences applied to line locations within a purchasing document draft. Rather than returning one row per shipment with fixed columns, the view pivots each modified attribute into its own row, carrying the primary key context (po_header_id, draft_id, po_line_id, line_location_id) alongside a col_name / col_value pair and an optional decoded col_desc.

Its role is primarily diagnostic and integration-oriented: it allows change-tracking reports, draft review screens, and downstream interfaces to enumerate exactly which shipment-level attributes were altered, and to compare draft values against the underlying line-location record. Because it surfaces values such as receiving_routing_id, tolerance settings, exception codes, and date fields, it is frequently consulted when auditing receiving configuration changes proposed in a draft.

Underlying Base Objects

The view is defined over three documented base objects:

  • PO_LINE_LOCATIONS_DRAFT_ALL (SYNONYM) — the primary source of shipment-level draft data. Columns such as shipment_num, ship_to_location_id, need_by_date, promised_date, receiving_routing_id, receive_close_tolerance, qty_rcv_tolerance, match_option, and the quantity/amount families (quantity, quantity_received, quantity_accepted, quantity_billed, amount, amount_received, amount_billed, amount_cancelled, amount_rejected, amount_accepted, amount_shipped) are drawn from this table.
  • MTL_UNITS_OF_MEASURE_TL (SYNONYM) — used by the inline DECODE to translate UNIT_MEAS_LOOKUP_CODE values into a language-specific unit of measure description via userenv('lang').
  • PO_GEN_DIFF_PKG (PACKAGE) — the Purchasing "generate difference" package that produces the modified-row key/value structure consumed by this view.

The outer query projects pk1_value through pk5_value (po_header_id, draft_id, po_line_id, line_location_id, and a null fifth key), col_name, col_value, and col_desc, giving each modified attribute a stable five-part addressing scheme.

Key Columns

  • pk1_value – pk5_value — the composite identifier of the modified shipment: po_header_id, draft_id, po_line_id, line_location_id, and null.
  • col_name — the name of the modified attribute (for example, UNIT_MEAS_LOOKUP_CODE, receiving_routing_id, need_by_date).
  • col_value — the character form of the modified value, cast via to_char for dates and numerics.
  • col_desc — a decoded description; populated for UNIT_MEAS_LOOKUP_CODE from MTL_UNITS_OF_MEASURE_TL, otherwise null.
  • receiving_routing_id — exposed as a to_char value in the inner projection, identifying the receiving routing associated with the shipment; the term the user searched on. It governs the receiving flow applied at receipt.
  • receipt_days_exception_code, qty_rcv_exception_code, allow_substitute_receipts_flag, enforce_ship_to_location_code, accrue_on_receipt_flag — receiving-control flags and exception codes projected onto the view.
  • need_by_date, promised_date, last_accept_date, clm_period_perf_start_date, clm_period_perf_end_date, days_early_receipt_allowed, days_late_receipt_allowed — scheduling and receipt-window attributes.

Common Use Cases and Queries

Typical scenarios include auditing draft shipment changes before submission, validating receiving configuration (routing, tolerances, exception codes), and feeding interfaces that reconcile draft to base line locations.

  • List all modified shipment attributes for a given draft:
SELECT pk1_value po_header_id, pk2_value draft_id, pk3_value po_line_id,
       pk4_value line_location_id, col_name, col_value, col_desc
FROM   apps.po_sgd_mod_linelocs_v
WHERE  pk2_value = :draft_id;
  • Isolate receiving routing changes for a shipment:
SELECT pk3_value po_line_id, pk4_value line_location_id, col_value receiving_routing_id
FROM   apps.po_sgd_mod_linelocs_v
WHERE  col_name = 'receiving_routing_id';
  • Join by line_location_id back to PO_LINE_LOCATIONS_ALL to compare draft versus base values, and use col_desc for readable unit-of-measure output when col_name = 'UNIT_MEAS_LOOKUP_CODE'.