Quantcast
Channel: SCN: Message List
Viewing all articles
Browse latest Browse all 8368

Error in available quantity for consumption of Subcontract component in MIGO

$
0
0

Dear Experts,

 

Firstly I would like to inform, I am posting this question after a series of search in SDN as well as for OSS notes and no solution could resolve my problem.  Or may be I could missed any of the thread which may be relevant.

 

Background :

 

 

We have recently carved out an entity from an existing SAP system (EHP 4) and moved to a new system (EHP 5) with new company code.
The functionality what I am looking for, was worked in the previous system and not working in new system.

 

Business Process:

 

 

Raw materials are procured and delivered directly (101-O) to Subcontract vendor.
Subcontracting PO raised for finished product and received (101) through MIGO during which the raw material is consumed (543). 
Batch determination for raw materials at vendor is activated with FEFO strategy and working fine.

 

Scenario where we face issue:

 

 

Subcontract PO with two line items FM1 - 100 qty, FM2 - 100 qty. In both the lines RM1 is one of the component with 50 qty (Total requirement for the PO - 100 qty).

 

We have stock with vendor as RM1 Batch1 - 30 qty, RM1 Batch2 - 100 qty, which is more than requirement.

 

While doing MIGO, for the first line item (FM1), batch determination of the component (RM1) the quantity is proposed as below:

Batch1 - 30 qty  (Available - 30 Qty)
Batch2 - 20 qty  (Available - 100 Qty)  which is correct.

 

And for the second line item (FM2), during batch determination of the component the quantity still proposes same as above.
Which in turn, throws an error message 'Deficit of Stock w. vendor unr.XXXX XXX XXX O' Message no. M7021, while posting.

 

In our old system, for the second line item the quantity proposal is as below:

(Batch1 not proposed at all)
Batch 2 - 50 Qty (Available - 80 qty) which should be the logical way.

 

I have done comparisons related to availability checks, checking rule (since batch determination working fine) in both the system and no difference.

Also took help from technical team to see if any development done on the old system but found nothing related to this.

 

Please suggest what are all the other areas that I may need to check and where I am missing. I have tried to explain in detail, still if any other details are required I can provide. 

 

Thanks in advance,

Ramesh


Viewing all articles
Browse latest Browse all 8368

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>