Search Results get_proxy

Overview

WSH_U_UTIL is a utility package body owned by APPS within the Oracle E-Business Suite Shipping (WSH) module. Its name and internal structure identify it as a general-purpose helper package that supports the broader WSH codebase rather than exposing a standalone business transaction API. The package is classified in the ETRM repository as a UTIL object, meaning its routines are intended to be called by other WSH packages and by custom extensions that require common low-level processing. It provides no user interface of its own and does not represent a business entity such as a delivery, shipment, or carrier. The source header indicates the file is WSHUUTLB.pls, with the last revision dated 2002 and a package directive version of 115.9, suggesting the object has been stable across the 12.1.1 and 12.2.2 release lines. Typical responsibilities for a package of this type include token parsing and carrier or proxy address resolution, both of which are reflected in the documented entry points.

Key Procedures and Functions

• CALCULATE_TOKEN — A private helper function that performs delimiter-based token parsing. Based on the documented source, it uses the percent character as a delimiter and strips the first token from an input message. When the delimiter is not found, the function returns the substring beginning at the start-token position through the end of the message. Debug instrumentation is embedded through the WSH_DEBUG_INTERFACE and WSH_DEBUG_SV calls, and the module is registered under the name wsh.plsql.WSH_U_UTL.CALCULATE_TOKEN. Parameters are passed as IN OUT NOCOPY, indicating the routine advances an internal cursor position as each token is extracted.
• GET_CARRIER_API_URL — A function that resolves the carrier API endpoint address used for shipping carrier integration. It centralizes URL construction or lookup so that carrier-facing calls can be issued consistently across WSH processes.
• GET_PROXY — The function the user searched for; it returns proxy configuration information used when the Shipping module must make outbound network calls, such as carrier API requests. By isolating proxy resolution in a utility routine, the proxy host, port, or bypass rules can be applied uniformly.

Tables Accessed

The ETRM metadata for this object records no referenced tables through APPS synonyms. This is consistent with the nature of a PL/SQL utility package: CALCULATE_TOKEN operates purely on in-memory string input, while GET_PROXY and GET_CARRIER_API_URL likely derive their values from profile options, initialization parameters, or environment settings rather than from direct table queries. No DML is performed against Shipping transaction tables. The absence of a table dependency footprint also means the package carries no concurrency or locking implications for the delivery and shipment data model.

Usage Notes

WSH_U_UTIL is invoked indirectly. Standard Shipping forms, concurrent programs, and the carrier integration layer call the public GET_PROXY and GET_CARRIER_API_URL functions when they need to construct outbound requests, while CALCULATE_TOKEN remains private and is consumed only within the package body. The metadata shows the package is referenced by zero other packages in the ETRM inventory, so its callers are primarily top-level WSH programs and customer-developed code. Customizations that extend Shipping behavior—particularly those replicating carrier calls or parsing delimited carrier messages—may invoke these functions directly. Because the routines are utility in scope and have been stable since the original file revision, they can generally be relied upon across both 12.1.1 and 12.2.2 without version-specific differences, provided appropriate EXECUTE grants on the APPS-owned package are in place.