Results for “receivable_application_id_cash”

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

Overview

IGI_AR_CASH_BASIS_DISTS is an APPS-owned, VALID database view within the IGI – Public Sector Financials International product family. Its documented purpose is to store and expose Combined Basis Accounting (CBA) cash basis distributions. In environments where an organization maintains both accrual and cash accounting ledgers, this view supplies the distribution-level detail that drives downstream General Ledger posting for the cash basis method. For Oracle EBS 12.1.1 and 12.2.2, the view functions primarily as a reporting and integration layer: it presents CBA Receivables distributions in a form that joins to receipts, payment schedules, and accounting flexfield combinations, while applying Multi-Org security filtering through ORG_ID. Because the view text references GL_POSTED_DATE, it is frequently targeted by queries seeking to reconcile cash basis distributions that have or have not yet been transferred to GL.

Underlying Base Objects

The view is defined over a single documented base object, IGI_AR_CASH_BASIS_DISTS_ALL, referenced as a synonym. This is the "_ALL" table that holds cash basis distribution rows for all operating units. The view selects the full column list from the base table without transformation, and the only filtering applied is the standard Multi-Org row-level security predicate against ORG_ID. The predicate evaluates USERENV('CLIENT_INFO') — the first character is tested for a space, and if not blank, the first ten characters are interpreted as the current operating unit identifier. The NVL chain compares this value against the stored ORG_ID, defaulting to -99 when no client information is available. Consequently, when accessed outside a properly initialized Multi-Org session, the view may return no rows or only rows associated with the fallback value.

Key Columns

• CASH_BASIS_DISTRIBUTION_ID — Primary identifier for each cash basis distribution row.
• RECEIVABLE_APPLICATION_ID and RECEIVABLE_APPLICATION_ID_CASH — Link the distribution to its Receivables application, including the cash-side relationship.
• SOURCE and SOURCE_ID — Identify the originating transaction or event.
• PAYMENT_SCHEDULE_ID — Payment schedule against which the distribution is recorded.
• GL_DATE and GL_POSTED_DATE — The accounting date and the date the distribution was actually posted to General Ledger; GL_POSTED_DATE is the column most relevant to the searched term and distinguishes unposted from posted rows.
• CODE_COMBINATION_ID — The accounting flexfield combination receiving the debit or credit.
• AMOUNT and ACCTD_AMOUNT — Entered and accounted amounts, distinguished by currency.
• POSTING_CONTROL_ID — Links the distribution to a posting batch or control record.
• ORG_ID — Operating unit identifier enforcing Multi-Org security.

Common Use Cases and Queries

Typical applications include reconciling posted versus unposted cash basis distributions, tracing distributions back to their Receivables applications, and validating that the Subledger Accounting transfer to GL completed. The most frequent pattern given the gl_posted_date search term is identifying distributions awaiting posting.

SELECT cash_basis_distribution_id,
       receivable_application_id,
       gl_date,
       gl_posted_date,
       currency_code,
       amount,
       acctd_amount,
       code_combination_id
FROM   apps.igi_ar_cash_basis_dists
WHERE  gl_posted_date IS NULL;

A second common query reports posted activity for a date range:

SELECT code_combination_id,
       SUM(acctd_amount) accounted_total
FROM   apps.igi_ar_cash_basis_dists
WHERE  gl_posted_date BETWEEN :from_date AND :to_date
GROUP  BY code_combination_id;

Because access requires an initialized Multi-Org session, reports and integrations should set the CLIENT_INFO context, or query IGI_AR_CASH_BASIS_DISTS_ALL directly with an explicit ORG_ID predicate where global visibility is intended.