Results for “insert_update_flag”

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

Overview

JAI_AR_TRX_INS_LINES_T is a transaction table owned by the JA schema (Asia/Pacific Localizations) in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It stores tax records that are generated from Oracle Receivables invoice activity. Per the ETRM documentation, the table holds tax records after AutoInvoice processing and after a manual invoice is saved, positioning it as a staging and detail repository for India/Asia-Pacific localizations taxation, including VAT and related line-level tax attributes. It functions alongside the Oracle Receivables transaction tables and the JAI common tax structures to preserve localization-specific tax detail that is not carried in the standard RA_CUSTOMER_TRX_LINES_ALL model.

Based on the FK topology supplied in the metadata, JAI_AR_TRX_INS_LINES_T can be modeled heuristically as a link (Data Vault classification: link). It records the association between Receivables transaction lines, localizations tax definitions, accounting flexfield combinations, ledgers, and operating units, and therefore behaves as an intersection of multiple business keys rather than a standalone hub or a pure descriptive satellite.

Key Information Stored

The table is documented with 28 columns in ETRM 12.2.2. The following are the most significant:

• CUSTOMER_TRX_ID — identifies the Receivables transaction header; foreign key to JAI_AR_TRXS.
• CUSTOMER_TRX_LINE_ID — identifies the Receivables transaction line; foreign key to RA_CUSTOMER_TRX_LINES_ALL.
• LINK_TO_CUST_TRX_LINE_ID — secondary link to RA_CUSTOMER_TRX_LINES_ALL, used to relate a tax line back to its associated source line or adjustment.
• VAT_TAX_ID — the applicable localization tax definition; foreign key to JAI_CMN_TAXES_ALL.
• TAX_RATE — the rate applied to the transaction line for the tax record.
• AMOUNT and ACCTD_AMOUNT — the entered and accounted tax amounts, respectively; EXTENDED_AMOUNT holds the extended line value.
• CODE_COMBINATION_ID — the accounting flexfield combination to which the tax is posted; foreign key to GL_CODE_COMBINATIONS.
• SET_OF_BOOKS_ID — the ledger in which the tax is accounted; foreign key to GL_LEDGERS.
• ORG_ID — the operating unit owning the record; foreign key to HR_ALL_ORGANIZATION_UNITS.
• LINE_NUMBER, LINE_TYPE, UOM_CODE — line sequencing and categorization attributes.
• GL_DATE — the accounting date for the tax record.
• INTERFACE_FLAG, INSERT_UPDATE_FLAG, ERROR_FLAG, ERR_MESG, SOURCE — processing controls indicating whether the row has been interfaced, whether it is an insert or update, and whether posting produced errors.
• Standard WHO audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — plus OBJECT_VERSION_NUMBER for optimistic locking.
• PADDR and CUST_TRX_LINE_SALES_REP_ID provide localization address and sales representative context.

The ETRM metadata does not document a single-column surrogate primary key or unique index for this table; the business key is therefore best approximated by the combination of CUSTOMER_TRX_ID, CUSTOMER_TRX_LINE_ID, VAT_TAX_ID, and ORG_ID/SET_OF_BOOKS_ID. CUSTOMER_TRX_LINE_ID and CUSTOMER_TRX_ID serve as the principal business-key candidates because all seven documented foreign keys anchor on these and the ledger/organization columns.

Common Use Cases and Queries

Typical usage centers on reconciliation and reporting of localized tax on Receivables transactions: verifying that tax lines produced after AutoInvoice or manual invoice save carry the correct VAT code and rate, confirming successful posting to GL via CODE_COMBINATION_ID, and diagnosing interface or posting errors using ERROR_FLAG and ERR_MESG.

A representative query joining the transaction line and tax definition is:

• SELECT t.customer_trx_id, t.customer_trx_line_id, t.vat_tax_id, t.tax_rate, t.amount, t.acctd_amount, t.gl_date FROM jai_ar_trx_ins_lines_t t WHERE t.org_id = :org_id AND t.gl_date BETWEEN :from_date AND :to_date;
• Join to JAI_CMN_TAXES_ALL on VAT_TAX_ID to retrieve the tax name and description for statutory reports.
• Filter on INTERFACE_FLAG or ERROR_FLAG to isolate rows pending interface or rejected by validation.

Common reporting scenarios include VAT/GST summary by tax code and period, tax payable reconciliation against GL balances using SET_OF_BOOKS_ID and CODE_COMBINATION_ID, and exception reports for rows where ERR_MESG is not null.

Related Objects

The documented foreign keys establish the following principal dependencies:

• JAI_AR_TRXS — joined on CUSTOMER_TRX_ID; the parent localization transaction record.
• RA_CUSTOMER_TRX_LINES_ALL — joined on CUSTOMER_TRX_LINE_ID and, separately, on LINK_TO_CUST_TRX_LINE_ID; the standard Receivables transaction lines.
• JAI_CMN_TAXES_ALL — joined on VAT_TAX_ID; the localization tax definition master.
• GL_CODE_COMBINATIONS — joined on CODE_COMBINATION_ID; the accounting flexfield combination for the tax posting.
• GL_LEDGERS — joined on SET_OF_BOOKS_ID; the ledger context (12.2.2 general ledger reference).
• HR_ALL_ORGANIZATION_UNITS — joined on ORG_ID; the operating unit that owns the tax record.

Downstream, the table feeds localization tax reporting and GL transfer processes, and it is typically consumed together with JAI_AR_TRXS and RA_CUSTOMER_TRX_LINES_ALL in any query that reconstructs the tax position of an invoice.