Search Results retroactive_date




Overview
Explore in AI Chat

Overview

The PO_AP_RETROACTIVE_DIST_V view is a Purchasing (PO) module database object owned by the APPS schema and defined with VALID status in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to capture the purchase order distributions that are candidates for retroactive invoice adjustment. In other words, it surfaces the distribution lines for which Purchasing has flagged an intent to re-price already-invoiced receipts or commitments, typically following a supplier price change that must flow back through Payables.

Within the EBS reporting and integration layer, this view functions as a pre-built, business-filtered projection over core Purchasing entities. It eliminates the multi-table join logic a developer would otherwise assemble manually and exposes a stable, named interface for concurrent programs, custom reports, Oracle Discoverer workbooks, and third-party integrations that require a list of distributions eligible for invoice adjustment. Because it is a view rather than a table, it carries no storage of its own and always reflects the current transactional state of the underlying Purchasing tables.

Underlying Base Objects

According to the documented ETRM 12.2.2 metadata, the view is defined over the following referenced base objects, all accessed through APPS synonyms:

The view text joins PO_HEADERS_ALL to PO_LINES_ALL on PO_HEADER_ID, PO_LINES_ALL to PO_LINE_LOCATIONS_ALL on PO_LINE_ID, and PO_LINE_LOCATIONS_ALL to PO_DISTRIBUTIONS_ALL on LINE_LOCATION_ID. The effective PO_HEADER_ID is derived using a DECODE on SHIPMENT_TYPE: for BLANKET shipments the header comes directly from the distribution, otherwise the line's FROM_HEADER_ID is used when present, falling back to the distribution header. Only distributions whose INVOICE_ADJUSTMENT_FLAG is 'R' (retroactive price change pending) or 'E' (adjustment in error/exception state) are returned.

Key Columns

  • PO_HEADER_ID — effective purchasing document header, resolved for blanket and standard agreements.
  • PO_LINE_ID, LINE_LOCATION_ID, PO_DISTRIBUTION_ID — the line, shipment/schedule, and distribution identifiers that uniquely key the record.
  • VENDOR_ID — supplier associated with the document, sourced from PO_HEADERS_ALL.
  • INVOICE_ADJUSTMENT_FLAG — the decisive filter column; 'R' and 'E' denote adjustment-eligible distributions.
  • UNIT_PRICE — the line unit price that drives the retroactive re-pricing calculation.
  • PRICE_OVERRIDE — indicates whether a shipment-level price override applies.
  • RETROACTIVE_DATE — the date from which the retroactive price adjustment takes effect; this is the column most often cited when users search for "retroactive_date".
  • ORG_ID — operating unit identifier supporting multi-org security and filtering.

Common Use Cases and Queries

Typical usage includes reconciliation of retroactive price adjustments against Payables invoices, identifying distributions that require invoice re-pricing, and building exception reports for adjustments flagged 'E'. A representative query restricted to a single operating unit and a retroactive date window is:

  • SELECT po_header_id, po_line_id, line_location_id, po_distribution_id, vendor_id, invoice_adjustment_flag, unit_price, price_override, retroactive_date, org_id FROM apps.po_ap_retroactive_dist_v WHERE org_id = :p_org_id AND retroactive_date >= :p_from_date AND retroactive_date < :p_to_date ORDER BY retroactive_date;

Because RETROACTIVE_DATE originates in PO_LINE_LOCATIONS_ALL, the view is the preferred access path for reporting on retroactive pricing by shipment or schedule. All references should be schema-qualified as APPS and accessed under the appropriate operating unit context.