Results for “xdp_adapter_audit_v”

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

Overview

The XDP_ADAPTER_AUDIT_V view is an APPS-owned database view within the Oracle E-Business Suite Provisioning (XDP) product. Its documented purpose is to expose audit information about all completed administration requests for adapters. In the ETRM metadata, the object is listed as VALID and is defined in the APPS schema, which is the customary location for EBS reporting views that join transactional data to lookup-based code meanings.

Functionally, the view serves as a reporting and integration surface over the underlying adapter audit records. Because it resolves coded values into user-facing meanings through FND_LOOKUPS, it is well suited for operational dashboards, troubleshooting adapter administration activity, and reconciling adapter lifecycle events. The presence of SERVICE_INSTANCE_ID among the exposed columns makes the view directly relevant to searches involving service instance identification, since it allows adapter administration history to be correlated with a specific provisioned service instance.

Underlying Base Objects

According to the documented metadata, XDP_ADAPTER_AUDIT_V references the following base objects: FND_GLOBAL (PACKAGE), FND_LOOKUPS (VIEW), XDP_ADAPTER_AUDIT (SYNONYM), and XDP_ADAPTER_TYPE_REQ_TYPES_V (VIEW). The principal driving object is XDP_ADAPTER_AUDIT, referenced through the synonym and aliased as AUD in the view text. This table supplies the raw audit rows for completed adapter administration requests.

The view enriches these records through correlated scalar subqueries. Two of these subqueries resolve request and adapter statuses and adapter types via FND_LOOKUPS using the lookup types XDP_REQUEST_STATUS, XDP_ADAPTER_STATUS, and XDP_ADAPTER_TYPE. A further subquery retrieves the request type meaning from XDP_ADAPTER_TYPE_REQ_TYPES_V, keyed by lookup code and adapter type. FND_GLOBAL is referenced for session or context resolution typical of EBS views. The relationships are therefore straightforward: the view is a read-only projection over XDP_ADAPTER_AUDIT decorated with decoded lookup meanings.

Key Columns

The view exposes the following columns: CHANNEL_NAME, REQUEST_TYPE, REQUEST_STATUS, REQUESTED_BY_USER, ADAPTER_NAME, ADAPTER_STATUS, ADAPTER_TYPE, SERVICE_INSTANCE_ID, COMPLETION_DATE, CONNECT_ON_DEMAND_FLAG, MAX_IDLE_TIME_MINUTES, CMD_LINE_OPTIONS, CMD_LINE_ARGS, LOG_FILE_NAME, and APPLICATION_ID.

• CHANNEL_NAME identifies the channel associated with the adapter audit record.
• REQUEST_TYPE is the decoded meaning of the administration request type, resolved through XDP_ADAPTER_TYPE_REQ_TYPES_V.
• REQUEST_STATUS is the decoded request status from the XDP_REQUEST_STATUS lookup.
• REQUESTED_BY_USER records the user who submitted the request.
• ADAPTER_NAME, ADAPTER_STATUS, and ADAPTER_TYPE identify the adapter and its decoded status and type.
• SERVICE_INSTANCE_ID is the service instance identifier associated with the audit record and is central to correlating requests with provisioned instances.
• COMPLETION_DATE indicates when the request completed.
• CONNECT_ON_DEMAND_FLAG and MAX_IDLE_TIME_MINUTES describe connection and idle-time behavior.
• CMD_LINE_OPTIONS and CMD_LINE_ARGS expose command-line parameters used during the request.
• LOG_FILE_NAME points to the log file for the request; APPLICATION_ID identifies the owning application context.

Common Use Cases and Queries

Typical scenarios include auditing completed adapter administration activity, troubleshooting failures by status, and tracing all requests against a given service instance. A basic query listing recent completions might be:

SELECT CHANNEL_NAME, ADAPTER_NAME, REQUEST_TYPE, REQUEST_STATUS, COMPLETION_DATE FROM APPS.XDP_ADAPTER_AUDIT_V ORDER BY COMPLETION_DATE DESC;

To retrieve history for a specific service instance, as implied by the "service_instance_id" search:

SELECT SERVICE_INSTANCE_ID, ADAPTER_NAME, ADAPTER_STATUS, REQUEST_STATUS, COMPLETION_DATE FROM APPS.XDP_ADAPTER_AUDIT_V WHERE SERVICE_INSTANCE_ID = :service_instance_id ORDER BY COMPLETION_DATE DESC;

To isolate completed requests for a particular adapter and status, filter on ADAPTER_NAME and REQUEST_STATUS. Because the view decodes statuses through FND_LOOKUPS, filters should use the displayed meanings or join back to the lookup codes as required. All access should respect APPS schema security and the view's read-only nature.