Search Results hz_adapter_users_n1

Overview

The AR.HZ_ADAPTER_USERS table is a reference and security-support structure within the Oracle E-Business Suite Trading Community Architecture (TCA) / Customer Relationship Management data model. It is owned by the AR schema and exposed to the applications layer through the APPS.HZ_ADAPTER_USERS synonym registered in FND Design Data. The table stores the set of authenticated user identities that are authorized to invoke a given data integration service adapter. In practical terms, it acts as an authorization roster that binds a named service consumer (USERNAME) to a specific adapter definition (ADAPTER_ID), enabling the adapter layer to determine whether an inbound request should be accepted and processed.

From a heuristic Data Vault classification standpoint, the table is modeled as a standalone object with no downstream dependencies. Because the documented Foreign Key metadata shows a single reference from ADAPTER_ID to HZ_ADAPTERS, the table is best described as a satellite-style attribute table attached to the adapter hub rather than a true hub or link. It carries descriptive authentication attributes about adapter users, and each physical row is uniquely identified by the ADAPTER_USER_ID surrogate key, enforced by the unique index HZ_ADAPTER_USERS_U1.

Key Information Stored

The table contains eight documented columns. The most significant are:

• ADAPTER_USER_ID (NUMBER 15, mandatory) — The surrogate primary key. This is the column indexed by the unique index HZ_ADAPTER_USERS_U1, and it is the business-key candidate for row-level identification.
• ADAPTER_ID (NUMBER 15, mandatory) — The foreign key to HZ_ADAPTERS. It identifies the data integration service adapter to which the user is authorized and is supported by the non-unique index HZ_ADAPTER_USERS_N1.
• USERNAME (VARCHAR2 100) — The user name passed to the service that requires authentication. This is the operative security attribute that the adapter layer matches against incoming credentials.
• CREATION_DATE (DATE) — Standard Who column recording when the authorization record was created.
• CREATED_BY (NUMBER 15) — Standard Who column identifying the application user who created the record.
• LAST_UPDATE_DATE (DATE) — Standard Who column recording the last modification timestamp.
• LAST_UPDATED_BY (NUMBER 15) — Standard Who column identifying the last modifying user.
• LAST_UPDATE_LOGIN (NUMBER 15) — Standard Who column capturing the login session of the last update.

The surrogate key (ADAPTER_USER_ID) is distinct from the composite business identifier of ADAPTER_ID plus USERNAME, which is not enforced as a unique constraint in the documented metadata.

Common Use Cases and Queries

Typical scenarios include auditing which users are authorized on a given integration adapter, verifying that a service account has been provisioned before enabling an interface, and reporting on authorization growth over time. Because the table is joined to HZ_ADAPTERS through ADAPTER_ID, reporting queries generally resolve the adapter name for readability.

A representative query lists all authorized users for every adapter:

• SELECT a.ADAPTER_USER_ID, a.ADAPTER_ID, a.USERNAME, a.CREATION_DATE FROM AR.HZ_ADAPTER_USERS a ORDER BY a.ADAPTER_ID, a.USERNAME;
• SELECT u.USERNAME, u.ADAPTER_ID, u.CREATION_DATE FROM AR.HZ_ADAPTER_USERS u WHERE u.ADAPTER_ID = :adapter_id;
• SELECT u.USERNAME, u.LAST_UPDATE_DATE, u.LAST_UPDATED_BY FROM AR.HZ_ADAPTER_USERS u WHERE u.USERNAME = :service_account;

These patterns are commonly embedded in custom concurrent programs, OAF-based setup pages, and diagnostic reports that validate integration provisioning before go-live.

Related Objects

The documented dependency model is narrow but critical to understanding the table's role:

• AR.HZ_ADAPTERS — The parent adapter definition table. Joined via HZ_ADAPTER_USERS.ADAPTER_ID = HZ_ADAPTERS.ADAPTER_ID. This is the only documented foreign key relationship.
• APPS.HZ_ADAPTER_USERS — The APPS-layer synonym through which applications and concurrent programs access the table.
• HZ_ADAPTER_USERS_U1 — The unique index on ADAPTER_USER_ID in tablespace APPS_TS_TX_IDX; the object the user searched for, providing direct row lookup by surrogate key.
• HZ_ADAPTER_USERS_N1 — The non-unique index on ADAPTER_ID, supporting adapter-centric access paths and the join to the adapter parent.

No other database objects are documented as referencing AR.HZ_ADAPTER_USERS, confirming its role as a leaf-level authorization attribute table within the TCA integration layer. Any maintenance access should be treated as privileged configuration data, since the USERNAME values control which external service identities can authenticate against the associated adapter.