Search Results get_delivery_defaults

Overview

The APPS.WSH_NEW_DELIVERY_ACTIONS package is a core Shipping Execution (WSH) server-side API in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It encapsulates the business actions that can be performed against a delivery or a set of deliveries after they have been created and assigned. In functional terms, this package provides the programmatic entry points used by the Shipping Transactions form, the Shipping Execution concurrent programs, and external integration code to firm, plan, unplan, confirm, close, tender, consolidate, and otherwise transition deliveries through their shipment lifecycle. Rather than exposing direct DML on the underlying WSH tables, the package enforces the validation, defaulting, and status-transition rules that Shipping Execution requires.

The package is declared with AUTHID CURRENT_USER and includes global variables that support the Ship Message Customization feature, such as g_ship_confirm_act, g_missing_inv_cntl_msg, g_break_ship_set_msg, g_break_smc_msg, and g_invalid_material_status_msg. The variable g_break_ship_set_or_smc is explicitly documented as being set in WSH_DELIVERY_VALIDATIONS.CHECK_CONFIRM and checked within CONFIRM_DELIVERY, illustrating how confirmation-time validations are coordinated across packages.

Key Procedures and Functions

ETRM documents twenty procedures and functions in this package. The principal ones, grouped by lifecycle stage, are:

• FIRM – Firms the specified deliveries, moving them into a confirmed planning state so they are eligible for further shipment processing.
• PLAN – Plans a delivery for shipment, invoking the planning engine logic for the delivery rows passed in.
• UNPLAN – Reverses the planning action on a delivery.
• CONFIRM_DELIVERY – Performs ship confirmation for a delivery. This is the procedure of primary interest to users searching for "confirm_delivery." It validates the delivery (including missing inventory controls, broken ship sets, broken ship method/carrier combinations, and invalid material status) and then updates delivery details and assignments to reflect the shipped state.
• GET_DELIVERY_DEFAULTS – Returns defaulted attribute values for a delivery, typically derived from customer, site, item, and organization setup.
• CHANGE_STATUS – Applies a status change to a delivery (for example open, closed, or in-transit) subject to the package's internal validation rules.
• UPDATE_LEG_SEQUENCE and PROCESS_LEG_SEQUENCE – Maintain and resequence delivery legs, which represent the stops or segments on a delivery itinerary.
• SET_LOAD_TENDER and GENERATE_LOADING_SEQ – Support load tendering to carriers and generation of loading sequences for warehouse execution.
• ASSIGN_DELIVERY_UPDATE – Assigns and updates delivery associations in bulk.
• PROCESS_CARRIER_SELECTION – Runs carrier and service selection logic against a delivery.
• ADJUST_PLANNED_FLAG – Adjusts the planned flag on delivery records.
• UPDATE_FREIGHT_TERMS – Updates freight terms on a delivery.
• SETCLOSE and SETINTRANSIT – Convenience procedures to move a delivery into closed or in-transit status respectively.
• UPDATE_SHIP_FROM_LOCATION – Changes the ship-from location on a delivery.
• ASSIGN_DEL_TO_CONSOL_DEL and UNASSIGN_DELS_FROM_CONSOL_DEL – Assign or unassign deliveries to and from a consolidated delivery.
• IS_DELIVERY_EMPTY – Returns whether a delivery has no remaining details, used to decide whether it can be closed or deleted.

Tables Accessed

The package reads and writes the principal Shipping Execution tables through APPS synonyms. WSH_DELIVERY_ASSIGNMENTS and WSH_DELIVERY_ASSIGNMENTS_S hold the link between delivery details and deliveries and are updated during confirmation and assignment actions. WSH_DELIVERY_DETAILS stores the item-level shipping lines. WSH_DELIVERY_LEGS stores itinerary legs maintained by the leg-sequence procedures. WSH_CARRIERS and WSH_CARRIER_SERVICES are consulted during carrier selection and tendering. MTL_SYSTEM_ITEMS, MTL_INTERORG_SHIP_METHODS, and MTL_CLIENT_PARAMETERS supply item, ship-method, and client-level defaults. Customer and location information is sourced from HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, HZ_LOCATIONS, and HZ_PARTY_SITES. FND_USER and HR_ORGANIZATION_INFORMATION provide user and organization context for defaulting and security.

Usage Notes

WSH_NEW_DELIVERY_ACTIONS is invoked internally by the Shipping Transactions form and by Shipping Execution concurrent programs such as the ship-confirm and interface programs. It is also the recommended API for custom code and integrations that need to firm, plan, confirm, close, or consolidate deliveries without performing direct table updates. Because the package is referenced by thirty-one other packages, customizations should call its public procedures rather than duplicating their logic. Callers should expect the package to raise validation errors through its return status parameters when confirmation-time checks such as BREAK_SHIP_SET, BREAK_SMC, MISSING_CONTROLS, or INVALID_MATERIAL_STATUS fail, with message text driven by the corresponding global constants. The behavior is consistent across 12.1.1 and 12.2.2; the file header indicates the package was last updated at release 12.2 level, and no signature differences affecting the procedures above are documented between the two releases.