Search Results get_batch_parameters

Overview

WSH_MDC_SRS is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified as an "OTHER" API within the ETRM repository. The acronym "MDC" refers to the Multi-stop Delivery Consolidation (also referred to as the Consolidation/Distribution Center) engine that underpins Oracle Shipping Execution's consolidation and deconsolidation planning. The package is built with AUTHID CURRENT_USER, meaning its SQL statements execute under the privileges of the calling schema rather than the definer's schema, an important consideration for any custom invocation.

Its purpose is to support the batch scheduling and execution of delivery consolidation. In Oracle Shipping, deliveries are grouped into consolidation batches that the planner evaluates against grouping rules, and WSH_MDC_SRS provides the server-side routines that create those batches, resolve the deliveries eligible for consolidation, evaluate grouping attributes and hash values, and finally generate consolidations and deconsolidation trips. The package therefore sits between the consolidation grouping rules maintained by the user and the physical delivery/trip records generated by the shipping engine.

Key Procedures and Functions

• SCHEDULE_BATCH — Schedules a consolidation batch, establishing the batch run context against which deliveries are subsequently evaluated.
• GET_BATCH_PARAMETERS — Retrieves the parameters associated with a consolidation batch for use by downstream processing.
• GET_DELIVERIES — The routine most often searched for by name; it resolves and returns the set of deliveries eligible for consolidation within the batch. This is the primary selection routine the consolidation engine uses before grouping.
• SET_INTERMEDIATE_LOCATION — Establishes intermediate stop locations used when a delivery moves through transfer or cross-dock points during consolidation.
• GET_GROUPING_ATTRS — Derives the grouping attribute values (such as region, zone, and stop attributes) that determine how deliveries consolidate together.
• GET_HASH_VALUE — Computes a hash value (and associated hash string) for a delivery or group of deliveries, functioning as the grouping key that the consolidation logic compares.
• CREATE_CONSOLIDATIONS — Persists the consolidations formed from the grouped deliveries.
• CREATE_DECONSOL_TRIPS — Generates deconsolidation trips from the consolidations, representing the break-down legs of the consolidated movement.

The package also declares public record and table types — addnl_del_attr_rec_type, addnl_del_attr_tab_type, and grp_attr_rec — used to carry parallel sets of additional delivery attributes (FOB, freight terms, weights, ship-to address components, consol index) and grouping attributes in memory between the routines above.

Tables Accessed

• WSH_CONSOL_BATCHES — the batch header records created and read by SCHEDULE_BATCH and GET_BATCH_PARAMETERS.
• WSH_CONSOL_GROUPING_RULES — user-defined rules driving GET_GROUPING_ATTRS and the grouping logic.
• WSH_DELIVERY_GROUP_S — the delivery-to-group association used to persist consolidation groupings.
• WSH_DELIVERY_LEGS, WSH_TRIP_STOPS — leg and stop information read when building consolidations and deconsolidation trips.
• WSH_LOCATIONS, WSH_REGION_LOCATIONS, WSH_ZONE_REGIONS — location, region, and zone definitions used in regional grouping and intermediate location assignment.
• MTL_PARAMETERS — organization-level inventory/shipping parameters (including UOM context) needed for weight and attribute interpretation.
• DBMS_UTILITY, DUAL, PLITBLM — utilities for hashing, singleton queries, and PL/SQL table manipulation.

Usage Notes

WSH_MDC_SRS is an internal engine package rather than a public, customer-facing API. It is most commonly invoked indirectly: the Oracle Shipping Execution consolidation planner (including its concurrent programs and the consolidation workbench UI) calls these routines during batch scheduling and execution. It is not referenced by any other documented package, so its callers are expected to be forms, concurrent programs, or consolidation engine code rather than dependent PL/SQL units.

Because the package is AUTHID CURRENT_USER and its routines manipulate shipping transactional data, custom code should not call it directly unless a full understanding of the consolidation batch context has been established via SCHEDULE_BATCH and GET_BATCH_PARAMETERS first. Direct calls bypassing this sequence risk incomplete grouping keys and orphaned consolidation records. The absence of documented parameters in this metadata means callers should inspect the shipped package specification in the target instance (12.1.1 or 12.2.2) before writing any wrapper code.