Search Results fnd_conc_program_serial_u1




Overview
Explore in AI Chat

Overview

APPLSYS.FND_CONCURRENT_PROGRAM_SERIAL is a seed data table in the Oracle E-Business Suite that stores information about incompatible concurrent programs — programs that must not execute simultaneously on the same logical database. Each row identifies a concurrent program and another concurrent program that is incompatible with it, and this relationship may be reflexive when a program is defined as incompatible with itself. The table records a directional pairing, so Oracle Application Object Library (AOL) creates two reciprocal rows for every incompatible pair (A → B and B → A), while a self-incompatible program requires only a single row. Oracle AOL consults this table at runtime to enforce the serialization rules that prevent conflicting programs from running together. The object resides in the APPS_TS_SEED tablespace, which is characteristic of seed data replicated across environments. From a heuristic Data Vault modeling perspective, this table is best classified as a link — it captures an association between two instances of the concurrent program reference entity rather than describing either program itself. It is owned by APPLSYS and carries FND design data under the internal name FND.FND_CONCURRENT_PROGRAM_SERIAL.

Key Information Stored

The table contains 14 documented columns. The most significant are the four identifier columns that together define the incompatibility relationship:

These four columns form both the primary key FND_CONC_PROGRAM_SERIAL_PK and the leading columns of the unique index FND_CONC_PROGRAM_SERIAL_U1, which adds ZD_EDITION_NAME as the trailing column. The business-key candidate is therefore the full four-column program pair. Standard Who columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN — provide audit lineage. UPDATE_SECURITY_GROUP_ID is retained but is not currently used. Additional classification columns RUNNING_TYPE, TO_RUN_TYPE, and INCOMPATIBILITY_TYPE further qualify the relationship, and ZD_EDITION_NAME supports Edition-Based Redefinition, enabling multiple editions of concurrent program definitions to coexist in 12.2.

Common Use Cases and Queries

Administrators and developers query this table to audit incompatibility definitions before submitting request sets, diagnosing why a program is waiting on a conflicting job, or migrating serialization rules between instances. A typical pattern retrieves all programs incompatible with a given program:

  • SELECT running_concurrent_program_id, to_run_concurrent_program_id FROM fnd_concurrent_program_serial WHERE running_application_id = :app_id AND running_concurrent_program_id = :prog_id;
  • Join to FND_CONCURRENT_PROGRAMS twice (aliased) to resolve program user names on both sides of the link.
  • Group by running_concurrent_program_id to count how many incompatible partners each program declares.
  • Filter on incompatibility_type or running_type to report only specific exclusion categories.

Reporting use cases include pre-upgrade validation of serialization rules, impact analysis when retiring a concurrent program, and reconciliation of seed data across environments.

Related Objects

The most significant dependent objects are those directly referenced through the documented foreign keys and the program definitions themselves:

  • FND_CONCURRENT_PROGRAMS — referenced twice, via RUNNING_APPLICATION_ID and TO_RUN_APPLICATION_ID, resolving both sides of the pair.
  • FND_CONCURRENT_PROGRAM_SERIAL_PK / FND_CONC_PROGRAM_SERIAL_U1 — the primary key and unique index enforcing pair uniqueness.
  • FND_CONCURRENT_REQUESTS — the runtime requests whose scheduling is governed by these serialization rules.
  • FND_CONCURRENT_PROGRAM_ELEMENTS and the concurrent program definition forms — context for the referenced programs.
  • FND_APPLICATION — resolves the application identifiers used in the four key columns.

Together these objects allow administrators to trace and maintain the incompatibility graph that Oracle AOL enforces during concurrent processing.