Results for “complex_rule_id”

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

Overview

FND_CONCURRENT_COMPLEX_RULES is a configuration table in the Oracle E-Business Suite Application Object Library (FND) that stores complex rules used to specialize concurrent managers. In Oracle EBS 12.1.1 and 12.2.2, concurrent managers process large volumes of concurrent requests submitted by users, and these managers must be directed to handle requests selectively based on combinations of criteria. Complex rules provide this selectivity by defining multi-condition logic that determines which requests a given manager, or set of managers, can process.

The table resides in the APPLSYS schema and is owned by the FND - Application Object Library product. Each row defines a named complex rule header, which is then decomposed into individual rule line conditions in the child table FND_CONCURRENT_COMPLEX_LINES. The combination of a rule header with its lines allows administrators to construct expressions such as "run only requests from this application and this program for this user group."

From a Data Vault modeling perspective, the mined relationship structure classifies this object as hub-leaning. It functions as a central identity anchor for complex rules, identified by a stable business key (application plus rule name) and referenced by dependent objects that carry the detailed qualifying conditions and queue content assignments.

Key Information Stored

The table contains nine documented columns. The most important are described below.

• APPLICATION_ID — Identifies the application that owns the complex rule. This column participates in both the primary key and the unique business key, and it is a foreign key to FND_APPLICATION.
• COMPLEX_RULE_ID — The surrogate identifier for the rule header. Together with APPLICATION_ID it forms the primary key FND_CONC_COMPLEX_RULES_PK.
• COMPLEX_RULE_NAME — The user-visible name of the rule. With APPLICATION_ID this forms the unique business key FND_CONC_CONCURRENT_COMPLEX_RULE_U2, making the pair (APPLICATION_ID, COMPLEX_RULE_NAME) the primary business-key candidate. A second unique index, FND_CONCURRENT_COMPLEX_RULE_U1, is defined on (APPLICATION_ID, COMPLEX_RULE_ID).
• DESCRIPTION — Free-text explanation of the rule's purpose, useful for administrators auditing manager configuration.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard FND audit columns recording who created and last modified each rule, and when.

Note that the actual conditional logic of a complex rule is not stored here; it is held in FND_CONCURRENT_COMPLEX_LINES, which references this table through (APPLICATION_ID, COMPLEX_RULE_ID).

Common Use Cases and Queries

Complex rules are typically inspected or audited when concurrent manager behavior must be explained, when tuning throughput, or when troubleshooting why a request is not being picked up. Reporting queries commonly join the rule header to the line table and to FND_CONCURRENT_QUEUE_CONTENT, which assigns rule content to a queue.

A representative query to list rules for an application:

SELECT r.complex_rule_id, r.complex_rule_name, r.description
FROM   apps.fnd_concurrent_complex_rules r
WHERE  r.application_id = :app_id
ORDER BY r.complex_rule_name;

A join to retrieve lines for each rule:

SELECT r.complex_rule_name, l.*
FROM   fnd_concurrent_complex_rules r,
       fnd_concurrent_complex_lines l
WHERE  r.application_id = l.application_id
AND    r.complex_rule_id = l.complex_rule_id;

Administrators also use these rows alongside FND_CONCURRENT_QUEUE_CONTENT to verify which rules are attached to which concurrent queues. Because rule names are unique per application, UI-based navigation and API calls typically locate rules by (APPLICATION_ID, COMPLEX_RULE_NAME).

Related Objects

• FND_APPLICATION — Referenced by APPLICATION_ID; supplies the owning application.
• FND_CONCURRENT_COMPLEX_LINES — Child table referencing (APPLICATION_ID, COMPLEX_RULE_ID); holds the individual rule conditions.
• FND_CONCURRENT_QUEUE_CONTENT — References the rule through TYPE_APPLICATION_ID and TYPE_ID, associating rule content with a concurrent queue.
• FND_CONCURRENT_QUEUES — The queues whose membership is specialized by these rules.
• FND_CONCURRENT_PROGRAMS and FND_USER — Frequently qualified by rule lines when defining request restrictions.
• FND_CONCURRENT_MANAGERS — The managers whose work assignment depends on the associated queue content.