Results for “trx_line_number”

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

Overview

AR_POSTED_TRANSACTIONS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite Receivables. It presents posted accounting activity that flows from Receivables subledger events into Oracle General Ledger, exposing the joining of Receivables transactions and adjustments with their corresponding journal entries. The view is documented as originating in Release 11 and remains valid through 12.1.1 and 12.2.2. Its principal role is to give report developers, integration specialists, and reconciliation analysts a single denormalized source that links an AR source document (an adjustment or receipt-driven distribution) to the GL journal batch, header, and line that posted it. Because the view combines transactional and accounting attributes, it is frequently used for subledger-to-GL reconciliation, drill-down reporting, and data extraction into external warehouses.

Underlying Base Objects

The view is defined over a set of AR, GL, and HR/party objects. The documented base objects are AR_ADJUSTMENTS_ALL, AR_CASH_RECEIPTS_ALL, AR_CASH_RECEIPT_HISTORY_ALL, AR_MISC_CASH_DISTRIBUTIONS_ALL, AR_RECEIVABLE_APPLICATIONS_ALL, FND_DOCUMENT_SEQUENCES, GL_IMPORT_REFERENCES, GL_JE_BATCHES, GL_JE_HEADERS, GL_JE_LINES, GL_LOOKUPS, HZ_CUST_ACCOUNTS, HZ_CUST_SITE_USES_ALL, HZ_PARTIES, RA_CUSTOMER_TRX_ALL, RA_CUSTOMER_TRX_LINES_ALL, and RA_CUST_TRX_LINE_GL_DIST_ALL. In the documented view text, AR_ADJUSTMENTS_ALL is the driving table, joined to RA_CUSTOMER_TRX_ALL through CUSTOMER_TRX_ID and to GL_IMPORT_REFERENCES through the adjustment identifier embedded in REFERENCE_3. GL_JE_LINES, GL_JE_HEADERS, and GL_JE_BATCHES supply the journal line, header, and batch details respectively. HZ_PARTIES, HZ_CUST_ACCOUNTS, and HZ_CUST_SITE_USES_ALL provide customer name and site context, while GL_LOOKUPS and FND_DOCUMENT_SEQUENCES resolve lookup meaning and document sequence names.

Key Columns

The view aliases its GL-side columns with a JE_ prefix and its transaction-side columns with a TRX_ prefix. JE_STATUS, JE_EFFECTIVE_DATE, JE_PERIOD_NAME, JE_BATCH_NAME, JE_HEADER_NAME, and JE_LINE_NUM identify the posting journal entry and its accounting period. JE_DESCRIPTION carries the journal line description, which is the column users commonly search for under the term "je_description." JE_ENTERED_DR, JE_ENTERED_CR, JE_ACCOUNTED_DR, JE_ACCOUNTED_CR, JE_CURRENCY_CODE, and JE_EXCHANGE_RATE expose amounts and currency conversion. TRX_NUMBER, TRX_LINE_NUMBER, TRX_DATE, TRX_GL_DATE, TRX_VEND_CUST_NAME, and TRX_VEND_CUST_SITE describe the originating Receivables document. TRX_ENTERED_DR and TRX_ENTERED_CR are derived by decoding REFERENCE_9 to distinguish receivable-type adjustments from adjustment-type entries. Document sequence values are surfaced through JE_DOC_SEQUENCE_VALUE, JE_DOC_SEQUENCE_NAME, TRX_DOC_SEQUENCE_VALUE, and TRX_DOC_SEQUENCE_NAME.

Common Use Cases and Queries

Typical uses include reconciling posted AR adjustments against their GL journal lines, tracing a customer transaction to the journal entry that posted it, and extracting posted activity for reporting. A representative query searching for the journal line description is:

• SELECT trx_number, je_header_name, je_line_num, je_description, je_accounted_dr, je_accounted_cred FROM ar_posted_transactions_v WHERE je_description LIKE '%ADJ%';
• SELECT trx_number, je_period_name, je_batch_name, je_status, trx_gl_date FROM ar_posted_transactions_v WHERE trx_date BETWEEN :p_from AND :p_to ORDER BY trx_date;
• SELECT je_batch_name, SUM(je_accounted_dr), SUM(je_accounted_cr) FROM ar_posted_transactions_v GROUP BY je_batch_name;

Because the view draws from many joined tables, queries should be filtered on indexed columns such as TRX_NUMBER, TRX_DATE, JE_PERIOD_NAME, or JE_BATCH_NAME to limit the row set and avoid full scans across the GL and AR base objects.