Results for “ecx_hub_users_u2”

12 results




Overview
Explore in AI Chat

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

Overview

ECX_HUB_USERS is a table owned by the ECX schema within the Oracle E-Business Suite XML Gateway module. As documented in the ETRM repository for releases 12.1.1 and 12.2.2, the table stores the hub user definitions that govern how inbound and outbound XML messages are authenticated and processed at a trading hub. Each row represents a single user credential registered against a specific hub, providing the identity context required when the XML Gateway dispatches or receives business documents on behalf of an external trading partner or internal application.

In Data Vault modeling terms, the ECX_HUB_USERS structure is heuristic-classified as satellite-leaning. This classification is a modeling suggestion derived from the foreign key topology: the table carries a single parent reference to ECX_HUBS plus descriptive credential attributes, which is characteristic of a satellite attached to a hub entity rather than an independent hub or an association link table.

Key Information Stored

The table comprises ten documented columns. The surrogate primary key is HUB_USER_ID, enforced by the ECX_HUB_USERS_PK constraint (with secondary unique index SYS_C00497458 on the same column). HUB_USER_ID uniquely identifies each hub user record and is the value propagated to dependent tables.

Business-key candidates are captured by the unique index ECX_HUB_USERS_U1 over the combination (HUB_ID, HUB_ENTITY_CODE, USERNAME). This composite index defines the natural uniqueness rule: within a given hub, an entity code and username pairing cannot repeat. A second unique index, ECX_HUB_USERS_U2, covers HUB_USER_ID alone.

  • HUB_USER_ID — surrogate primary key and the identifier referenced by downstream tables.
  • HUB_ID — foreign key to ECX_HUBS, identifying the trading hub to which the user belongs.
  • HUB_ENTITY_CODE — the entity identifier used within the hub to scope the user, forming part of the natural business key.
  • USERNAME — the login name presented during XML Gateway authentication, completing the natural key with HUB_ID and HUB_ENTITY_CODE.
  • PASSWORD — the stored credential associated with the username for hub-level authentication.
  • CREATED_BY, CREATION_DATE — standard EBS audit columns recording the creating user and timestamp.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns capturing the most recent modification user, timestamp, and login context.

Common Use Cases and Queries

Administrators and integrators query ECX_HUB_USERS to audit which credentials exist per hub, to reconcile users against trading partner agreements, and to diagnose authentication failures during XML message processing. A typical lookup resolves all users for a named hub:

  • SELECT u.hub_user_id, u.username, u.hub_entity_code FROM ecx_hub_users u, ecx_hubs h WHERE u.hub_id = h.hub_id AND h.hub_name = :p_hub_name;
  • SELECT * FROM ecx_hub_users WHERE hub_id = :p_hub_id AND username = :p_username; — point lookup by the natural key elements.
  • SELECT hub_user_id, username, creation_date, last_update_date FROM ecx_hub_users ORDER BY last_update_date DESC; — reporting on recently maintained credentials.

Because the PASSWORD column stores sensitive credential data, reporting extracts should generally project only identifying and audit columns unless a controlled security review requires otherwise.

Related Objects

The table participates in two documented foreign key relationships that define its place in the XML Gateway schema.

  • ECX_HUBS — parent table referenced through ECX_HUB_USERS.HUB_ID; supplies the hub definition against which each user is registered.
  • ECX_TP_DETAILS — child table referencing ECX_HUB_USERS.HUB_USER_ID; trading partner detail records depend on the hub user identity, so deletions or key changes in ECX_HUB_USERS must respect this dependency.
  • ECX_HUB_USERS_PK / ECX_HUB_USERS_U1 / ECX_HUB_USERS_U2 — the constraints and unique indexes that enforce identity and natural-key uniqueness on the table.

Collectively, ECX_HUBS, ECX_HUB_USERS, and ECX_TP_DETAILS form the core configuration chain for hub-based XML message routing and authentication in Oracle EBS XML Gateway.