Search Results connection_required_flag

Overview

XDP_ADAPTER_TYPES_VL is a multilingual (VL) reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the XDP – Provisioning product. Its stated purpose is to show all seeded and user-defined Adapter Types. Adapter Types in XDP define the transport mechanisms and processing characteristics used when provisioning interacts with external targets, and the view acts as the translation-complete, read-only presentation layer over the underlying adapter type definition tables. Because it joins the base table to its translation table and filters on the session language, it returns exactly one row per adapter type with the display name appropriate to the current user's language environment. The view is documented as VALID in both the 12.1.1 and 12.2.2 reference material, and its column list is identical across those releases, making it a stable object for custom reporting. In practice it serves as the supported query surface for administrators, integrators, and developers who need to enumerate available adapters, inspect their configuration attributes, or resolve the base_adapter_type inheritance relationship without touching the underlying _B and _TL tables directly.

Underlying Base Objects

The view is defined over two documented base objects, both referenced in the ETRM metadata as synonyms in the APPS schema: XDP_ADAPTER_TYPES_B and XDP_ADAPTER_TYPES_TL. XDP_ADAPTER_TYPES_B holds the language-independent definition of each adapter type, including its class, mode, flags, and buffer settings. XDP_ADAPTER_TYPES_TL holds the translated display name for each adapter type and language. The view text joins the two on ADAPTER_TYPE and constrains T.LANGUAGE = USERENV('LANG'), the standard Oracle EBS multilingual pattern that returns translated content only for the caller's current language. The B.ROWID is exposed as ROW_ID, and the descriptive columns are drawn entirely from the base table while DISPLAY_NAME is drawn from the translation table. No other tables, lookups, or views are referenced, so the view presents a clean one-to-one projection of the definition table augmented with a single translated attribute.

Key Columns

• ROW_ID — the ROWID of the underlying base table row, supporting row-based addressing and certain updatable-view behaviors.
• ADAPTER_TYPE — the primary business key identifying each adapter type; the join key between the base and translation tables.
• ADAPTER_CLASS — the implementation class associated with the adapter, which determines its runtime behavior.
• APPLICATION_MODE — indicates the application integration mode in which the adapter is used.
• INBOUND_REQUIRED_FLAG — indicates whether inbound processing is mandatory for the adapter.
• MAX_BUFFER_SIZE — the maximum buffer size configured for the adapter.
• CMD_LINE_OPTIONS and CMD_LINE_ARGS — command-line configuration attributes passed to the adapter.
• CONNECTION_REQUIRED_FLAG — indicates whether a connection is required for the adapter to operate.
• BASE_ADAPTER_TYPE — identifies the parent or base adapter type from which the current adapter type is derived, establishing the adapter inheritance hierarchy the user searched for.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the underlying framework.
• DISPLAY_NAME — the translated, user-facing name of the adapter type for the session language.

Common Use Cases and Queries

Typical scenarios include listing all available adapters with their translated names, identifying adapters that inherit from a specific base adapter type, and auditing configuration flags such as connection or inbound requirements. A representative query enumerating adapter types and their base relationship is:

SELECT adapter_type, display_name, base_adapter_type, adapter_class, connection_required_flag FROM apps.xdp_adapter_types_vl ORDER BY adapter_type;

To find all adapters derived from a given base adapter type, the BASE_ADAPTER_TYPE column is filtered directly:

SELECT adapter_type, display_name, adapter_class FROM apps.xdp_adapter_types_vl WHERE base_adapter_type = :p_base_adapter_type;

To review connection and inbound behavior for integration planning:

SELECT adapter_type, display_name, application_mode, connection_required_flag, inbound_required_flag FROM apps.xdp_adapter_types_vl;

Because the view is multilingual, results reflect the language set in the user's session; queries executed by users with different language settings may return different DISPLAY_NAME values for the same ADAPTER_TYPE. Custom code should therefore avoid joining on DISPLAY_NAME and should use ADAPTER_TYPE as the stable key. All queries should be run against the APPS synonym with appropriate read privileges.