Results for “seq_in_fe”

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

Overview

XDP_ADAPTER_REG is an Oracle E-Business Suite table owned by the XDP (Provisioning) schema. As its documented description states, it "stores configuration data pertaining to all Adapters." In the context of XDP provisioning, an adapter is the runtime component that physically moves or transforms data between the provisioning engine and external or internal targets — file transfer adapters, database-link adapters, concurrent-manager adapters, and similar mechanisms. Each row in XDP_ADAPTER_REG represents one named, registered adapter channel, capturing both its identity and the operational parameters that the provisioning framework uses to invoke, schedule, monitor, and diagnose it.

Because provisioning configuration must be version-aware, the table carries the ZD_EDITION_NAME column, which participates in both documented unique indexes and indicates the table is edition-enabled. This is consistent with Oracle EBS 12.2.2 multi-tenant and editioning behavior, where configuration rows may exist across multiple editions.

From a Data Vault modeling perspective, the metadata's FK structure suggests this table behaves as a link: it associates a channel with an adapter type, a front-end engine, a concurrent queue/service instance, a security group, and an error reference. The heuristic classification is offered as a modeling suggestion only; the physical table is a conventional relational construct with a surrogate primary key.

Key Information Stored

The documented primary key is XDP_ADAPTER_REG_PK, defined on the CHANNEL_NAME column. CHANNEL_NAME is therefore the surrogate identifier used by the provisioning engine to look up a specific adapter registration. However, two unique indexes are also documented and act as business-key candidates:

• XDP_ADAPTER_REG_U1 on (CHANNEL_NAME, ZD_EDITION_NAME) — the channel identity combined with its edition.
• XDP_ADAPTER_REG_U2 on (ADAPTER_DISPLAY_NAME, ZD_EDITION_NAME) — the user-facing adapter name combined with its edition.

Among the 34 documented columns, the most operationally significant are:

• ADAPTER_NAME and ADAPTER_DISPLAY_NAME — internal and user-facing identifiers for the adapter.
• ADAPTER_TYPE — the adapter category; a foreign key to XDP_ADAPTER_TYPES_B.
• ADAPTER_STATUS, STATUS_ACTIVE_TIME, and LAST_VERIFIED_TIME — runtime health and verification state.
• FE_ID — the front-end engine this adapter is bound to; a foreign key to XDP_FES.
• APPLICATION_ID and SERVICE_INSTANCE_ID — concurrent processing context, referencing FND_CONCURRENT_QUEUES.
• STARTUP_MODE, CONNECT_ON_DEMAND_FLAG, and MAX_IDLE_TIME_MINUTES — lifecycle and connection-management controls.
• CMD_LINE_OPTIONS and CMD_LINE_ARGS — command-line parameters passed at invocation.
• LOG_LEVEL, LOG_FILE_NAME, and DEBUG_MODE — diagnostic configuration.
• ERROR_REF_ID — diagnostic pointer to XDP_DQ_EXCEPTIONS.
• SECURITY_GROUP_ID — data-security partitioning, referencing FND_SECURITY_GROUPS.
• OBJECT_VERSION_NUMBER — optimistic locking, standard in EBS.

Common Use Cases and Queries

Typical scenarios include auditing which adapters are active, locating adapters attached to a specific front-end engine, and diagnosing faulted channels via ERROR_REF_ID or LAST_VERIFIED_TIME.

To list all currently active adapters by type:

• SELECT a.CHANNEL_NAME, a.ADAPTER_NAME, t.ADAPTER_TYPE_NAME FROM XDP.XDP_ADAPTER_REG a, XDP.XDP_ADAPTER_TYPES_B t WHERE a.ADAPTER_TYPE = t.ADAPTER_TYPE AND a.ADAPTER_STATUS = 'ACTIVE';

To find adapters bound to a specific front-end engine:

• SELECT a.CHANNEL_NAME, f.FE_NAME FROM XDP.XDP_ADAPTER_REG a, XDP.XDP_FES f WHERE a.FE_ID = f.FE_ID;

To review diagnostics for adapters that reference an exception:

• SELECT a.CHANNEL_NAME, a.LOG_LEVEL, e.ERROR_MESSAGE FROM XDP.XDP_ADAPTER_REG a, XDP.XDP_DQ_EXCEPTIONS e WHERE a.ERROR_REF_ID = e.ERROR_ID;

Reporting use cases include adapter inventory reports, capacity planning against MAX_IDLE_TIME_MINUTES, and configuration drift checks across ZD_EDITION_NAME values.

Related Objects

• XDP_FES — joined via XDP_ADAPTER_REG.FE_ID = XDP_FES.FE_ID; identifies the front-end engine owning each adapter.
• XDP_ADAPTER_TYPES_B — joined via ADAPTER_TYPE; provides the adapter classification.
• FND_CONCURRENT_QUEUES — joined via APPLICATION_ID and SERVICE_INSTANCE_ID; links the adapter to concurrent processing queues.
• XDP_DQ_EXCEPTIONS — joined via ERROR_REF_ID; supplies diagnostic exception detail.
• FND_SECURITY_GROUPS — joined via SECURITY_GROUP_ID; enforces data-security partitioning.
• XDP_ADAPTER_REG_PK / XDP_ADAPTER_REG_U1 / XDP_ADAPTER_REG_U2 — primary key and unique indexes supporting consistent lookup by channel, display name, and edition.