Results for “xdp_adapter_audit”

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

Overview

The XDP_ADAPTER_AUDIT table resides in the XDP schema and belongs to the Provisioning (XDP) product family within Oracle E-Business Suite 12.1.1 and 12.2.2. It functions as the audit repository for completed administration requests issued against Adapters registered in the EBS environment. Every time an adapter administrative operation—such as a start, stop, refresh, or configuration change—reaches completion, a corresponding row is recorded in this table, preserving a historical trace of the request, its outcome, and the operator who initiated it.

From a data-modeling perspective, the heuristic Data Vault classification mined from the foreign-key structure suggests treating XDP_ADAPTER_AUDIT as a link entity. It sits between the adapter definition (XDP_ADAPTER_TYPES_B) and the concurrent-processing infrastructure (FND_CONCURRENT_QUEUES, FND_SECURITY_GROUPS), capturing the association between an adapter, the service instance it targets, and the administrative request executed against it. This classification is advisory rather than prescriptive; implementers modeling XDP data for warehousing purposes may find it useful when designing hub-and-link structures.

Key Information Stored

The table contains 23 documented columns. The surrogate primary key is ADAPTER_AUDIT_ID, enforced by the constraint XDP_ADAPTER_AUDIT_PK and reinforced by the unique index XDP_ADAPTER_AUDIT_U1, which also serves as a business-key candidate for the adapter audit record. The most operationally significant columns include:

• ADAPTER_NAME / ADAPTER_TYPE – identify the adapter and its classification; ADAPTER_TYPE carries a foreign key to XDP_ADAPTER_TYPES_B.
• REQUEST_TYPE / REQUEST_STATUS / REQUESTED_BY_USER – describe the nature of the administrative request, its disposition, and the requesting user.
• COMPLETION_DATE – timestamp marking successful or terminal completion of the audited request.
• ADAPTER_STATUS – the resulting adapter state following the request.
• CHANNEL_NAME / SERVICE_INSTANCE_ID / APPLICATION_ID – contextual routing information; APPLICATION_ID participates in a composite foreign key to FND_CONCURRENT_QUEUES along with SERVICE_INSTANCE_ID.
• CONNECT_ON_DEMAND_FLAG / MAX_IDLE_TIME_MINUTES – connection lifecycle settings applied during the request.
• CMD_LINE_OPTIONS / CMD_LINE_ARGS / LOG_FILE_NAME – execution metadata useful for troubleshooting adapter invocations.
• SECURITY_GROUP_ID – partitions the row for multi-tenant or reporting security; references FND_SECURITY_GROUPS.
• OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – standard EBS WHO columns and optimistic locking.

Common Use Cases and Queries

Typical uses include diagnosing failed adapter administration requests, auditing who changed adapter state and when, and correlating adapter activity with concurrent manager throughput. A common pattern filters recent activity by adapter:

SELECT ADAPTER_AUDIT_ID, ADAPTER_NAME, REQUEST_TYPE, REQUEST_STATUS,
       REQUESTED_BY_USER, COMPLETION_DATE
FROM   XDP.XDP_ADAPTER_AUDIT
WHERE  ADAPTER_NAME = :adapter
AND    COMPLETION_DATE >= SYSDATE - 7
ORDER BY COMPLETION_DATE DESC;

Reporting alternatives include grouping by REQUEST_STATUS to measure success rates, joining SERVICE_INSTANCE_ID and APPLICATION_ID to FND_CONCURRENT_QUEUES to identify the servicing queue, and tracing CMD_LINE_OPTIONS for execution forensics. Purge strategies commonly target rows by COMPLETION_DATE to control table growth.

Related Objects

• XDP_ADAPTER_TYPES_B – joined via ADAPTER_TYPE; defines adapter metadata.
• FND_CONCURRENT_QUEUES – joined via SERVICE_INSTANCE_ID and APPLICATION_ID; identifies the concurrent queue handling the request.
• FND_SECURITY_GROUPS – joined via SECURITY_GROUP_ID; enforces data segregation.
• XDP_ADAPTER_AUDIT_PK / XDP_ADAPTER_AUDIT_U1 – the primary and unique constraints enforcing record identity.
• FND_USER – referenced logically through REQUESTED_BY_USER for user attribution in reports.

Together these relationships position XDP_ADAPTER_AUDIT as the central audit link between adapter configuration and the EBS concurrent processing infrastructure.