Results for “log_level_display”

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

Overview

XDP_ADAPTER_REG_V is a provisioning-layer view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes configuration and runtime status data for all adapters registered within the Oracle iProcurement/Provisioning (XDP) fulfillment infrastructure. Adapters in this context are service processes that connect fulfillment elements to external systems, and the view consolidates their channel assignments, adapter types, workflow bindings, concurrent manager associations, and operational state into a single denormalized result set suitable for reporting and troubleshooting.

The view is defined over the base adapter registration table XDP_ADAPTER_REG and joins it to fulfillment element and adapter type definitions, converting internal lookup codes into translated display meanings. This makes it the principal reference object for administrators and technical consultants who need to inspect how provisioning adapters are configured, which service instances they run under, and when their status last changed. The user search term status_active_time corresponds directly to the STATUS_ACTIVE_TIME column, which records the timestamp at which an adapter most recently transitioned into its current active state.

Underlying Base Objects

The documented base objects referenced by XDP_ADAPTER_REG_V are:

• XDP_ADAPTER_REG (SYNONYM) — the primary registration table holding per-adapter configuration, status, workflow, and timing attributes.
• XDP_FES_VL (VIEW) — the fulfillment element view supplying FE_ID, FULFILLMENT_ELEMENT_NAME, and display names.
• XDP_ADAPTER_TYPES_VL (VIEW) — the adapter type view providing ADAPTER_TYPE and its display label.
• FND_CONCURRENT_QUEUES (SYNONYM) — joined on SERVICE_INSTANCE_ID and APPLICATION_ID to resolve the target concurrent manager node.
• FND_LOOKUPS (VIEW) — used in scalar subqueries to translate status, usage code, startup mode, and log level codes into meanings.
• FND_GLOBAL (PACKAGE) — referenced for session context (application/user) used in view access and lookup resolution.

The joins establish referential integrity between an adapter and its fulfillment element, its adapter type, and the concurrent queue that hosts its service instance.

Key Columns

• CHANNEL_NAME, ADAPTER_NAME, ADAPTER_DISPLAY_NAME — identity of the adapter and its parent channel.
• FE_ID, FULFILLMENT_ELEMENT_NAME, FE_DISPLAY_NAME — the fulfillment element the adapter serves.
• TARGET_NODE — the concurrent manager node resolved through FND_CONCURRENT_QUEUES.
• PROCESS_ID — operating system process identifier of the running adapter.
• ADAPTER_STATUS, ADAPTER_STATUS_DISPLAY, STATUS_MEANING — the adapter state code and its translated lookup meaning (lookup type XDP_ADAPTER_STATUS).
• WF_ITEM_TYPE, WF_ITEM_KEY, WF_ACTIVITY_NAME — the workflow binding used for adapter orchestration.
• CONNECT_ON_DEMAND_FLAG, MAX_IDLE_TIME_MINUTES — lifecycle behavior controls.
• ADAPTER_TYPE, ADAPTER_TYPE_DISPLAY — the adapter category.
• USAGE_CODE, USAGE_CODE_DISPAY, STARTUP_MODE, STARTUP_MODE_DISPLAY, LOG_LEVEL, LOG_LEVEL_DISPLAY — translated configuration attributes drawn from FND_LOOKUPS.
• SERVICE_INSTANCE_ID, APPLICATION_ID, LOG_FILE_NAME — service instance and log location.
• LAST_VERIFIED_TIME — the last time the adapter configuration was validated.
• STATUS_ACTIVE_TIME — the timestamp the adapter last entered its active state.
• SEQ_IN_FE, OBJECT_VERSION_NUMBER — ordering within the fulfillment element and optimistic locking version.

Common Use Cases and Queries

Typical scenarios include verifying which adapters are active, comparing STATUS_ACTIVE_TIME against LAST_VERIFIED_TIME to detect stale or restarted processes, and auditing the concurrent manager node hosting each adapter.

SELECT adapter_name, adapter_display_name, adapter_status_display,
       target_node, status_active_time, last_verified_time
FROM   apps.xdp_adapter_reg_v
WHERE  adapter_status = 'ACTIVE'
ORDER BY status_active_time DESC;

To isolate adapters by fulfillment element and node:

SELECT fulfillment_element_name, adapter_name, target_node,
       startup_mode_display, max_idle_time_minutes
FROM   apps.xdp_adapter_reg_v
WHERE  fulfillment_element_name = :fe_name;

Because the view resolves lookup meanings internally, it should be preferred over direct queries against XDP_ADAPTER_REG whenever human-readable status and usage values are required.