Results for “usage_code_dispay”

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

Overview

APPS.XDP_ADAPTER_REG_V is a reporting and inquiry view in Oracle E-Business Suite that consolidates configuration and runtime state information for ETRM (Electronic Technical Reference Manual) fulfillment adapters. ETRM is the framework that processes fulfillment elements through channels such as XML Gateway, EDI, and other inbound/outbound integration mechanisms. The view joins the adapter registration base table to its associated fulfillment element, adapter type, and concurrent manager queue definitions, then decorates the raw code columns with human-readable lookup meanings.

Its principal role is to present a denormalized, display-ready projection of adapter registration data. Rather than requiring a report or form to separately resolve lookup codes, the view embeds scalar subqueries against FND_LOOKUPS for adapter status, usage code, startup mode, and log level. Consumers therefore read a single row that already contains both the coded value and its corresponding meaning, which simplifies ad hoc querying and diagnostic reporting without compromising the underlying transactional tables.

The view is read-only and is defined in the APPS schema. It is not itself an interface table and performs no DML; it is intended purely for inquiry, monitoring, and integration between reporting layers that need adapter metadata in a friendly form.

Underlying Base Objects

The view is defined over four primary sources joined on their natural keys, plus lookup and package references:

• XDP_ADAPTER_REG (synonym to the base adapter registration table) — the driving table, supplying channel, adapter identity, process, workflow, connection, logging, sequence, and service instance attributes.
• XDP_FES_VL — the fulfillment element view, joined on FE_ID, providing the fulfillment element name and display name.
• XDP_ADAPTER_TYPES_VL — the adapter type view, joined on ADAPTER_TYPE, supplying the type code and its display name.
• FND_CONCURRENT_QUEUES (synonym) — joined on CONCURRENT_QUEUE_ID and APPLICATION_ID to resolve the concurrent manager target node.
• FND_LOOKUPS — referenced in inline scalar subqueries for lookup type XDP_ADAPTER_STATUS, XDP_ADAPTER_USAGE_CODE, XDP_ADAPTER_STARTUP_MODE, and AFLOG_LEVELS.

The documented ETRM metadata lists FND_GLOBAL (package) among referenced objects, reflecting standard EBS view conventions where session context (such as application or responsibility) may be resolved at query time. The joins are all equality-based on the adapter registration keys, so the view returns one row per registered adapter, enriched with the corresponding fulfillment element, adapter type, concurrent queue, and lookup descriptions.

Key Columns

• CHANNEL_NAME, ADAPTER_NAME, ADAPTER_DISPLAY_NAME — identity of the owning channel and the adapter instance.
• FE_ID, FULFILLMENT_ELEMENT_NAME, DISPLAY_NAME — the fulfillment element the adapter serves.
• TARGET_NODE — the concurrent manager node from FND_CONCURRENT_QUEUES where the adapter executes.
• PROCESS_ID, SERVICE_INSTANCE_ID, APPLICATION_ID — process and service instance identifiers, the latter tied to the concurrent queue.
• ADAPTER_STATUS, ADAPTER_STATUS_DISPLAY, STATUS_MEANING — coded adapter status plus its lookup meaning (XDP_ADAPTER_STATUS).
• USAGE_CODE, USAGE_CODE_DISPAY — the usage code and its lookup meaning (XDP_ADAPTER_USAGE_CODE). Note the documented column name contains the misspelling USAGE_CODE_DISPAY rather than DISPLAY; queries must reference the misspelled identifier.
• STARTUP_MODE, STARTUP_MODE_DISPLAY — startup behavior and its meaning (XDP_ADAPTER_STARTUP_MODE).
• LOG_LEVEL, LOG_LEVEL_DISPLAY — logging verbosity and its meaning (AFLOG_LEVELS).
• WF_ITEM_TYPE, WF_ITEM_KEY, WF_ACTIVITY_NAME — workflow linkage for the adapter.
• CONNECT_ON_DEMAND_FLAG, MAX_IDLE_TIME_MINUTES, LOG_FILE_NAME — connection management and logging attributes.
• SEQ_IN_FE, CMD_LINE_OPTIONS, CMD_LINE_ARGS — ordering and invocation parameters.
• LAST_VERIFIED_TIME, STATUS_ACTIVE_TIME, OBJECT_VERSION_NUMBER — runtime state and optimistic locking metadata.

Common Use Cases and Queries

The view is typically used to audit adapter configuration, verify lookup-driven display values, and diagnose adapters by channel or fulfillment element. Because the usage display column is misspelled, the term usage_code_dispay returns results only when referenced exactly.

List adapters with their decoded usage code:

SELECT adapter_name,
       usage_code,
       usage_code_dispay,
       adapter_status_display
FROM   apps.xdp_adapter_reg_v
WHERE  usage_code IS NOT NULL;

Find adapters by channel and node:

SELECT channel_name, adapter_name, target_node,
       startup_mode_display, log_level_display
FROM   apps.xdp_adapter_reg_v
WHERE  channel_name = :channel
ORDER  BY seq_in_fe;

Monitor adapters not recently verified:

SELECT adapter_name, adapter_status_display,
       last_verified_time, connect_on_demand_flag
FROM   apps.xdp_adapter_reg_v
WHERE  last_verified_time < SYSDATE - 1
ORDER  BY last_verified_time;

In practice, the view serves operational dashboards, concurrent program extracts, and integration points that require adapter metadata already resolved to display values, avoiding repeated lookup joins at the consuming layer.