Results for “workitem_instance_id”

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

Overview

The XDP_ADAPTER_JOB_QUEUE table resides in the XDP schema and belongs to the Oracle E-Business Suite XDP – Provisioning product family. It functions as the job queue for the NEM (Network Element Manager) adapter layer within Oracle's provisioning infrastructure. In practical terms, the table acts as a staging and coordination mechanism that tracks discrete provisioning jobs submitted to the NEM, capturing the workflow context, foreign-key references to fulfillment and runtime entities, error linkage, and hold state for each job.

From a Data Vault modeling perspective, the metadata classifies this object heuristically as standalone. This suggests the table is best treated as an independent structure rather than as a strict hub, link, or satellite; it contains both identifying keys and descriptive attributes, and its foreign keys point outward to multiple parent entities without a single dominant business hub. Analysts modelling XDP for downstream reporting may choose to decompose the table into a hub on JOB_ID, links to the referenced entities, and a satellite for the descriptive timestamps and codes, but the source structure itself does not enforce that pattern.

Key Information Stored

The table is defined with 18 documented columns in ETRM 12.2.2. Its surrogate primary key is JOB_ID, enforced by the constraint XDP_ADAPTER_JOB_QUEUE_PK. Two unique indexes act as business-key candidates: XDP_ADAPTER_JOB_QUEUE_U1 on JOB_ID (mirroring the PK) and XDP_ADAPTER_JOB_QUEUE_U2 on the composite of WF_ITEM_TYPE and WF_ITEM_KEY, which together identify the associated Oracle Workflow item. The most significant columns include:

• JOB_ID — surrogate primary key uniquely identifying each queued adapter job.
• FE_ID — foreign key to XDP_FES, identifying the fulfillment element associated with the job.
• QUEUED_ON — timestamp at which the job was placed on the queue.
• WF_ITEM_TYPE / WF_ITEM_KEY — composite business key linking the job to its Oracle Workflow item instance.
• WF_ACTIVITY_NAME — the workflow activity responsible for the job.
• CHANNEL_USAGE_CODE — classification of the communication channel used by the adapter.
• ORDER_ID — reference to the originating order.
• WORKITEM_INSTANCE_ID — FK to XDP_FULFILL_WORKLIST, tying the job to a fulfillment work item.
• FA_INSTANCE_ID — FK to XDP_FA_RUNTIME_LIST, referencing the fulfillment action runtime instance.
• ERROR_REF_ID — FK to XDP_DQ_EXCEPTIONS, populated when the job fails and an exception is recorded.
• SYSTEM_HOLD — flag indicating whether the system has placed the job on hold.
• SECURITY_GROUP_ID — FK to FND_SECURITY_GROUPS, supporting multi-org security partitioning.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns.

Common Use Cases and Queries

Operational support teams query this table to monitor NEM provisioning throughput, identify stalled jobs, and correlate failures to data-quality exceptions. A typical pattern counts queued jobs by fulfillment element:

SELECT fe_id, COUNT(*) jobs, MIN(queued_on) oldest
FROM   xdp.xdp_adapter_job_queue
GROUP  BY fe_id;

To surface failed jobs joined to their exceptions:

SELECT j.job_id, j.order_id, e.*
FROM   xdp.xdp_adapter_job_queue j, xdp.xdp_dq_exceptions e
WHERE  j.error_ref_id = e.exception_id;

Reports frequently filter on system_hold = 'Y' to list held jobs, or join on WF_ITEM_TYPE/WF_ITEM_KEY to reconcile with WF_ITEMS in the Workflow schema. Auditors may extract CREATION_DATE ranges to reconstruct submission volume.

Related Objects

• XDP_FES — joined via FE_ID; parent fulfillment element definitions.
• XDP_FULFILL_WORKLIST — joined via WORKITEM_INSTANCE_ID; work item tracking.
• XDP_FA_RUNTIME_LIST — joined via FA_INSTANCE_ID; fulfillment action runtime state.
• XDP_DQ_EXCEPTIONS — joined via ERROR_REF_ID; data-quality failures.
• FND_SECURITY_GROUPS — joined via SECURITY_GROUP_ID; security partitioning.
• WF_ITEMS (Workflow) — correlated via WF_ITEM_TYPE/WF_ITEM_KEY.
• OE_ORDER_HEADERS_ALL — optionally joined via ORDER_ID for order context.