on 06-05-2014 9:56 PM
Hi all,
My name is Ryan, and I am one of the material controllers for my company. The materials that I am addressing my comments about are WM using fixed (static) bins. For what its worth we use pick parts in our BOMs for these materials.
We are currently performing, in my opinion too many transactions when issuing materials through MIGO that are not part of Process Orders. Our process has a high degree of variability and therefore material will need to be issued to process orders that were not part of the original BOM or the materials will need to be issued to cost centers. Presently whenever we do this a TR is generated which auto-converts to a TO trying to pull material from our JIT warehouse location. Then someone from the warehouse or myself will kill the TO trying to pull the material from the warehouse. Because of this we tell operators to hit the "Do not generate TR" box in the WM field in MIGO.
Our manufacturing operators then have to generate their own TR's using LB01, convert them to TO's using LT04 and then pick/confirm using LT12. Because our company has been using SAP for less than a year, we are not familiar with all of the nuanced transactions which might allow us to skip steps. Can anyone recommend a way to streamline this process? The best I can think of is to use LT01 and then LT12.
Thank you for your assistance!
Ryan Burke
Hi Ryan,
SAP standard flow to transfer the stock to line side against production order / process order it that
1) Create a Process order / production order
2) Release the process order / production order
3) Run WM material staging within production order(this creates Transfer requirement with reference to Process/ Production order which you can see in the requirement number field also system validates the stock required and the stock sitting in the Line side and creates TR only for balance quantity)
or this can be run separately using LP10 / LP12 transaction which allows you to create TO directly so u can skip step 4
4) List of open TR against the Order using transaction LB13, you can use the TO create option to create Transfer order from the detail screen
5) Pick the required stock against the TO from warehouse bin and transfer to line side
6) Confirm the transfer order using LT12
Now you mention that your manufacturing team create TR at their own which means they are ignoring the validation mentioned in the step 3 or manually controlling by using pen and paper which means they transfer the exact quantity required for production order or over and above the production / process order. Also since they are creating this manually i am hoping that they mention the Production / Process order number in the requirement field manually so that later on u can trace it which TR is against which production / process order also as per standard SAP to transfer the stock to Line side there is a separate movement type 319 is there so i hope they are creating the TR using that.
Again if you are planning to use LT01 then you are ignoring the above validation as well as keeping track of the TO is bit difficult (if there is a need to segregate how many TO is against transfer order
One thing to remember that SAP is very flexible and provide n number of ways to perform the same process, user can adopt the process as per their operational requirement
Hope the above information address your query
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Manish,
Thank you for your reply.
Allow me to provide some additional detail to our process.
Our normal workflow is as you mentioned in steps 1-6. My question relates to a divergence which occurs after step 6. Because we used fixed (static bins), material that is in the manufacturing area (already moved with LT12), can be used for any process order, even if it wasn't reserved for it. Therefore when a material is issued to a Process Order which does not call for it on the Bill of Materials, a Negative quantity is generated in a dynamic bin related to the Process Order. My question has to do with reconciling inventory, after a 261/201/551 movement type in MIGO.
I hope this helps to direct the discussion.
Thanks,
Ryan Burke
HI Steve
If I have understood you correctly, you only need to use LB10 and LT12 to complete.
In LB10 you will see the open TR that you have created when generating your 201/261/551 movement.
Tick line, click on TO in Foreground (TO in Background will also work if material is fixed bin managed) and select the bin from where the stock was taken from then SAVE. LT12 to confirm adhoc pick.
Hope this helps
It's a good idea to test in your sandpit if you have one
Regards
Darren
Hi Darren,
You understand correctly. The only problem is that whenever performing 201/551, our system auto generates a TO to try and pull these materials from our JIT, which makes us have to kill a TO and then start from scratch. I did just get work from our SAP guys that they are about to fix the auto-TO functionality, and they confirmed that LB10->LT12 to be viable.
Thanks,
Ryan
Hi Ryan,
As far as 261 mvt are concern you can very much control this via Control cycle, and no need to adjust the negative and positive Quant system will automatically do this please have a look on the below steps
for eg.
Master data one time setup per material : Define the control cycle record using LPK1 and enter the Destination bin as a PSA Bin where u r transferring the stock as part of Step 1, Take the help from PP team to get the Production supply area
Transactional Data
Transfer the stock to PSA bin using BIN to Bin without considering the requirement before the start of the shift
At the line side operator consume the stock against any production order and pass the detail to system user and user post the detail using MIGO into SAP system, here i am trying to post the consumption against the first line item only
Order creation 60003889
Consumption posting
Stock after consumption posting
For Mvt 201/ 551 since system automatically creates TO you can ask the SAP team to remove the Auto to creation flag as shown below
IMG PATH
SPRO------LE---WM---ACTIVITIES----Define Movement type
Remove any value from the field Automatic TO, if it is blank system won't generate TO automatically
Thanks for your answer Manish.
I know that some of our materials are goods issued, 261, across multiple storage bins in the same storage type, which would defy the specificity of the control cycle I imagine. Howevver for the materials that are department and static bin specific, I am having our SAP team look into the feasability of implementation.
Thanks!
Ryan
User | Count |
---|---|
108 | |
12 | |
11 | |
6 | |
6 | |
4 | |
4 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.