Search Results jai_ar_sup_lines




Overview

JAI_AR_SUP_LINES is a transactional table owned by the JA (Asia/Pacific Localizations) schema in Oracle E-Business Suite, available in both 12.1.1 and 12.2.2. It stores supplementary transaction details for individual receivable line items together with the original invoice details that those lines originated from. The table is central to the JA localization requirement for capturing excise, tax, and pricing adjustments raised against specific invoice lines, most notably for India and other Asia/Pacific legislative regimes where a supplementary invoice must reference the original invoice line it corrects or supplements.

Within the ETRM metadata, the heuristic Data Vault classification for JAI_AR_SUP_LINES is a link. This classification reflects the fact that the table is primarily composed of foreign key relationships to customer transactions, customer transaction lines, tax categories, and supplementary change records. In a Data Vault model it would function as a link table connecting these business entities, with its measurable amounts and dates handled as link-level attributes or moved to a satellite.

Key Information Stored

The table contains 31 documented columns. Its surrogate primary key is defined by JAI_AR_SUP_LINES_PK on CUSTOMER_TRX_LINE_ID, which uniquely identifies each supplementary line record and is also a foreign key to RA_CUSTOMER_TRX_LINES_ALL. The most significant columns include:

Standard audit columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY, OBJECT_VERSION_NUMBER, INTERFACE_LINE_ATTRIBUTE2) are also present for concurrency control and interface traceability. CUSTOMER_TRX_LINE_ID serves as the natural business key in practice, since it corresponds one-to-one with the original invoice line.

Common Use Cases and Queries

JAI_AR_SUP_LINES supports supplementary invoice reporting, excise reconciliation, and audit of price or tax corrections on previously invoiced lines. A typical query joins the table to its parent lines and headers:

  • Listing all supplementary lines for a given supplementary transaction, returning LINE_NUMBER, INVENTORY_ITEM_ID, QUANTITY, OLD_SELLING_PRICE, NEW_SELLING_PRICE, and the three difference columns.
  • Reconciling excise liability by comparing EXIST_EXCISE_AMT against NEW_EXCISE_AMT and grouping by TAX_CATEGORY_ID.
  • Auditing mapping changes through PL_MAPPING_ID and AL_MAPPING_ID against JAI_AR_SUP_CHANGES_ALL.
  • Reporting original versus revised assessable values for statutory submissions using OLD_ASSESSABLE_VALUE and NEW_ASSESSABLE_VALUE.

Standard joins are JAI_AR_SUP_LINES.CUSTOMER_TRX_ID = RA_CUSTOMER_TRX_ALL.CUSTOMER_TRX_ID and JAI_AR_SUP_LINES.CUSTOMER_TRX_LINE_ID = RA_CUSTOMER_TRX_LINES_ALL.CUSTOMER_TRX_LINE_ID.

Related Objects

  • RA_CUSTOMER_TRX_ALL – parent header; joined on CUSTOMER_TRX_ID.
  • RA_CUSTOMER_TRX_LINES_ALL – parent line; joined on CUSTOMER_TRX_LINE_ID.
  • JAI_CMN_TAX_CTGS_ALL – tax category definitions; joined on TAX_CATEGORY_ID.
  • JAI_AR_SUP_CHANGES_ALL – supplementary change records; referenced twice via PL_MAPPING_ID and AL_MAPPING_ID.
  • JAI_AR_SUP_HEADERS (related JA supplementary header table) – header context for the supplementary transaction.
  • JAI_AR_TRX_LINES and related JA localization views that consume these line-level excise details.
  • AR interface and concurrent programs that populate supplementary invoices from original transaction data.