WMS Outbound Consolidation

• Consolidation is the process of bringing materials from different locations of warehouse to a consolidated location for packing and shipping.
• Consolidation can occur at one or more points during outbound process
• Mostly this has been performed during picking, so that picked materials can be consolidated for packing before shipping
• Some warehouses do this even after packing to consolidate in pallets which can be shipped later

Oracle WMS allows 8 types of system directed consolidation based on following key factors

• Should material be consolidated in a consolidated locator or directly in a staging lane
• Should consolidation occur at LPN level
• Can material from different deliveries be consolidated based on the operation plan while upholding the consolidation rules such as no loose material is allowed in the outer most LPN

LPN Based Consolidation in a Staging Lane Within Delivery

• This is the default method for outbound consolidation.
• This allows consolidation of materials in a single delivery directly to a LPN in a staging lane
• System suggests the last LPN dropped off for this delivery in this staging lane

Direct Consolidation in a Staging Lane across Deliveries

• This allows to consolidate materials across deliveries in a staging lane
• Don’t consolidate material in a consolidation LPN within a staging lane
• System does not suggest a drop LPN for the dropping

Direct Consolidation in a Staging Lane within Deliveries

• This allows to consolidate materials for a single delivery
• System will not suggest any LPN

LPN based Consolidation in Consolidation Locator Across Deliveries in Staging Lane

• This allows to consolidate materials across deliveries into a consolidated LPN in a consolidation locator
• After consolidation, materials can be moved to staging lane using mass move functionality

LPN based consolidation in Consolidation Locator within Delivery in Staging Lane

• This allows to consolidate materials within a delivery into a consolidated LPN in a consolidation locator
• After consolidation, materials can be moved to staging lane using mass move functionality

LPN Based consolidation in Staging Lane Across Deliveries

• This allows to consolidate materials across multiple deliveries into a consolidation LPN in a staging lane

Locator based Consolidation in Consolidation Locator Across Deliveries in Staging Lane

• This allows to consolidate each deliveries in separate consolidation locator
• Then consolidate material for multiple deliveries in same staging lane

Locator based Consolidation in Consolidation Locator within Delivery in Staging Lane

• This allows to consolidate materials for a delivery in a consolidation locator
• Then move the materials to staging lane

Basic Setups for consolidation

 Define Default Consolidation Mode in the Organization Parameters window

Define consolidation locators

Define locator dropping order

Define operation plan selection rules

Consolidation Validation

• All lines in the From and To LPN, if the material resides in an existing LPN, must be assigned to a delivery
• The destination LPN must be in a locator type Staging
• The destination LPN must not have any loose material. If LPNs are nested, the nested LPNs can contain loose material
• All tasks loaded into the From LPN and To LPN must have an operation plan if the consolidation method set to across deliveries

Error in Pack Slip Generation during Ship Confirmation

Pack Slip Generating Issues

During Ship confirmation, below error is coming and Pack Slip is not generating

Error

Error: There is an error generating/validating the sequence number. Please check the assignments are defined and are valid.

————————————

Warning: Pack Slip information could not be automatically created for delivery 115506201.

————————————

Error: There is an error generating/validating the sequence number. Please check the assignments are defined and are valid.

————————————

Warning: Bill of Lading information could not be automatically created for Delivery 115506201.

————————————

Submitted 1 out of 1 documents for this document set. (REQ_IDS=293613)

————————————

Warning: Failed to submit document set for delivery 115506201

————————————

Interface Trip Stop request 293614 has been submitted

————————————

Warning: 1 deliveries will be marked as In-Transit/Closed.

Issue:

This order will be able to ship confirm, if re-queried but Pack Slip will not be generated.

Solution:

As in this case, this is not able to properly generate the sequence number, it cannot insert record into WSH_DOCUMENT_INSTANCES table

In most business, Delivery Name been used as the pack slip number.

So for every pack slip document, data being inserted into the table with entity_id as the delivery name.

So as in this case, it is not able to generate the sequence number, this will not be inserted in the table and pack slip canot be generated.

So for this issue, the solution is to do the below profile option setup in following level

Profile Option: Sequential Numbering

Value: Always Used

Level: Application

Application Level values: Shipping Execution and Order Management

If you don’t want to use the same value across all sites, then you can do the setup at specific responsibility levels too.

Picking, Packing and Shipping an order by Scheduled program

To achieve this, you have to follow below steps

1. Define the Picking and Shipping Document set

2. Define a Ship confirm rule and add the shipping document here.

3. Define a a Pick Release rule

    (Make sure Auto Pick Confirm, Auto Create Delivery, Auto Pack Delivery are set as Yes)

4. Add the ship confirm rule in the shipping tab

5. Add the Picking Document set in Pick release rule

6. Make sure Auto allocate is Yes in Inventory tab.

7. Now use “Release Sales Order SRS” and Schedule it as per the frequency you need for the Pick release rule you have created.