Results for “jl_br_inv_api_trx_lines_t”

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

Overview

JL_BR_INV_API_TRX_LINES_T is a temporary (staging) table owned by the JL schema within the Oracle E-Business Suite Latin America Localizations product. Its documented purpose is to store Brazilian electronic invoice line attributes that are generated or consumed during the Receivables Invoice API processing cycle. The table functions as a 1:1 extension to the Receivables Invoice API PL/SQL line-detail table, meaning that each row in this table corresponds to exactly one line record passed through the invoice API. Because it is a temporary staging object, rows are typically populated at the start of an invoice API call, consumed by the Brazilian electronic invoice (Nota Fiscal Eletrônica) generation logic, and then purged or reused across processing cycles.

From a Data Vault modeling perspective, the supplied metadata classifies this object heuristically as standalone. This classification is a modeling suggestion only, reflecting the absence of tables that functionally depend on it. The two foreign keys it carries (to CN_TRX_LINES_ALL and PN_VAR_TRX_HEADERS_ALL) are outbound references, which would normally suggest a link or satellite role. In practice, however, the structure is closer to a satellite carrying descriptive Brazilian localization attributes, with the foreign keys acting as degenerate references to the parent header and line rather than forming a true Data Vault link.

Key Information Stored

The table contains 41 documented columns. The most business-significant are:

• TRX_LINE_ID – The line identifier, and the primary foreign key to CN_TRX_LINES_ALL. This is the surrogate key linking each staging row back to the corresponding standard Receivables invoice line.
• TRX_HEADER_ID – The header identifier, foreign keyed to PN_VAR_TRX_HEADERS_ALL. This ties the line attributes to the parent transaction header being processed.
• INDUSTRY_ATTRIBUTE1 through INDUSTRY_ATTRIBUTE30 – A large block of thirty generic industry-flex attributes reserved for Brazilian Nota Fiscal Eletrônica line-level fields, such as fiscal codes, tax classification, CFOP values, and other localization-specific data that has no native column in the base Receivables model.
• SRV_EXEC_DATE – The service execution date, a required field for Brazilian fiscal documents describing when the service underlying the invoice line was performed.
• TOWING_VEH_PLATE_NUMBER2 through TOWING_VEH_PLATE_NUMBER5 and the corresponding TOWING_VEH_PLATE_STATE_CODE2 through STATE_CODE5 – Attributes capturing additional towing-vehicle license plate numbers and their issuing states. These support the specific Brazilian fiscal model for towing and freight services, where up to five vehicle plates must be reported on the electronic invoice line.

The surrogate primary key is TRX_LINE_ID, which also serves as the primary business key candidate in combination with TRX_HEADER_ID. The documented metadata does not list any unique indexes beyond these reference columns.

Common Use Cases and Queries

Typical queries against this table fall into three categories: diagnostics during invoice API submission, fiscal reporting, and reconciliation of localization attributes to the base Receivables line. Because the table is temporary, queries are almost always executed in a narrow window around the API call that populated it.

A common diagnostic pattern joins the staging row to the base line table to compare the localization attributes against the standard line:

SELECT t.TRX_LINE_ID,
       t.TRX_HEADER_ID,
       t.SRV_EXEC_DATE,
       t.INDUSTRY_ATTRIBUTE1,
       c.LINE_NUMBER
FROM   JL_BR_INV_API_TRX_LINES_T t,
       CN_TRX_LINES_ALL c
WHERE  t.TRX_LINE_ID = c.TRX_LINE_ID
AND    t.TRX_HEADER_ID = :p_header_id;

Reporting use cases include verifying that mandatory fiscal attributes (for example, SRV_EXEC_DATE or plate numbers on towing lines) were populated before the Nota Fiscal Eletrônica is generated, and tracing why a line failed Brazilian fiscal validation. Reconciliation queries join to PN_VAR_TRX_HEADERS_ALL to confirm that every staged line belongs to a header in an expected transaction status.

Related Objects

• CN_TRX_LINES_ALL – The base Receivables transaction line table; joined on TRX_LINE_ID. This is the most important dependent relationship, since the staging table is a 1:1 extension of this entity.
• PN_VAR_TRX_HEADERS_ALL – The transaction header table; joined on TRX_HEADER_ID. Provides the parent context for each staged line.
• Receivables Invoice API PL/SQL tables – The documented source of the 1:1 mapping. Standard API structures such as AR_INVOICE_API_PUB line tables pass data that is mirrored here for Brazilian localization processing.
• JL_BR_INV_API_TRX_HEADERS_T – The analogous header-level staging table in the same product, typically populated in tandem with this line-level table during a single API call.
• Brazilian Electronic Invoice generation logic – The concurrent programs and PL/SQL packages in the JL product that read rows from this table to produce Nota Fiscal Eletrônica output.