Results for “concurrent_time_period_id”

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

Overview

FND_CONCURRENT_TIME_PERIODS is a reference table in the APPLSYS schema of Oracle E-Business Suite (validated for 12.1.1 and 12.2.2). It belongs to the FND — Application Object Library product and stores concurrent processing work shifts. Each row defines a named time period during which the Oracle Concurrent Manager is permitted to process requests, using a combination of start/end clock times, day-of-week ranges, or specific calendar dates. Because the Concurrent Manager governs all concurrent program execution in EBS, this table directly influences when batch jobs, reports, and interfaces run within a given environment.

From a Data Vault modeling perspective, the mined relationship structure is classified as satellite-leaning. The table is keyed by an application-scoped surrogate identifier rather than representing a pure business hub, and it carries descriptive attributes (times, days, dates) plus foreign-key dependencies, which is consistent with a satellite attached to an application hub or process dimension.

Key Information Stored

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

• CONCURRENT_TIME_PERIOD_ID — surrogate identifier for the time period.
• APPLICATION_ID — owning application; together with CONCURRENT_TIME_PERIOD_ID forms the primary key FND_CONCURRENT_TIME_PERIODS_PK.
• CONCURRENT_TIME_PERIOD_NAME — the user-facing name of the work shift (business-key candidate via FND_CONC_TIME_PERIODS_UK1 / U2).
• START_TIME, END_TIME — the clock window during which processing is allowed.
• FROM_WEEK_DAY, TO_WEEK_DAY — the day-of-week range for recurring shifts.
• SPECIFIC_DATE — a single calendar date for non-recurring periods.
• CONCURRENT_DAYS_SPEC_METHOD — indicates how days are specified (weekday range vs. specific date).
• DESCRIPTION — free-text explanation of the shift.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard audit columns.
• ZD_EDITION_NAME — editioning support column present in 12.2.2 unique indexes.

The surrogate key is CONCURRENT_TIME_PERIOD_ID; the business-key candidates are (APPLICATION_ID, CONCURRENT_TIME_PERIOD_NAME) and, in 12.2.2, the edition-aware index variants.

Common Use Cases and Queries

Concurrent administrators use this table to audit which work shifts exist for an application, to verify that a shift covers a required processing window, and to troubleshoot why a request stayed pending because no appropriate time period was active.

• List all shifts for an application:

  SELECT concurrent_time_period_name, start_time, end_time, from_week_day, to_week_day, specific_date FROM fnd_concurrent_time_periods WHERE application_id = :app_id;

• Identify shifts restricted to specific dates:

  SELECT * FROM fnd_concurrent_time_periods WHERE concurrent_days_spec_method = ... AND specific_date IS NOT NULL;

• Join queue sizes to their governing time periods for capacity reporting:

  SELECT q.concurrent_queue_name, p.concurrent_time_period_name FROM fnd_concurrent_queue_size q JOIN fnd_concurrent_time_periods p ON q.period_application_id = p.application_id AND q.concurrent_time_period_id = p.concurrent_time_period_id;

• Audit recent changes using the standard audit columns.

  SELECT concurrent_time_period_name, last_updated_by, last_update_date FROM fnd_concurrent_time_periods ORDER BY last_update_date DESC;

Related Objects

• FND_APPLICATION — referenced by FND_CONCURRENT_TIME_PERIODS.APPLICATION_ID; identifies the owning application.
• FND_CONCURRENT_QUEUE_SIZE — references this table via PERIOD_APPLICATION_ID and CONCURRENT_TIME_PERIOD_ID; defines how many managers run during a shift.
• FND_CONCURRENT_QUEUES — queues governed by queue-size and time-period rules.
• FND_CONCURRENT_PROGRAMS — programs scheduled against the Concurrent Manager during defined shifts.
• FND_CONCURRENT_REQUESTS — request execution reflects the active time period at run time.
• FND_CONCURRENT_WORKSHIFT (related shift definition area) — complements shift scheduling configuration.

These objects collectively describe the scheduling and capacity framework within which FND_CONCURRENT_TIME_PERIODS operates.