Results for “fnd_conc_state_lookup_types”

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

Overview

FND_CONC_STATE_LOOKUP_TYPES is a reference table in the Oracle E-Business Suite Application Object Library (FND) schema, owned by APPLSYS. It defines the sets of values — the lookup types — that categorize the various states a concurrent request or concurrent manager can occupy within the Concurrent Processing framework. Rather than hard-coding status codes, Oracle EBS stores concurrent state definitions as lookups, allowing administrators and, in some cases, patching utilities to maintain the enumeration of states that govern request lifecycle transitions.

The table sits at the top of a small hierarchical structure. Each row represents one lookup type, and child rows in FND_CONC_STATE_LOOKUPS hold the individual state values belonging to that type. The release-state comparison mechanism in FND_CONC_RELEASE_STATES also references this table, tying lookup type definitions to release-phase processing. Because the primary key is a surrogate (LOOKUP_TYPE_ID) and the descriptive name is maintained in a separate translation table (FND_CONC_STATE_LOOKUP_TYPES_TL), the table exhibits classic reference-data behavior. Under a heuristic Data Vault classification, it is satellite-leaning: it stores descriptive and audit attributes attached to a stable business key, with the lookup type itself functioning as the grain.

Key Information Stored

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

• LOOKUP_TYPE_ID — the system-generated surrogate primary key (FND_CONC_STATE_LOOKUP_TYPES_PK), also enforced by unique index FND_CONC_STATE_LOOKUP_TYPES_U1. This is the column every child table joins on.
• LOOKUP_TYPE_NAME — the business-key candidate, protected by unique constraint FND_CONC_STATE_LOOKUP_TYPES_UK. It is the human-readable identifier for the set of states.
• ENABLED_FLAG — indicates whether the lookup type is active and available for use.
• START_DATE_ACTIVE and END_DATE_ACTIVE — date-range columns that control the effective window during which the lookup type may be applied.
• OWNER_REQ_ID, OWNER_SCH_ID, and OWNER_SCH_APP_ID — ownership columns identifying the request and scheduling context under which the lookup type was created, supporting the seed-data model where lookups can be owned by a specific concurrent program or schedule.
• CREATED_BY and LAST_UPDATED_BY — standard WHO columns referencing FND_USER, recording the application user responsible for creation and last modification.
• LAST_UPDATE_LOGIN — references FND_LOGINS, capturing the login session associated with the most recent change.
• CREATION_DATE and LAST_UPDATE_DATE — audit timestamps for row creation and the most recent update.

The split between surrogate key (LOOKUP_TYPE_ID) and business key (LOOKUP_TYPE_NAME) is significant for integration work, since downstream tables persist the numeric ID rather than the name.

Common Use Cases and Queries

Typical usage centers on decoding concurrent state values in reports and diagnosing request lifecycle behavior. A common pattern joins the lookup value table back to the lookup type to resolve readable status descriptions:

• Resolving state values for a report on concurrent request completions by joining FND_CONC_STATE_LOOKUPS to this table on LOOKUP_TYPE_ID and filtering on the desired LOOKUP_TYPE_NAME.
• Auditing which lookup types are currently enabled and within their active date window, using ENABLED_FLAG, START_DATE_ACTIVE, and END_DATE_ACTIVE.
• Tracing ownership of seeded lookup types through OWNER_REQ_ID and the OWNER_SCH_ID / OWNER_SCH_APP_ID columns when investigating why a state value appears in a particular scheduling context.
• Translating the numeric identifier into a display name by joining FND_CONC_STATE_LOOKUP_TYPES_TL on LOOKUP_TYPE_ID for multilingual reporting.
• Validating referential integrity between FND_CONC_RELEASE_STATES and the lookup definitions before troubleshooting release-phase processing errors.

Because the table is small and effectively static, queries against it are inexpensive and often embedded as inline lookups in larger concurrent manager reconciliation scripts.

Related Objects

• FND_CONC_STATE_LOOKUPS — the child table holding individual state values, joined on LOOKUP_TYPE_ID.
• FND_CONC_STATE_LOOKUP_TYPES_TL — the translation table storing language-specific lookup type names, joined on LOOKUP_TYPE_ID.
• FND_CONC_RELEASE_STATES — references LOOKUP_TYPE_ID, linking lookup type definitions to release phase processing.
• FND_USER — referenced by CREATED_BY and LAST_UPDATED_BY.
• FND_LOGINS — referenced by LAST_UPDATE_LOGIN to identify the originating session.

Together these objects form the complete concurrent state reference model used throughout the FND schema.