Results for “jai_ar_trx_lines_pk”

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

Overview

JAI_AR_TRX_LINES is a transaction-line extension table owned by the JA schema and delivered as part of the Asia/Pacific Localizations (Oracle E-Business Suite, releases 12.1.1 and 12.2.2). It stores localization-specific information for receivable transaction lines, complementing the base Oracle Receivables line structure with attributes required for statutory tax and invoicing compliance across Asia/Pacific geographies — excise, VAT, GST, and region-specific form reporting.

Its documented role is to persist transaction-line detail that the standard Oracle Receivables model does not natively accommodate. The table is tightly coupled to the core AR transaction tables through foreign keys and shares the primary key column CUSTOMER_TRX_LINE_ID with RA_CUSTOMER_TRX_LINES_ALL.

Under a heuristic Data Vault classification inferred from its foreign-key topology, this table is best modeled as a link. It joins a receivable transaction line, its parent transaction header, and the common tax category reference into a single associative record. This classification should be treated as a modeling suggestion rather than an authoritative designation, since the table also carries a substantial descriptive payload (58 documented columns) that behaves in a satellite-like manner.

Key Information Stored

The physical schema in ETRM 12.2.2 documents 58 columns. The most significant include:

• CUSTOMER_TRX_LINE_ID — surrogate primary key, defined by the unique index JAI_AR_TRX_LINES_PK. It is also the documented business-key candidate and the join to the base AR line table.
• CUSTOMER_TRX_ID — identifies the parent transaction header in RA_CUSTOMER_TRX_ALL.
• LINE_NUMBER, DESCRIPTION, INVENTORY_ITEM_ID — line identification and item reference.
• QUANTITY, UNIT_CODE, UNIT_SELLING_PRICE — pricing and unit-of-measure detail.
• LINE_AMOUNT, TAX_AMOUNT, TOTAL_AMOUNT — monetary breakdown at line level.
• TAX_CATEGORY_ID — foreign key to JAI_CMN_TAX_CTGS_ALL, driving tax determination.
• ASSESSABLE_VALUE, VAT_ASSESSABLE_VALUE, GST_ASSESSABLE_VALUE — assessable bases for VAT and GST computation.
• EXCISE_INVOICE_NO, EXCISE_INVOICE_DATE, PREPRINTED_EXCISE_INV_NO — excise invoicing attributes.
• VAT_EXEMPTION_FLAG, VAT_EXEMPTION_TYPE, VAT_EXEMPTION_DATE, VAT_EXEMPTION_REFNO — VAT exemption tracking.
• GST_INVOICE_NO, GST_INVOICE_DATE — GST invoice references.
• AR3_FORM_NO, AR3_FORM_DATE — region-specific statutory form data.
• INTERFACE_FLAG, INTERFACE_EVENT — interface processing state.
• Standard WHO audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical reporting retrieves localization tax and invoicing detail per transaction line. A representative join pattern:

• Reconcile localization line attributes against base AR lines using CUSTOMER_TRX_LINE_ID.
• Report assessable values and tax amounts by tax category.
• Extract excise, VAT exemption, and GST invoicing detail for statutory filings.
• Identify lines pending interface processing via INTERFACE_FLAG.

A common query selects CUSTOMER_TRX_LINE_ID, LINE_AMOUNT, TAX_AMOUNT, ASSESSABLE_VALUE, and TAX_CATEGORY_ID, joining RA_CUSTOMER_TRX_LINES_ALL on CUSTOMER_TRX_LINE_ID and RA_CUSTOMER_TRX_ALL on CUSTOMER_TRX_ID, filtered by GL_DATE or LINE_NUMBER.

Related Objects

• RA_CUSTOMER_TRX_LINES_ALL — joined on CUSTOMER_TRX_LINE_ID; supplies base line data.
• RA_CUSTOMER_TRX_ALL — joined on CUSTOMER_TRX_ID; supplies transaction header context.
• JAI_CMN_TAX_CTGS_ALL — joined on TAX_CATEGORY_ID; provides tax category definitions.
• Oracle Receivables transaction APIs that populate AR lines, which this table extends for localization processing.

Together these relationships establish JAI_AR_TRX_LINES as the localization extension point for receivable transaction lines in the JA product family.