Search Results ar_llca_adj_trx_lines_u1
Overview
AR.AR_LLCA_ADJ_TRX_LINES_GT is a global temporary table owned by the Receivables (AR) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is a transient staging structure used by the Receivables LLCA (Late Charge / Line Level Charge Adjustment) adjustment processing logic to hold transaction line rows while adjustments are being computed and applied. As a global temporary table with a data duration of SYS$TRANSACTION, the data placed in the table by one session is visible only to that session and is automatically removed at the end of the transaction. No persistent, shared data resides in this object.
Because the table stores transient, session-scoped rows rather than durable master or transactional entities, a Data Vault modeling heuristic would classify it as a standalone staging structure — effectively a work or link-style construct joining a transaction, its line, and a receivables activity for the duration of a processing run. It is not itself a permanent hub, link, or satellite in the warehouse sense; the closest analogy is a transient link associating a customer transaction and its line with a receivables activity and an amount.
Key Information Stored
The object exposes a narrow, four-column structure that is entirely focused on identifying adjustment lines and their monetary values:
- CUSTOMER_TRX_ID (NUMBER 15) — identifies the Receivables transaction to which the adjustment line belongs. This is the header-level foreign reference and is used by the non-unique index AR_LLCA_ADJ_TRX_LINES_N1.
- CUSTOMER_TRX_LINE_ID (NUMBER 15) — identifies the individual transaction line being adjusted. This column carries the unique index AR_LLCA_ADJ_TRX_LINES_U1, making it a business-key candidate for the row and the natural driver of line-level lookups.
- RECEIVABLES_TRX_ID (NUMBER 15) — identifies the receivables activity (in AR_RECEIVABLES_TRX_ALL) that the adjustment represents, such as a specific adjustment, charge, or activity type. This column forms a foreign-key relationship to AR_RECEIVABLES_TRX_ALL.
- LINE_AMOUNT (NUMBER) — the monetary amount associated with the adjustment line, expressed in the transaction's currency context and used to load or verify the adjustment value.
No surrogate system-generated primary key column is documented. The unique index on CUSTOMER_TRX_LINE_ID serves as the business-key candidate, while CUSTOMER_TRX_ID supports the non-unique access path for header-level grouping.
Common Use Cases and Queries
The table is populated and consumed within a single transaction by Receivables adjustment programs, typically during LLCA processing. Typical diagnostic and development uses include inspecting stage rows while debugging adjustment generation, validating that a line was staged before posting, and reconciling staged amounts against the posted adjustment.
Representative query patterns include:
- Retrieve all staged lines for a transaction:
SELECT CUSTOMER_TRX_LINE_ID, RECEIVABLES_TRX_ID, LINE_AMOUNT FROM AR.AR_LLCA_ADJ_TRX_LINES_GT WHERE CUSTOMER_TRX_ID = :trx_id; - Locate a single staged line via the unique key:
SELECT * FROM AR.AR_LLCA_ADJ_TRX_LINES_GT WHERE CUSTOMER_TRX_LINE_ID = :line_id; - Join to receivables activity definitions to resolve activity names:
SELECT t.CUSTOMER_TRX_LINE_ID, r.NAME, t.LINE_AMOUNT FROM AR.AR_LLCA_ADJ_TRX_LINES_GT t JOIN AR.AR_RECEIVABLES_TRX_ALL r ON r.RECEIVABLES_TRX_ID = t.RECEIVABLES_TRX_ID;
Because the table is session-private and transaction-scoped, queries must be issued from the same session and transaction that inserted the rows; otherwise the result set will be empty.
Related Objects
The most significant related objects are those referenced by the documented dependencies and those that share the adjustment context:
- AR.AR_RECEIVABLES_TRX_ALL — referenced via RECEIVABLES_TRX_ID; holds receivables activity definitions used to classify each staged adjustment line.
- AR.RA_CUSTOMER_TRX_ALL — the transaction header referenced conceptually by CUSTOMER_TRX_ID.
- AR.RA_CUSTOMER_TRX_LINES_ALL — the transaction line referenced by CUSTOMER_TRX_LINE_ID.
- AR.AR_ADJUSTMENTS — the resulting posted adjustments that the staged rows ultimately produce.
- AR.AR_RECEIVABLE_APPLICATIONS_ALL — downstream application records affected when the adjustment is applied.
These relationships are join-driven rather than enforced by declared constraints, since only the RECEIVABLES_TRX_ID foreign key is documented. The table itself is exposed to the APPS schema as AR_LLCA_ADJ_TRX_LINES_GT for use by Receivables concurrent programs and PL/SQL packages.
-
INDEX: AR.AR_LLCA_ADJ_TRX_LINES_U1
12.2.2
owner:AR, object_type:INDEX, object_name:AR_LLCA_ADJ_TRX_LINES_U1, status:VALID,
-
INDEX: AR.AR_LLCA_ADJ_TRX_LINES_U1
12.1.1
owner:AR, object_type:INDEX, object_name:AR_LLCA_ADJ_TRX_LINES_U1, status:VALID,
-
TABLE: AR.AR_LLCA_ADJ_TRX_LINES_GT
12.1.1
owner:AR, object_type:TABLE, fnd_design_data:AR.AR_LLCA_ADJ_TRX_LINES_GT, object_name:AR_LLCA_ADJ_TRX_LINES_GT, status:VALID,
-
TABLE: AR.AR_LLCA_ADJ_TRX_LINES_GT
12.2.2
owner:AR, object_type:TABLE, fnd_design_data:AR.AR_LLCA_ADJ_TRX_LINES_GT, object_name:AR_LLCA_ADJ_TRX_LINES_GT, status:VALID,
-
12.1.1 DBA Data
12.1.1
-
12.2.2 DBA Data
12.2.2
-
12.1.1 DBA Data
12.1.1
-
12.2.2 DBA Data
12.2.2
-
eTRM - AR Tables and Views
12.1.1
description: Territory information ,
-
eTRM - AR Tables and Views
12.2.2
description: Territory information ,