Search Results fnd_concurrent_programs




Overview
Explore in AI Chat

Overview

The FND_CONCURRENT_PROGRAMS table is a core Application Object Library (FND) table in Oracle E-Business Suite (EBS) that serves as the master repository for all concurrent program definitions. A concurrent program is a report, executable, or batch process that runs in the background within the EBS environment. This table stores the fundamental metadata that defines a program's executable, runtime behavior, output format, and security. It is central to the Concurrent Processing framework, enabling users to submit, schedule, and monitor long-running jobs without disrupting their interactive session. The integrity of this table is critical, as it is directly referenced by the request submission and processing engines.

Key Information Stored

The table's primary key is a composite of APPLICATION_ID and CONCURRENT_PROGRAM_ID, ensuring uniqueness across all EBS modules. A unique key on APPLICATION_ID and CONCURRENT_PROGRAM_NAME provides an alternative identifier. Essential columns define the program's operational characteristics. The EXECUTABLE_APPLICATION_ID and EXECUTABLE_ID columns form a foreign key to FND_EXECUTABLES, linking to the actual executable file or method. The CONCURRENT_PROGRAM_NAME and USER_CONCURRENT_PROGRAM_NAME (in the related _TL table) store the internal and user-facing names. Other critical columns control execution, such as ENABLED_FLAG (to activate/deactivate), QUEUE_CONTROL_FLAG, and QUEUE_METHOD_CODE for managing request queues. Output is managed via OUTPUT_FILE_TYPE and columns referencing FND_PRINTER and FND_PRINTER_STYLES for printing configurations.

Common Use Cases and Queries

This table is frequently queried for system administration, auditing, and troubleshooting. Common scenarios include identifying all programs within a specific application, diagnosing why a program is not visible, or generating an inventory of concurrent programs. A typical query joins with FND_APPLICATION and FND_EXECUTABLES to get a readable list.

  • Sample Query: List active programs for an application:
    SELECT fcp.concurrent_program_name,
    fcp.user_concurrent_program_name,
    fe.executable_name
    FROM fnd_concurrent_programs fcp,
    fnd_application fa,
    fnd_executables fe
    WHERE fcp.application_id = fa.application_id
    AND fcp.executable_application_id = fe.application_id
    AND fcp.executable_id = fe.executable_id
    AND fa.application_short_name = 'PO'
    AND fcp.enabled_flag = 'Y';
  • Use Case: Security administrators use this table to verify program definitions when assigning program responsibilities. Developers reference it to understand the parameters and setup of existing programs when creating new ones or debugging issues.

Related Objects

As a central hub, FND_CONCURRENT_PROGRAMS has extensive relationships within the FND schema and beyond. The primary foreign keys documented link it to foundational tables: FND_APPLICATION (APPLICATION_ID), FND_EXECUTABLES (EXECUTABLE_APPLICATION_ID, EXECUTABLE_ID), and FND_CONCURRENT_REQUEST_CLASS (CLASS_APPLICATION_ID, CONCURRENT_CLASS_ID). Crucially, it is the parent table for FND_CONCURRENT_REQUESTS (via PROGRAM_APPLICATION_ID, CONCURRENT_PROGRAM_ID), which stores every submitted instance of a program. Other key dependent objects include the translation table FND_CONCURRENT_PROGRAMS_TL, the alert action table ALR_ACTIONS, and the attachment tables (FND_ATTACHED_DOCUMENTS, FND_ATTACHMENT_FUNCTIONS). It is also referenced by specialized modules, as seen in FA_RX_REPORTS and FND_CONCURRENT_COMPLEX_LINES for defining report sets and complex program logic.