Search Results arrgta_categories




Overview
Explore in AI Chat

Overview

APPS.AR_CORRECT_GL_LINES_V is a Receivables (AR) diagnostic and reporting view that exposes the correction records maintained by the AutoAccounting GL correction process. It surfaces rows from the AR_CCID_CORRECTIONS table, joining them to the originating Receivables transactions, adjustments, distributions, receipt instruments, and customer parties so that a user can review which general ledger code combinations were remapped or corrected, in which context, and for which customer. The view is designed to support the "Correct GL Lines" and AutoAccounting troubleshooting investigations in Oracle E-Business Suite 12.1.1 and 12.2.2.

The view is a UNION ALL of two branches. The first branch resolves corrections whose source table is 'GLD' — that is, corrections applied to transaction line level GL distributions. The second branch resolves corrections whose source table is 'ADJ' — corrections applied to adjustment records. This structure allows a single query surface to cover corrections across both transaction and adjustment contexts.

Because the view is queried in Receivables reporting and diagnostics rather than stored data, it is a read-only presentation layer and inherits the security and performance characteristics of its underlying joins. The presence of ARPT_SQL_FUNC_UTIL and FND_GLOBAL references indicates that the view resolves lookup meanings at runtime using the ARPL lookup types.

Underlying Base Objects

The view is owned by APPS and is defined over the documented base objects. The primary driver object is AR_CCID_CORRECTIONS (SYNONYM), aliased ACC, which holds the correction records for both branches. The 'GLD' branch additionally joins 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. The 'ADJ' branch joins AR_ADJUSTMENTS, RA_CUSTOMER_TRX, HZ_PARTIES, and HZ_CUST_ACCOUNTS.

Additional package and view references documented in the metadata include ARPT_SQL_FUNC_UTIL, FND_GLOBAL, and IBY_FNDCPT_TRXN_PUB, plus AR_CASH_RECEIPTS, AR_CASH_RECEIPT_HISTORY, AR_MISC_CASH_DISTRIBUTIONS, AR_RECEIVABLE_APPLICATIONS, and AR_TRANSACTION_HISTORY, which support the wider correction and receipt-distribution context. The joins between AR_CCID_CORRECTIONS and its parent transaction (ACC.PARENT_ID = TRX.CUSTOMER_TRX_ID) and distribution (ACC.DISTRIBUTION_ID = GLD.CUST_TRX_LINE_GL_DIST_ID) are the defining relationships of the view.

Key Columns

  • distribution_type — the correction distribution type. The view returns both a decoded lookup meaning (via ARPT_SQL_FUNC_UTIL.GET_LOOKUP_MEANING) and the raw value, using lookup type DISTRIBUTION_SOURCE_TYPE or AUTOGL_TYPE depending on whether the value is 'REC' or otherwise.
  • category_type — the category of the transaction or adjustment, decoded against lookup types INV/CM/ADJ for GLD rows and ARRGTA_CATEGORIES for adjustment rows. This column is directly relevant to the search term arrgta_categories, which is the lookup type referenced in the adjustment branch of the view.
  • distribution_id and parent_id — the distribution identifier and the parent transaction or adjustment identifier that anchor the correction to its source record.
  • source_table — indicates whether the correction derives from 'GLD' (transaction line GL distributions) or 'ADJ' (adjustments).
  • code_combination_id — the corrected GL code combination applied by the correction.
  • trx_number and name — the transaction number and transaction type name for GLD corrections.
  • gl_date — the general ledger date associated with the correction.
  • src.name and srep.name — batch source and salesperson names for GLD corrections.
  • party_name — the customer party name derived from HZ_PARTIES.
  • Instrument columns — a decoded instrument value returning the bank account number for 'BANKACCOUNT' instrument type or the card number for 'CREDITCARD'.

Common Use Cases and Queries

The most common use is investigating why a transaction or adjustment received a particular GL code combination, and which corrections were recorded against it. A typical query filters by transaction number or by source table:

SELECT trx_number, name, distribution_type, category_type, code_combination_id, gl_date, party_name FROM apps.ar_correct_gl_lines_v WHERE source_table = 'GLD' AND trx_number = :trx_number;

For adjustment-related diagnostics, filtering on source_table = 'ADJ' returns adjustment number, reason code, decoded category type from ARRGTA_CATEGORIES, and the customer party. This is the primary path for readers searching on arrgta_categories, since that lookup type appears only in the adjustment branch:

SELECT distribution_id, parent_id, category_type, code_combination_id, gl_date, party_name FROM apps.ar_correct_gl_lines_v WHERE source_table = 'ADJ' AND parent_id = :adjustment_id;

A third scenario is auditing corrections across a GL date range or a customer, useful in period-close validation and in confirming that AutoAccounting corrections produced the intended code combinations.