Search Results concurrent_period_id




Overview
Explore in AI Chat

Overview

The FND_CONC_RELEASE_PERIODS table is a core data object within the Application Object Library (FND) module of Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. Owned by the APPLSYS schema, it serves as the master repository for defining concurrent periods, which are essential components for building Advanced Schedules in the Concurrent Processing framework. These periods represent specific, named time intervals (e.g., "Month-End," "Quarterly Close") that can be logically grouped and referenced when scheduling complex, recurring concurrent requests. The table's structure enforces data integrity through primary and foreign key constraints, linking it to fundamental EBS entities like users and supporting multilingual capabilities via its associated translation table.

Key Information Stored

The table stores the definitional attributes for each concurrent period. Its structure is anchored by a composite primary key consisting of APPLICATION_ID and CONCURRENT_PERIOD_ID. The APPLICATION_ID ties the period to a specific product application, while CONCURRENT_PERIOD_ID is the unique internal identifier. A separate unique key constraint on APPLICATION_ID and CONCURRENT_PERIOD_NAME ensures period names are unique within an application. Other critical columns include CONCURRENT_PERIOD_NAME for the user-defined name, and standard EBS WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) for auditing. The table's relationship with FND_LOGINS and FND_USER via foreign keys on the WHO columns is explicitly documented in the provided metadata.

Common Use Cases and Queries

This table is primarily accessed for administrative configuration, troubleshooting, and reporting on Advanced Schedules. Common scenarios include auditing period definitions, identifying periods used in specific schedules, and cleaning up orphaned records. A typical query retrieves all periods for an application, often joining with the translation table (FND_CONC_RELEASE_PERIODS_TL) for the user-language name.

  • Listing All Periods for an Application: SELECT p.concurrent_period_name, p.creation_date, u.user_name AS created_by FROM apps.fnd_conc_release_periods p, fnd_user u WHERE p.application_id = :app_id AND p.created_by = u.user_id ORDER BY 1;
  • Finding Periods in a Specific Schedule: Queries often join through FND_CONC_REL_DISJ_MEMBERS, which links periods to schedule definitions.
  • Auditing and Maintenance: Administrators may run scripts to identify periods not referenced in any active schedule or to synchronize data after migrations.

Related Objects

FND_CONC_RELEASE_PERIODS is central to the Advanced Schedules architecture and has several key dependencies, as outlined in the metadata.

  • FND_CONC_RELEASE_PERIODS_TL: The translation table that stores the user-viewable name of the period in multiple languages.
  • FND_CONC_REL_DISJ_MEMBERS: A junction table that associates a period (via PERIOD_APPLICATION_ID and PERIOD_ID) with a schedule definition, indicating its membership in a disjunction (an "OR" group) within an Advanced Schedule.
  • FND_USER and FND_LOGINS: Standard EBS tables referenced via foreign key for the CREATED_BY, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN columns.