Search Results fun_interface_batches

Overview

FUN_INTERFACE_GROUP_ID_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, catalogued under the FND — Application Object Library product. Its documented status is VALID in both release 12.1.1 and 12.2.2. The view serves a specific presentation purpose: it aggregates interface batch records by their source system and group identifier, then produces a single human-readable label describing the batches belonging to each group. Rather than exposing one row per interface batch, the view collapses many rows into one summary row per SOURCE and GROUP_ID combination, supplying a derived BATCHES column suitable for display in concurrent program parameters, lookups, or diagnostic queries against the interface staging tables.

Users searching for fun_interface_batches are typically investigating the underlying interface staging data. This view is the grouping companion to that table, and it is most relevant when the objective is to enumerate distinct interface groups rather than individual batch rows.

Underlying Base Objects

The view is defined over a single documented base object, FUN_INTERFACE_BATCHES, referenced as a synonym within the APPS schema. The view text confirms a straightforward aggregate query:

• It selects B.SOURCE and B.GROUP_ID from FUN_INTERFACE_BATCHES.
• It groups by B.SOURCE and B.GROUP_ID, so each output row represents one distinct source/group pairing.
• The BATCHES column is derived with a CASE expression that checks the row count within each group.

Because the view references the documented base object only through a synonym and contains no joins to other tables, its result set is entirely determined by the contents of FUN_INTERFACE_BATCHES. Any data loaded into or purged from that base table is immediately reflected in the view.

Key Columns

• SOURCE — Identifies the originating interface or feeder system for the batch record. It forms the first half of the view's grouping key and distinguishes batches that share a group identifier but originate from different sources.
• GROUP_ID — The interface group identifier assigned to the batch. It forms the second half of the grouping key and is the value most commonly consumed by downstream processing that needs to resolve a group to its batches.
• BATCHES — A derived descriptive label. The CASE expression applies two rules: when exactly one batch exists in the group, the view emits that batch's BATCH_NUMBER, defaulting to the literal string (NO BATCHES) when the batch number is null; when more than one batch exists, the view emits a count string of the form (n BATCHES). This design produces a compact, readable summary without requiring the caller to write conditional formatting logic.

Common Use Cases and Queries

The view is most useful for enumerating interface groups and providing a display label for selection lists or concurrent program parameters. Typical uses include:

• Listing all distinct source and group combinations currently present in the interface staging table.
• Determining whether a given group contains a single batch or many, without scanning batch detail rows.
• Supplying a friendly description in validation queries or diagnostics during interface troubleshooting.

A representative query is:

SELECT source, group_id, batches FROM apps.fun_interface_group_id_v ORDER BY source, group_id;

To isolate groups with multiple batches, a caller can filter on the derived column, for example WHERE batches LIKE '(% BATCHES)', which excludes single-batch groups whose label is a batch number. Because the column is computed, such filtering is applied at the view level and does not benefit from an index on the base table. All queries should be issued with the APPS schema context or an appropriate synonym and privileges.