Results for “fnd_concurrent_processors”

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

Overview

FND_CONCURRENT_PROCESSORS is a core Application Object Library (FND) table owned by the APPLSYS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the definitions of immediate concurrent program libraries, commonly known as concurrent processors. Each row identifies a named processor associated with an application in the E-Business Suite, providing the registration point against which concurrent queues and processor-to-program assignments are configured. In this sense, it defines the available processing "engines" that the concurrent manager infrastructure can target when executing immediate or specialized concurrent programs.

The table participates in standard EBS audit and multi-language conventions, carrying WHO columns and, in 12.2.2, an online patching edition column (ZD_EDITION_NAME). Based on the foreign key structure and given its role as an independent registry of processor definitions that is referenced by dependent tables, the Data Vault classification heuristic suggests a hub-leaning object: it holds the unique business identity of each processor and is the target of incoming references.

Key Information Stored

The table is composed of 12 documented columns. The most significant are:

• APPLICATION_ID — the owning application identifier; part of the primary key and a foreign key to FND_APPLICATION.
• CONCURRENT_PROCESSOR_ID — the surrogate identifier for the processor; with APPLICATION_ID it forms the composite primary key FND_CONCURRENT_PROCESSORS_PK.
• CONCURRENT_PROCESSOR_NAME — the user-facing name of the processor; combined with APPLICATION_ID it is a business-key candidate exposed via the unique index FND_CONCURRENT_PROCESSORS_U2.
• DESCRIPTION — free-text description of the processor's purpose.
• LIBRARY_TYPE — classifies the library implementation associated with the processor.
• LAST_REBUILT — timestamp indicating when the processor definition was last rebuilt or refreshed.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns tracking creation and modification.
• ZD_EDITION_NAME — the 12.2 online patching edition discriminator; in 12.2.2 it participates in the unique indexes U1 and U2, enabling edition-aware lookups.

Common Use Cases and Queries

Administrators and developers query FND_CONCURRENT_PROCESSORS to inventory the defined processors, to map processor names to their owning applications, and to troubleshoot assignments referenced by concurrent queues and processor programs. Typical SQL patterns include:

• Listing all processors for an application:

  SELECT concurrent_processor_id, concurrent_processor_name, description
  FROM   fnd_concurrent_processors
  WHERE  application_id = :app_id;

• Joining to FND_APPLICATION to resolve the application short name:

  SELECT p.concurrent_processor_name, a.application_short_name
  FROM   fnd_concurrent_processors p, fnd_application a
  WHERE  p.application_id = a.application_id;

• Finding processor-program mappings through FND_CONC_PROCESSOR_PROGRAMS, and queue usage through FND_CONCURRENT_QUEUES, to audit which programs run on a given processor.

These queries support reporting on concurrency configuration, migration validation between environments, and diagnosing misconfigured or orphaned processor references before patching.

Related Objects

• FND_APPLICATION — referenced by FND_CONCURRENT_PROCESSORS.APPLICATION_ID; provides the application owning the processor.
• FND_CONCURRENT_QUEUES — references this table via PROCESSOR_APPLICATION_ID and CONCURRENT_PROCESSOR_ID, linking queues to their assigned processor.
• FND_CONC_PROCESSOR_PROGRAMS — references this table via PROCESSOR_APPLICATION_ID and CONCURRENT_PROCESSOR_ID, mapping concurrent programs to processors.
• The unique indexes FND_CONCURRENT_PROCESSORS_U1 and FND_CONCURRENT_PROCESSORS_U2 enforce business-key uniqueness and support edition-aware lookups.