Search Results ece_compare_addresses

Overview

The APPS.ECE_TRADING_PARTNERS_PUB package body is a public API within the Oracle E-Business Suite e-Commerce Gateway (ECE) module. Its principal business function is to resolve, retrieve, and compare trading partner address information used during inbound and outbound electronic data interchange (EDI) transactions. Trading partners in Oracle EBS are represented as parties, customer accounts, account sites, and locations across the Oracle Trading Community Architecture (TCA) and Human Resources location models. Because EDI documents such as purchase orders, invoices, and advance ship notices routinely require the sender or receiver address to be matched against a known trading partner location, this package centralizes that resolution logic.

The package exposes both a low-level address wrapper that accepts and returns a full set of address attributes, and higher-level routines that retrieve addresses and location codes for a given trading partner. The ECE_COMPARE_ADDRESSES procedure, which is the specific object a user searching that term would encounter, provides the comparison logic used to determine whether two address representations correspond to the same trading partner location.

Key Procedures and Functions

The package body documents seven callable units:

• ECE_GET_ADDRESS_WRAPPER — The primary address API. It accepts transaction and organization context along with a complete address payload (lines, city, county, state, zip, province, country, and region elements) and returns the resolved entity, organization, and address identifiers together with the corresponding location code, translator code, location name, and normalized address attributes.
• ECE_GET_ADDRESS — Retrieves address information for a trading partner location, serving as the internal resolution routine invoked by the wrapper.
• ECE_COMPARE_ADDRESSES — Compares addresses to determine whether they represent the same trading partner location, supporting matching and validation during EDI processing.
• SCRUB — Normalizes or cleanses address components prior to comparison or persistence, ensuring consistent matching behavior.
• GET_TP_ADDRESS — Returns the address associated with a specified trading partner.
• GET_TP_ADDRESS_REF — Returns address reference information for the trading partner, used to link address data to the appropriate reference identifier.
• GET_TP_LOCATION_CODE — Returns the trading partner location code, the EDI-relevant identifier used to distinguish one partner site from another.

Tables Accessed

The package reads and writes through APPS synonyms across the ECE and TCA schemas:

• ECE_TP_HEADERS and ECE_TP_DETAILS — the e-Commerce Gateway trading partner header and detail tables that store the partner definition and its associated location and translator mappings.
• HZ_PARTIES, HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES, and HZ_CUST_ACCT_SITES_ALL — the TCA party, account, and account site entities that anchor a trading partner's identity and addresses.
• HZ_PARTY_SITES, HZ_LOCATIONS, and HZ_CONTACT_POINTS — the party site assignment, location, and contact point records that hold the actual address and communication details.
• HR_LOCATIONS_ALL and HR_LOCATIONS_ALL_TL — the HR location tables used where an address is modeled as an internal organization location, including the translated location names.

Usage Notes

This package is typically invoked from e-Commerce Gateway transaction processing logic, from EDI-related concurrent programs, and from custom PL/SQL that must resolve or validate a trading partner address. It follows standard EBS API conventions: an p_api_version_number for version checking, initialization of the message list via FND_API.G_FALSE, a simulation flag, a commit flag, a validation level defaulting to FND_API.G_VALID_LEVEL_FULL, and the standard x_return_status, x_msg_count, and x_msg_data output parameters. Callers should always inspect x_return_status and, when errors occur, iterate the message stack. As a public (PUB) API referenced by four other packages, it should not be modified; customizations should layer on top of it. The module revision history identifies the source as ECVNWTPB.pls, shared across the 12.1.1 and 12.2.2 code lines.