Search Results jai_ar_sup_inv_t




Overview
Explore in AI Chat

Overview

JAI_AR_SUP_INV_T is a transient staging table owned by the JA schema (Asia/Pacific Localizations) within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores temporary information about supplier invoices used by the India generation process for the Suggestive Supplementary Report. The table acts as an intermediate holding area where receipt and invoice data are correlated before the report is produced, and its contents are typically populated and consumed within the report run cycle rather than retained as a permanent transactional record.

From a data modeling perspective, the object carries a heuristic Data Vault classification of link. This classification is derived from its foreign key structure, which references multiple distinct business entities — the receivable transaction (RA_CUSTOMER_TRX_ALL), the supplementary change record (JAI_AR_SUP_CHANGES_ALL), the ledger (GL_LEDGERS), the trading partner (HZ_PARTIES), the operating unit (HR_ALL_ORGANIZATION_UNITS), and the customer site (HZ_PARTY_SITES). The table therefore functions as a junction that associates these entities in the context of a supplementary invoice computation, rather than acting as a hub of its own or as a descriptive satellite.

Key Information Stored

The documented physical schema contains 18 columns in the 12.2.2 ETRM repository. The most significant columns are the following:

  • CUSTOMER_TRX_ID — foreign key to RA_CUSTOMER_TRX_ALL; identifies the receivable transaction against which supplementary information is generated.
  • MAPPING_ID — foreign key to JAI_AR_SUP_CHANGES_ALL; ties the staging row to the supplementary change mapping record.
  • SET_OF_BOOKS_ID — foreign key to GL_LEDGERS; identifies the ledger context of the transaction.
  • CUSTOMER_ID — foreign key to HZ_PARTIES; the party (customer) associated with the invoice.
  • CUSTOMER_SITE — foreign key to HZ_PARTY_SITES; the specific party site used on the transaction.
  • ORG_ID — foreign key to HR_ALL_ORGANIZATION_UNITS; the operating unit that owns the record, enforcing multi-org security.
  • TRX_DATE and EFFECTIVE_DATE — transaction and effective dates used for period selection and reporting scope.
  • INTERFACE_HEADER_CONTEXT — the descriptive flexfield context for the interface header.
  • INTERFACE_HEADER_ATTRIBUTE1, ATTRIBUTE6, ATTRIBUTE7 — descriptive flexfield segments carrying supplementary invoice attributes.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.
  • OBJECT_VERSION_NUMBER — optimistic locking column used by the framework.

The ETRM metadata does not document a single-column surrogate primary key or a named unique index for this table; the identifying relationships are carried through the foreign key columns listed above, with CUSTOMER_TRX_ID and MAPPING_ID serving as the principal business-key candidates for linking a staging row to its source documents.

Common Use Cases and Queries

Because the table is populated for the Suggestive Supplementary Report, typical use is to join the staged rows back to the originating sales transaction and the supplementary change record. A representative query pattern is:

  • Join JAI_AR_SUP_INV_T to RA_CUSTOMER_TRX_ALL on CUSTOMER_TRX_ID to retrieve the invoice number, transaction date, and bill-to information for a report column.
  • Join to JAI_AR_SUP_CHANGES_ALL on MAPPING_ID to resolve the supplementary change that triggered inclusion of the row.
  • Join to HZ_PARTIES on CUSTOMER_ID and to HZ_PARTY_SITES on CUSTOMER_SITE to render the customer name and site for the report output.
  • Filter on ORG_ID to respect operating unit security and on SET_OF_BOOKS_ID to scope the report to a single ledger.
  • Use TRX_DATE and EFFECTIVE_DATE to constrain reporting to a fiscal period.

Operational diagnostics frequently involve checking whether a staging run produced rows for a given CUSTOMER_TRX_ID, or whether the WHO audit columns indicate a stale or failed population. Because the table is a temporary container, data volume can be unexpectedly large during report execution and should be validated rather than assumed.

Related Objects

The following related objects are documented through the foreign key structure of JAI_AR_SUP_INV_T:

  • RA_CUSTOMER_TRX_ALL — referenced via CUSTOMER_TRX_ID; the receivable transaction header.
  • JAI_AR_SUP_CHANGES_ALL — referenced via MAPPING_ID; the supplementary change mapping record.
  • GL_LEDGERS — referenced via SET_OF_BOOKS_ID; defines the ledger and accounting context.
  • HZ_PARTIES — referenced via CUSTOMER_ID; the trading partner master.
  • HZ_PARTY_SITES — referenced via CUSTOMER_SITE; the customer site used on the document.
  • HR_ALL_ORGANIZATION_UNITS — referenced via ORG_ID; the operating unit enforcing multi-org access.

These relationships confirm the table's role as a link object and define the join paths used by the Suggestive Supplementary Report and any downstream analysis of India localization supplementary invoicing.