cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

No valid bin types found (storage type: XXXX, HU type: )

0 Likes
5,334

Hello,

While creating WT I am getting below error in SLG1

Error - No valid bin types found (storage type: 1003, HU type: ) - screenshot attached.

Below are the config steps done:-

Inbound Delivery has HU packing.

1) Storage type has "HU Check" selected.

2) Assign Storage Bin Types to Storage Types

3) Define HU Types for Each Warehouse Number and Assign HU Type Group

4) Define HU Types for Each Storage Type

5) Define HU Types for Each Storage Bin Type

6) Storage bins has "Bin type" assigned"

error.png

Regards,

Mihir

Accepted Solutions (0)

Answers (9)

Answers (9)

JuergenPitz
Product and Topic Expert
Product and Topic Expert

Hi,

ok, I tested this in my system, and I actually guess we have a little functionality gap here.

In the process you have the process step IB02 (always assuming you use the standard BC set setting). IB02 is a deconsolidation step. Means the system will check if you have a requirement for a deconsolidation and if yes, move the pallet via a deconsolidation work center.

This type of step requires that the final WTs (step IB03) are either created before or with the step IB02. Techncially where ever the flag for the "Product WT" is set in the customizing for the process, these final WTs are created BEFORE the WT for the step where the flag is set.

So if your sequence is:

- IB01
- IB02
- IB03

and the "Prod/HU WT" flag is set at IB01, the system FIRST creates the WTs for IB03, then the WT for IB01. If the "Prod/HU WT" flag is set at IB02, the WT for IB01 is created (manually or however). Once you confirm the first WT and the system triggers the next steps, it first creates the WTs for IB03, then for IB02.

Again: The deconsolidation step requires this. For any other combination of (inbound) steps, you would set the "Prod/HU WT" flag most probably at the step IB03.

Now what the problem is: if the storage types which are determined for the step IB03 have a HU type check, the system does not now what HU type you have and does not find a bin.

The HU you have in that moment is not used (how should it, as you will have to deconsolidate). Usually the system will look for a pack spec for palletization (via the determination procedure you have assigned in the warehouse number). But in combination of settings this seems not to work. At least I did not get the system to find the one I have created. The is also a determination procedure for deconsolidation, but for this one I actually have never found out how it should work.

My recommendation would be: do not use IB02. This step is not practical (in my opinion) due to that it requires the WTs for the final bin to be created before. If the deconsolidation takes a longer time, the final bin is blocked all the time. It is also very difficult to change the quantity in case you want to pack less. And yes, as the system does not seem to find a packaging specification, it anyway will always try to find one bin for the complete quantity.

Instead: use a packing step. In my system I can find a step IPK1 (Pack (Inbound)). Or define you own. That way, you only create the final WTs once the step at the pack work center is done. OK, the negative side is that every HU which is in the process has to move via the pack work center, if a deconsolidation is required or not. But probably it is helpful when you receive HUs to check them there anyway. And the disadvantage of the early WT creation and the additional settings for the determination of the deconsolidation requirement is much more (again, in my opionion).

Brgds

Juergen

0 Likes

Hi mihir.sharma,
did you get a solution to your problem? I am also facing the same issue.
Thanks

Regards

martinprokop
Participant
0 Likes

Hello Mihir,

I have exacty the same deconsolidation scenario, as you describe.

For deconsolidation, the system creates ALWAYS product-WT for step IB03. Therefore no check on HU-Type is performed at this step (and it is not necessary to set it up for the HU-Type of unloaded HU).

But, as I can see in yout log, the main issue seems to be, the system was not able to create Penalty table to collect all possible combinations of NLTYP, NLBER, NPTYP.

This is probably due to missing (I don't see it in your list) setup of Altenative bin type sequence for your storage type and bin type, which might be specified in your product master:

BR

Martin

JuergenPitz
Product and Topic Expert
Product and Topic Expert
0 Likes

Hi,

"product-WT for step IB03. Therefore no check on HU-Type is performed at this step"

the one thing has nothing to do with the other. Also with product-WTs the system can create a HU type check. The problem here is that the system does not know which HU type to use.

Brgds

Juergen

martinprokop
Participant
0 Likes

Hi Juergen,


you are right. there are 2 separate questions there.

First, let me comment on the HU-type check, you wrote lastly:

In the EWM standard the HU-Type will only be set in Product-WT only if one of these conditions is true:
1) There is a suitable packspec for the quantity of the product WT.
or
2) The product WT moves the full quantity of the source HU (we call this a homogeneous HU move)

If it is a mixed HU (like in our example) the HU type of the source HU cannot be taken over, as it is clear that that HU cannot be putawayed (since there are many different product WTs with different destination bins, the source HU will be split up). In this case, the HU-Type check is not performed during putaway strategy.

But the main issue (destination bin was not found) is probably caused by missing setup, as I described.

Have a nice day

Martin

JuergenPitz
Product and Topic Expert
Product and Topic Expert
0 Likes

Hi,

"2) The product WT moves the full quantity of the source HU (we call this a homogeneous HU move)"

Did I wrote that somewhere? OK, might be.

Again, yes, the HU type check can not be made, because the system does not know which HU type to use. But again, this has nothing to do with the HU-WT or product-WT.

And the missing setup for alternative bin types is something you only use if you directly assign a bin type to the product, but not when you have a HU type check based on the HU type through a pack spec or received HU, for that the table with the assingment HU type to bin type is used ... I think at least. Never checked that. But I would not think so.

Brgds

Juergen

Ajit_Routray
Active Contributor
0 Likes

Hi mihir.sharma,

Could you please check HU Type is present in HU-1*95 (). HU Type maintained in Pack material and or spec ?

Kind Regards,

Ajit

0 Likes

Hello Eric,

hu-bin-type.png

I have maintained the assignment in "Define HU Types for Each Storage Bin Type". PFA screenshot.

Regards,

Mihir

0 Likes

Hello Juergen,

Thanks for your response. You got it right. Let me explain the whole scenario

Process - Deconsolidation (HU based) & POSC

When I create inbound delivery, I have 2 different type of materials. In Inbound Delivery they are packed in a same box(menas a HU is created in VL31n). In EWM, I unload the delivery and my first step IB01 is triggered. I confirm the WO of it and automatically two WT for IB03 and 1 WT for IB02(Decons) are triggered(if HU type is passed in debug mode for IB03 step). But at IB03 level the HU type is not found and thus goes into error as shown in my first shared screenshot.

To your first question = HU type is assigned to warehouse and HU type Group. Also assigned to 2 Storage types which are used for IB03 step as 2 material goes to 2 different storage types(step for final putaway after Deconsolidation) and these 2 storage types are HU Type checked at storage type level. Decons storage type is not HU type checked.

I store 2 materials in two different box while put away into final destination bins. Do you mean to say although the new pack Boxes will be mentioned in Decons tcode /SCWM/DCONS, the packaging specifications need to be maintained so that HU type is determined while WT creation at IB03 step? OR can I trigger IB03 step only after IB02 WT confirmation and decons step executed(/SCWM/DCONS)? but how?

Regards,

Mihir

0 Likes

HI Mihir..Have you checked your assignment under node GR Process->HU type->Define HU type for each storage bin type.

I was also facing the similar issue and after maintaining the entries it worked and destination data determined successfully.

JuergenPitz
Product and Topic Expert
Product and Topic Expert
0 Likes

Hi,

and after looking into the log a little bit more I think I know what is happening.

What are you trying exactly? You have a process oriented storage control, but the setting is done to create the final WT immediately at the beginning of the process. In this situation the system does not know which HU you putaway and at least seem to need a packaging specification for palletization in order to find a HU type.

Brgds

Juergen

JuergenPitz
Product and Topic Expert
Product and Topic Expert
0 Likes

Hi mihir.sharma ,

this line: "No valid bin types found (storage type: 1003, HU type: )" with a big nothing after the HU type" shows that no HU type seems to exist. Does you have have any HU type?

Brgds

Juergen

---
Want to learn EWM?
Check for EWM courses @ https://training.sap.com/trainingpath/Applications-Logistics+Execution+%26+Warehouse+Management-SAP+...
Get a SAP Learning Hub Subscription: https://training.sap.com/shop/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!

0 Likes

Hi!

I think it is happening because the system creates product WT, so HU type doesn't taken into account. You have to create HU WT if you need control HU type in St.Type.

BR, Alex.

JuergenPitz
Product and Topic Expert
Product and Topic Expert
0 Likes

Hi,

sorry, but that is wrong. Of course you don't need a HU WT for a HU type check.

Brgds

Juergen