Search Results fnd_concurrent_complex_rules




Overview
Explore in AI Chat

Overview

The FND_CONCURRENT_COMPLEX_RULES table is a core Application Object Library (FND) table within the Oracle E-Business Suite (EBS) architecture, specifically for releases 12.1.1 and 12.2.2. It serves as the master definition repository for complex rules, which are advanced criteria used to specialize the behavior of concurrent managers. These rules enable administrators to define sophisticated logic for controlling how concurrent requests are assigned and processed by specific managers or manager groups, going beyond basic classification by program or request type. The table is owned by the APPLSYS schema and is integral to the concurrent processing subsystem's configuration and operational control.

Key Information Stored

The table stores the metadata that defines each complex rule. Its structure, as indicated by the primary and unique keys, centers on two critical identifiers. The APPLICATION_ID column links the rule to its owning application via a foreign key relationship to FND_APPLICATION. The COMPLEX_RULE_ID is the primary system identifier, while the COMPLEX_RULE_NAME provides a unique, human-readable name within the application context. While the specific descriptive columns are not detailed in the provided metadata, such a table typically includes fields for an enabled flag, a description, creation and last update dates, and potentially the rule type or class. The actual conditional logic of the rule is stored in the related child table, FND_CONCURRENT_COMPLEX_LINES.

Common Use Cases and Queries

This table is primarily accessed for configuration, auditing, and troubleshooting complex manager specialization. Common operational scenarios include identifying all defined complex rules within the system or for a specific application to review specialization logic. Administrators may query this table to diagnose why a particular concurrent request was picked up or excluded by a specialized manager. A typical reporting query would join FND_CONCURRENT_COMPLEX_RULES with FND_APPLICATION to get the application name and with FND_CONCURRENT_COMPLEX_LINES to summarize the rule's conditions.

  • Listing all complex rules: SELECT rule.COMPLEX_RULE_NAME, app.APPLICATION_NAME FROM APPLSYS.FND_CONCURRENT_COMPLEX_RULES rule, FND_APPLICATION app WHERE rule.APPLICATION_ID = app.APPLICATION_ID;
  • Finding rules referenced by a specific manager: SELECT rule.COMPLEX_RULE_NAME FROM FND_CONCURRENT_COMPLEX_RULES rule, FND_CONCURRENT_QUEUE_CONTENT content WHERE content.TYPE_APPLICATION_ID = rule.APPLICATION_ID AND content.TYPE_ID = rule.COMPLEX_RULE_ID AND content.CONCURRENT_QUEUE_ID = [QUEUE_ID];

Related Objects

The FND_CONCURRENT_COMPLEX_RULES table is central to a key relationship hierarchy within concurrent processing. It is a parent table to FND_CONCURRENT_COMPLEX_LINES, which stores the individual condition lines that compose the full rule logic. It is referenced by FND_CONCURRENT_QUEUE_CONTENT, which associates these rules (and other object types) with specific concurrent manager queues to implement the specialization. The table also enforces referential integrity with FND_APPLICATION via its APPLICATION_ID foreign key, ensuring every rule is linked to a valid application.