Search Results document_line_item

Overview

APPS.JAI_REPOEXT_V is an Oracle E-Business Suite (EBS) reporting view that belongs to the JA product family, which provides the India Localization (formerly "JAIN") functionality for tax, excise, and statutory reporting. In EBS 12.1.1 and 12.2.2, this view exposes repository or extract data relating to tax and transaction lines used by the India Localization tax engine (ETRM). Its principal purpose is to present the contents of the JAI_TRX_REPO_EXTRACT_GT global temporary table in a de-duplicated, aggregated, reporting-friendly form. The view consolidates transaction line attributes — supplier/party details, document identifiers, item identifiers, quantities, amounts, and tax amounts — into a single row per logical transaction line, making it suitable for reporting, reconciliation, and downstream integration.

Underlying Base Objects

The view is defined exclusively over a single documented base object: JAI_TRX_REPO_EXTRACT_GT, exposed as a synonym. This global temporary table is populated during India Localization tax extraction routines that gather transaction line data from purchasing, payables, and related sub-ledgers for tax repository processing. Because the base object is a global temporary table, its data is session-scoped, and the view is therefore most meaningful while extraction processing is active within the same database session. The view applies GROUP BY and aggregate functions (MIN, MAX, SUM, DECODE) to collapse duplicate extraction rows into consolidated output.

Key Columns

• DOCUMENT_LINE_ID — the identifier of the transaction line; central to the view's grouping logic and the field the user searched for. It drives the conditional tax aggregation via DECODE(DOCUMENT_LINE_ID, NULL, SUM(...), MAX(...)).
• TRANSACTION_REPOSITORY_ID / TRANSACTION_REFERENCE_ID — repository and reference identifiers, aggregated with MIN() to yield one representative value per group.
• TRANSACTION_SOURCE, SOURCE_TRX_TYPE — indicate the originating transaction type and source system.
• PARTY_NAME, PARTY_ID — supplier or party details associated with the transaction.
• DOCUMENT_NUMBER, DOCUMENT_DATE, DOCUMENT_CURRENCY_CODE — invoice/document header attributes; currency defaults to 'INR' via NVL.
• DOCUMENT_LINE_NUM, DOCUMENT_LINE_ITEM, DOCUMENT_LINE_DESC, DOCUMENT_LINE_QTY, DOCUMENT_LINE_UOM, DOCUMENT_LINE_AMT — descriptive and quantitative line attributes.
• REPOSITORY_TAX_AMT — tax amount, aggregated conditionally depending on whether a document line identifier exists.
• ORGANIZATION_ID, LOCATION_ID, INVENTORY_ITEM_ID — inventory and shipping context.
• UPDATABLE_FLAG, GL_DATE, ST_INV_NUMBER, SERVICE_TYPE_CODE — processing flags and accounting date fields.

Common Use Cases and Queries

A typical use is retrieving repository tax extract lines for a given document line, which aligns directly with the user's search term:

• Locate tax repository data by document line: SELECT document_number, document_line_num, document_line_amt, repository_tax_amt FROM apps.jai_repoext_v WHERE document_line_id = :line_id;
• Summarize tax by party and document: SELECT party_name, document_number, SUM(repository_tax_amt) FROM apps.jai_repoext_v GROUP BY party_name, document_number;
• Reconcile extracted lines against source sub-ledger transactions using DOCUMENT_ID and DOCUMENT_LINE_ID join keys.

Because the underlying object is a global temporary table, queries generally return data only within the extraction session context. Report developers should confirm that the extract process has populated JAI_TRX_REPO_EXTRACT_GT before querying the view, and should reuse it for India Localization tax reporting rather than querying the temporary table directly.