Results for “fnd_concurrent_complex_lines”

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

Overview

FND_CONCURRENT_COMPLEX_LINES is a core configuration table in the Oracle E-Business Suite Application Object Library (FND) product, owned by the APPLSYS schema. It stores the individual lines that make up concurrent manager complex rules. A complex rule allows an administrator to group multiple concurrent programs, request classes, or Oracle database users into a single logical unit, so that the Conflict Resolution Manager can evaluate incompatibility and compatibility between concurrent requests at a higher level than individual programs. Each row in FND_CONCURRENT_COMPLEX_LINES represents one inclusion or exclusion entry within a parent complex rule.

The table operates as a child of FND_CONCURRENT_COMPLEX_RULES and participates in several foreign key relationships, making it a classic junction or association table. Based on the heuristic Data Vault classification derived from its foreign key structure, this object is best modeled as a link table, connecting complex rules to the programs, request classes, or users they reference. This classification is a modeling suggestion and should be validated against specific reporting or warehousing requirements.

Key Information Stored

The table contains 12 documented columns. The most significant are listed below.

• APPLICATION_ID – Identifies the application that owns the complex rule; part of the primary key and both unique indexes.
• COMPLEX_RULE_ID – Foreign key to FND_CONCURRENT_COMPLEX_RULES, identifying the parent rule to which the line belongs.
• COMPLEX_RULE_LINE_ID – Surrogate identifier for the individual line; part of the primary key.
• INCLUDE_FLAG – Indicates whether the referenced entity is included in or excluded from the rule.
• TYPE_CODE – Specifies the kind of entity referenced on the line (for example, program, request class, or user).
• TYPE_APPLICATION_ID – Application context of the referenced entity, used with TYPE_ID for lookups against FND_CONCURRENT_PROGRAMS and FND_CONCURRENT_REQUEST_CLASS.
• TYPE_ID – Identifier of the referenced entity; joins to FND_ORACLE_USERID, FND_USER, FND_CONCURRENT_PROGRAMS, or FND_CONCURRENT_REQUEST_CLASS depending on TYPE_CODE.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN – Standard WHO audit columns recording who created and last modified each line and when.

The surrogate primary key is FND_CONC_COMPLEX_LINES_PK (APPLICATION_ID, COMPLEX_RULE_ID, COMPLEX_RULE_LINE_ID). Two unique indexes act as business-key candidates: FND_CONCURRENT_COMPLEX_LINE_U1 mirrors the primary key columns, while FND_CONCURRENT_COMPLEX_LINE_U2 (APPLICATION_ID, COMPLEX_RULE_ID, INCLUDE_FLAG, TYPE_CODE, TYPE_APPLICATION_ID, TYPE_ID) enforces uniqueness of the actual rule content.

Common Use Cases and Queries

Administrators and developers query this table to audit complex rule composition, troubleshoot concurrent program conflicts, and migrate rule definitions between environments. A typical join returns each rule alongside its referenced entities:

• Listing all lines for a given rule: SELECT * FROM fnd_concurrent_complex_lines WHERE complex_rule_id = :rule_id;
• Resolving included programs by joining TYPE_APPLICATION_ID and TYPE_ID to FND_CONCURRENT_PROGRAMS.
• Reporting excluded users by joining TYPE_ID to FND_USER where TYPE_CODE indicates a user entry.
• Auditing recent changes using LAST_UPDATE_DATE and LAST_UPDATED_BY.

Related Objects

• FND_CONCURRENT_COMPLEX_RULES – Parent table joined on APPLICATION_ID and COMPLEX_RULE_ID.
• FND_CONCURRENT_PROGRAMS – Referenced via TYPE_APPLICATION_ID and TYPE_ID.
• FND_CONCURRENT_REQUEST_CLASS – Referenced via TYPE_APPLICATION_ID and TYPE_ID.
• FND_USER – Referenced via TYPE_ID for user-based rule lines.
• FND_ORACLE_USERID – Referenced via TYPE_ID for database user entries.