Search Results xdp_adapter_admin_reqs

Overview

XDP_ADAPTER_ADMIN_REQS is an Oracle E-Business Suite table owned by the XDP schema (Provisioning module). It stores all adapter-specific pending jobs — that is, administrative requests that have been queued against a particular adapter channel and are awaiting processing. In EBS 12.1.1 and 12.2.2 the table serves as the transient work queue that drives adapter-side execution: entries are created when provisioning work is submitted for an adapter, and they are updated as the request moves through its lifecycle to completion or error. Because the table is registered as a VALID object in the ETRM repository, it can be queried directly for operational troubleshooting and reconciliation, though its row population is highly volatile by design.

Heuristic Data Vault classification, mined from the foreign-key structure, suggests this object models as a standalone entity rather than a hub, link, or satellite. Practically, this means the table is best treated as an independent transactional work table whose relationships to other XDP and FND objects are enforced through individual foreign keys rather than through a normalized hub-and-link pattern.

Key Information Stored

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

• REQUEST_ID — the surrogate primary key, enforced by XDP_ADAPTER_ADMIN_REQS_PK and additionally backed by the unique index XDP_ADAPTER_ADMIN_REQS_U1. This is the single business-key candidate documented for the table and should be used as the join key in downstream queries.
• CHANNEL_NAME — the adapter channel to which the pending job belongs; drives which adapter process will pick up the request.
• REQUEST_TYPE — the category of administrative work being requested.
• FE_ID — foreign key to XDP_FES, identifying the functional entity (FE) associated with the request.
• REQUEST_STATUS — the processing state of the pending job (queued, in progress, complete, errored).
• REQUEST_DATE and REQUEST_TIMEZONE — when the job was submitted, with explicit time-zone context for cross-region scheduling.
• REQUEST_PRIORITY and REQUEST_FREQUENCY — scheduling attributes controlling ordering and recurrence.
• REQUESTED_BY_USER — the user who originated the request.
• REQUEST_PROCESSED_DATE — the timestamp at which the adapter completed the job.
• ERROR_REF_ID — foreign key to XDP_DQ_EXCEPTIONS, populated when the request fails; links the failure to the data-quality exception record.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, supporting multi-tenant/security-group filtering.
• JOB_ID — correlation to the concurrent or adapter job that executed the request.
• Standard audit columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Primary usage centers on monitoring pending adapter workload and diagnosing failures. Typical patterns include:

• Listing outstanding jobs by channel: SELECT REQUEST_ID, CHANNEL_NAME, REQUEST_TYPE, REQUEST_STATUS, REQUEST_DATE FROM XDP.XDP_ADAPTER_ADMIN_REQS WHERE REQUEST_STATUS = 'PENDING' ORDER BY REQUEST_PRIORITY;
• Identifying failed requests and joining to the exception table: SELECT r.REQUEST_ID, r.CHANNEL_NAME, e.* FROM XDP.XDP_ADAPTER_ADMIN_REQS r, XDP.XDP_DQ_EXCEPTIONS e WHERE r.ERROR_REF_ID = e.<pk>;
• Throughput reporting, measuring elapsed time between REQUEST_DATE and REQUEST_PROCESSED_DATE grouped by CHANNEL_NAME and REQUEST_TYPE.
• Reconciliation against concurrent manager output using JOB_ID, and audit reporting filtered by SECURITY_GROUP_ID for multi-org visibility.

Related Objects

• XDP_FES — joined via XDP_ADAPTER_ADMIN_REQS.FE_ID = XDP_FES.<pk>; identifies the functional entity each pending job targets.
• XDP_DQ_EXCEPTIONS — joined via ERROR_REF_ID; captures error detail for failed adapter requests.
• FND_SECURITY_GROUPS — joined via SECURITY_GROUP_ID; enforces security-group scoping in multi-tenant deployments.
• XDP_ADAPTER_ADMIN_REQS_PK / XDP_ADAPTER_ADMIN_REQS_U1 — the primary key constraint and unique index on REQUEST_ID.
• Related concurrent-manager and audit objects (FND_CONCURRENT_REQUESTS, FND_USER) are commonly joined in troubleshooting and audit queries using JOB_ID and REQUESTED_BY_USER respectively.