Search Results get_cost_factor
Overview
The APPS.WSH_TPA_FREIGHT_COSTS_PKG package body is a generated integration layer that supports Oracle EBS Trading Partner Access (TPA) functionality for freight cost determination within the Shipping Execution (WSH) module. TPA enables external trading partners or third-party logistics providers to exchange data with Oracle EBS through a standardized interface framework, and this package is the freight cost entry point produced by the TPA Generate Utility.
The header comment explicitly states that the file is always generated and must not be edited manually, which confirms that the package is a wrapper artifact created by configuration in the TPA setup rather than a hand-coded solution. Its business purpose is to expose freight cost factor retrieval to the TPA framework so that carrier and freight charges can be resolved against a delivery and its associated container instance. The 12.1.1 and 12.2.2 releases use identical source, with the version stamp indicating an early lineage preserved across releases.
Key Procedures and Functions
The package body documents a single function:
- GET_COST_FACTOR — the sole entry point exposed by the package. It returns a VARCHAR2 value representing the freight cost factor associated with a given delivery and container instance, and returns an outgoing status indicator to the caller. The function does not perform the cost calculation itself; rather, it delegates to
WSH_FC_INTERFACE_PKG.Get_Cost_Factor, passing the delivery identifier and container instance identifier through to the interface layer and returning the resulting cost factor string. Its internal variables include program unit and layer provider identifiers, a customization-level variable, and layer and code-conversion collections used by the TPA utility framework. The exception block performs a simpleWHEN OTHERS THEN RAISE, propagating all errors unchanged to the calling environment.
No other procedures or functions are documented for this package.
Tables Accessed
The documented metadata lists no direct table references for this package body through APPS synonyms. This is consistent with its design as a thin delegating wrapper: all persistence, lookup, and freight cost resolution logic resides in WSH_FC_INTERFACE_PKG, which this package invokes. Data such as delivery details, container instance attributes, and freight cost factor definitions are therefore read indirectly by the interface package rather than directly by WSH_TPA_FREIGHT_COSTS_PKG. Implementers reviewing the freight cost path should consult WSH_FC_INTERFACE_PKG for the actual table and view access.
Usage Notes
Because the package is generated by the TPA Generate Utility, it is invoked automatically by the TPA framework in response to configured trading partner actions — typically when an inbound or outbound freight cost exchange requires a cost factor for a delivery and container. It is not intended for direct calling from custom forms, concurrent programs, or personalizations. Any code that bypasses the wrapper and calls WSH_FC_INTERFACE_PKG directly, or that modifies this generated body, will be overwritten the next time the TPA utility regenerates the package. The return status parameter should be inspected by callers to distinguish success from error conditions before consuming the returned cost factor string.
-
PACKAGE BODY: APPS.WSH_TPA_FREIGHT_COSTS_PKG
12.1.1
-
PACKAGE BODY: APPS.WSH_TPA_FREIGHT_COSTS_PKG
12.2.2
-
PACKAGE: APPS.WSH_TPA_FREIGHT_COSTS_PKG
12.1.1
-
PACKAGE: APPS.WSH_FC_INTERFACE_PKG
12.1.1
-
PACKAGE: APPS.WSH_TPA_FREIGHT_COSTS_PKG
12.2.2
-
PACKAGE: APPS.WSH_FC_INTERFACE_PKG
12.2.2
-
APPS.WSH_FC_INTERFACE_PKG dependencies on WSH_FC_INTERFACE_PKG
12.2.2
-
PACKAGE BODY: APPS.WSH_FC_INTERFACE_PKG
12.1.1
-
APPS.WSH_FC_INTERFACE_PKG dependencies on WSH_FC_INTERFACE_PKG
12.1.1
-
PACKAGE BODY: APPS.WSH_FC_INTERFACE_PKG
12.2.2
-
APPS.WSH_FC_INTERFACE_PKG dependencies on WSH_DEBUG_SV
12.1.1
-
APPS.WSH_FC_INTERFACE_PKG dependencies on WSH_DEBUG_SV
12.2.2