Subcontracting component PR remains in MD04 after GR of finished product

[former_member332424]

Dear,

i have the following case.

1 finished product to be assembled by a subcontractor

The finished product consists of 3 components of which 2 are supplied to the subcontractor directly from the vendor, and 1 is supplied to the subcontractor from our storage location.

The BOM explode generates 1 subcontractor PR for the finished product and a PR for each component.

I create a PO for the finished product PR

Now the 2 PR's for the external vendors are converted into PO's and received in subcontractor stock which raised the subcon stock

The other component has also a PR and according to this scenario (link) I should do the posting via ME2O (http://saphelp.ucc.ovgu.de/NW750/EN/8f/a9ce5314894208e10000000a174cb4/frameset.htm)

Now at this stage all the component stock is at the subcontractor.

After GR of the finished product in our storage location the following happens:

Finished product after GR is raised in our storage location (correct)

Component from vendor booked to 0 after GR of finished product in storage location (correct)

Component which is supplied from our storage location to the subcontractor still has an open PR even after GR of the finished product in our sloc

Also in ME2O i keep seeing an open reservation

In the MRP area of the subcontractor (LBW_LUM) i have entered special procurement key 20 for the components from external vendor and 45 for the component from sloc (i have to enter a special procurement key). Without speical procurement key the subcontracting process works fine on MRP 1 level NOT MRP area level. Here i work with deliveries, the MRP area i do the posting directly from ME2O as the documentation in the link describes.

Any idea why the PR is not disappearing after the GR of the finished product?

[former_member332424]

The problem is most likely that i need a stock transfer reservation but the system created a purchase requisition for a stock transport from sloc to sloc. Could this be due to mrp run settings in mbdt? I have entered 1, that is should only create PR's?

Next to that we do use STO's for sloc to sloc with Badi BADI MD_EXT_SUP, since it should use different slocs to create STO's from. I use special procurment key 45 for this in case it should take sloc A and Z1 when it should take sloc B. Can this me the cause?

Please let me know.

Thanks.

[former_member332424]

Issue solved!

I created a new special procurement key for subcon deliveries and entered that in the mrp area of the subcontractor in the component. I made the mistake to take 45 itself for the Badi to determine the issuing storage location instead of making a Z copy of it (which i did for the other issuiing storage locations. So i had 45 as spec proc key in the MRP are of the subcon but also in the MRP area of the to be replenished storlocs. Now with the Badi active it took the issuing storage location i defined in 45 (with the active Badi) so now it not only created a PR for sloc to sloc but also for sloc to subcontractor which is not correct, it should make a stock transfer reservartion. Now i created a copy of the original 45 settings (which creates a reserveration) and put that special proc key in the mrp area of the subcon of the component. Issue solved.