Search Results transaction_direction

Overview

The view APPS.ECX_TP_DETAILS_V is a reporting and integration object within the Oracle E-Business Suite XML Gateway module (product code ECX). It exposes trading partner detail information consolidated from several XML Gateway configuration tables. In EBS 12.1.1 and 12.2.2, the ECX schema stores the setup that governs how outbound and inbound business documents are exchanged with external trading partners over various transport protocols. The base configuration is spread across header, detail, process, standard, and hub-related tables; ECX_TP_DETAILS_V denormalizes this structure into a single, query-friendly result set. The view is documented as VALID in the APPS schema and its description states simply that it "contains the trading partner detail information." It is used by XML Gateway runtime code and by administrators and consultants who need to inspect, report on, or troubleshoot trading partner communication setup without joining the underlying tables manually.

Underlying Base Objects

The view is defined over six base objects, all referenced through synonyms owned by APPS in the documented metadata: ECX_TP_DETAILS, ECX_EXT_PROCESSES, ECX_TRANSACTIONS_B, ECX_STANDARDS_B, ECX_HUB_USERS, and ECX_HUBS. ECX_TP_DETAILS is the driving (primary) table, aliased TPD, holding the trading partner mapping and connection detail rows. It is joined to ECX_EXT_PROCESSES (EP) on EXT_PROCESS_ID, which in turn links to ECX_TRANSACTIONS_B (ET) on TRANSACTION_ID and to ECX_STANDARDS_B (ES) on STANDARD_ID, supplying the transaction type, subtype, and standard code. The hub user table ECX_HUB_USERS (EHU) and hub table ECX_HUBS (EH) are outer-joined using NVL(...,0) predicates, so rows without a hub user or hub are still returned. This outer-join pattern is central to the view's behavior, since it applies DECODE logic based on whether HUB_USER_ID and HUB_ID are populated.

Key Columns

The view exposes 27 columns. Identification columns include TP_HEADER_ID, TP_DETAIL_ID, MAP_ID, EXT_PROCESS_ID, and HUB_ID. Transaction classification is provided by TRANSACTION_TYPE, TRANSACTION_SUBTYPE, STANDARD_CODE, EXT_TYPE, EXT_SUBTYPE, and DIRECTION (listed in the column metadata as TRANSACTION_DIRECTION). Connection attributes include CONNECTION_TYPE, HUB_USER_ID, PROTOCOL_TYPE, PROTOCOL_ADDRESS, USERNAME, PASSWORD, ROUTING_ID, and CONFIRMATION. The DECODE expressions are significant: when CONNECTION_TYPE is 'DIRECT', protocol type and address are taken from the detail row; otherwise they are drawn from the hub. Similarly, when HUB_USER_ID is null, username, password, and source location come from the detail row, otherwise from the hub user record. Audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and OMB_SYNC and location codes complete the projection.

Common Use Cases and Queries

Typical uses include verifying partner connectivity setup, auditing protocol and credential assignment, and tracing which transaction types and standards a given trading partner detail row supports.

• List all trading partner connections with protocol and direction:

  SELECT tp_detail_id, transaction_type, standard_code,
         connection_type, protocol_type, protocol_address, direction
  FROM   apps.ecx_tp_details_v
  ORDER  BY tp_detail_id;

• Identify direct-connect partners and their addresses:

  SELECT tp_detail_id, ext_type, protocol_type, protocol_address,
         username, source_tp_location_code
  FROM   apps.ecx_tp_details_v
  WHERE  connection_type = 'DIRECT';

• Find connections routed through a hub user:

  SELECT tp_detail_id, hub_id, hub_user_id, username,
         protocol_type, external_tp_location_code
  FROM   apps.ecx_tp_details_v
  WHERE  hub_user_id IS NOT NULL;

Because the view masks stored values for direct versus hub-based credentials, it should be treated as configuration-sensitive data, consistent with the Oracle Proprietary, Confidential Information marking on the source documentation.