Search Results ar_correct_gl_lines_v




Overview
Explore in AI Chat

Overview

AR_CORRECT_GL_LINES_V is a read-only view owned by the APPS schema in Oracle E-Business Suite Releases 12.1.1 and 12.2.2. It belongs to the Oracle Receivables (AR) product family and exposes general ledger correction lines associated with the Subledger Accounting (SLA) CCID correction process. The view is the primary extraction point for the ar_ccid_corrections search context and is designed to present the corrections captured in AR_CCID_CORRECTIONS alongside the descriptive attributes of the underlying Receivables transactions, adjustments, salesreps, customers, and payment instruments.

Its role is diagnostic and reporting-oriented: it allows functional and technical users to review which Receivables distributions had their accounting flexfield (Code Combination ID) corrected, when the correction is effective (GL_DATE), and which parent transaction or adjustment the correction belongs to. Because it resolves lookup codes into user-facing meanings, it is also a convenient source for concurrent programs, BI Publisher reports, and reconciliation extracts.

Underlying Base Objects

Documented metadata for 12.2.2 lists the following referenced objects: ARPT_SQL_FUNC_UTIL (package), AR_ADJUSTMENTS, AR_CASH_RECEIPTS, AR_CASH_RECEIPT_HISTORY, AR_CCID_CORRECTIONS, AR_MISC_CASH_DISTRIBUTIONS, AR_RECEIVABLE_APPLICATIONS, AR_TRANSACTION_HISTORY, FND_GLOBAL (package), HZ_CUST_ACCOUNTS, HZ_PARTIES, IBY_FNDCPT_TRXN_PUB (package), IBY_TRXN_EXTENSIONS_V (view), RA_BATCH_SOURCES, RA_CUSTOMER_TRX, RA_CUST_TRX_LINE_GL_DIST, RA_CUST_TRX_LINE_SALESREPS, RA_CUST_TRX_TYPES, and RA_SALESREPS (view).

The view text is a UNION ALL of two branches. The first branch joins AR_CCID_CORRECTIONS to RA_CUSTOMER_TRX, RA_CUST_TRX_LINE_GL_DIST, RA_CUST_TRX_TYPES, RA_BATCH_SOURCES, IBY_TRXN_EXTENSIONS_V, RA_CUST_TRX_LINE_SALESREPS, RA_SALESREPS, HZ_PARTIES, and HZ_CUST_ACCOUNTS, restricted to SOURCE_TABLE = 'GLD'. The second branch handles adjustment sources (SOURCE_TABLE = 'ADJ') joining AR_ADJUSTMENTS, RA_CUSTOMER_TRX, HZ_PARTIES, and HZ_CUST_ACCOUNTS. The lookup decoding is performed by the ARPT_SQL_FUNC_UTIL.GET_LOOKUP_MEANING function, which converts lookup codes such as distribution type and category type into readable meanings.

Key Columns

  • DISTRIBUTION_TYPE / DISTRIBUTION_TYPE_MEANING — the SLA distribution source type (for example REC vs. non-receivable) and its decoded meaning.
  • CATEGORY_TYPE / CATEGORY_TYPE_MEANING — category of the underlying distribution, decoded against the INV/CM/ADJ or ARRGTA_CATEGORIES lookup.
  • DISTRIBUTION_ID — identifier of the corrected distribution (GLD row or adjustment row).
  • PARENT_ID — the parent transaction or adjustment identifier used to join back to the source.
  • SOURCE_TABLE — the origin of the correction, GLD or ADJ.
  • CODE_COMBINATION_ID — the corrected accounting flexfield combination.
  • TRX_NUMBER / ADJUSTMENT_NUMBER — the Receivables transaction number or adjustment number.
  • GL_DATE — the accounting date on which the corrected distribution is recognized.
  • NAME, SALESREP, PARTY_NAME — transaction type, batch source, salesrep, and customer party descriptors derived from the joined master data.

Common Use Cases and Queries

The view is typically queried to reconcile CCID corrections against receivable activity, to verify that corrected distributions carry the expected GL date and category, and to feed downstream reconciliation or audit reports. The following sample restricts output to a single transaction number:

SELECT DISTRIBUTION_TYPE_MEANING, CATEGORY_TYPE_MEANING, DISTRIBUTION_ID, PARENT_ID, SOURCE_TABLE, CODE_COMBINATION_ID, TRX_NUMBER, GL_DATE, PARTY_NAME FROM APPS.AR_CORRECT_GL_LINES_V WHERE TRX_NUMBER = :p_trx_number;

Because the view already resolves lookup meanings and joins the major descriptive entities, it removes the need for callers to replicate the multi-table join logic themselves. It should be treated as a reporting surface rather than a transactional one, and users should be aware that the CATEGORY_TYPE decoding differs between the GLD and ADJ branches, which is reflected in the reported meaning values.