Results for “xdp_request_type”

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

Overview

APPS.XDP_ADAPTER_TYPE_REQ_TYPES_V is a reporting and integration view in Oracle E-Business Suite that exposes the set of request types valid for a given adapter type registered within the eCommerce/XML Gateway infrastructure (the XDP schema). Its primary role is to resolve which request types an adapter can legitimately process, driven by the intersection of the XDP_REQUEST_TYPE lookup values held in FND_LOOKUPS and the adapter hierarchy defined in XDP_ADAPTER_TYPES_B. The view presents a normalized LOOKUP_CODE (the request type name with the adapter-qualifying prefix stripped), a translated MEANING, and the owning ADAPTER_TYPE.

This view is commonly surfaced when a user searches on "xdp_request_type," since the underlying lookup type is 'XDP_REQUEST_TYPE'. It is the queryable expression of the request-type-to-adapter mapping used by adapter configuration and runtime request routing.

Underlying Base Objects

The documented base objects referenced by this view are:

• FND_LOOKUPS (VIEW) — the Applications lookup definitions. The view restricts to LOOKUP_TYPE = 'XDP_REQUEST_TYPE' and only active, in-date rows (ENABLED_FLAG = 'Y' and SYSDATE between START_DATE_ACTIVE and END_DATE_ACTIVE).
• XDP_ADAPTER_TYPES_B (SYNONYM) — the base table of adapter definitions, alias XAT. It holds ADAPTER_TYPE, BASE_ADAPTER_TYPE, and CONNECTION_REQUIRED_FLAG, and is used both as the driving adapter record and as the source of a CONNECT BY hierarchy.
• FND_GLOBAL (PACKAGE) — the standard EBS session context package, referenced for environment/context resolution within the eTRM definition.

The lookup records embed the target adapter type as the prefix of the lookup code, separated by a colon (adapter_type:request_type). The view joins that prefix against the adapter hierarchy, so a request type is returned for an adapter if it belongs to the adapter's ancestor chain, or to an explicit connection-independent set.

Key Columns

• LOOKUP_CODE — the request type identifier, derived as SUBSTR(lookup_code, INSTR(lookup_code, ':') + 1), i.e. the portion after the colon.
• MEANING — the user-facing description of the request type from FND_LOOKUPS.
• ADAPTER_TYPE — the adapter from XDP_ADAPTER_TYPES_B for which the request type is valid.

Although not projected, the predicate logic relies on BASE_ADAPTER_TYPE and CONNECTION_REQUIRED_FLAG from XDP_ADAPTER_TYPES_B to govern applicability.

Common Use Cases and Queries

Typical scenarios include adapter configuration validation, request routing diagnostics, and reporting on which request types a given adapter supports. The universal request types STARTUP, SHUTDOWN, VERIFY, TERMINATE, SUSPEND, and RESUME are always returned, while OPEN and CLOSE return only when the adapter requires a connection.

Representative query listing valid request types for all adapters:

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

Filtering to a specific adapter:

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

Verifying whether a given request type is valid for an adapter:

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

Because the view encapsulates lookup enablement, date-effectivity, and adapter-hierarchy traversal, consumers should query it rather than reconstructing the join against FND_LOOKUPS and XDP_ADAPTER_TYPES_B directly.