Search Results hz_adapters_u1

Overview

The AR.HZ_ADAPTERS table is a configuration seed table within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 data model, owned by the AR schema and registered under FND Design Data as AR.HZ_ADAPTERS. It stores information about adapters configured to provide data integration services, most notably address validation and related content-source services. Each row describes an adapter, whether it is enabled, the invocation method used to call the service, the message format exchanged, and the authentication and batching parameters required to communicate with the external provider. Because the table resides in the APPS_TS_SEED tablespace, it is treated as reference or seed data rather than high-volume transactional data, and changes to its contents are typically performed through Oracle's seeded setup rather than ad hoc DML.

From a Data Vault modeling perspective, the mined metadata classifies this object heuristically as standalone. In practice this suggests modeling the adapter definition as a hub keyed on ADAPTER_ID, with descriptive attributes — enabled flag, invoke method, message format, host address, batching parameters — carried on a satellite, and the content-source identifier acting as a business key candidate rather than a foreign key to another hub.

Key Information Stored

The table contains twenty documented columns. The most significant are summarized below.

• ADAPTER_ID (NUMBER, mandatory) — the surrogate primary key defined by HZ_ADAPTERS_PK; uniquely identifies each adapter.
• ADAPTER_CONTENT_SOURCE (VARCHAR2(30)) — the human-readable content source that uniquely identifies the adapter. It is the second business-key candidate, enforced by the unique index HZ_ADAPTERS_U2.
• ENABLED_FLAG — indicates whether the adapter is active (Y) or disabled (N).
• SYNCHRONOUS_FLAG — distinguishes synchronous (Y) from asynchronous (N) service invocation.
• INVOKE_METHOD_CODE (VARCHAR2(30)) — the transport method used to call the service, for example HTTP.
• MESSAGE_FORMAT_CODE (VARCHAR2(30)) — the format of the message payload exchanged with the service.
• HOST_ADDRESS (VARCHAR2(240)) — the hostname of the external service provider.
• USERNAME and ENCRYPTED_PASSWORD — credentials passed to services that require authentication.
• MAXIMUM_BATCH_SIZE and DEFAULT_BATCH_SIZE — the upper and default record counts the adapter can process in a single batch.
• DEFAULT_REPLACE_STATUS_LEVEL (VARCHAR2(30)) — the default service status code that must be exceeded before a record is updated.
• OBJECT_VERSION_NUMBER, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY — standard EBS who-columns supporting concurrency control and audit.
• ADAPTER_TYPE and ZD_EDITION_NAME — adapter classification and the editioning column used for EBS online patching in 12.2.2.

Note that both unique indexes include ZD_EDITION_NAME in 12.2.2, so uniqueness of ADAPTER_ID and ADAPTER_CONTENT_SOURCE is scoped to the active edition.

Common Use Cases and Queries

Typical reporting and diagnostic scenarios include verifying which adapters are enabled, auditing endpoint and credential configuration, and troubleshooting integration failures.

• List active adapters with their endpoint and format:

  SELECT adapter_content_source, host_address,
         invoke_method_code, message_format_code
    FROM ar.hz_adapters
   WHERE enabled_flag = 'Y';

• Identify asynchronous adapters and their batching limits:

  SELECT adapter_content_source, default_batch_size, maximum_batch_size
    FROM ar.hz_adapters
   WHERE synchronous_flag = 'N';

• Locate an adapter by its business key, leveraging HZ_ADAPTERS_U2:

  SELECT adapter_id, enabled_flag
    FROM ar.hz_adapters
   WHERE adapter_content_source = :source;

• Audit configuration changes using the who-columns (LAST_UPDATE_DATE, LAST_UPDATED_BY).

Related Objects

The primary documented dependency is the foreign-key relationship from HZ_ADAPTER_USERS.ADAPTER_ID to AR.HZ_ADAPTERS.ADAPTER_ID, which records user-level associations with an adapter. Joining the two on ADAPTER_ID yields the assignment of users to a given adapter:

SELECT a.adapter_content_source, u.*
  FROM ar.hz_adapters a, ar.hz_adapter_users u
 WHERE a.adapter_id = u.adapter_id;

Beyond this relationship, the table participates in the broader HZ (Trading Community Architecture) data-quality and address-validation framework served by the AR schema, and its rows are referenced where integration services resolve the appropriate adapter for a given content source.