SAP S4 HANA-EWM Quantity Classification in outbound process

[sulemanbasha]

Introduction

In this blog post you will learn about picking of full pallet and partial pallet quantity (by using quantity classification)from separate source storage type with separate warehouse orders where in one warehouse order is devoted for full pallet and the other one for half pallet.

Business case, when customer order for full pallet quantity then always system should propose full pallet picking area to forklift operator. In case of customer order is less than full pallet quantity then system should propose partial pallet picking to forklift operator.

It has to be noted that separate forklift operator are different for full pallet and partial pallet picking area.

Business advantage is without breaking full pallet system will propose case picking/partial pallet picking area to pick less than full pallet quantity.

 

Solution Approach:

Below solution steps needs to be followed to achieve functionality.

Assumption:-  other configurations like warehouse order creation rule , activity areas, storage type, storage bins are in place.

 

1. In this customization we can define the quantity classification in the warehouse, and so specify the packing unit in which a product is put away.

SPRO -->SCM Extended Warehouse Management-->Extended Warehouse Management-->Cross-Process Settings-->Warehouse Task -->Define Quantity Classifications

Figure 1: Quantity classifier (Click on screenshot to enlarge)

 

2. in this step we are assign a quantity classification to a unit of measure (UoM) to warehouse .

SPRO -->SCM Extended Warehouse Management-->Extended Warehouse Management-->Master Data-->Product-->Define Unit of Measure Attributes

Figure 2: Quantity classifier assignment to UOM  (Click on screenshot to enlarge)

 

3. In this step we are creating two sequences one for full pallet quantity and another sequence   for partial pallet quantity

SPRO -->SCM Extended Warehouse Management-->Extended Warehouse Management-->Goods Issue Process-->Strategies-->Specify Storage Type Search Sequence

Figure 3: Storage type search  (Click on screenshot to enlarge)

 

4. In this step we can specify the full pallet storage type search for full pallet picking with quantity classification “P” and assign partial pallet storage type sequence without quantity classification

SPRO -->SCM Extended Warehouse Management-->Extended Warehouse Management-->Goods Issue Process-->Strategies-->Optimize Access Strategies for Stor. Type Determination in Stock Removal

 

Figure 4: Optimize access sequence (Click on screenshot to enlarge)

 

Master data

Create packaging specification for product by using transaction code /SCWM/PACKSPEC

Figure 5: Packspec (Click on screenshot to enlarge)

 

At level 1 in warehouse stab select quantity classification from drop down "P" for picking full pallets.

Figure 6: Packspec (Click on screenshot to enlarge)

 

 

Test case 1:-

Outbound delivery is created with quantity one full pallet and one case.

Once wave is released system has created two warehouse orders one for full pallet pick and another is for partial pallet pick

(Click on screenshot to enlarge)

Display warehouse task full pallet quantity is 256 PC and case quantity is 8 PC

full pallet warehouse order 2000002318 is having source storage type as full pallet area where as warehouse order 2000002319 is having source storage type as partial pallet area(all storage types are picked from picking search sequence)

 

Test case 2:-

Outbound delivery is created with quantity one full pallet 256 PC

Once wave is released system has created one warehouse orders and one warehouse task for one for full pallet.

(Click on screenshot to enlarge)

Above Warehouse order has created for full pallet quantity 256 PC with source storage type as full pallet area

 

Test case 3:-

Outbound delivery is created with one case 8 PC (less than full pallet )

Once wave is released system has created one warehouse orders and one warehouse task for case quantity here source storage type is from case picking area.

(Click on screenshot to enlarge)

 

Conclusion:

In this blog post, we learn by using quantity classification we can create separate warehouse orders for full pallet and partial picking areas which is very much helpful for warehouse operator during picking operations in warehouse.

 

i believe this blog is helpful, Please let me know your feedback in the comment section. Any feedback is highly appreciated.

 

Many Thanks

Suleman Basha Khadri

[former_member851585]

Hi Suleman,

Excellent excellent information you shared. Thanks a lot. It's a great help. Keep sharing info and helping us.

Thanks,

Imran

[former_member695540]

Excellent. Very useful information.

 

Thanks

Rafi

[former_member851586]

Nice explanation Suleman.Very useful information 👍

[JuergenPitz]

Hi,

maybe you should make up your mind which way you want to go ;-).

In step 2 you assign a quantity classification to the AUoM. That works, if your product has AUoMs.

In the part Master Data you define a pack spec where you assign a quantity classification to a pack level. That works as well.

But only one of these things is necessary. Using the pack spec is the "classic" way (means this exists for a long time), while assigning the quantity classification to the AUoM came a bit later.

Brgds

Juergen

---
All the above is no official SAP statement.

Want to learn EWM?
Check for EWM courses: https://training.sap.com/trainingpath/Applications-Extended+Warehouse+Management-EWM+in+S4HANA
Get a SAP Learning Hub Subscription: https://training.sap.com/learninghub

And it is EWM. NOT eWM - Duh!
And if your question includes the word "transfer order" - do NOT tag the question with Extended Warehouse Management!

[JonDiegoli32]

Hi Juergen,

Does that mean the WT just needs the UoM details from the product master to determine which qty class to use?

Thanks,
Jon

[JuergenPitz]

Hello Jon,

yes, that should work.

I did have an issue a while ago where it did not work properly if the flag for stock-specific UoM was not set, but that must have been a bug.

Edit: the strategy you describe is called "Stock Removal Suggestion According to Quantity" (https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/9832125c23154a179bfa1784cdc9577a/4fc0108a76ac209de10000000a42189d.html). On this page is a reference to another strategy, "Partial Quantities First" (https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/9832125c23154a179bfa1784cdc9577a/4fc0104a76ac209de10000000a42189d.html), where it says 

"

• You have defined a packaging specification for the product in Customizing for SCM Basis under Packing   Packaging Specification.

  Alternatively, instead of defining a packaging specification you can assign the quantity classification to the unit of measure in Customizing for EWM under Master Data  Product  Define Unit of Measure Attributes."

Brgds

Juergen

[Raje1]

thanks for sharing information

[sulemanbasha]

Thank you Rajesh hope it is helpful

[REMOJ]

Hello,

i hope this is still active. I am configuring a quantity classification PICK strategy in S4 EWM. I have 3 classifications, P(PAL), C(CAR) and 1(EA). This used to work until EWM 9.5, but when I tried this in S4 EWM, PAL is working fine, but for CAR, I always get a decimal carton quantity.

For example, the material has the following UOM: 

PAL = 100 EA

CAR = 10 EA

Delivery Quantity is 112 EA. Expectation is to split this into the following breakdown:

P = 100 EA (or 1PAL)

C= 10EA (or 1 CAR)

1 = 2 EA

The actual result is:

P = 100 EA (or 1PAL)

C = 12 EA (1.2 CAR)

I wonder why the CAR classification is getting the remaining 12 EA, when it should be getting 10EA only. Is it a standard bug?

Current Configuration

Packspec - I have 3 levels, EA, CAR and PAL. Each level has quantity classification active with condition record for task Creation (0WHT).

Process Type - WPT 2010 is set to rounding rule = 3 (round down to multiples of a unit)

Pick Strategy - I set 3 different search strategy for each classification

When I check the logs of WT creation, it correctly reads the configuration, but the remaining quantity is being assigned to CAR classification even if it has loose quantity intended for other search strategy.

I hope someone can enlighten.

[kai1961]

thx for your explanation.