Results for “get_address_id”

30 results




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

Overview

ECX_TRADING_PARTNER_PVT is a private PL/SQL package in the APPS schema that supports Oracle E-Business Suite's e-Commerce Exchange (ECX) and EDI Gateway infrastructure. Its core business function is to resolve and return trading partner details — party identifiers, party site identifiers, operating unit identifiers, and administrative email addresses — for both inbound and outbound electronic transactions. In ETRM terms, the package acts as the partner-resolution layer that maps trading partner setups defined in partner setup forms to the runtime data required by the EDI transaction processors. The package is declared with AUTHID CURRENT_USER, meaning it executes with the privileges of the calling user against APPS synonyms, which is typical of internal EBS private APIs. Because it is classified as a private package (API classification PVT), it is not a public, supported API and is not documented for direct customer invocation.

Key Procedures and Functions

The package exposes 13 documented procedures and functions. Their purposes are as follows:

  • GET_TP_INFO — Returns trading partner details as defined in the partner setup, using the trading partner header identifier as input.
  • GET_ADDRESS_ID — Returns the entity address identifier for a given address type or location code.
  • GET_RECEIVERS_TP_INFO — Returns trading partner information for the receiver of an inbound transaction, using package global variables.
  • GET_SENDERS_TP_INFO — Returns trading partner information for the sender of an outbound transaction, using package global variables.
  • GET_TP_COMPANY_EMAIL — Retrieves the company email address associated with a trading partner party site, optionally filtered by transaction type, subtype, and party type.
  • GET_SYSADMIN_EMAIL — Returns the system administrator email address, typically used for error notification when partner resolution fails.
  • GET_TP_DETAILS — Returns broader trading partner detail attributes beyond the basic identifiers.
  • GET_ERROR_TYPE — Classifies an error condition encountered during partner processing.
  • GETENVELOPEINFORMATION — Extracts envelope-level information from the trading partner context, relevant to EDI interchange and group envelope construction.
  • SETORIGINALREFERENCEID — Sets the original reference identifier used to correlate a transaction with its originating document.
  • GETOAGLOGICALID — Returns the Oracle Application Gateway logical identifier for the trading partner.
  • ISUSERAUTHORIZED — Determines whether a given user is authorized for the trading partner context.
  • VALIDATETPUSER — Validates a trading partner user against the configured partner setup.

Tables Accessed

The package references three ECX tables through APPS synonyms, plus the DBMS_SQL built-in package.

  • ECX_TP_HEADERS — The primary trading partner header table. GET_TP_INFO and the sender/receiver resolution routines read this table to obtain party, party site, organization, and administrative email values.
  • ECX_DOCLOGS — The document log table, used to record and correlate transaction processing events associated with a trading partner.
  • ECX_TRANSACTIONS — The transactions table, which holds the inbound and outbound transaction records whose partner context is resolved by the package.
  • DBMS_SQL — Used for dynamic SQL construction, typically where address or partner lookups must be assembled at runtime.

Usage Notes

ECX_TRADING_PARTNER_PVT is invoked internally by the EDI Gateway and e-Commerce Exchange transaction processing flow, including inbound receiver resolution and outbound sender resolution. It is referenced by 10 other packages, confirming its role as a shared internal dependency rather than a standalone entry point. It is not intended to be called directly from Oracle Forms, concurrent programs, or custom code; the supported route for partner configuration is the standard EDI trading partner setup user interface, and the supported route for transaction submission is the EDI Gateway concurrent programs. Custom development that requires trading partner information should use publicly documented EBS APIs or views rather than this private package, since private APIs are subject to change across releases and upgrades, including the transition from 12.1.1 to 12.2.2. The package header carries a version marker from 2005, indicating the object has remained largely stable across the EBS 12.x line.