Search Results ar_process_status

Overview

APPS.AR_INTEREST_BATCHES_V is a reporting and inquiry view in the Oracle E-Business Suite Receivables (AR) module. It exposes interest batch records maintained by the Interest Calculation and Interest Invoicing processes, presenting both the raw stored attributes of each batch and several derived values that would otherwise require procedural logic. The view is defined over the AR_INTEREST_BATCHES base object and enriches each row with a decoded lookup meaning, a computed batch amount, and standard audit and multi-organization columns.

The view is particularly significant for users who search on the "ar_process_status" lookup. The TRANSFERRED_STATUS column stores the internal lookup code, and the view adds TRANSFERRED_STATUS_M, which resolves that code to its translated meaning through the AR_PROCESS_STATUS lookup type. This makes the view the natural source for reporting on the lifecycle state of an interest batch without forcing the report author to join to FND_LOOKUP_VALUES manually.

Underlying Base Objects

The view is defined over three documented dependencies:

• AR_INTEREST_BATCHES (synonym) — the driving base object. Every column prefixed with IB in the view definition originates from this synonym, which resolves to the underlying AR_INTEREST_BATCHES table. It holds one row per interest batch and supplies the primary key INTEREST_BATCH_ID along with BATCH_NAME, GL_DATE, BATCH_STATUS, TRANSFERRED_STATUS, ORG_ID, and the WHO audit columns.
• ARPT_SQL_FUNC_UTIL (package) — supplies GET_LOOKUP_MEANING, a SQL-callable function invoked as GET_LOOKUP_MEANING ('AR_PROCESS_STATUS', IB.TRANSFERRED_STATUS) to produce the TRANSFERRED_STATUS_M column.
• AR_INTEREST_BATCHES_PKG (package) — supplies GET_BATCH_AMOUNT, invoked as GET_BATCH_AMOUNT(IB.INTEREST_BATCH_ID) to produce the BATCH_AMOUNT column.

Because the view calls a PL/SQL function per row, it carries a per-row execution cost that is absent from a simple table projection. This is relevant when the view is used inside large reporting queries or concurrent program extracts.

Key Columns

• INTEREST_BATCH_ID — primary identifier of the interest batch; the key passed to GET_BATCH_AMOUNT.
• BATCH_NAME — user-assigned name of the interest batch.
• TRANSFERRED_STATUS — stored lookup code (AR_PROCESS_STATUS lookup type) indicating the batch's processing state.
• TRANSFERRED_STATUS_M — decoded, translated meaning of TRANSFERRED_STATUS, resolved at query time.
• BATCH_STATUS — status flag of the batch itself.
• CALCULATE_INTEREST_TO_DATE — the date through which interest is calculated for the batch.
• GL_DATE — accounting date associated with the batch.
• BATCH_AMOUNT — total interest amount for the batch, computed by AR_INTEREST_BATCHES_PKG.GET_BATCH_AMOUNT.
• ORG_ID — operating unit identifier supporting Multi-Org filtering.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.
• OBJECT_VERSION_NUMBER — optimistic locking column.

Common Use Cases and Queries

The view is used to report on interest batch processing status, to reconcile batch amounts by operating unit, and as a source for custom concurrent programs or integrations that need decoded status text. A typical status-driven query is:

SELECT interest_batch_id,
       batch_name,
       transferred_status,
       transferred_status_m,
       batch_status,
       gl_date,
       batch_amount,
       org_id
FROM   apps.ar_interest_batches_v
WHERE  transferred_status_m = 'Complete'
ORDER  BY creation_date DESC;

Because TRANSFERRED_STATUS_M is a function-derived column, filtering on the stored code is more efficient and index-friendly:

SELECT interest_batch_id, batch_name, transferred_status_m, batch_amount
FROM   apps.ar_interest_batches_v
WHERE  transferred_status = :p_status
AND    org_id = :p_org_id;

For a multi-organization summary of batch amounts by status:

SELECT org_id,
       transferred_status_m,
       COUNT(*)        batch_count,
       SUM(batch_amount) total_interest
FROM   apps.ar_interest_batches_v
GROUP  BY org_id, transferred_status_m;

All queries should be executed against the APPS schema or a synonym with appropriate grants, and should apply the ORG_ID predicate to respect Multi-Org security.