Search Results general_ledger_date




Overview

ARBV_APPLICATION_DISTRIBUTIONS is an APPS-owned reporting view in Oracle E-Business Suite Receivables (AR). It exposes the accounting distributions created when a receipt is applied to a transaction, presented alongside descriptive attributes from the receivable application, the ledger, and the subledger accounting engine. The view is a Business Intelligence-style (BIV) construct: the alias comments (for example, APPLICATION DISTRIBUTIONS, UNIQUE ATTRIBUTES, REGULAR ATTRIBUTES, RESOLVED FK RESOLUTIONS, and WHO COLUMNS) and the embedded _LA: and _KF: directives indicate that this view supplies value sets, lookups, and key flexfield metadata to Oracle's analytical and reporting layers rather than to transactional processing.

The view is a UNION of two branches. The first returns distributions whose SOURCE_TYPE is one of REC, UNAPP, UNID, or ACC — that is, applied, unapplied, unidentified, and adjustment-style applications. This branch joins AR_RECEIVABLE_APPLICATIONS to the subledger lines view AR_XLA_ARD_LINES_V on SOURCE_ID = RECEIVABLE_APPLICATION_ID with SOURCE_TABLE = 'RA'. The second branch returns earned discount distributions (SOURCE_TYPE = 'EDISC') for applications where EARNED_DISCOUNT_TAKEN is populated and non-zero. Both branches carry the same column projection, so the view presents a homogeneous row shape regardless of which source produced the distribution.

Underlying Base Objects

The documented dependencies are:

  • AR_RECEIVABLE_APPLICATIONS (synonym) — the application record that links a receipt (or other cash) to a transaction, and the driver of the join on RECEIVABLE_APPLICATION_ID.
  • AR_XLA_ARD_LINES_V (view) — the subledger accounting distributions view providing the debit/credit amounts, code combination, and source identifiers. Only rows with SOURCE_TABLE = 'RA' are used.
  • GL_CODE_COMBINATIONS (synonym) — the accounting flexfield combination behind each distribution, joined on CODE_COMBINATION_ID. The _KF:SQLGL:GL#:GCC directive resolves the GL key flexfield structure for reporting.
  • HR_ALL_ORGANIZATION_UNITS (synonym) — the operating unit, joined with an outer join (+) on RA.ORG_ID = AOU.ORGANIZATION_ID, supplying the resolved organization name.
  • XLA_AE_HEADERS (synonym) — the subledger journal header, joined on AE_HEADER_ID, supplying GL_TRANSFER_STATUS_CODE for the "posted to GL" flag.

Key Columns

  • RECEIVABLE_APPLICATION_ID — primary link to the application; also the view's unique key.
  • AMOUNT_DR / AMOUNT_CR — entered debit and credit amounts of the distribution.
  • ACCTD_AMOUNT_DR / ACCTD_AMOUNT_CR — accounted (converted) debit and credit amounts, in the ledger currency.
  • GL_DATE — accounting date of the distribution, sourced from the application.
  • ACCOUNT_TYPE — derived via DECODE over RA.STATUS, mapping UNAPP→UNAPP, APP→REC, UNID→UNID, ACC→ACC; earned-discount rows are hard-coded to EDISC. The lookup type is AR_LOOKUPS.
  • GL_TRANSFER_STATUS — resolved to a Yes/No meaning from HED.GL_TRANSFER_STATUS_CODE, indicating whether the journal has been transferred to General Ledger.
  • ORG_ID — operating unit identifier; CODE_COMBINATION_ID — accounting flexfield combination.
  • WHO columnsCREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE.

Common Use Cases and Queries

Typical usage is reconciliation and reporting: listing all accounting entries generated for a specific application, tracing the GL impact of applied, unapplied, unidentified, and adjustment amounts, or verifying that entries have been transferred to GL.

SELECT RECEIVABLE_APPLICATION_ID,
       ACCOUNT_TYPE,
       GL_DATE,
       AMOUNT_DR,
       AMOUNT_CR,
       ACCTD_AMOUNT_DR,
       ACCTD_AMOUNT_CR,
       GL_TRANSFER_STATUS,
       CODE_COMBINATION_ID
  FROM APPS.ARBV_APPLICATION_DISTRIBUTIONS
 WHERE RECEIVABLE_APPLICATION_ID = :application_id;
SELECT ACCOUNT_TYPE,
       SUM(ACCTD_AMOUNT_DR) AS total_dr,
       SUM(ACCTD_AMOUNT_CR) AS total_cr
  FROM APPS.ARBV_APPLICATION_DISTRIBUTIONS
 WHERE GL_DATE BETWEEN :from_date AND :to_date
 GROUP BY ACCOUNT_TYPE;

Note that the leading string "dist\BillingSoftware.exe" does not correspond to any column or object in this view; it is an external file-path artifact and is unrelated to the ETRM metadata for this database object.