Search Results xdp_adapter_type_req_types_v




Overview
Explore in AI Chat

Overview

APPS.XDP_ADAPTER_TYPE_REQ_TYPES_V is a reporting and validation view in the Oracle E-Business Suite provisioning module (XDP). Its documented purpose is to provide the set of valid request and control operations available for every adapter type defined in the provisioning framework. An adapter type represents a class of target system or integration endpoint, and each adapter type supports a specific subset of control operations such as startup, shutdown, verify, terminate, suspend, resume, open, and close, in addition to its own request types. The view resolves this relationship by joining the request-type lookup definitions against the adapter type hierarchy, returning only operations that are legitimately applicable to a given adapter type.

Because the view exposes a clean, pre-filtered result set of three columns, it is commonly consumed by provisioning setup screens, adapter configuration validation, and custom integrations that must confirm which operations a given adapter can accept before submitting a request. It is also useful for administrators auditing adapter capability across the environment.

Underlying Base Objects

The view is owned by APPS and is defined over the following documented base objects:

The join logic works in two parts. First, the lookup code is parsed at the colon delimiter; the portion before the colon is compared against the adapter type hierarchy resolved by an Oracle hierarchical query (START WITH ADAPTER_TYPE = XAT.ADAPTER_TYPE CONNECT BY PRIOR BASE_ADAPTER_TYPE = ADAPTER_TYPE), meaning an adapter inherits request types from its base adapters. Second, universal control operations (STARTUP, SHUTDOWN, VERIFY, TERMINATE, SUSPEND, RESUME) are always included, while OPEN and CLOSE are included only when exactly one adapter type in the set requires a connection.

Key Columns

  • LOOKUP_CODE — the request or control operation code, extracted as the substring following the colon in the source lookup code. This is the operation identifier passed to provisioning APIs.
  • MEANING — the user-facing, translatable description of the operation, taken from FND_LOOKUPS.MEANING.
  • ADAPTER_TYPE — the adapter type to which the operation applies, sourced from XDP_ADAPTER_TYPES_B. This is the primary filter column for callers.

Common Use Cases and Queries

The view is typically queried to populate an LOV or to validate an operation before submission. A standard lookup for a specific adapter type:

  • SELECT lookup_code, meaning FROM xdp_adapter_type_req_types_v WHERE adapter_type = :p_adapter_type ORDER BY meaning;

To determine whether a particular control operation is valid for an adapter:

  • SELECT COUNT(*) FROM xdp_adapter_type_req_types_v WHERE adapter_type = :p_adapter_type AND lookup_code = :p_operation;

To list all operations across every adapter type for setup review:

  • SELECT adapter_type, lookup_code, meaning FROM xdp_adapter_type_req_types_v ORDER BY adapter_type, lookup_code;

Because inheritance is resolved through the hierarchical query, querying a base adapter type returns operations inherited by its descendants, which is the intended behaviour for capability discovery in provisioning integrations.