Hi,
Thank you very much for your answer.
Unfortunately there is no 551 movement.
Regards.
Julien.
Hi,
Thank you very much for your answer.
Unfortunately there is no 551 movement.
Regards.
Julien.
Hi,
Thank you.
1) Yes I know, it was to show you that the stock for batch 408152 is only in LS24, it is doesn't appears in MMBE because there is no stock (=0).
2) Yes the stock is under restricted, but we can't transfer to unrestricted using MIGO because of stock = 0 in MM.
Regards
Julien.
Hi
I have looked through the links for this question and i cant seem to see one that fits my criteria
I have TR's from Production and i am splitting TO's based on Picking areas and this is working fimr,
I would now like to add another criterial where the TO also splits based on the number of lines per TO for when a lot of picks are in the same picking area.
The scenario would be that we have say 100 lines in the same area and i would like the TO's to get to say 20 lines maximum and then start another TO
The only thing i can see is to split by Volume but the help on this is not very clear.
Anybody used this??
Regards
Frenchy
since you are talking split within a split (first picking area wise and then number of line item), In my opinion with standard SAP it would be difficult to achieve that you need to write your own code in user exit MWMTO012
without proper analysis it is not advisable to delete this entry, if I have to find out then using t-code LT26 I will first try to find out how the stock got moved to 999/ SCHROTT, Based on this detail probably I can try to find out the RCA why there is a mismatch in between IM / WM at batch level
I suspect they recommend it's run via background job to avoid user error, I also suspect the report program has not been made into a transaction for that reason. End users will not have access to the report unless your security team is giving every one SE38. If end users triggered it in the foreground they could easily select the wrong warehouse or clear quants when only bin data should be cleared. Running it via batch job will allow/force the system to apply a variant and avoid user error.
That's my thought on the "technical reasons". It's technically safer to run it via batch job then manually by support staff every year.
Hi, thank you.
Stock has been moved to 999 SCHROTT using manuel transfer (999).
We have a lot of manual WM transfers (922 TR-ZONE, 921-TRANSFER, 999-SCHROTT, ...) that's why it's very difficult to analyse and reproduce the error.
I'd like to correct the error because we already spend a lot of time to understand how the differencie has been generated, and for the moment we can't explain it.
Regards.
Julien.
Hi
To generate a negative qty there must have been a movement to remove the stock at IM level which should then generate a Transfer Requirement at WM level which needs to be processed.
I would check MB51 to find the movement that generated the removal of the 14 pieces (such as 551, 201,261 etc) I would then check LB10 (remember to select partially delivered as well) and see if there is a corresponding TR which you can then process.
Stock does not get to 999 by itself there has to be a movement to do that and if the stock has gone from IM in MMBE then it should show in MB51
I hope that this helps
Frenchy
what exactly is LS24 showing for this material?
If you have a negative qty you should have a positive one to balance it out as you say the report shows no
inconsistencies
Hello,
I would like to create a transfer order for a group of deliveries in background.
I try to used the LT42 but it's only in foreground.
Does anyone know a program to create this kind of transfer order?
I create my group with the VL06P transaction for the pick and then I would like automatic TO creation. My WM movement is not linked with a MM movement.
Best regards,
Gwen
Hello Gurus
Hoping you are doing well!
Our Process is :
1. Create & Release Purchase order ( ME21n, ME29n)
2. Movement type 101 posting, via MIGO.
Resultant , a Quant is created into WM System in Storage type 902. But Requirement Type field LQUA.BETYP like "B" and
Requirement Number field LQUA.BENUM Like "Purchase Order Number" is not being coping in.
What is the reason?
Configuration is as follow
Movement type
Requirement Type:
Interfaces MM-IM to LE-WM
Thank you very much in advance.
Best Regards!
Adnan
Resultant , a Quant is created into WM System in Storage type 902.
your resultant observation is not correct, Quant gets created only upon putaway TO creation and not upon MIGO, Upon MIGO System create Material documents which internally creates TR and once you will create TO against material document (LT06) or against TR(LT04) system creates entry for 902
Please rerun the scenario and upon MIGO check the stock using T-CODE LX02 you will not find any entry for 902
To All
I have logged a call with SAP to resolve this error.
I had tried to re-create the error but was unable to repleciate the error. Going back through stock movements it was clear that a user had moved stock between bins, added stock, cancelled docs and other misc stock movements. My patience wore thin after 4 hours trying to unravel all of the TOs, PI docs!!
Thank you for all your assistance.
Darren
combine similar materials to one line item in the TO. by adding quantity---Not able to visualize your requirement it because if the material is store in multiple bins how do you want system to suggest one line item with all the source bin. Probably I am missing some point can you please elaborate in detail what is the expectation from system and scenario
If you requirement is to club multiple sales order from different customer then you can look for 2 step picking process in which in the first step system will club the requirement for all the delivery, perform the picking and in second step distribute the material against individual outbound delivery
The stock is Blocked stock. If you scroll to the right in MMBE I would expect you to see the stock there under column header 'Blocked'
Have you looked for any PI count record in table LINV to get some more info.
Manish is correct (which is usually the case ) that by viewing the TO movements you can pretty much work out what has happened and how to correct
Good Luck
One more observations you mention that you use LT01 to create TO for movement type 101 however your setting for movement type 101 says "Manual TO creation is not allowed"
SAP differentiates between posting changes and transfer orders. Posting changes are used if nothing has to be moved, while transfer orders are the medium if a human has to move some material between bins.
What you described is a transfer posting, it just changes the ownership or an allocation or even a batch number, but the stock will not be moved physically.
Still SAP has not use the interim storage types to document such kind of transfers (posting changes) within the WM system. SAP does not just exchange a value in a quant.
Actually pretty similar to MM, where you also have 2 items in your material document, a reduction from the general stock and an increase of the sales order stock.
Such posting changes have to be processed in LU04 transaction.
In this LU04 transaction you can also find historic documents, those documents which you did not see in case the stock was from a single bin in your example, but check it, you can see that those also used the 922 storage type.
You need to talk to your WM counterpart to know about your local customizing.
You should also try yourself the LU04 or let the WM guy show it to you, so that you can see what you have to do there, as this is what you would need to replicate with a function module http://help.sap.com/saphelp_46c/helpdata/de/c6/f83a294afa11d182b90000e829fbfe/content.htm
hi guys,
I met a probelm about the storage bin search.
We have two storage bins A and B. They all have 12 quant capacity. When we putaway the quant one by one until 3 quant in storage bin. Then move one quant to storage B like below. F44-01-00 is Stroage bin A. F44-02-00 is storage bin B.
Then i move the another quant click the create transfer order found it search the F44-02-00 storage bin automatically. But the Storage bin A is not full . Why it automatically search the storage bin B not A? Thanks.
Dear experts
We have a shipment sent to the external customer. this shipment generate a EDI to create inbound delivery .
But now we want to delete the shipment due to some reasons.
an Error generates , Message No VL001
"ASN-EDI is already exist"
How to delete the shipment when the IDOC already sent to customer successfully?
thanks in advance!