Results for “collected_tax_ccid”

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

Overview

The RA_CUST_TRX_LINE_GL_DIST_V view is an APPS-owned, VALID database view within the Oracle Receivables (AR) module. It presents distribution accounting information for receivable transaction lines, joining the underlying distribution table with descriptive attributes drawn from transaction lines, accounting rules, and Receivables lookups. Its primary purpose is to expose general ledger distribution rows—keyed by customer transaction, transaction line, code combination, and amount—enriched with human-readable meanings for account class and line type, extended line amounts, and the accounting rule name. Because it resolves foreign keys into descriptive text, the view is commonly used in reporting, reconciliation, and integration scenarios where raw distribution identifiers would otherwise require additional joins. The view retains release 115 lineage, meaning its definition has been stable across many releases and continues to be deployable in Oracle EBS 12.1.1 and 12.2.2 environments.

Underlying Base Objects

The view is defined over four documented base objects. RA_CUST_TRX_LINE_GL_DIST supplies the canonical distribution rows (aliased LGD) and is the driving table. RA_CUSTOMER_TRX_LINES appears twice—once as CTL for the primary transaction line, and once as CTL_LINE joined through the LINK_TO_CUST_TRX_LINE_ID relationship—permitting the view to return either the linked line number or the original line number depending on whether a link exists. AR_LOOKUPS is also referenced twice: AL_CLASS resolves the ACCOUNT_CLASS value against lookup type AUTOGL_TYPE, while AL_TYPE resolves the transaction line type against STD_LINE_TYPE. RA_RULES is joined via the accounting rule identifier on the transaction line to expose the rule name. All joins to the secondary transaction line, line type lookup, and dependent objects are outer joins, ensuring distribution rows are not lost when ancillary attributes are absent.

Key Columns

• CUST_TRX_LINE_GL_DIST_ID, CUSTOMER_TRX_ID, and CUSTOMER_TRX_LINE_ID — primary distribution identifier and its parent transaction and line keys.
• AMOUNT, ACCTD_AMOUNT, and EXTENDED_AMOUNT — entered, accounted, and extended line amounts used for balancing and reporting.
• ACCOUNT_CLASS and its lookup MEANING (via AUTOGL_TYPE) — classification of the distribution, such as revenue, tax, freight, or receivables.
• CODE_COMBINATION_ID and CONCATENATED_SEGMENTS — the GL account and its readable segment string.
• GL_DATE, ORIGINAL_GL_DATE, and GL_POSTED_DATE — accounting, original, and posting dates.
• SET_OF_BOOKS_ID — the ledger context for the distribution.
• NAME (from RA_RULES) and line number columns — the accounting rule name and the effective transaction line number.
• REC_OFFSET_FLAG, USER_GENERATED_FLAG, and ROUNDING_CORRECTION_FLAG — indicators distinguishing receivables offsetting, manually created, and rounding correction distributions.
• WHO columns and request/program identifiers — audit and concurrent program tracking columns.

Common Use Cases and Queries

The view is typically queried to reconcile transaction distributions against the general ledger, to report revenue by account class, or to feed downstream systems with descriptive distribution data. A representative query retrieves revenue distributions for a transaction:

• SELECT customer_trx_id, account_class, meaning, concatenated_segments, amount, acctd_amount, gl_date FROM ra_cust_trx_line_gl_dist_v WHERE customer_trx_id = :p_trx_id AND account_class = 'REV';
• Reporting revenue and tax by ledger: filter on set_of_books_id and gl_date range, grouping by concatenated_segments.
• Reconciliation to GL: compare acctd_amount and gl_posted_date against posted balances using code_combination_id.
• Audit of manual and offsetting entries: filter on user_generated_flag or rec_offset_flag.

Because the view exposes decoded meanings and the accounting rule name, it reduces the need for ad hoc joins in custom reports and interfaces, though consumers should still be aware that outer-joined columns may return nulls when source relationships are absent.