Results for “igi_ar_rec_applications”

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

Overview

IGI_AR_REC_APPLICATIONS is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the IGI — Public Sector Financials International product. Its documented purpose is to hold information about receipt applications, exposing the cash application records that link an Oracle Receivables receipt to the transaction it settles. In the ETRM 12.1.1 and 12.2.2 object registries the object is listed with status VALID and is classified as a VIEW rather than a table.

The view functions as an organizational security layer. Rather than presenting the full contents of the underlying table, it filters rows by the operating unit context established in the user's session, so that a query executed by a given responsibility returns only receipt applications belonging to the accessible organization. This makes the view suitable for reporting, concurrent programs, and integration extracts where the caller expects the standard EBS multi-org filtering to be applied automatically.

Underlying Base Objects

The view is defined over a single documented base object, the synonym IGI_AR_REC_APPLICATIONS_ALL. The view text performs a projection of nine columns and applies a WHERE clause that compares ORG_ID against the value derived from the USERENV('CLIENT_INFO') session parameter:

• ORG_ID is compared to a decoded value taken from the first ten characters of CLIENT_INFO.
• The NVL wrapper and the sentinel value -99 cause rows with a null ORG_ID to be treated consistently with rows whose session context cannot be resolved.
• The DECODE on the first character of CLIENT_INFO suppresses the comparison when the session context begins with a space, which is the standard EBS convention for a globally scoped session.

Because the filtering is embedded in the view definition, callers cannot obtain cross-operating-unit results from IGI_AR_REC_APPLICATIONS without bypassing the view and querying IGI_AR_REC_APPLICATIONS_ALL directly, which requires the appropriate data access privileges.

Key Columns

The view exposes the following columns, all inherited from the base object:

• RECEIVABLE_APPLICATION_ID — primary identifier of the receipt application record.
• ARC_POSTING_CONTROL_ID — identifier of the posting control record that governs how the application is processed through accounting.
• ARC_GL_POSTED_DATE — the General Ledger posting date associated with the receipt application. This is the column most frequently requested in ad hoc reporting, since it establishes the accounting period into which the associated journal entry falls.
• ORG_ID — operating unit identifier, and the column used by the view's security predicate.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns recording who created and last changed the row, and when.

Common Use Cases and Queries

The principal use case is reconciliation reporting: identifying which receipt applications have been posted to the General Ledger, and in which period. A query against ARC_GL_POSTED_DATE supports period-close analysis and the detection of applications still awaiting posting. Note that rows where the posting date is null have not yet been transferred to GL.

A representative query is:

• SELECT receivable_application_id, arc_posting_control_id, arc_gl_posted_date, org_id FROM apps.igi_ar_rec_applications WHERE arc_gl_posted_date BETWEEN :from_date AND :to_date ORDER BY arc_gl_posted_date;
• SELECT COUNT(*) FROM apps.igi_ar_rec_applications WHERE arc_gl_posted_date IS NULL;

Because the view enforces operating unit security through CLIENT_INFO, these queries return only the receipt applications visible to the current session. Reports intended to span multiple operating units must run under a responsibility configured accordingly, or query the base synonym directly. Published documentation for this object is limited to the column list and view text reproduced in the ETRM registry; no additional business rules are documented.