Results for “hub_name”

2 results




Overview
Explore in AI Chat

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

Overview

The APPS.ECX_TP_API package body provides the programmatic interface for managing trading partner definitions within the Oracle E-Business Suite e-Commerce Gateway (ECX) module. In the Oracle EBS 12.1.1 and 12.2.2 releases, this package serves as the primary API layer through which trading partner header records, detail records, and associated cross-reference data are created, maintained, and queried. Trading partners represent the external organizations, customer sites, and supplier sites with which an enterprise exchanges electronic business documents. By encapsulating the read and write logic for the ECX trading partner schema, ECX_TP_API allows forms, concurrent programs, and custom extensions to manipulate trading partner configuration without issuing direct DML against the underlying tables.

The package is classified as an API in the ETRM metadata and is owned by the APPS schema. Because the header comment references ECXTPXAB.pls with a 2006 revision stamp, the package body is a long-standing component of the ECX data model that has been carried forward across the 12.1.1 and 12.2.2 application releases.

Key Procedures and Functions

The package exposes eleven documented procedures and functions, organized around two related entities: trading partner headers and trading partner details.

  • RETRIEVE_TRADING_PARTNER — Accepts party type, party identifier, and party site identifier, validates that these mandatory parameters are populated, confirms the party type is valid via ECX_UTIL_API.validate_party_type, and returns the corresponding trading partner header identifier along with audit and contact information. It returns status codes such as G_NULL_PARAM and G_INVALID_PARAM through its output parameters.
  • CREATE_TRADING_PARTNER — Creates a new trading partner header record for a given party and site combination.
  • UPDATE_TRADING_PARTNER — Modifies attributes of an existing trading partner header.
  • DELETE_TRADING_PARTNER — Removes an existing trading partner header definition.
  • RETRIEVE_TP_DETAIL — Returns trading partner detail information associated with a header.
  • CREATE_TP_DETAIL — Inserts new trading partner detail rows.
  • UPDATE_TP_DETAIL — Maintains existing trading partner detail rows.
  • DELETE_TP_DETAIL — Removes trading partner detail rows.
  • RAISE_TP_EVENT — Raises the business event associated with trading partner changes, supporting the Oracle Workflow event subscription model used by ECX.

Together these routines provide a complete create, read, update, and delete interface for trading partner configuration.

Tables Accessed

The package reads and writes the core ECX trading partner tables: ECX_TP_HEADERS and its _S sequence-supporting table ECX_TP_HEADERS_S, plus ECX_TP_DETAILS and ECX_TP_DETAILS_S. Configuration and control data reside in ECX_HUBS, ECX_HUB_USERS, ECX_EXT_PROCESSES, ECX_MAPPINGS, ECX_XREF_DTL, and ECX_XREF_DTL_TL. Transactional context is drawn from ECX_TRANSACTIONS and ECX_TRANSACTIONS_TL. Party master data is validated against the Trading Community Architecture tables HZ_PARTIES, HZ_PARTY_SITES, and HZ_LOCATIONS.

Usage Notes

ECX_TP_API is typically invoked from the e-Commerce Gateway trading partner setup forms, from concurrent programs that load or migrate trading partner definitions, and from custom PL/SQL extensions requiring validated access to trading partner data. The metadata records that the package is referenced by four other packages, confirming its role as a shared dependency within the ECX codebase. Callers should inspect the x_return_status and x_msg outputs on every invocation.