Search Results get_all

Overview

APPS.AR_AI_BATCH_SOURCE_V is a reporting view in the Oracle E-Business Suite Receivables module (AR). It exposes batch source definitions of type FOREIGN from the underlying batch source repository. Its defining characteristic is a UNION ALL construct that returns each qualifying batch source name twice: once with the flag GET_ALL set to 'Y' and a de-duplicated aggregate row, and once with GET_ALL set to 'N' and the individual row detail. This pattern is a common Oracle Applications technique used to support both "all values" and "specific value" LOV or parameter list behavior from a single view definition without requiring a separately maintained lookup.

The view is owned by the APPS schema and is therefore accessible to any concurrent program, form, or report that connects as APPS or that has been granted SELECT on the object. In EBS 12.1.1 and 12.2.2 the view is not an interface or staging object; it is read-only reference data used for validation, list-of-values population, and reporting on foreign-currency batch sources.

Underlying Base Objects

The view is defined over a single documented base object: the synonym RA_BATCH_SOURCES_ALL, which resolves to the Receivables batch sources table in the APPS schema. The synonym is listed in ETRM as the referenced base object, meaning the view definition is not built on a private or temporary structure — all columns originate from RA_BATCH_SOURCES_ALL.

Because the synonym points at the _ALL table, the view is multi-organization aware. The underlying table carries ORG_ID, and the view surfaces ORG_ID both directly (in the 'N' branch) and via MAX(ORG_ID) (in the 'Y' branch). Callers are expected to apply an operating-unit predicate through the standard Multi-Org views or through an explicit ORG_ID filter. There are no joins, functions, or external lookups in the view text; the only predicate is BATCH_SOURCE_TYPE = 'FOREIGN', applied in both branches of the UNION ALL.

Key Columns

• NAME — The batch source name (for example, a foreign-currency remittance or lockbox source). It is the grouping key for the aggregate branch and the primary human-readable identifier in the detail branch.
• DESCRIPTION — Free-text description of the batch source. In the 'Y' branch this is MAX(DESCRIPTION); in the 'N' branch it is the stored value.
• BATCH_SOURCE_ID — The surrogate primary key from RA_BATCH_SOURCES_ALL. In the 'Y' branch it is returned as MAX(BATCH_SOURCE_ID), which is the mechanism that collapses multiple same-named rows into one aggregate row. This is the column most frequently referenced by callers searching for "batch_source_id."
• ORG_ID — The operating unit identifier. Returned as MAX(ORG_ID) in the aggregate branch and as the literal column value in the detail branch.
• GET_ALL — A literal discriminator: 'Y' marks the aggregated "all" row, 'N' marks the per-row detail. This flag is what allows a single view to serve dual LOV semantics.

Common Use Cases and Queries

Typical uses include populating batch source list-of-values in Receivables entry forms, validating a user-supplied source during AutoInvoice or remittance import, and reporting on which foreign batch sources exist in each operating unit.

To retrieve only the "all values" pseudo-row for LOV usage:

SELECT name, description, batch_source_id, org_id
FROM   apps.ar_ai_batch_source_v
WHERE  get_all = 'Y'
AND    org_id = :p_org_id
ORDER BY name;

To resolve a specific batch source identifier from a name within an operating unit:

SELECT batch_source_id
FROM   apps.ar_ai_batch_source_v
WHERE  get_all   = 'N'
AND    name      = :p_source_name
AND    org_id    = :p_org_id;

To detect duplicate names that the aggregate branch collapses (useful before making name-based assumptions in custom code):

SELECT name, COUNT(*) row_count
FROM   apps.ar_ai_batch_source_v
WHERE  get_all = 'N'
GROUP BY name
HAVING COUNT(*) > 1;

Because the view filters to BATCH_SOURCE_TYPE = 'FOREIGN', it cannot be used to enumerate manual or other source types; those must be queried directly from RA_BATCH_SOURCES_ALL. Callers that require exchange-rate or currency attributes must join back to RA_BATCH_SOURCES_ALL on BATCH_SOURCE_ID and ORG_ID, since the view exposes no currency columns.