Search Results ecx_hub_users_pk




Overview

The ECX_HUB_USERS table is a core repository within the Oracle E-Business Suite XML Gateway (ECX) module. It functions as the master definition table for all users configured to operate within the XML Gateway's hub-based architecture. In this context, a "hub" represents a central integration point, and a "hub user" is a logical entity that defines the security, routing, and processing parameters for a specific trading partner or internal application exchanging XML messages. The table is essential for enabling and securing B2B and A2A integrations, as it stores the credentials and configuration necessary for inbound and outbound document transmission.

Key Information Stored

The table's primary identifier is the HUB_USER_ID column, which is enforced by the primary key constraint ECX_HUB_USERS_PK. A critical foreign key relationship exists via the HUB_ID column, which links each user definition to a specific hub in the ECX_HUBS table. While the exact column list is not detailed in the provided metadata, typical columns in such a definition table would include the hub user's name, password or security token, contact information (email, phone), status (active/inactive), and various protocol-specific settings (e.g., for AS2, FTP, or HTTP). These attributes collectively define a unique endpoint for electronic data interchange.

Common Use Cases and Queries

This table is central to integration setup, monitoring, and troubleshooting. Common operational scenarios include validating active trading partner connections, auditing user setup for compliance, and diagnosing message transmission failures. Administrators frequently query this table to generate user lists or verify configurations. Sample SQL patterns include joining with the hub and trading partner detail tables to get a comprehensive view.

  • Listing all active users for a specific hub: SELECT * FROM ECX_HUB_USERS WHERE HUB_ID = <hub_id> AND STATUS = 'ACTIVE';
  • Finding the hub user associated with a trading partner detail: SELECT ehu.* FROM ECX_HUB_USERS ehu, ECX_TP_DETAILS etd WHERE ehu.HUB_USER_ID = etd.HUB_USER_ID AND etd.TP_DETAIL_ID = <detail_id>;

Related Objects

The ECX_HUB_USERS table sits at the center of a key relationship network within the XML Gateway schema. Its primary dependencies, as confirmed by the metadata, are:

  • ECX_HUBS: The parent table. The HUB_ID foreign key in ECX_HUB_USERS references this table, defining which logical hub the user belongs to.
  • ECX_TP_DETAILS: A child table. The ECX_TP_DETAILS.HUB_USER_ID foreign key references ECX_HUB_USERS, linking specific trading partner execution details to a hub user definition. This is a critical relationship for mapping inbound and outbound transactions.

Additionally, this table is likely referenced by various XML Gateway concurrent programs, APIs, and the ECXDIAG diagnostic utility for user authentication and transaction processing.

  • Table: ECX_HUB_USERS 12.1.1

    owner:ECX,  object_type:TABLE,  fnd_design_data:ECX.ECX_HUB_USERS,  object_name:ECX_HUB_USERS,  status:VALID,  product: ECX - XML Gatewaydescription: This table contains the hub user definitions ,  implementation_dba_data: ECX.ECX_HUB_USERS

  • Table: ECX_HUB_USERS 12.2.2

    owner:ECX,  object_type:TABLE,  fnd_design_data:ECX.ECX_HUB_USERS,  object_name:ECX_HUB_USERS,  status:VALID,  product: ECX - XML Gatewaydescription: This table contains the hub user definitions ,  implementation_dba_data: ECX.ECX_HUB_USERS