Search Results class_info

Overview

The view FND_CONC_RELEASE_CLASSES_VL is an Application Object Library (FND) database object owned by the APPS schema. It presents a "VL" (translated, or "value list") representation of concurrent program release classes, combining the language-independent attributes stored in the base transaction table with the language-dependent, translatable attributes stored in the corresponding translation table. Release classes govern how the Concurrent Manager schedules and resubmits concurrent programs, for example controlling the interval at which a request is automatically resubmitted after it completes.

Because it is a VL view, it automatically enforces the session language through the predicate T.LANGUAGE = USERENV('LANG'), returning exactly one row per release class in the language of the current user session. This makes it the canonical source for reporting and integration logic that needs a single, translated row for each release class. In Oracle EBS 12.1.1 and 12.2.2 it is classified as "Retrofitted," and it is read-only from an application standpoint, deriving all of its content from the underlying synonym targets.

Underlying Base Objects

The view is defined over two documented base objects, both exposed to APPS as synonyms:

• FND_CONC_RELEASE_CLASSES — the base table holding the non-translatable, language-independent columns of each release class.
• FND_CONC_RELEASE_CLASSES_TL — the translation table holding the language-dependent columns.

The join is performed on the composite key RELEASE_CLASS_ID and APPLICATION_ID, with the additional language filter on FND_CONC_RELEASE_CLASSES_TL. In the view text, alias B denotes the base table and alias T the translation table. All stored columns are taken from B except the user-facing name and description, which are drawn from T as USER_RELEASE_CLASS_NAME and DESCRIPTION. The ROW_ID column is derived from B.ROWID.

Key Columns

• APPLICATION_ID, RELEASE_CLASS_ID — the composite identifier of the release class.
• RELEASE_CLASS_NAME — the internal (development) name of the release class.
• USER_RELEASE_CLASS_NAME, DESCRIPTION — the translated, user-facing name and description from the TL table; these are the values shown in the concurrent managers and request submission windows.
• ENABLED_FLAG, START_DATE_ACTIVE, END_DATE_ACTIVE — control whether and when the class is active.
• CLASS_TYPE, CLASS_INFO — classify the release class and carry additional type-specific information.
• OWNER_REQ_ID — the request that owns the class definition where applicable.
• DATE1, DATE2 — auxiliary date columns used by release-class logic.
• RESUBMIT_INTERVAL, RESUBMIT_INTERVAL_UNIT_CODE, RESUBMIT_INTERVAL_TYPE_CODE — the interval, its unit, and its type that determine automatic resubmission cadence. These are the columns most directly relevant to the user's search term resubmit_interval.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, UPDATED_FLAG.

Common Use Cases and Queries

The view is typically queried to list enabled release classes, to review automatic resubmission settings, or to join release classes to schedule definitions for integration and diagnostics. A representative query listing resubmission configuration is:

• SELECT release_class_id, application_id, user_release_class_name, resubmit_interval, resubmit_interval_unit_code, resubmit_interval_type_code, enabled_flag FROM fnd_conc_release_classes_vl WHERE enabled_flag = 'Y';
• Filtering by application_id to scope results to a single product.
• Joining to FND_CONC_RELEASE_CLASSES or related schedule tables when the internal name is required alongside translated text.

Because the view depends on USERENV('LANG'), sessions using different language settings will see translated names accordingly, and any integration reading user-facing labels should rely on this view rather than the base table.