Consignment Pick-Up - To be posted directly into blocked stock

[basmax]

Hi Guys,

i googled and browsed a lot, but couldn´t find a proper solution on that topic.

We have a requirement to post consigment stock upon a Consignment Pick-Up directly into blocked stock.

SAP standard is using (and only has) Sched.L.Cat. F1 with Movement type 632 for that process, and it will always get posted into unrestricted use.

I also tried out recommendations on some posts in the forum - such as change movement type to 657 -, but this also doesn´t solve it in my opinion. -> If for example using movement type 657, then yes it posts it into blocked stock, but it is NOT updating the consignment stock.

Does it perhaps work to use QM so that the upon posting goods receipt, the stock is cleared out of the consignment stock, posted back into the own storage location, and into quality inspection?
What would be the necessary settings for that? In a first test this also didn´t work.

Thanks a lot in advance!

[basmax · Accepted solution]

Hi 3a9e4ce873a94034b33dc62b0ce600ee,

sorry for the late reply. Just wanted to quickly share how we solved the problem, perhaps this will also help other people for the future.

We solved it now with a development/enhancement in BADI LE_SHP_GOODSMOVEMENT.

The enhancement extends the functionality of the interface IF_EX_LE_SHP_GOODSMOVEMENT so that during post goods receipt not only the movement via 632 into unrestricted but directly afterwards a second posting with movement 344 is processed. Relevant information that needs to be copied over into the second movement posting from table MSEG includes MATNR, WERKS and LGORT. Fields SOBKZ and KUNNR need to be empty as stock is no longer consignment stock after the first goods receipt posting 632.

Then when checking the material document, you can see all movements including:

632 W -, 632 + blank, 344 - blank and 344 + blank.

KR,
Sebastian

[DominikTylczyn · Accepted solution]

Thank you for the update 🙂

[jignesh_mehta3 · Accepted solution]

@basmax

Appreciate you coming back and updating the Forum on the Implemented Solution.

Thanks,

[DominikTylczyn]

Hello basmax

I don't think you are going to find a single material movement type in SAP standard setting that would post consignment pick up to blocked stock. 657 will not do here as it's to post returns not consignment pick ups.

Having said that I can see two ways to implement your requirement.

The first one is to tweak quantity update settings of 632 movement type. The quantity update is driven by quantity string, which is MAV4 in case of 632 - transaction OMJJ:

The quantity string is defined in T156M table:

My educated guess is that by changing L01 and C01 to LS1 and CS1 respectively, you'll make the consignment pick up to post to blocked stock. However, no guarantees here - I've not tested that. Bear in mind that if you go this way, you are on SAP turf, changing system tables that counts as a system modification. Thus if anything goes wrong, you are on your own. Of course, test carefully, also for any side effects. Better yet create a copy of 632 and copy of MVA4 quantity string and make any changes to the copies only.

Another, more standard approach would be to use standard 632 and post consignment pick ups to unrestricted stock and trigger a transfer posting with 344 from the unrestricted stock to blocked stock. The automation can be implemented either with a custom output type from 632 material document or with material document posting BadI MB_DOCUMENT_BADI or user exit MB_CF001. Personally I prefer the custom output type approach that gives you a good visibility of second step material documents and good monitoring. The exact, step-by-step implementation is a bit out of the scope of a simple Q&A, however it's not that difficult once you know your way around MM configuration and ABAP programming.

The former approach is more risky but it implements the requirement with a single material document. The latter is 100% standard at a price of two step postings.

Best regards

Dominik Tylczynski

[basmax]

Hi Dominic,

thanks a lot, i really appreciate your detailed answer, and a very good explanation.

I will check that with MM/ABAP colleagues, and as soon i´ve tested and checked that i will post again with the results and what/if that worked out.

But again: Thanks!

[Lakshmipathi]

When you post a query and give further updates, please add the content under "Comments" and not under "Answer" as you were not answering to a query but only providing additional informations as asked by the members. Also, when you add the text under Comments, it will be intimated to the person to whom you are responding whereas, if you add the text under Answer, the member will not be intimated. By the way, your above answer has been converted as comment by me.