Results for “fnd_conc_stat_periods”

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

Overview

FND_CONC_STAT_PERIODS is a configuration table in the Oracle E-Business Suite Application Object Library (FND) schema, owned by APPLSYS. It stores the period definitions that govern how the Concurrent Manager collects and retains concurrent request run-time statistics. Concurrent processing statistics are the raw input for the Concurrent Managers form and for the "Concurrent Processing" system profile-driven diagnostic reports that help administrators tune manager workload, worker counts, and throughput.

From a Data Vault modeling perspective, the mined FK structure classifies this object as standalone, meaning it neither acts as a hub of shared business keys nor as a link between entities. It is best treated as a reference or code-set table whose business key (VALUE) uniquely identifies a statistics period. The heuristic classification is a modeling suggestion rather than a documented fact.

Key Information Stored

The table contains eight documented columns. The most significant are:

• VALUE — The single business-key column. It is enforced by both the primary key FND_CONC_STAT_PERIODS_PK and the unique index FND_CONC_STAT_PERIODS_U1, confirming it as the natural identifier of each statistics period.
• ROTATION — Controls how frequently collected statistics are rotated or purged, supporting retention policy configuration.
• ROTATE_DATE — The date on which the next rotation is scheduled to occur.
• CREATION_DATE, CREATED_BY — Standard WHO columns capturing the row's creation audit trail.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO columns capturing the most recent modification and the login session responsible for it.

Because VALUE is both the primary key and the sole unique business key, no separate surrogate column is documented; VALUE serves the surrogate role in practice.

Common Use Cases and Queries

Administrators and DBAs query this table to verify which statistics periods are configured and when the next rotation will occur. A typical inspection query is:

• SELECT value, rotation, rotate_date FROM applsys.fnd_conc_stat_periods ORDER BY value;

Reporting scenarios include auditing retention policy, correlating rotation dates with purge jobs in FND_CONC_STAT, and validating configuration after a clone or upgrade between 12.1.1 and 12.2.2. Joining to concurrent request statistics lets you attribute behavior to the active period:

• SELECT s.period, s.request_id, p.rotate_date FROM fnd_conc_stat s, fnd_conc_stat_periods p WHERE s.period = p.value;

These queries inform capacity tuning, purge scheduling, and troubleshooting of performance degradation in the concurrent manager tier.

Related Objects

The mined relationship data classifies FND_CONC_STAT_PERIODS as standalone, so no foreign keys were detected in the ETRM metadata. Related objects are therefore identified by functional dependency. The primary consumers are:

• FND_CONC_STAT — Stores individual concurrent request statistics; its period column corresponds to FND_CONC_STAT_PERIODS.VALUE.
• FND_CONC_STAT_SUMMARY — Aggregated statistics keyed by reporting period.
• FND_CONCURRENT_REQUESTS — Request header rows whose durations feed the statistics.
• FND_CONCURRENT_PROGRAMS and FND_CONCURRENT_QUEUES — Define the programs and managers being measured.
• FND_CONC_PURGE and related purge/rotation routines — Consumer logic driven by ROTATION and ROTATE_DATE.

Collectively these objects form the concurrent statistics subsystem that this table configures.