Search Results set_proxy

Overview

HZ_LOCATION_SERVICES_PUB is the public PL/SQL API package within the Oracle Trading Community Architecture (TCA) that governs address validation processing in Oracle E-Business Suite 12.1.1 and 12.2.2. The package is owned by APPS, is classified as a public API, and is declared with AUTHID CURRENT_USER so that it executes under the privileges of the calling schema. Its principal business purpose is to submit outbound address validation requests to third-party or internal validation engines, track the results returned by those engines, and support the correction and standardization of address data held against parties, customer accounts, and locations.

The header comment identifies the package as "Location Service" and references the Location Service APIs chapter of the Oracle Trading Community Architecture Technical Implementation Guide (120hztig.pdf). The package is registered against the HZ_ADDRESS business entity and is marked active in its lifecycle metadata. Because it is a PUB-classified API, it is intended for direct invocation by external code rather than being restricted to internal TCA processing.

Key Procedures and Functions

• SET_PROXY — Configures the HTTP proxy parameters used when the validation engine requires outbound network access through a proxy. This is the procedure most commonly associated with the "set_proxy" search term and is typically executed before issuing validation requests.
• SET_AUTHENTICATION — Establishes authentication context for an outbound HTTP request initiated through UTL_HTTP, applied against a specific adapter.
• ADDRESS_VALIDATION — The primary entry point for launching an address validation run. It exposes filtering options such as validation status, validation code, validated date, last update date, country, adapter content source, and an overwrite threshold.
• ADDRESS_VALIDATION_WORKER — The worker routine invoked per batch to process a defined slice of the validation population, parameterized by adapter, country, validation status and date ranges, and batch sequencing.
• GET_VALIDATED_XML — Retrieves the XML payload associated with a validated address for a given adapter, location, country, and structured address elements.
• SUBMIT_ADDRVAL_REQUEST — Submits an address validation request for processing, generally driving the concurrent request that invokes the worker.
• SUBMIT_ADDRVAL_DOC — Submits a validation request for a validation document, allowing batches of address data to be processed as a unit.
• GET_ADAPTER_ID — Returns the adapter identifier required by the other procedures, resolving the configured validation adapter.
• INDOC_RULE — Defines the inbound document rule used to interpret responses received from the validation provider.
• OUTDOC_RULE — Defines the outbound document rule that formats the request payload sent to the validation provider.

Tables Accessed

The package references its data through APPS synonyms. Party and address data is read and updated in HZ_PARTIES, HZ_PARTY_SITES, HZ_CUST_ACCT_SITES_ALL, HZ_LOCATIONS, and HZ_LOCATION_PROFILES. Adapter configuration and processing results are held in HZ_ADAPTERS, HZ_ADAPTER_LOGS, and HZ_ADAPTER_TERRITORIES, while HZ_GEO_NAME_REFERENCE_LOG records geography name reference activity. Concurrent processing state is tracked in FND_CONCURRENT_REQUESTS and FND_NEW_MESSAGES, and Oracle Workflow integration for validation events uses WF_EVENT_T and WF_PARAMETER_LIST_T. UTL_HTTP supplies the HTTP request context, and DBMS_LOB handles large XML document content.

Usage Notes

HZ_LOCATION_SERVICES_PUB is normally invoked indirectly through concurrent programs that perform address validation, and through TCA forms and the Trading Community Architecture address validation UI. Administrators set proxy and authentication parameters before launching validation so that the outbound call to the validation provider can traverse the required network path. Custom code should call the documented public procedures only; SET_PROXY must be invoked before request submission when a proxy is required. The package is referenced by one other package, and because it is AUTHID CURRENT_USER, the calling schema requires appropriate grants on the underlying APPS objects.