Results for “fnd_conflicts_domain_status”

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

Overview

FND_CONFLICTS_DOMAIN_STATUS is a table owned by the APPLSYS schema in Oracle E-Business Suite, belonging to the FND — Application Object Library product. The ETRM documentation describes the object as "Retrofitted," indicating it was introduced or adapted to support conflict-domain tracking in a later release of the 12.1.1 / 12.2.2 code line rather than being part of the original schema design. It records the status of conflict domains — logical groupings used by concurrent processing and related subsystems to determine whether conflicting requests may execute simultaneously.

From a Data Vault modeling perspective, the documented composite primary key (CD_ID, APPLICATION_ID) and the foreign key references to FND_USER and FND_LOGINS suggest a link-style classification. The table connects a conflict domain identifier to an application, while standard WHO columns provide audit lineage. This is a heuristic suggestion; the documented schema does not formally declare a Data Vault construct.

Key Information Stored

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

• CD_ID — Identifier of the conflict domain. Part of the composite primary key.
• APPLICATION_ID — Application owning or defining the conflict domain. Part of the composite primary key.
• LOCKED — Status flag indicating whether the conflict domain is currently locked, restricting conflicting concurrent requests.
• REQUEST_ID — Reference to the concurrent request associated with the domain state, enabling correlation to FND_CONCURRENT_REQUESTS.
• LAST_UPDATE_DATE — Timestamp of the most recent modification to the row.
• LAST_UPDATED_BY — User who performed the most recent update; foreign key to FND_USER.
• CREATION_DATE — Timestamp when the row was first created.
• CREATED_BY — User who created the row; foreign key to FND_USER.
• LAST_UPDATE_LOGIN — Login identifier for the session that last updated the row; foreign key to FND_LOGINS.

The surrogate primary key is defined by the constraint FND_CONFLICTS_DOMAIN_STATUS_PK over (CD_ID, APPLICATION_ID). No separate unique index is documented in the ETRM excerpt, so these two columns serve simultaneously as the business-key candidates and the physical primary key.

Common Use Cases and Queries

Typical use cases center on diagnosing concurrent manager behavior, auditing conflict-domain locking, and reporting on request conflicts per application.

• Identify domains currently locked: SELECT CD_ID, APPLICATION_ID, REQUEST_ID FROM FND_CONFLICTS_DOMAIN_STATUS WHERE LOCKED = 'Y';
• Audit recent changes with user attribution by joining to FND_USER on CREATED_BY or LAST_UPDATED_BY.
• Correlate a conflict domain lock to a concurrent request via REQUEST_ID against FND_CONCURRENT_REQUESTS.
• Report conflicts grouped by APPLICATION_ID to identify applications generating frequent conflict states.
• Trace session-level history through LAST_UPDATE_LOGIN joined to FND_LOGINS.

Related Objects

The documented foreign keys define the principal relationships:

• FND_USER — joined on CREATED_BY and LAST_UPDATED_BY.
• FND_LOGINS — joined on LAST_UPDATE_LOGIN.
• FND_CONCURRENT_REQUESTS — correlated through REQUEST_ID.
• FND_CONCURRENT_PROGRAMS and FND_APPLICATION — related through APPLICATION_ID for conflict-domain context.
• FND_CONFLICTS_DOMAIN_STATUS_PK — the primary key constraint enforcing uniqueness on (CD_ID, APPLICATION_ID).

Because the ETRM record is limited, administrators should treat these relationships as the documented core and verify any additional dependencies against the live 12.1.1 or 12.2.2 data dictionary.