Search Results ar_correct_gl_accounts_v




Overview
Explore in AI Chat

Overview

AR_CORRECT_GL_ACCOUNTS_V is a Receivables (AR) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is a correction-staging view designed to expose records from the AR_CCID_CORRECTIONS table for GL account (code combination) correction activity. The view filters the underlying correction data by restricting to rows where SUBMISSION_ID IS NULL, meaning only correction entries that have not yet been packaged into a submission are returned. This makes the view a working set of pending code combination corrections rather than an audit of completed submissions.

The object referenced by the search term new_code_combination_id appears directly in the view's projection. The view exposes both the current CODE_COMBINATION_ID and the NEW_CODE_COMBINATION_ID, which together express the before-and-after state of a Receivables accounting flexfield correction. In reporting and integration contexts, the view provides a read-only, lookup-enriched representation of correction data that can feed diagnostics, reconciliation scripts, and supporting queries when analyzing why a Receivables distribution points to a given GL account.

Underlying Base Objects

Per the documented ETRM metadata, the view is defined over two referenced base objects:

  • AR_CCID_CORRECTIONS (SYNONYM) — the primary data source. The view selects directly from AR_CCID_CORRECTIONS (aliased ACC) and returns its correction rows.
  • ARPT_SQL_FUNC_UTIL (PACKAGE) — a Receivables SQL utility package. Two calls to ARPT_SQL_FUNC_UTIL.GET_LOOKUP_MEANING are made inside the SELECT list to translate coded values into descriptive meanings.

The view relies on DECODE logic to choose the correct lookup context. For DISTRIBUTION_MEANING, if DISTRIBUTION_TYPE is 'REC', the package is invoked with the context 'DISTRIBUTION_SOURCE_TYPE'; otherwise, if SOURCE_TABLE is 'GLD', the context is 'AUTOGL_TYPE', falling back to 'DISTRIBUTION_SOURCE_TYPE'. For CATEGORY_MEANING, when SOURCE_TABLE is 'GLD' the context is 'INV/CM/ADJ', otherwise 'ARRGTA_CATEGORIES'. The view uses SELECT DISTINCT, so duplicate source rows that resolve to identical projected values are collapsed.

Key Columns

  • DISTRIBUTION_MEANING — decoded description of the distribution source type, derived through GET_LOOKUP_MEANING.
  • DISTRIBUTION_TYPE — the raw distribution type code from AR_CCID_CORRECTIONS.
  • CATEGORY_MEANING — decoded description of the category type, resolved against either INV/CM/ADJ or ARRGTA_CATEGORIES depending on the source table.
  • CATEGORY_TYPE — the raw category code used as the lookup input.
  • CODE_COMBINATION_ID — the existing accounting flexfield combination currently associated with the correction record.
  • NEW_CODE_COMBINATION_ID — the replacement code combination applied by the correction. This is the column most relevant to the user's search, as it identifies the target GL account for pending Receivables corrections.

Common Use Cases and Queries

Typical uses include reviewing unsubmitted code combination corrections, validating the target GL account before submission, and diagnosing Receivables distributions that reference an incorrect accounting flexfield.

  • List all pending corrections with their old and new accounts: 
    SELECT distribution_meaning,
       category_meaning,
       code_combination_id,
       new_code_combination_id
FROM   apps.ar_correct_gl_accounts_v;
  • Find corrections targeting a specific new code combination: 
    SELECT distribution_type, category_type, code_combination_id
FROM   apps.ar_correct_gl_accounts_v
WHERE  new_code_combination_id = :p_new_ccid;
  • Group pending corrections by category: 
    SELECT category_meaning, COUNT(*)
FROM   apps.ar_correct_gl_accounts_v
GROUP  BY category_meaning;

Because the view only returns rows where SUBMISSION_ID IS NULL, queries against it reflect the current correction backlog that has not yet been processed into a submission.