Results for “tax_invoice_no”

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

Overview

JAI_AR_TRXS is a localization table owned by the JA (Asia/Pacific Localizations) schema within Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. Its documented purpose is to store supplementary information about Oracle Receivables invoices that the standard RA_CUSTOMER_TRX_ALL table does not capture, specifically the statutory and fiscal attributes required by Asia/Pacific tax regimes. In practice the table functions as a companion (extension) record to the Receivables transaction header, keyed one-to-one on CUSTOMER_TRX_ID.

From a Data Vault modeling perspective, the FK topology mined from the schema is satellite-leaning: the table's primary key is a single foreign key (CUSTOMER_TRX_ID) pointing to RA_CUSTOMER_TRX_ALL, and the remaining columns are predominantly descriptive attributes (amounts, flags, tax document numbers and dates). This suggests treating JAI_AR_TRXS as a satellite hanging off the Receivables transaction hub, rather than as an independent hub or a link table.

Key Information Stored

The table carries 34 documented columns. The surrogate/business key is CUSTOMER_TRX_ID, enforced by the JAI_AR_TRXS_PK primary key; it is simultaneously a foreign key to RA_CUSTOMER_TRX_ALL, making it the natural join path back to the base invoice. The most significant attributes are:

• CUSTOMER_TRX_ID – Primary key and link to the Receivables invoice header.
• TRX_NUMBER – The invoice number, retained locally for reporting convenience.
• LEGAL_ENTITY_ID – Legal entity that issued the invoice (FK to FV_LEGAL_ENTITIES); central to statutory reporting.
• SET_OF_BOOKS_ID – Ledger context for the transaction (FK to GL_LEDGERS).
• ORGANIZATION_ID and LOCATION_ID – Operating unit/organization and location identifiers (FKs to HR_ALL_ORGANIZATION_UNITS and HR_LOCATIONS_ALL).
• BATCH_SOURCE_ID – Source of the invoice batch (FK to RA_BATCH_SOURCES_ALL).
• TAX_INVOICE_NO, VAT_INVOICE_NO, VAT_INVOICE_DATE, GST_INVOICE_NO, GST_INVOICE_DATE, ST_INV_NUMBER – Statutory tax document identifiers and dates for VAT, GST and sales tax reporting.
• TOTAL_AMOUNT, LINE_AMOUNT, TAX_AMOUNT – Denormalized amount snapshots used by localization reports.
• COMPLETE_FLAG, ONCE_COMPLETED_FLAG, UPDATE_RG_FLAG, UPDATE_RG23D_FLAG – Processing/status flags controlling tax report generation.

Standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and OBJECT_VERSION_NUMBER provide audit and optimistic-locking support.

Common Use Cases and Queries

The principal use case is statutory tax reporting across Asia/Pacific legislations, where invoice-level VAT/GST document numbers must be reconciled against Receivables data. A typical join retrieves the localized attributes alongside the base invoice:

• Reconciling tax invoice numbers to receivables transactions: SELECT t.trx_number, j.vat_invoice_no, j.gst_invoice_no, j.tax_amount FROM ra_customer_trx_all t, jai_ar_trxs j WHERE t.customer_trx_id = j.customer_trx_id;
• Reporting by legal entity and ledger: filter on LEGAL_ENTITY_ID and SET_OF_BOOKS_ID to produce entity-level tax summaries.
• Identifying incomplete localization processing: query rows where COMPLETE_FLAG is not set to drive exception reports.
• Auditing tax amounts versus Receivables headers by comparing TOTAL_AMOUNT and TAX_AMOUNT to RA_CUSTOMER_TRX_ALL totals.

Related Objects

JAI_AR_TRXS is tightly coupled to the following objects, with the join columns shown:

• RA_CUSTOMER_TRX_ALL – parent invoice header (JAI_AR_TRXS.CUSTOMER_TRX_ID = RA_CUSTOMER_TRX_ALL.CUSTOMER_TRX_ID).
• HR_ALL_ORGANIZATION_UNITS – via ORGANIZATION_ID.
• HR_LOCATIONS_ALL – via LOCATION_ID.
• RA_BATCH_SOURCES_ALL – via BATCH_SOURCE_ID.
• GL_LEDGERS – via SET_OF_BOOKS_ID.
• FV_LEGAL_ENTITIES – via LEGAL_ENTITY_ID.
• JAI_AR_TRX_INS_HDRS_T and JAI_AR_TRX_INS_LINES_T – localization interface tables that reference JAI_AR_TRXS.CUSTOMER_TRX_ID, used to load invoice header and line localization data.

Together these relationships confirm the table's role as a localization satellite anchored to the core Receivables transaction header.