Results for “jai_ar_sup_hdrs_all”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The JAI_AR_SUP_HDRS_ALL table is a core transactional data object within the JA – Asia/Pacific Localizations product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores supplementary transaction header details associated with Oracle Receivables customer transactions. Its principal purpose is to capture the additional tax and statutory attributes required by Asia/Pacific localization requirements — particularly excise and supplementary invoicing amounts — that are not accommodated by the standard RA_CUSTOMER_TRX_ALL structure.

The table is owned by the JA schema and is documented as VALID in ETRM. From a Data Vault modeling perspective, the mined foreign-key structure suggests this object behaves as a link entity. It connects a Receivables transaction, a customer party, a customer site, a ledger, and an operating unit into a single localized supplementary record. This link classification is a heuristic suggestion based on the FK topology rather than a formally declared Oracle data model designation.

Key Information Stored

The table holds 28 documented columns. The most significant are outlined below.

• SUP_HDR_ID — Surrogate primary key, enforced by JAI_AR_SUP_HDRS_ALL_PK. This is the internal unique identifier for each supplementary header record.
• CUSTOMER_TRX_ID — Foreign key to RA_CUSTOMER_TRX_ALL; links the supplementary record to its parent Receivables transaction.
• SUPP_INV_TYPE and CUSTOMER_TRX_ID — Together form the business-key candidate JAI_AR_SUP_HDRS_ALL_UK1, the unique index defining the supplementary invoice type per transaction.
• SUPPLEMENTARY_NUM — The supplementary invoice or document number presented to the customer or tax authority.
• CUSTOMER_ID, CUSTOMER_SITE — Party and site references to HZ_PARTIES and HZ_PARTY_SITES.
• SET_OF_BOOKS_ID — Ledger reference to GL_LEDGERS, supporting multi-ledger reporting.
• ORG_ID — Operating unit reference to HR_ALL_ORGANIZATION_UNITS, enforcing multi-org security.
• TRX_DATE and SUPP_INV_DATE — Transaction date and supplementary invoice date.
• EXIST_NET_SALES_AMT, EXIST_EXCISE_AMT, EXIST_OTHER_AMT — Previously recorded net sales, excise, and other amounts.
• NEW_NET_SALES_AMT, NEW_EXCISE_AMT, NEW_OTHER_AMT — Revised amounts used to compute adjustments.
• EXCISE_DIFF_AMT and OTHER_DIFF_AMT — Calculated differences between existing and new values.
• CHOSEN_FOR_PROCESS, PROCESS_DATE, SUPP_INV_RAISED_IND, BATCH_ID — Workflow and processing control attributes governing supplementary invoice generation.
• Audit and concurrency: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, OBJECT_VERSION_NUMBER.

Common Use Cases and Queries

Typical usage centers on supplementary invoicing, excise tax reconciliation, and statutory reporting for Asia/Pacific localization deployments.

• Retrieving all supplementary headers for a given Receivables transaction:

  SELECT sup_hdr_id, supp_inv_type, supplementary_num,
         new_excise_amt, excise_diff_amt
  FROM   jai_ar_sup_hdrs_all
  WHERE  customer_trx_id = :p_customer_trx_id;

• Identifying records pending processing within an operating unit:

  SELECT sup_hdr_id, batch_id, supp_inv_date
  FROM   jai_ar_sup_hdrs_all
  WHERE  chosen_for_process = 'Y'
  AND    org_id = :p_org_id;

• Reconciling excise differences between existing and revised amounts at ledger level.
• Reporting supplementary invoice volumes and values by customer or site for tax filing.
• Joining to RA_CUSTOMER_TRX_ALL to produce combined standard and supplementary invoice extracts.

Because of multi-org partitioning, queries should generally filter on ORG_ID to respect operating unit security.

Related Objects

The table participates in several documented foreign-key relationships and is commonly joined with the following objects:

• RA_CUSTOMER_TRX_ALL — joined on CUSTOMER_TRX_ID; the parent transaction.
• HZ_PARTIES — joined on CUSTOMER_ID; the customer or party.
• HZ_PARTY_SITES — joined on CUSTOMER_SITE; the customer site.
• GL_LEDGERS — joined on SET_OF_BOOKS_ID; the accounting ledger.
• HR_ALL_ORGANIZATION_UNITS — joined on ORG_ID; the operating unit.

These relationships confirm the table's role as a localized supplementary link between Receivables, Trading Community (HZ), General Ledger, and organization structures.