Results for “get_sysadmin_email”

8 results




Overview
Explore in AI Chat

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

Overview

The ECX_TRADING_PARTNER_PVT package body is a private PL/SQL API within the Oracle E-Business Suite E-Commerce eXtension (ECX) module, which underpins the EDI Gateway and Trading Partner integration framework. Its principal responsibility is to resolve the identity, contact, and organizational context of a trading partner — the customer, supplier, or internal entity exchanging electronic business documents with the enterprise — from configuration data held in the ECX trading partner setup tables. In Oracle EBS 12.1.1 and 12.2.2, this private package functions as the shared infrastructure layer consumed by public ETRM APIs and concurrent programs that process inbound and outbound EDI transactions.

The metadata provided does not associate this object with the specific search phrase used, which appears to reference a legal entity name and city. No trading partner configuration, site, or location record for that entity is present in the documented content; the package itself is generic and operates solely on whatever partner records exist in the ECX configuration tables for the operating unit.

Key Procedures and Functions

Thirteen documented units comprise the package's interface, of which the following are the most significant:

  • GET_TP_INFO — Returns trading partner details as defined in partner setup, including the party identifier, party site, operating unit, and administrative e-mail. The excerpt shows it validates the supplied header identifier and derives the operating unit by joining to HZ_CUST_ACCT_SITES_ALL, HZ_CUST_ACCOUNTS, or PO_VENDOR_SITES_ALL depending on whether the partner type is customer ('C') or supplier ('S').
  • GET_ADDRESS_ID — Retrieves the address identifier associated with a trading partner, used when constructing document envelopes and delivery routing.
  • GET_RECEIVERS_TP_INFO and GET_SENDERS_TP_INFO — Resolve the receiving and sending trading partner configuration respectively for a transaction, supplying the routing and identification values required for message exchange.
  • GET_TP_COMPANY_EMAIL and GET_SYSADMIN_EMAIL — Return notification addresses for the partner company and for the system administrator, supporting error and status communications.
  • GET_TP_DETAILS — Returns broader partner attribute detail beyond the core identifiers.
  • GET_ERROR_TYPE — Classifies an error condition, enabling the EDI Gateway to route failures appropriately.
  • GETENVELOPEINFORMATION — Assembles the envelope-level identification data required for the interchange, group, and transaction headers of outgoing documents.
  • SETORIGINALREFERENCEID — Establishes the original reference identifier on a transaction for correlation and reconciliation.
  • GETOAGLOGICALID — Returns the logical identifier of the Oracle Application Gateway, used in document header construction.
  • ISUSERAUTHORIZED and VALIDATETPUSER — Perform authorization checks against the trading partner user, controlling whether the user may act on behalf of the partner.

Tables Accessed

  • ECX_TP_HEADERS — The primary trading partner setup table, providing party, site, type, and administrator e-mail for a given header identifier.
  • ECX_DOCLOGS — The document log, recording processing activity and supporting error classification and reference identification.
  • ECX_TRANSACTIONS — Stores transaction records read and updated for reference and status purposes.
  • DBMS_SQL — The Oracle-supplied dynamic SQL package, used because the operating unit derivation is constructed dynamically and executed conditionally based on partner type.

Usage Notes

As a private package, ECX_TRADING_PARTNER_PVT is not intended for direct invocation by customers. It is referenced by ten other packages and is invoked internally by the ETRM public APIs and by the EDI Gateway concurrent programs when translating, validating, and transmitting business documents. Typical call points include inbound document processing, where partner identity and authorization must be established before a transaction is accepted, and outbound processing, where sender and receiver configuration and envelope identifiers are assembled. Customizations should call public ETRM APIs rather than this private body, as its signature and internal logic are subject to change across patch levels, as evidenced by the 2008 revision header carried into the 12.1.1 and 12.2.2 code lines.