Search Results xdp_wf_process_coord_u1

Overview

XDP.XDP_WF_PROCESS_COORD is an Oracle E-Business Suite base table owned by the XDP schema, the workflow process coordination schema used by the ETRM (Enterprise Transaction and Reporting Manager) product family. The table stores the state required to coordinate multiple child workflow processes spawned by a single parent workflow activity. As documented in the ETRM metadata, it is designed as an enhancement to the standard Oracle Workflow ContinueFlow and WaitForFlow features, allowing a parent activity to suspend and later resume based on the completion of a known number of child processes. The object is classified as VALID, registered in FND Design Data, and is explicitly documented as intended for internal use only, meaning it is not a supported integration point for customer extensions or direct data manipulation.

Physically, the table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, and its unique index is stored separately in APPS_TS_TX_IDX. The heuristic Data Vault classification mined from the relationship structure is standalone, though the presence of a single-column primary key (WF_COORDINATION_ID) and a foreign-key-style reference to FND_SECURITY_GROUPS suggests it can be modeled as a hub-like entity for coordination events, with the who-columns and mutable counters (CHILD_PROCESS_NUM) behaving as satellite attributes. In practice, it holds transient runtime coordination state rather than master or transactional reference data.

Key Information Stored

The table contains twelve documented columns spanning workflow identity, coordination counters, and standard audit fields.

• WF_COORDINATION_ID (NUMBER) — the surrogate primary key, defined by XDP_WF_PROCESS_COORD_PK. It also serves as the business-key candidate via the unique index XDP_WF_PROCESS_COORD_U1, which is the object named in the user's search. This column identifies each coordination event.
• WF_ITEM_TYPE (VARCHAR2) — the parent workflow item type, tying the coordination record to a specific workflow definition.
• WF_ITEM_KEY (VARCHAR2, 240) — the parent workflow item key, identifying the specific runtime instance of that item type.
• WF_ACTIVITY_NAME (VARCHAR2, 40) — the parent activity that initiated the coordination, i.e., the activity that must wait or continue.
• CHILD_PROCESS_NUM (NUMBER) — the current number of child workflow processes the parent activity is coordinating with. This is the operative counter that drives the ContinueFlow/WaitForFlow logic.
• CALLBACK (VARCHAR2, 4000) — reserved for future use; documented but not currently active.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns recording insert and last-modification context.
• SECURITY_GROUP_ID (NUMBER) — used in hosted/multi-tenant environments, and the only column documented as referencing another object (FND_SECURITY_GROUPS).

Common Use Cases and Queries

Because the table is internal, the principal use cases are diagnostic and support-oriented rather than analytic. Administrators troubleshooting a workflow that appears stuck in a WaitForFlow state can query XDP_WF_PROCESS_COORD to confirm whether the expected number of children were registered. The canonical query is:

• SELECT WF_COORDINATION_ID, WF_ITEM_TYPE, WF_ITEM_KEY, WF_ACTIVITY_NAME, CHILD_PROCESS_NUM FROM XDP.XDP_WF_PROCESS_COORD WHERE WF_ITEM_TYPE = :item_type AND WF_ITEM_KEY = :item_key;
• Counting outstanding coordination rows per parent item: SELECT WF_ITEM_TYPE, WF_ITEM_KEY, WF_ACTIVITY_NAME, COUNT(*) FROM XDP.XDP_WF_PROCESS_COORD GROUP BY WF_ITEM_TYPE, WF_ITEM_KEY, WF_ACTIVITY_NAME;
• Aging analysis using CREATION_DATE to find coordination rows that have persisted longer than expected, indicating a stalled or orphaned workflow.
• Joining to FND_SECURITY_GROUPS on SECURITY_GROUP_ID in hosted environments to scope results by tenant.

Direct DML should be avoided; remediation should proceed through supported Oracle Workflow administration APIs.

Related Objects

Documented dependency information is limited. The table references no database objects other than the implicit lookup through SECURITY_GROUP_ID, and the ETRM metadata notes that it is referenced by XDP.XDP_WF_PROCESS_COORD# (the underlying object referenced by the synonym or view). Significant related objects include:

• FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID; the only documented foreign-key relationship.
• XDP_WF_PROCESS_COORD_U1 — the unique index on WF_COORDINATION_ID and the exact object named in the originating search.
• WF_ITEMS — the standard Workflow runtime item table, joined on WF_ITEM_TYPE and WF_ITEM_KEY to resolve parent item context.
• WF_ACTIVITIES / WF_PROCESS_ACTIVITIES — relate WF_ACTIVITY_NAME to the workflow definition.
• WF_ITEM_ACTIVITY_STATUSES — correlates the parent activity's runtime status with coordination state.
• WF_NOTIFICATIONS and the Workflow Engine APIs (WF_ENGINE.ContinueFlow, WF_ENGINE.WaitForFlow) — the standard features this table augments.