Results for “wsh_u_track”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

WSH_U_TRACK is a public PL/SQL package in the APPS schema that provides the server-side integration layer between Oracle E-Business Suite Shipping Execution and third-party carrier tracking services. Its naming and record definitions indicate it is purpose-built for the UPS "Enhanced Tracking" interface, handling both single-shipment tracking inquiries and multi-piece shipment summaries. The package is declared AUTHID CURRENT_USER, meaning it executes with the privileges of the calling user rather than the definer, which is typical of EBS utility packages invoked from forms, concurrent programs, or custom extensions under the Applications security model.

The package is classified as OTHER within the ETRM API registry, confirming that it is not a formalized, published EBS API but rather an internal integration utility. It is referenced by one other package, suggesting its data structures and logic are consumed by a higher-level tracking orchestration routine within the WSH (Shipping Execution) module.

Key Procedures and Functions

The sole documented program unit is ENHANCEDTRACKING. In the context of the record types defined in the package specification, this procedure is the entry point through which callers submit a tracking request and receive parsed carrier responses. The specification declares a rich set of record and collection types that ENHANCEDTRACKING operates against:

• EnhancedTrackInRec — the input record, carrying the inquiry number, inquiry type, internal shipment key, sender shipper number, pickup date range, destination postal code, and destination country.
• TrackHeaderRec — the response header, including the UPSOnLine indicator, application version, response type, and echoed inquiry attributes.
• TrackErrorRec — carries the UPS return code, message number, and message text for error reporting.
• TrackAddress and TrackAddressTblTyp — address records (name, address lines, city, state, postal code, country) and an index-by table of them, used for consignee and shipper address resolution.
• MultiSumHdrRec / MultiSumHdrTblTyp — multi-piece shipment header data, including service level description, pickup date, scheduled delivery date, total shipment weight and UOM, and counts of packages delivered, active, and in the shipment.
• MultiSumDtlRec — the detail record for the individual package tracking numbers belonging to a multi-piece shipment.

Together these structures let ENHANCEDTRACKING process both straightforward single-package inquiries and complex multi-piece consignments, returning structured results back to the calling application.

Tables Accessed

The ETRM metadata for this package documents no direct table references through APPS synonyms. This is consistent with its role as a protocol and parsing utility: it transforms and validates data structures rather than persisting them. Any shipment or delivery records that must be updated are typically written by the calling WSH package or concurrent program, which owns the transactional tables. The package's output records are passed back to that caller for storage.

Usage Notes

WSH_U_TRACK is normally invoked indirectly. A carrier-tracking concurrent program or a Shipping Execution form performs the user-facing action, calls the referencing package, which in turn delegates to ENHANCEDTRACKING for the UPS protocol exchange. Because the header comment references a 2002 revision (115.7), the package is a long-standing component of the WSH codebase present in both 12.1.1 and 12.2.2.

Custom code should not call ENHANCEDTRACKING directly unless it can supply every attribute required by EnhancedTrackInRec and correctly interpret the returned header, error, address, and multi-summary collections. Where a formal supported interface exists in WSH for tracking, that interface should be preferred over direct invocation of this utility, since it is an internal integration artifact rather than a frozen public API.