Results for “alr_scheduled_programs”

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

Overview

The ALR_SCHEDULED_PROGRAMS view is a legacy compatibility object owned by the APPS schema in Oracle E-Business Suite, registered under the Alert (ALR) product. Its ETRM record carries the descriptive note "- Retrofitted," indicating that the object was reconstructed during an upgrade or migration cycle to preserve the expected data contract for dependent Alert Manager components after the underlying file-based or obsolete implementation was retired.

Despite the "scheduled programs" name, the view does not store execution schedules. It presents a curated enumeration of the specific concurrent programs and concurrent queue entries that the Alert Manager product treats as schedulable entities, normalized into the column shape that legacy ALR code paths expect. In this sense it functions as a lookup or reference view rather than a transactional reporting source. It is most often encountered indirectly, when a search on CONCURRENT_PROGRAM_ID surfaces it as one of the many APPS-level objects that expose that identifier for Alert-related processing.

Underlying Base Objects

Per the documented ETRM 12.2.2 metadata, the view is defined over two referenced base objects:

• FND_CONCURRENT_PROGRAMS_VL (VIEW) — the multi-language translation view over FND_CONCURRENT_PROGRAMS, supplying program definitions in the current session language.
• FND_CONCURRENT_QUEUES (SYNONYM) — the synonym resolving to the concurrent queue definition table used by the concurrent managers.

The view body is a UNION ALL of two branches. The first branch selects from FND_CONCURRENT_PROGRAMS_VL where APPLICATION_ID equals 160 (the ALR application identifier) and CONCURRENT_PROGRAM_NAME is restricted to the literal short names 'ALEPPE' and 'ALPPIM'. The second branch selects from FND_CONCURRENT_QUEUES where APPLICATION_ID equals 0 and CONCURRENT_QUEUE_ID equals 1, mapping the standard concurrent queue into the same column layout and stamping it with a constant product tag of 'FND'.

Key Columns

• APPLICATION_ID — the owning application of the program or queue. Returns 160 for the Alert programs and 0 for the queue branch.
• CONCURRENT_PROGRAM_ID — the concurrent program identifier for ALR-sourced rows, and the concurrent queue identifier (CONCURRENT_QUEUE_ID) for the queue branch, since the UNION aligns these into a single column.
• CONCURRENT_PROGRAM_NAME — the internal short name, such as ALEPPE, ALPPIM, or the literal 'ICM' contributed by the queue branch.
• USER_CONCURRENT_PROGRAM_NAME — the translated user-facing program name, or the concurrent queue name for the queue row.
• APPLICATION_SHORT_NAME — a literal tag ('ALR' or 'FND') identifying which branch produced the row.

Common Use Cases and Queries

Typical usage is diagnostic and integration-oriented: resolving a CONCURRENT_PROGRAM_ID back to a schedulable Alert entity, confirming which ALR programs are recognized by the Alert subsystem, or driving custom code that must mirror the legacy Alert scheduling list.

A simple listing of all schedulable entries:

• SELECT application_short_name, concurrent_program_id, concurrent_program_name, user_concurrent_program_name FROM apps.alr_scheduled_programs ORDER BY application_short_name, concurrent_program_id;

Resolving a specific program identifier, the pattern implied by the original search term:

• SELECT concurrent_program_name, user_concurrent_program_name FROM apps.alr_scheduled_programs WHERE concurrent_program_id = :program_id;

Because the view joins only definition-level objects, queries against it are inexpensive and safe for read-only reporting. Callers should note that CONCURRENT_PROGRAM_ID is polymorphic across the UNION and that no row exists for programs outside the hardcoded ALR set, so this view must not be used as a general concurrent program registry.