Search Results fnd_conc_state_lookup_types




Overview
Explore in AI Chat

Overview

The FND_CONC_STATE_LOOKUP_TYPES table is a core Application Object Library table within Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It functions as a master repository for defining distinct sets of lookup values, specifically for managing concurrent processing states. Each record in this table represents a unique lookup type, which acts as a container for a related group of state codes and their meanings. This structure is fundamental to the Concurrent Manager architecture, enabling the system to categorize and interpret the status of concurrent requests and releases in a modular and translatable manner. Its role is to provide the metadata framework for state lookups, which are then populated in detail within related child tables.

Key Information Stored

The table stores metadata for each lookup type definition. The primary columns include LOOKUP_TYPE_ID, a unique system-generated identifier serving as the primary key, and LOOKUP_TYPE_NAME, a unique name for the lookup set. Standard Oracle EBS audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) track the creation and modification history of each lookup type record. While the specific descriptive meaning of each lookup type is stored in the corresponding translation table (FND_CONC_STATE_LOOKUP_TYPES_TL), this base table holds the essential structural definition that links a lookup type to its associated state values.

Common Use Cases and Queries

This table is primarily queried in conjunction with its child tables for reporting and diagnostic purposes within concurrent management. A common use case is to generate a list of all defined state lookup types and their associated meaningful values for a given language. Developers may also reference this table when customizing or extending concurrent processing functionality to understand existing state groupings. A typical diagnostic query joins the type table with its lookups and translations:

  • SELECT lt.lookup_type_name, tl.meaning, l.lookup_code
    FROM fnd_conc_state_lookup_types lt,
    fnd_conc_state_lookups l,
    fnd_conc_state_lookup_types_tl tl
    WHERE lt.lookup_type_id = l.lookup_type_id
    AND lt.lookup_type_id = tl.lookup_type_id
    AND tl.language = USERENV('LANG')
    ORDER BY lt.lookup_type_name, l.lookup_code;

Direct manipulation of data in this table via INSERT or UPDATE statements is rare and typically reserved for specific application patching or upgrade scenarios, as the data is largely seeded by Oracle.

Related Objects

As documented in the ETRM metadata, FND_CONC_STATE_LOOKUP_TYPES maintains several key relationships. It is referenced by three child tables via foreign keys on the LOOKUP_TYPE_ID column: FND_CONC_STATE_LOOKUPS (which stores the actual code-meaning pairs for each type), FND_CONC_RELEASE_STATES (which defines states for concurrent release functionality), and FND_CONC_STATE_LOOKUP_TYPES_TL (which holds the translated names and descriptions for the lookup types). Furthermore, the table references standard EBS audit tables: FND_USER for the CREATED_BY and LAST_UPDATED_BY columns, and FND_LOGINS for the LAST_UPDATE_LOGIN column. These relationships solidify its position as a central metadata table in the concurrent processing lookup hierarchy.