Search Results jai_retro_line_changes




Overview
Explore in AI Chat

Overview

The JAI_RETRO_LINE_CHANGES table is a core data repository within the Oracle E-Business Suite Asia/Pacific Localizations module (Product JA). Its primary function is to log and store retroactive changes made to transactional documents, specifically within the procurement domain. This table is critical for audit trails and compliance in regions requiring detailed tracking of post-facto adjustments to documents like purchase orders. It operates as a child table to the main transactional tables, capturing the delta between the original and revised states of document lines to support processes such as retroactive pricing or quantity adjustments and their subsequent impact on tax and accounting entries.

Key Information Stored

The table's structure is defined by its extensive foreign key relationships, which indicate the specific data points captured for each change record. The primary key is the unique LINE_CHANGE_ID. Each record stores identifiers linking it to the original document component being modified, including DOC_HEADER_ID, DOC_LINE_ID, and LINE_LOCATION_ID, which reference standard Purchase Order tables. To track the source of the change, it holds FROM_HEADER_ID and FROM_LINE_ID. The table also captures the item context (INVENTORY_ITEM_ID and ORGANIZATION_ID), supplier details (VENDOR_ID and VENDOR_SITE_ID), and the concurrent request (RETRO_REQUEST_ID) that processed the retroactive change. A self-referencing foreign key on SOURCE_LINE_CHANGE_ID allows for chaining or versioning of multiple changes to the same line.

Common Use Cases and Queries

The primary use case is generating audit reports for retroactive adjustments to purchase orders, which is essential for financial reconciliation and tax reporting in localized implementations. Support and development teams query this table to diagnose issues with the retroactive pricing process or to analyze the change history for a specific document. A typical diagnostic query would join to the standard PO tables to provide context:

  • SELECT rlc.line_change_id, poh.segment1 po_number, pol.line_num, rlc.retro_request_id
    FROM jai_retro_line_changes rlc,
    po_headers_all poh,
    po_lines_all pol
    WHERE rlc.doc_header_id = poh.po_header_id
    AND rlc.doc_line_id = pol.po_line_id
    AND poh.segment1 = '<PO_NUMBER>';

Another common pattern is to trace all changes spawned from a single retroactive concurrent request for performance or validation purposes, using the RETRO_REQUEST_ID column.

Related Objects

The JAI_RETRO_LINE_CHANGES table is centrally connected to several key EBS entities, as documented by its foreign key constraints.