Results for “process_id”

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

Overview

The DOM_OCS_SYNC_PENDING_DATA table is a standalone staging and synchronization table within the DOM (Document Management and Collaboration) product module of Oracle E-Business Suite. It is owned by the DOM schema and is documented as VALID in both EBS 12.1.1 and 12.2.2. The object supports integration between Oracle EBS and Oracle Content Server (OCS), holding synchronization work items that have not yet been applied to the content server or have been queued for reconciliation. From a Data Vault modeling perspective, the mined metadata classifies this table as standalone — that is, neither a strict hub, link, nor satellite. This classification is a heuristic suggestion only; functionally the object behaves as a transactional work queue where each row represents a pending synchronization event tied to a specific document, revision, and content category. Its PROCESS_FLAG and PROCESS_ID columns strongly indicate batch consumption by a concurrent program, while the presence of EBS_ROLE and OCS_ROLE reflects the role-mapping aspect of the EBS-to-OCS user synchronization process.

Key Information Stored

Each row captures one pending synchronization record. The most significant columns include:

• DOC_ID, REV_ID, CHANGE_ID — identify the document, its revision, and the specific change event pending propagation to OCS.
• CAT_ID — the content category; a foreign key to BEN_TCS_CAT, linking the pending item to the category definition that governs its OCS behavior.
• USER_ID and GRP_ID — the EBS user and group affected by the synchronization.
• EBS_ROLE and OCS_ROLE — the role mapping pair, showing which EBS role must be mirrored as which OCS role.
• PROCESS_ID and PROCESS_FLAG — the batch/process identifier and status flag used by the concurrent program to claim and complete queued rows.
• ST_DATE and ED_DATE — the effective start and end dates for the synchronization window or role assignment.
• REP_ID — the repository identifier, distinguishing target content repositories.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS WHO columns providing audit lineage.

The documented schema lists 18 columns; no surrogate primary key or unique index is identified in the metadata. Candidate business keys are therefore composite in nature, most plausibly DOC_ID + REV_ID + CHANGE_ID + CAT_ID + USER_ID, or PROCESS_ID + DOC_ID for batch scoping.

Common Use Cases and Queries

DBAs and integration developers query this table to monitor synchronization backlog and diagnose stalled OCS updates. A typical diagnostic query returns unprocessed rows grouped by repository and category:

• SELECT PROCESS_FLAG, REP_ID, CAT_ID, COUNT(*) FROM DOM.DOM_OCS_SYNC_PENDING_DATA GROUP BY PROCESS_FLAG, REP_ID, CAT_ID;
• SELECT DOC_ID, REV_ID, USER_ID, EBS_ROLE, OCS_ROLE FROM DOM.DOM_OCS_SYNC_PENDING_DATA WHERE PROCESS_FLAG IS NULL ORDER BY CREATION_DATE;
• Joining to BEN_TCS_CAT via CAT_ID to resolve category names for a pending-items report.
• Filtering by ST_DATE and ED_DATE to audit role assignment windows pushed to OCS.
• Correlating PROCESS_ID with concurrent request logs to identify failed or long-running OCS synchronization jobs.

Related Objects

• BEN_TCS_CAT — referenced via DOM_OCS_SYNC_PENDING_DATA.CAT_ID; defines the content category governing the pending item.
• DOM_OCS_SYNC_DATA / OCS synchronization staging tables — sibling DOM objects holding completed or in-flight sync records.
• FND_USER — the USER_ID column resolves to EBS users whose role mappings are being synchronized.
• FND_USER_RESP_GROUPS or PER_ROLES tables — supply the EBS_ROLE values propagated to OCS_ROLE.
• FND_CONCURRENT_REQUESTS — PROCESS_ID correlates the pending row with the concurrent program that consumes it.
• OCS integration APIs / DOM concurrent programs — the executables that read these rows and push updates to Oracle Content Server.