Search Results fnd_conc_program_serial_pk

Overview

The FND_CONCURRENT_PROGRAM_SERIAL table resides in the APPLSYS schema and belongs to the FND - Application Object Library product within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the definition of incompatible concurrent programs — the configuration that governs which concurrent programs may not execute at the same time. When a user submits a concurrent request, the Concurrent Manager consults this table to determine whether a program is currently running that conflicts with the requested program, and if so, the request is either held, deferred, or allowed based on the incompatibility type defined here.

From a data modeling perspective, the metadata's heuristic Data Vault classification for this object is link. This reflects the table's structure: it does not describe a distinct business entity on its own but rather captures a many-to-many relationship between concurrent programs — a "running" program and a "to run" program — each identified by the composite of application ID and concurrent program ID. The link classification is a modeling suggestion derived from the foreign key topology, where both sides of the relationship resolve to FND_CONCURRENT_PROGRAMS.

Key Information Stored

The table contains 14 documented columns. The most operationally significant are the four columns forming the primary key and unique business key:

• RUNNING_APPLICATION_ID — Application ID of the program that is currently executing; the first component of the running side.
• RUNNING_CONCURRENT_PROGRAM_ID — Concurrent program ID of the executing program. Together with RUNNING_APPLICATION_ID it identifies the running program.
• TO_RUN_APPLICATION_ID — Application ID of the program attempting to run.
• TO_RUN_CONCURRENT_PROGRAM_ID — Concurrent program ID of the program attempting to run. Together with TO_RUN_APPLICATION_ID it identifies the target program.
• RUNNING_TYPE and TO_RUN_TYPE — Qualify the nature of each side of the incompatibility relationship.
• INCOMPATIBILITY_TYPE — Controls how the conflict is enforced (for example, whether the target request is held outright or deferred).
• UPDATE_SECURITY_GROUP_ID — Security group context for the row.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns.
• ZD_EDITION_NAME — Editioning column supporting the EBR (Edition-Based Redefinition) model in 12.2.2.

The surrogate primary key is FND_CONC_PROGRAM_SERIAL_PK, defined over the four relationship columns (RUNNING_APPLICATION_ID, RUNNING_CONCURRENT_PROGRAM_ID, TO_RUN_APPLICATION_ID, TO_RUN_CONCURRENT_PROGRAM_ID). A second unique index, FND_CONC_PROGRAM_SERIAL_U1, extends the same four columns with ZD_EDITION_NAME, serving as the business-key candidate across editions.

Common Use Cases and Queries

Administrators and developers query this table to audit or modify incompatibility rules. A typical pattern resolves both sides of the relationship to program names:

SELECT rcp.user_concurrent_program_name AS running_program,
       tcp.user_concurrent_program_name AS blocked_program,
       serial.incompatibility_type
FROM   fnd_concurrent_program_serial serial,
       fnd_concurrent_programs_vl rcp,
       fnd_concurrent_programs_vl tcp
WHERE  rcp.concurrent_program_id = serial.running_concurrent_program_id
AND    rcp.application_id       = serial.running_application_id
AND    tcp.concurrent_program_id = serial.to_run_concurrent_program_id
AND    tcp.application_id       = serial.to_run_application_id;

Reporting use cases include identifying all programs blocked by a high-impact program, reconciling incompatibility configurations migrated between environments, and troubleshooting requests stuck in a pending or held state due to a conflicting run. Concerned responses are frequently automated or reverse-engineered into FNDLOAD configuration files for migration.

Related Objects

• FND_CONCURRENT_PROGRAMS — The primary referenced table; joined twice on RUNNING_APPLICATION_ID/RUNNING_CONCURRENT_PROGRAM_ID and TO_RUN_APPLICATION_ID/TO_RUN_CONCURRENT_PROGRAM_ID.
• FND_CONCURRENT_PROGRAMS_VL — The translated view used to surface user-facing program names in reports.
• FND_CONCURRENT_REQUESTS — Holds submitted requests whose scheduling depends on incompatibility rows defined here.
• FND_CONCURRENT_QUEUES and FND_CONCURRENT_WORKER — Manage the managers and workers that enforce these rules at runtime.
• FND_APPLICATION — Resolves application IDs referenced on both sides of the relationship.
• FNDLOAD / FND_CONCURRENT_PROGRAM_SERIAL forms — Configuration utilities for exporting and maintaining incompatibility definitions.