Search Results complex_rule_id




Overview
Explore in AI Chat

Overview

The FND_CONCURRENT_COMPLEX_LINES table is a core data object within the Application Object Library (FND) of Oracle E-Business Suite (EBS). It functions as the detailed repository for defining the constituent rules of a concurrent manager complex rule. A complex rule is a sophisticated, multi-line condition used to control which concurrent managers are eligible to run specific concurrent requests. This table stores the individual lines that collectively form the complete logic of a rule, enabling precise control over request assignment based on programs, request types, users, or Oracle user IDs. Its role is integral to the concurrent processing architecture, directly influencing workload distribution and manager specialization.

Key Information Stored

The table's structure is defined by composite keys and foreign key relationships that enforce data integrity. The primary key (FND_CONC_COMPLEX_LINES_PK) uniquely identifies a rule line using APPLICATION_ID, COMPLEX_RULE_ID, and COMPLEX_RULE_LINE_ID. The COMPLEX_RULE_ID column, central to the user's search, is the foreign key linking each line to its parent rule defined in FND_CONCURRENT_COMPLEX_RULES. Each line specifies a condition component through key columns: INCLUDE_FLAG (indicating inclusion or exclusion), TYPE_CODE (defining the entity type, such as 'P' for Program or 'U' for User), TYPE_APPLICATION_ID, and TYPE_ID (together identifying the specific entity instance, like a program or user ID).

Common Use Cases and Queries

This table is primarily queried for diagnostic, reporting, and administrative purposes related to concurrent manager behavior. A common scenario involves investigating why a specific concurrent request is assigned to, or excluded from, a particular manager. Administrators can trace this by querying the complex rule lines associated with the manager's rule set. A typical query pattern joins FND_CONCURRENT_COMPLEX_LINES to FND_CONCURRENT_COMPLEX_RULES and the relevant entity table (e.g., FND_CONCURRENT_PROGRAMS) based on the TYPE_CODE and TYPE_ID. For example, to find all program-specific lines for a given COMPLEX_RULE_ID:

  • SELECT fcl.*, fcp.concurrent_program_name
  • FROM apps.fnd_concurrent_complex_lines fcl,
  • apps.fnd_concurrent_programs fcp
  • WHERE fcl.complex_rule_id = :rule_id
  • AND fcl.type_code = 'P'
  • AND fcl.type_application_id = fcp.application_id
  • AND fcl.type_id = fcp.concurrent_program_id;

Related Objects

FND_CONCURRENT_COMPLEX_LINES maintains critical foreign key relationships with several core FND tables, as documented. Its primary parent is FND_CONCURRENT_COMPLEX_RULES. The TYPE_ID and TYPE_APPLICATION_ID columns reference different tables depending on the TYPE_CODE, creating relationships with FND_CONCURRENT_PROGRAMS, FND_CONCURRENT_REQUEST_CLASS, FND_USER, and FND_ORACLE_USERID. This design allows a single line table to conditionally reference multiple entity types. Understanding these relationships is essential for constructing accurate joins when reporting on the complete logic of a complex rule.