Search Results get_tp_address

Overview

EC_TRADING_PARTNER_PVT is a private PL/SQL package owned by the APPS schema within the Oracle E-Business Suite E-Commerce Gateway (EC) module. Its API classification as a "PVT" (private) package indicates that it is an internal implementation utility rather than a public, customer-facing API. The package encapsulates the core logic required to resolve, validate, and interpret trading partner identity and address information across the E-Commerce Gateway's inbound and outbound transaction processing flows.

The package operates within the ETRM (E-Business Suite Technical Reference Manual) 12.1.1 and 12.2.2 environments. It holds global constants representing notable entity types — 'BANK', 'CUSTOMER', 'SUPPLIER', and 'LOCATION' — and a status constant 'G_TP_NOT_FOUND' set to 'X'. These constants drive the decision logic used when E-Commerce Gateway transactions must map external trading partner identifiers and location codes to internal Oracle entities and their associated addresses. The package is referenced by five other packages, confirming its role as a shared low-level utility within the EC schema's dependency chain.

Key Procedures and Functions

The documented API surface consists of four procedures/functions:

• GET_TP_ADDRESS — A private API that retrieves Supplier/Customer and Address information for a given trading partner. It accepts input parameters including an API version number, initialization message list flag, simulate flag, commit flag, validation level, translator code, external location code, and an information type, and returns status, message count, message data, entity ID, and entity address ID. This is the primary resolution routine for turning an external trading partner location code into a valid internal entity/address pair.
• GET_TP_ADDRESS_REF — A companion implementation of GET_TP_ADDRESS produced specifically at the request of the automotive team. Its signature and purpose mirror the base routine, providing an alternate reference-oriented lookup path for address resolution.
• GET_TP_LOCATION_CODE — Resolves or returns the location code associated with a trading partner entity, supporting the translation between internal address records and the external location codes used by trading partners.
• IS_ENTITY_ENABLED — A boolean-style validation function that determines whether a given entity (customer, supplier, bank, or location) is enabled for E-Commerce Gateway trading partner processing.

Tables Accessed

The package reads from several core EBS tables via APPS synonyms:

• ECE_TP_DETAILS and ECE_TP_HEADERS — The E-Commerce Gateway trading partner definition tables, which store the header and detail configuration of each trading partner, including translator codes and location codes queried by GET_TP_ADDRESS and GET_TP_LOCATION_CODE.
• HZ_PARTIES, HZ_CUST_ACCOUNTS, and HZ_CUST_ACCT_SITES — TCA (Trading Community Architecture) tables used to link a resolved trading partner to its party, customer account, and address site records, returning the entity ID and entity address ID.
• HZ_CONTACT_POINTS — Stores contact point information, used when resolving address or communication details for the identified entity.

Usage Notes

Because EC_TRADING_PARTNER_PVT is a private package, it is not intended for direct invocation by customer extensions. It is called internally by the E-Commerce Gateway transaction processing programs and by the five documented dependent packages during translation, validation, and mapping of inbound and outbound EDI/XML transactions. Users conducting a search such as "VS ELECTRO SERVICES partners" are typically investigating how a specific trading partner is configured and resolved within the gateway; the relevant runtime path flows through these routines to match the configured translator and location codes to internal TCA entities. Custom code should not call this package directly, as its signature and behavior may change between releases; developers requiring trading partner address resolution should use the public E-Commerce Gateway APIs instead.