Results for “xdp_request_status”

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

Overview

APPS.XDP_ADAPTER_AUDIT_V is a reporting view in the Oracle E-Business Suite 12.1.1 and 12.2.2 environments, owned by the APPS schema. It presents a decoded, human-readable projection of the underlying XDP_ADAPTER_AUDIT table, which stores audit information about the adapter requests and services processed by the e-Commerce Gateway / XDP (eXtensible Data Processor) infrastructure used for inbound and outbound electronic document exchange. Rather than exposing raw lookup codes, the view resolves each status and type code to its corresponding FND_LOOKUPS meaning, and correlates request type codes to adapter types through a dedicated validation view. The result is a single denormalized result set well suited for operational monitoring, integration diagnostics, and ad hoc reporting on adapter activity.

Underlying Base Objects

The view is defined over the following documented objects:

• XDP_ADAPTER_AUDIT (referenced through a synonym) — the base audit table supplying all core adapter transaction records, including channel, request, adapter identifiers, service instance, and command-line metadata.
• XDP_ADAPTER_TYPE_REQ_TYPES_V (view) — used in a scalar subquery to translate a request_type lookup code into a meaningful description scoped by adapter_type.
• FND_LOOKUPS (view) — queried three times to decode request_status, adapter_status, and adapter_type against the lookup types XDP_REQUEST_STATUS, XDP_ADAPTER_STATUS, and XDP_ADAPTER_TYPE respectively.
• FND_GLOBAL (package) — referenced by dependency metadata, typically associated with the security/context functions used elsewhere in the XDP adapter framework.

The view is a pure read-only construct: it performs no DML and introduces no persistent storage of its own.

Key Columns

• CHANNEL_NAME — the e-Commerce Gateway trading partner channel through which the adapter request was processed.
• REQUEST_TYPE — decoded description of the request type, resolved via XDP_ADAPTER_TYPE_REQ_TYPES_V using request_type and adapter_type.
• REQUEST_STATUS — decode of the code stored in XDP_REQUEST_STATUS.
• REQUESTED_BY_USER — the application user who initiated the request.
• ADAPTER_NAME — the adapter program or service name handling the request.
• ADAPTER_STATUS — decode of the code stored in XDP_ADAPTER_STATUS.
• ADAPTER_TYPE — decode of the code stored in XDP_ADAPTER_TYPE (this is the column directly relevant to the search term "xdp_adapter_type").
• SERVICE_INSTANCE_ID, COMPLETION_DATE, CONNECT_ON_DEMAND_FLAG, MAX_IDLE_TIME_MINUTES — service execution and lifecycle attributes.
• CMD_LINE_OPTIONS, CMD_LINE_ARGS, LOG_FILE_NAME — runtime invocation details useful for troubleshooting.
• APPLICATION_ID — the owning Oracle application identifier.

Common Use Cases and Queries

The view is most commonly used to monitor adapter processing outcomes and to troubleshoot integration failures. A typical query filtering on a specific adapter type would be:

• Adapter activity by type: SELECT channel_name, adapter_name, adapter_type, adapter_status, completion_date FROM apps.xdp_adapter_audit_v WHERE adapter_type = '&adapter_type';
• Failed or pending requests: filter on REQUEST_STATUS or ADAPTER_STATUS to isolate non-successful activity over a date range using COMPLETION_DATE.
• User-submitted audit trail: group by REQUESTED_BY_USER and REQUEST_TYPE to review inbound document volumes by originator.
• Runtime diagnostics: select CMD_LINE_OPTIONS, CMD_LINE_ARGS, and LOG_FILE_NAME to correlate a failed adapter instance to its server-side log.

Because the view performs correlated scalar subqueries against FND_LOOKUPS and XDP_ADAPTER_TYPE_REQ_TYPES_V, large unfiltered queries may be costly; constraining the result set by adapter_type, channel_name, or completion_date is advisable.