Search Results xdp_adapter_admin_reqs_u1

Overview

XDP.XDP_ADAPTER_ADMIN_REQS is a transactional table in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments, owned by the XDP schema. It serves as the repository for maintenance requests directed at adapter instances. Specifically, it defines the lifecycle operations that may be scheduled or executed against a registered adapter channel, including STARTUP, SHUTDOWN, SUSPEND, RESUME, DISCONNECT, and CONNECT. Beyond one-time requests, the table supports periodic maintenance by storing a request frequency, allowing recurring administration jobs to be queued and processed at defined intervals.

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. From a Data Vault modeling perspective, the provided metadata classifies this object heuristically as standalone, meaning it is not treated as a hub, link, or satellite. This classification is a suggestion derived from FK structure rather than a mandate, and the table's centralized REQUEST_ID key effectively behaves like a transaction hub for adapter administration activity.

Key Information Stored

The most significant columns capture the identity, nature, timing, and ownership of each maintenance request:

• REQUEST_ID — NUMBER; the surrogate primary key (XDP_ADAPTER_ADMIN_REQS_PK) and the single unique business-key candidate, indexed by XDP_ADAPTER_ADMIN_REQS_U1.
• CHANNEL_NAME — VARCHAR2(40); identifies the adapter instance against which the request is submitted.
• REQUEST_TYPE — VARCHAR2(40); the operation being requested (suspend/resume, shutdown/startup, disconnect/connect).
• REQUEST_DATE — DATE; the date and time the request is scheduled for processing.
• REQUEST_FREQUENCY — NUMBER; defines how often the request recurs.
• REQUESTED_BY_USER — VARCHAR2(40); the submitting user, including the internal SYSTEM account. Requests submitted by SYSTEM are treated as internal and cannot be modified by users.
• JOB_ID — NUMBER; the job ID of the adapter administration request, linking to concurrent job infrastructure.
• FE_ID — foreign key to XDP_FES.
• ERROR_REF_ID — foreign key to XDP_DQ_EXCEPTIONS.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS; used in hosted environments.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO columns for audit tracking.

Common Use Cases and Queries

Administrators and support analysts query this table to audit scheduled and executed adapter maintenance. A typical pattern lists pending requests ordered by schedule:

• Pending maintenance view: SELECT REQUEST_ID, CHANNEL_NAME, REQUEST_TYPE, REQUEST_DATE FROM XDP_ADAPTER_ADMIN_REQS WHERE REQUEST_DATE >= SYSDATE ORDER BY REQUEST_DATE;
• Internal vs. user requests: filter REQUESTED_BY_USER = 'SYSTEM' to isolate system-generated jobs that cannot be edited.
• Recurring jobs: WHERE REQUEST_FREQUENCY IS NOT NULL to identify periodic administration.
• Exception tracing: join ERROR_REF_ID to XDP_DQ_EXCEPTIONS to diagnose failed adapter operations.

Reporting use cases include adapter availability trending by CHANNEL_NAME and REQUEST_TYPE, count summaries of startup/shutdown cycles per channel, and auditing of who scheduled maintenance across environments.

Related Objects

The following objects are most significant in relation to this table:

• XDP.XDP_FES — joined via FE_ID; identifies the adapter/FE context.
• XDP.XDP_DQ_EXCEPTIONS — joined via ERROR_REF_ID for failure diagnostics.
• FND_SECURITY_GROUPS — joined via SECURITY_GROUP_ID in hosted deployments.
• FND_CONCURRENT_REQUESTS / FND_CONCURRENT_PROGRAMS — indirectly related through JOB_ID for job scheduling context.
• XDP_ADAPTER_ADMIN_REQS_PK / XDP_ADAPTER_ADMIN_REQS_U1 — the primary key constraint and unique index enforcing REQUEST_ID.