Results for “fnd_conc_stat_prog”

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

Overview

FND_CONC_STAT_PROG is a table owned by the APPLSYS schema in Oracle E-Business Suite, belonging to the FND (Application Object Library) product. It is documented in ETRM with status VALID and a description of "Retrofitted." The table participates in concurrent processing diagnostics and status reporting within the EBS concurrent manager architecture. Its documented physical schema in ETRM 12.2.2 lists a single column, NAME, which also serves as the table's primary key through the constraint FND_CONC_STAT_PROG_PK. The same single-column definition and primary key are mirrored in 12.1.1, indicating structural stability across both releases.

From a Data Vault modeling perspective, the mined FK/PK relationship data classifies this object as "standalone." In heuristic terms, this suggests treating FND_CONC_STAT_PROG as a hub candidate: a table whose identity rests on a single business key and which does not appear to resolve into link or satellite roles based on documented foreign key structure. No dependent foreign keys were mined, so the standalone classification should be read as a modeling suggestion rather than a strict assertion of dimensional or Data Vault semantics.

Key Information Stored

The documented metadata for FND_CONC_STAT_PROG identifies exactly one physical column. The salient characteristics are as follows:

• NAME — The sole documented column in APPLSYS.FND_CONC_STAT_PROG. It represents the business identifier for the row and simultaneously constitutes the surrogate primary key declared by FND_CONC_STAT_PROG_PK.

Because ETRM documents only one column, there is no distinction to draw between a system-generated surrogate key and an alternate business key; NAME fulfills both roles under the documented schema. In practice within the EBS concurrent manager subsystem, this column typically holds the program short name (the internal identifier such as FNDSCURS or similar concurrent program names) used to reference individual concurrent programs in status and statistics contexts. The NAME column functions as a unique index candidate by virtue of the primary key constraint, making it the natural join key for any query that correlates this table with concurrent program definitions.

Common Use Cases and Queries

Typical scenarios involving FND_CONC_STAT_PROG include validating the set of concurrent programs that the concurrent manager recognizes for status reporting, auditing which program identifiers are present in the APPLSYS schema, and joining to FND_CONCURRENT_PROGRAMS to reconcile short names. A representative query pattern is:

• SELECT NAME FROM APPLSYS.FND_CONC_STAT_PROG ORDER BY NAME;
• SELECT p.concurrent_program_name, s.name FROM APPLSYS.FND_CONC_STAT_PROG s JOIN APPLSYS.FND_CONCURRENT_PROGRAMS p ON p.concurrent_program_name = s.name;
• SELECT COUNT(*) FROM APPLSYS.FND_CONC_STAT_PROG WHERE NAME LIKE 'FND%';

Reporting use cases center on inventory reconciliation: comparing the rows here against FND_CONCURRENT_PROGRAMS and FND_CONCURRENT_REQUESTS to detect orphaned or missing program references. Because the table is small and keyed on a single column, queries against it are inexpensive and can be safely executed in production for diagnostic purposes. DBAs performing concurrent manager troubleshooting may also use it to confirm that program names being requested by the conflict resolution manager exist within this reference set.

Related Objects

The following objects are the most significant for joining and dependency analysis, grounded in the documented primary key column NAME and the broader EBS concurrent processing model:

• FND_CONCURRENT_PROGRAMS — join on CONCURRENT_PROGRAM_NAME = FND_CONC_STAT_PROG.NAME to resolve application and executable attributes.
• FND_CONCURRENT_REQUESTS — join on CONCURRENT_PROGRAM_NAME to correlate program identity with submitted requests.
• FND_CONCURRENT_PROGRAMS_TL — supplies translated user-facing names for matching program identifiers.
• FND_CONCURRENT_QUEUES — references programs through the concurrent manager configuration model.
• FND_CONCURRENT_WORKER_REQUESTS — relates worker activity to program names during runtime processing.
• FND_CP_SERVICES — concurrent processing service definitions that reference program short names.

Because the mined relationship data classifies this table as standalone with no outbound or inbound documented foreign keys, the joins above are based on matching the NAME business key rather than declared referential constraints.