Results for “ecx_hub_users_u1”

12 results




Overview
Explore in AI Chat

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

Overview

ECX.ECX_HUB_USERS is a seed data table within the ECX (eCommerce Exchange / EDI Gateway) schema that stores the hub user definitions used for outbound and inbound trading partner connectivity in Oracle E-Business Suite 12.1.1 and 12.2.2. Each row associates a specific hub with the receiving location code and the credentials (username and password) required to authenticate against that hub. The table resides in the APPS_TS_SEED tablespace, confirming its classification as reference and setup data rather than transaction data, and it is registered under FND Design Data as ECX.ECX_HUB_USERS with a status of VALID.

From a heuristic Data Vault modeling perspective, this object is satellite-leaning. It carries descriptive, versionable attributes (USERNAME, PASSWORD, and the standard Who columns) that qualify a parent hub record rather than acting as a standalone hub or a pure link between two business entities. The single foreign key into ECX_HUBS reinforces this reading: ECX_HUB_USERS functions as a dependent descriptor set hanging off the hub definition.

Key Information Stored

The table contains ten documented columns. HUB_USER_ID is the surrogate primary key, enforced by the unique index ECX_HUB_USERS_PK. A second unique index, ECX_HUB_USERS_U2, also covers HUB_USER_ID, while ECX_HUB_USERS_U1 (HUB_ID, HUB_ENTITY_CODE, USERNAME) is the composite business-key candidate: it prevents duplicate usernames for the same hub and location code.

  • HUB_USER_ID — surrogate identifier for the hub user record; primary key.
  • HUB_ID — foreign key to ECX.ECX_HUBS, identifying the parent hub.
  • HUB_ENTITY_CODE — hub location code (VARCHAR2 100), part of the U1 business key.
  • USERNAME — receiving username (VARCHAR2 512), also part of U1.
  • PASSWORD — receiving password (VARCHAR2 500) used during authentication.
  • CREATED_BY / LAST_UPDATED_BY — FND_USER foreign keys recording row ownership.
  • CREATION_DATE / LAST_UPDATE_DATE — audit timestamps for the row lifecycle.
  • LAST_UPDATE_LOGIN — FND_LOGINS foreign key capturing the operating system login of the last updater.

Common Use Cases and Queries

Typical usage centers on EDI and eCommerce gateway administration, troubleshooting failed authentications against a trading partner, and auditing which credentials are configured per hub. Because the table holds seed data, reporting is normally read-only lookup style.

Retrieving all hub users with their parent hub context:

SELECT h.HUB_USER_ID, h.HUB_ID, h.HUB_ENTITY_CODE, h.USERNAME, h.LAST_UPDATE_DATE FROM ECX.ECX_HUB_USERS h WHERE h.HUB_ID = :p_hub_id;

Joining to the parent hub to resolve descriptive hub attributes and filter by location code:

SELECT u.USERNAME, u.HUB_ENTITY_CODE, hb.HUB_NAME FROM ECX.ECX_HUB_USERS u, ECX.ECX_HUBS hb WHERE u.HUB_ID = hb.HUB_ID AND u.HUB_ENTITY_CODE = :p_entity_code;

Auditing recent changes via the standard Who columns:

SELECT HUB_USER_ID, USERNAME, LAST_UPDATED_BY, LAST_UPDATE_DATE FROM ECX.ECX_HUB_USERS ORDER BY LAST_UPDATE_DATE DESC;

Related Objects

  • ECX.ECX_HUBS — parent hub definition; joined on HUB_ID. This is the sole documented outbound foreign key.
  • ECX.ECX_TP_DETAILS — trading partner details that reference ECX_HUB_USERS via HUB_USER_ID, representing the principal inbound dependency.
  • ECX.ECX_HUB_USERS# — the underlying base object referenced by this table per the dependency listing.
  • FND_USER — source for CREATED_BY and LAST_UPDATED_BY lookups.
  • FND_LOGINS — source for LAST_UPDATE_LOGIN resolution.