Results for “xdp_adapter_usage_code”

12 results




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

Overview

The APPS.XDP_ADAPTER_TYPE_V view is a reporting construct within the Oracle E-Business Suite application schema that summarizes how adapters are registered and classified by their usage category. It is defined in the ETRM repository and is present in both the 12.1.1 and 12.2.2 releases. Rather than storing data itself, the view aggregates rows from the adapter registration table and joins them to the Oracle Application Object Library lookup table to translate internal usage codes into user-facing display names.

The object name references the Oracle XML Publisher / BI Publisher adapter framework (the XDP prefix). Users who search for "xdp_adapter_usage_code" are typically looking for the seeded lookup type that this view depends on. The view provides a convenient, pre-grouped list of adapter features grouped by usage code, making it suitable for administrative reports, integration diagnostics, and configuration audits.

Underlying Base Objects

The view text declares the following sources:

  • XDP_ADAPTER_REG — the adapter registration synonym. The view reads the fe_id and usage_code columns from this object.
  • FND_LOOKUPS — the Oracle Application Object Library lookup view, filtered to lookup_type = 'XDP_ADAPTER_USAGE_CODE' and joined on lookup_code.
  • FND_GLOBAL — documented as a referenced package, generally supplying session context (such as the applications identifier) during view compilation or access.

The relationship is a straightforward inner join: each registered adapter row must match a valid lookup code. Adapters with an unmapped or orphaned usage code will not appear in the result set.

Key Columns

  • FE_ID — the identifier of the adapter feature or feature entity within the registration table. This is the grouping key that distinguishes one adapter definition from another.
  • USAGE_CODE — the internal code indicating the adapter's usage classification; this is the raw value that the "xdp_adapter_usage_code" lookup type enumerates.
  • DISPLAY_NAME — the translated meaning obtained from FND_LOOKUPS.MEANING, providing a readable label for the usage code.
  • USAGE_COUNT — the result of COUNT(*), giving the number of registration rows for each combination of feature, usage code, and meaning.

Common Use Cases and Queries

Typical applications include auditing which adapters are configured, verifying that every registration maps to a seeded lookup value, and producing a count of adapter instances per feature. Because the view already aggregates and decodes the data, reporting tools can consume it directly without additional joins.

The following query lists all usage types and their counts:

  • SELECT fe_id, usage_code, display_name, usage_count FROM apps.xdp_adapter_type_v ORDER BY fe_id, usage_code;

To isolate adapters of a specific type, filter on the display name:

  • SELECT * FROM apps.xdp_adapter_type_v WHERE usage_code = '&p_usage_code';

To confirm that the lookup values exist for the code used:

  • SELECT lookup_code, meaning FROM fnd_lookups WHERE lookup_type = 'XDP_ADAPTER_USAGE_CODE';

Note that because the view aggregates with COUNT(*) and groups by feature and usage code, it is read-only and intended strictly for reporting and diagnostic purposes.