Results for “app_application_id”

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

Overview

AR_RECEIVABLE_APPS_L_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It is classified under the Oracle Receivables (AR) product family and is documented as a "receivable application line extract." The view presents a denormalized, extract-oriented projection of receivable application activity, exposing the core attributes of rows from AR_RECEIVABLE_APPLICATIONS_ALL together with supporting columns sourced from the Subledger Accounting (SLA/XLA) extraction infrastructure and cash basis distribution data. Its naming convention — the "_L_V" suffix and the internal "APP_" column prefixes — indicates that it is a line-level extract view designed for consumption by downstream processes rather than for direct online transaction entry.

Functionally, the view plays a supporting role in the Receivables to General Ledger accounting flow and in external reporting or data-warehouse extraction. Because it reflects the state of applied receipts, credit memos, on-account cash, and adjustments, it is used to report on how transactions have been settled and how those settlements have been accounted. The view is marked VALID in the ETRM metadata, confirming that its definition compiles successfully against the referenced base objects.

Underlying Base Objects

The documented metadata identifies three referenced base objects, all exposed to APPS as synonyms:

• AR_RECEIVABLE_APPLICATIONS_ALL — the primary transactional base table. The view aliases this as RAA and derives the majority of its columns directly from it, including RECEIVABLE_APPLICATION_ID and the full APP_* attribute family.
• AR_XLA_LINES_EXTRACT — the Subledger Accounting line extraction table, aliased as LI. The view's definition carries the hint /*+ INDEX(LI AR_XLA_LINES_EXTRACT_N1) */, confirming a join to this table and its supporting index. This linkage associates receivable applications with their generated accounting lines.
• AR_CASH_BASIS_DISTS_ALL — the cash basis distribution table, which supports cash-basis accounting treatment of Receivables activity.

The view therefore acts as a consolidated, join-ready layer across application transactions, their subledger accounting lines, and cash basis distributions.

Key Columns

The projection renames each source column with an "APP_" prefix to distinguish application-level attributes from the joined extract and distribution data. Significant columns include:

• APP_APPLICATION_ID — mapped from RAA.RECEIVABLE_APPLICATION_ID; the unique identifier of the receivable application.
• APP_APPLICATION_TYPE, APP_APPLICATION_REF_NUM, APP_APPLICATION_REF_TYPE, APP_APPLICATION_REF_REASON — describe the nature and reference of the application event.
• APP_APPLY_DATE, APP_GL_DATE, APP_REVERSAL_GL_DATE — the application date and the associated GL accounting and reversal dates.
• APP_CODE_COMBINATION_ID, APP_EARNED_DISCOUNT_CCID, APP_UNEARNED_DISCOUNT_CCID — accounting flexfield references for the primary distribution and discount handling.
• APP_EDISC_TAX_ACCT_RULE, APP_UNEDISC_TAX_ACCT_RULE, APP_TAX_CODE — tax accounting rules and tax code context.
• APP_STATUS, APP_CONFIRMED_FLAG, APP_TRANS_TO_RECEIPT_RATE — status, confirmation, and currency conversion rate fields.
• APP_ATTR1–APP_ATTR15, APP_ATTR_CAT, APP_GLOBAL_ATTR1–APP_GLOBAL_ATTR10, APP_GLOBAL_ATTR_CAT — the descriptive flexfield and global descriptive flexfield attribute sets.
• APP_COMMENTS and APP_USSGL_TRANSACTION_CODE — free-text and federal USSGL reporting context.

Common Use Cases and Queries

Typical uses include reconciliation of applications to their accounting entries, cash basis reporting, and extraction of application data into external systems.

To list recent applications with GL dates:

• SELECT app_application_id, app_application_type, app_apply_date, app_gl_date, app_status FROM apps.ar_receivable_apps_l_v WHERE app_apply_date >= TRUNC(SYSDATE)-30;

To review discount and tax accounting context for a given application:

• SELECT app_application_id, app_code_combination_id, app_earned_discount_ccid, app_tax_code FROM apps.ar_receivable_apps_l_v WHERE app_application_id = :app_id;

To aggregate activity by status for a reporting period:

• SELECT app_status, COUNT(*) FROM apps.ar_receivable_apps_l_v WHERE app_gl_date BETWEEN :start_date AND :end_date GROUP BY app_status;

Because the view joins the XLA lines extract and cash basis distributions, queries that reference only application-level columns should be constrained on indexed application columns to avoid unnecessary work against the accounting extract join.