Search Results alloc_row_id

Overview

The APPS.JG_ZZ_TA_JE_LINES_V view is a Regional Localizations (JG) reporting object that exposes journal entry line detail in a flattened, query-friendly form. It sits in the APPS schema and carries a VALID status in Oracle E-Business Suite 12.1.1 and 12.2.2. Rather than presenting raw General Ledger table rows, the view joins subledger journal lines to their GL headers, batches, conversion types, document sequences, reconciliation rows, and a localization-specific allocated-lines table, and then projects the combined result through a single set of column aliases.

The object is relevant to the search term invoice_identifier because that attribute is surfaced directly: the view maps JLI.INVOICE_IDENTIFIER (from GL_JE_LINES) to the column INVOICE_IDENTIFIER, alongside related fiscal attributes such as INVOICE_DATE, INVOICE_AMOUNT, TAX_CODE, USSGL_TRANSACTION_CODE, and STAT_AMOUNT. This makes it a convenient access point where an external invoice reference must be correlated to a posted journal line without drilling into GL_JE_LINES directly.

Underlying Base Objects

The view is defined over seven documented base objects, all referenced through APPS synonyms:

• GL_JE_LINES — the primary line source (aliased JLI); supplies amounts, invoice fields, tax code, and the descriptive flexfield segments (CONTEXT, CONTEXT2..18, ATTRIBUTE1..20).
• GL_JE_HEADERS — header context (aliased HDR): currency, period, journal name, doc sequence value, conversion rate and date.
• GL_JE_BATCHES — batch attributes (aliased BAT): batch name and batch status.
• GL_DAILY_CONVERSION_TYPES — the user conversion type description (aliased CONV).
• FND_DOCUMENT_SEQUENCES — the document sequence name (aliased SEQ).
• GL_JE_LINES_RECON — reconciliation reference (aliased JLR), contributing JGZZ_RECON_REF.
• JG_ZZ_TA_ALLOCATED_LINES — the localization allocated-lines source (aliased ALO).

The join path effectively means each output row represents an allocated line tied to a GL journal line, enriched by its header, batch, sequence, and reconciliation context. Because it hydrates multiple base tables, the view is read-only and intended for inquiry, not DML.

Key Columns

• INVOICE_IDENTIFIER — the subledger invoice reference carried on the GL journal line; the field most directly tied to the search.
• INVOICE_DATE, INVOICE_AMOUNT, TAX_CODE — companion invoice attributes used for fiscal and tax reporting.
• JE_BATCH_ID, JE_HEADER_ID, JE_LINE_NUM — the journal identity chain.
• ACCOUNTED_DR, ACCOUNTED_CR, ENTERED_DR, ENTERED_CR, STAT_AMOUNT — monetary measures in both entered and accounted currencies.
• CURRENCY_CODE, CURRENCY_CONVERSION_TYPE, CURRENCY_CONVERSION_DATE, CURRENCY_CONVERSION_RATE — conversion context.
• PERIOD_NAME, EFFECTIVE_DATE, LEDGER_ID — accounting period and ledger placement.
• SUBLEDGER_DOC_SEQUENCE_ID, SUBLEDGER_DOC_SEQUENCE_VALUE, JE_DOC_SEQUENCE_VALUE, JE_DOC_SEQUENCE_NAME — sequencing references.
• JGZZ_RECON_REF — localization reconciliation reference.
• CONTEXT, CONTEXT2..18, ATTRIBUTE1..20 — descriptive flexfield payload.
• ROW_ID, ALLOC_ROW_ID — ROWID pseudo-columns for row-level addressing.

Common Use Cases and Queries

Typical uses include invoice-to-journal reconciliation, localization reporting on allocated lines, and audit extracts that require both the invoice identifier and its posted GL amounts.

Locating a journal line by invoice identifier:

• SELECT je_header_id, je_line_num, invoice_identifier, invoice_date, invoice_amount, tax_code, accounted_dr, accounted_ce FROM apps.jg_zz_ta_je_lines_v WHERE invoice_identifier = :p_invoice_id;

Extracting localization reconciliation detail for a period:

• SELECT period_name, je_batch_name, je_header_name, je_line_num, entered_dr, entered_ce, jgzz_recon_ref, currency_code FROM apps.jg_zz_ta_je_lines_v WHERE period_name = :p_period AND ledger_id = :p_ledger ORDER BY je_batch_name, je_header_name, je_line_num;

Audit query joining header totals to invoice identifiers:

• SELECT je_header_id, invoice_identifier, SUM(accounted_dr) dr, SUM(accounted_ce) ce FROM apps.jg_zz_ta_je_lines_v GROUP BY je_header_id, invoice_identifier HAVING SUM(accounted_dr) <> 0;

Because the view aggregates several large GL tables, queries should be constrained by LEDGER_ID, PERIOD_NAME, JE_HEADER_ID, or INVOICE_IDENTIFIER to remain performant. Access is granted to APPS responsibilities, and the object should be treated strictly as a read-only reporting interface.