Results for “concurrent_request_id”

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

Overview

The BEN_BATCH_MONITOR_V view is a reporting object owned by the APPS schema within the Oracle E-Business Suite, belonging to the BEN — Advanced Benefits product family. Its purpose is to consolidate the state of benefit batch processes that are executed through the Oracle Concurrent Manager. Rather than presenting raw technical identifiers alone, the view joins concurrent request data with translatable program names and lookup meanings, producing a monitoring-friendly result set that pairs each benefit action with a human-readable request status and concurrent program name.

Because benefit batch processes — such as eligibility determination, life event processing, and open enrollment maintenance — are submitted as concurrent requests, administrators require a single, denormalized source that answers the operational question: which benefit batch ran, what was it called, and did it succeed? BEN_BATCH_MONITOR_V answers that question directly. It functions primarily as a read-only reporting and integration artifact rather than a transactional object; no DML is expected against it. In a 12.1.1 or 12.2.2 environment, the view remains valid and is commonly used in custom concurrent programs, OAF/ADF-based monitoring pages, and diagnostic queries issued during benefit processing windows.

Underlying Base Objects

The ETRM-documented definition references four APPS synonyms plus the FND_GLOBAL package:

• BEN_BENEFIT_ACTIONS — the driving table, supplying the BENEFIT_ACTION_ID and the REQUEST_ID that links a benefit action to its concurrent request.
• FND_CONCURRENT_REQUESTS — supplies the REQUEST_ID, CONCURRENT_PROGRAM_ID, and the STATUS_CODE for each submitted request.
• FND_CONCURRENT_PROGRAMS_TL — the translatable concurrent programs table, providing USER_CONCURRENT_PROGRAM_NAME in the session language.
• FND_LOOKUPS — filtered on LOOKUP_TYPE = 'CP_STATUS_CODE', translating STATUS_CODE into the descriptive MEANING value.
• FND_GLOBAL — the standard EBS package used for session context resolution (such as business group and language), referenced in the documented metadata.

The join is an inner-join chain: benefit actions to concurrent requests on REQUEST_ID, then to the program definition on CONCURRENT_PROGRAM_ID, and finally to the status lookup on STATUS_CODE. Because FND_CONCURRENT_PROGRAMS_TL is language-sensitive, the program name rendered depends on the NLS environment, which is a key consideration when this view feeds multilingual reporting.

Key Columns

• BENEFIT_ACTION_ID — identifier of the benefit action associated with the batch execution.
• CONCURRENT_REQUEST_ID — the concurrent request identifier (aliased in documentation as REQUEST_ID), the primary link to the Concurrent Manager.
• CONCURRENT_PROGRAM_NAME — the user-facing concurrent program name, resolved from FND_CONCURRENT_PROGRAMS_TL.
• BUSINESS_GROUP_ID — the business group owning the benefit action, supporting multi-organization filtering.
• STATUS_CODE — the internal concurrent request status code (for example, P, R, C, E, W) sourced from FND_CONCURRENT_REQUESTS.
• STATUS — the translated lookup meaning for STATUS_CODE (Pending, Running, Normal, Error, Warning), suitable for direct display.

Common Use Cases and Queries

A typical operational query lists currently running or recently failed benefit batches:

• SELECT concurrent_program_name, concurrent_request_id, status FROM ben_batch_monitor_v WHERE status_code IN ('R','E','W');
• Restricting by business group: ... WHERE business_group_id = :p_bg_id;
• Joining to FND_CONCURRENT_REQUESTS again for timing details (actual_start_date, completion_text) not exposed by the view.
• Embedding the view in a custom concurrent program or BI Publisher report so users can monitor benefit batch health without navigating the Concurrent Manager forms.

Note that the view exposes only BENEFIT_ACTION-linked requests; unrelated concurrent requests are excluded by the inner join to BEN_BENEFIT_ACTIONS.