Results for “fnd_conc_processor_programs_u1”

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

Overview

FND_CONC_PROCESSOR_PROGRAMS is an Application Object Library (FND) intersection table in the APPLSYS schema that defines which immediate concurrent programs are included in a concurrent program library. In Oracle EBS 12.1.1 and 12.2.2, a concurrent processor (a specialization of a concurrent manager) executes a defined library of immediate programs; this table is the association that binds a specific program to a specific processor. Because it carries only the associations between two independent entities, the metadata's heuristic Data Vault classification is link: a resolution table that joins the concurrent processor hub to the concurrent program hub, rather than a hub or satellite that stores descriptive attributes.

Key Information Stored

The table has nine documented columns. Four form the composite primary key, FND_CONC_PROCESSOR_PROGRAMS_PK, and constitute the natural business key of the association:

• PROCESSOR_APPLICATION_ID — the application owning the concurrent processor; the first component of the PK and part of the foreign key to FND_CONCURRENT_PROCESSORS.
• CONCURRENT_PROCESSOR_ID — the concurrent processor (for example, an immediate or specialized manager) to which the program is assigned; second PK component. This is the column most commonly referenced by the search term concurrent_processor_id.
• PROGRAM_APPLICATION_ID — the application owning the concurrent program; third PK component and part of the foreign key to FND_CONCURRENT_PROGRAMS.
• CONCURRENT_PROGRAM_ID — the immediate concurrent program included in the processor's library; fourth PK component.

The remaining columns are standard FND Who columns used for auditing and concurrency: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN.

Two unique indexes are documented, both covering all four key columns in differing orders: FND_CONC_PROCESSOR_PROGRAMS_U1 (PROCESSOR_APPLICATION_ID, CONCURRENT_PROCESSOR_ID, PROGRAM_APPLICATION_ID, CONCURRENT_PROGRAM_ID) and FND_CONC_PROCESSOR_PROGRAMS_U2 (CONCURRENT_PROGRAM_ID, PROGRAM_APPLICATION_ID, CONCURRENT_PROCESSOR_ID, PROCESSOR_APPLICATION_ID). These confirm the surrogate composite PK as the true business key and enforce uniqueness of each processor/program pairing, while supporting lookups from either direction.

Common Use Cases and Queries

Typical use cases include auditing which immediate programs a given concurrent manager is permitted to run, diagnosing why an immediate program fails to execute because it is missing from the processor's library, and documenting processor configuration during upgrades or cloning.

SELECT fcp.concurrent_processor_id,
       fcp.processor_application_id,
       fcp.concurrent_program_id,
       fcp.program_application_id
FROM   applsys.fnd_conc_processor_programs fcp
WHERE  fcp.concurrent_processor_id = :processor_id;

Reverse lookup — finding every processor that includes a given program — is efficient because of the U2 index:

SELECT fcp.concurrent_processor_id
FROM   applsys.fnd_conc_processor_programs fcp
WHERE  fcp.concurrent_program_id    = :program_id
AND    fcp.program_application_id   = :program_app_id;

Join patterns to resolve names generally pass through the parent tables on the composite keys (PROCESSOR_APPLICATION_ID + CONCURRENT_PROCESSOR_ID to FND_CONCURRENT_PROCESSORS, and PROGRAM_APPLICATION_ID + CONCURRENT_PROGRAM_ID to FND_CONCURRENT_PROGRAMS). Reporting on library memberships, comparing libraries across environments, and validating that requested immediate programs are correctly registered are the primary analytical uses.

Related Objects

• FND_CONCURRENT_PROCESSORS — parent of the PROCESSOR_APPLICATION_ID and CONCURRENT_PROCESSOR_ID columns; defines the processor's identity and attributes.
• FND_CONCURRENT_PROGRAMS — parent of the PROGRAM_APPLICATION_ID and CONCURRENT_PROGRAM_ID columns; defines the executable program metadata.
• FND_CONCURRENT_QUEUES — associates concurrent managers/processors that consume the program libraries defined here.
• FND_CONCURRENT_PROGRAM_SERIAL — records runtime execution of the programs referenced through this link.
• FND_CONCURRENT_REQUESTS — the runtime request table that ultimately schedules the immediate programs listed in the processor library.
• FND_CP_GSM_* and concurrency manager configuration views — surface processor/library relationships to administration forms and diagnostics.

The table is maintained through the Concurrent Managers and Concurrent Programs setup forms in Application Object Library; direct DML is not supported. In summary, FND_CONC_PROCESSOR_PROGRAMS is the link table that governs which immediate concurrent programs each concurrent processor is authorized to execute.