Search Results jai_ar_sup_changes_all




Overview

JAI_AR_SUP_CHANGES_ALL is a transactional mapping table owned by the JA (Asia/Pacific Localizations) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to store mapping information for the customer and customer site combinations that are considered during the supplemental invoice (supp inv) process, a localization feature used primarily for regional tax and statutory reporting in Asia/Pacific deployments. The table effectively records which party/site pairing is captured for a given ledger, operating unit, and batch run, together with the attributes required to reconcile those records against downstream supplemental invoice, line, and tax tables.

Under the heuristic Data Vault classification derived from its foreign key structure, this object is hub-leaning. It carries a single-column surrogate primary key, JAI_AR_SUP_CHANGES_ALL_PK on MAPPING_ID, and functions as a central reference point from which multiple dependent detail tables hang. In a Data Vault model it would most naturally be modeled as a hub (the mapping identity) with attached satellites for the temporal and conversion attributes, and links to customer, site, ledger, and organization hubs.

Key Information Stored

The table is documented with 19 columns. The most significant are:

The business-key candidate is effectively the composite of SET_OF_BOOKS_ID, ORG_ID, CUSTOMER_ID, SITE_USE_ID, and the effective dates; however, only MAPPING_ID is formally backed by a unique index in the documented schema.

Common Use Cases and Queries

Typical usage centers on diagnosing and reporting supplemental invoice mappings. A common pattern joins the header mapping to its detail tables:

  • Mapping audit by ledger and operating unit — filter on SET_OF_BOOKS_ID, ORG_ID, and PROCESS_DATE to list all mappings processed in a period.
  • Point-in-time reconstruction — restrict on EFFECTIVE_FROM_DATE <= :as_of AND (EFFECTIVE_TO_DATE IS NULL OR EFFECTIVE_TO_DATE > :as_of) to reproduce the mapping state at a prior date.
  • Batch reconciliation — group by BATCH_ID, including the self-referenced parent rows, to verify completeness of a supplemental run.
  • Customer/site drill-down — join CUSTOMER_ID to HZ_PARTIES and SITE_USE_ID to HZ_PARTY_SITES to report which parties were included.
  • Rate verification — compare CONVERSION_RATE against GL daily rates for the PROCESS_DATE.

Sample SQL: SELECT c.mapping_id, c.customer_id, c.site_use_id, c.conversion_rate FROM jai_ar_sup_changes_all c WHERE c.set_of_books_id = :sob AND c.org_id = :org AND c.process_date BETWEEN :from AND :to ORDER BY c.batch_id, c.mapping_id;

Related Objects

The FK structure identifies the following significant dependencies:

  • JAI_AR_SUP_INV_T — references this table via MAPPING_ID; holds supplemental invoice header detail.
  • JAI_AR_SUP_LINES — references this table through both PL_MAPPING_ID and AL_MAPPING_ID, linking line-level records back to their mappings.
  • JAI_AR_SUP_TAXES — references MAPPING_ID; stores tax detail attributed to each mapping.
  • JAI_AR_TRX_SUP_INV_T — references MAPPING_ID; the transaction-level supplemental invoice table.
  • GL_LEDGERS — referenced via SET_OF_BOOKS_ID.
  • HR_ALL_ORGANIZATION_UNITS — referenced via ORG_ID for operating unit context.
  • HZ_PARTIES — referenced via CUSTOMER_ID.
  • HZ_PARTY_SITES — referenced via SITE_USE_ID.
  • JAI_AR_SUP_CHANGES_ALL (self-referencing) — BATCH_ID links child mappings to their batch parent.