Special Movement in WM1 view does not default in MIGO

[Former Member]

Hello fellow experts, I have recently configured a Special Movement indicator in WM and properly linked it in the IM-WM interface IMG node. Specifically the function of this SMI is to automatically place the stock into a fixed bin upon PO GR.

One thing is stumping me.  For my test material in the sandbox, I have indicated this SMI on the WM1 view of the material master.  I then created a PO for the material and in MIGO when I was performing the goods receipt, I was assuming that the value stored on the WM1 view would be adopted into the WM tab when performing the goods receipt.  Is there some reason why this might not be taking place?  I verified that the plant and warehouse match the material master and that the plant/SLOC on the PO match the warehouse value where the WM1 value was maintained.  I don't really see the purpose of SAP putting the indicator on the WM1 view if the value isn't going to be adopted for MM-IM transactions like MIGO and I have to insert it manually.

[Former Member · Accepted solution]

Hi,

If you have maintained the data properly, the SPI should be defaluted in MIGO screen automatically.

Please verify the settings once again,  refer below link for details.

http://help.sap.com/saphelp_470/helpdata/en/c6/f83cfb4afa11d182b90000e829fbfe/content.htm

Regards

Vijay

[Former Member · Accepted solution]

OK, so I tested further this morning - last night I stopped completely and did not save the MIGO transaction because the value on the WM tab for Special Movement was null and I was expecting the value from the material master.  Despite the value in MIGO being null, when I saved the GR, the stock was correctly placed in the desired fixed bin in 100 (instead of a dynamic bin in 902). 

So it would appear that, at least in my client's system, the system behavior is as follows:

In MIGO, irrespective of the maintenance status in the material master, the value for Special Movement is null. 

If Special Movement is maintained in the material master, that value is adopted in the background.

At this point I'm assuming that either something is amiss in this installation or...SAP's intent is that the material master value is considered in the background and MIGO will always show null so that a user can select an alternate Special Movement (if more than one is configured).

Juergen / Thierry / Vijaya - is this an accurate summation of the behavior in your systems or is something different (e.g., you actually see the value maintained in the material master defaulted in MIGO)?

[JL23 · Accepted solution]

In my production system the BSSKZ is visible in MIGO  and got defaulted from material master.

However, I just tested it again in an IDES system and the indicator did not show up.

I did not post, so I cannot tell if it is still taken in background

if it is taken in background, I would still think this is a bug when it is not shown in MIGO.

How can a user replace this indicator with a blank entry if the field is empty in the screen in any case?

[Former Member · Accepted solution]

My guess at the intention, if the IDES behavior is "correct", is that if BSSKZ is set in the material master it means the intent is to ALWAYS invoke that value for BSSKZ (in the background) and that the system will process all goods movements using that material master value unless the user selects a different value for BSSKZ (although not a null value).  I think this means that if you EVER wish to process a goods movement ignoring the value in the material master and instead use the inital (null) value, do not maintain a value in the material master and instead handle on a transaction by transaction basis.

In my mind it seems to be similar to how Special Procurement works on the MRP2 view with MRP generated requisitions if, for example, you set a value of "30" for Subcon.  All the reqs will have an item category of "L" which is nonmodifiable.  I think the concept is similar here, although a bit more complex since the value is not visible in MIGO in my system as it seems to be in yours.

Wondering if the IDES system (and my system) have an issue or if there's some config or exit in your system which is copying the material master value so it's visible in MIGO. 

[JL23 · Accepted solution]

Just compared a different production system, and the BSSKZ field was not defaulted to MIGO.

Then searched thru our Modification database and did not find any document.

finally I searched the place where the MIGO strcuture gets filled and found a modification.

if current_sugg_bsskz is initial and not mlvs-bsskz is initial.

  current_sugg_bsskz = mlvs-bsskz.

endif.

Sorry for the confustion caused. I have to make an appointment with my colleague next week.

[Former Member · Accepted solution]

Thanks Jürgen, I can consistently count on you and the other experts to help me out in a bewildering situation!

So at the end of the day it would seem that this behavior of the Special Movement field in MIGO always defaulting to null/initial instead of defaulting the value maintained on the material master (and stored in table MLGN and/or structure MLVS) is SAP standard.  It is good to know about the modification in your system that does copy it into MIGO.  I might ask our developer to insert that since, from a user training perspective, it makes a lot more sense (this is a brand new implementation for them).

Regards,

Jason

[andrea_dn · Accepted solution]

Dear jrgen.lins,

where did you perform the modification?

if current_sugg_bsskz is initial and not mlvs-bsskz is initial.
current_sugg_bsskz = mlvs-bsskz.
endif.

In a BADI/user exit or in the standard code (include LMIGOKW1) ?

Thanks

[JL23]

I am very certain that the special movement indicator will default from material master to the MIGO screen, I just verified it again in my system.

Maybe you have a bug in your system, check this OSS Note 1617602 - WM data disappears after you choose "Enter" to confirm

[Former Member]

Hi,

I have the same issue on my system. This flag is not shown in MIGO !!!

Not sure if OSS note given will solve it... Let's see.

Thx

[JL23]

but you see the field in MIGO, right?

is that field eventually made mandatory?

[Former Member]

We can see this field in migo, you're right but is not mandatory...

But by reading SAP documentation it seems standard not to take this value in material masterdata ???

Why is not flagged by default in this case... mystery !!!