Where does MIGO store the GI GR reference link?

[former_member627818]

Dear All,

We have been developing custom transaction codes for Split Valuation to do "Goods Issue" and "Goods Receipt" like MIGO, since we are dealing with various Valuation Types during our process.

My question is, when a Goods Issued material (Ex: Material no: 810 from Plant 0101 to Plant 0105), once received using MIGO, if we try to receive the same Material Document again, it shows a error pop-up screen stating that the "Batch ******* has already been posted in stock". Check this image migo.jpg for your reference.

I believe MIGO stores some reference data somewhere to perform this validation. Can anyone tell me where and how does this reference data gets stored (Table or Dynamic checking or etc...). I need this option to be implemented in our custom transaction to check the link between Movement type 351 and 101.

Please help me...

Thanks,

Ashwin.

[former_member191936]

Hi Ashwin B,

If I am understanding correct, you are trying to understand where does the validation happens for this message" Batch ******* has already been posted in stock(M7(668)).

In batch management tables MCHA, MCH1, there is a field which stores last goods received date (LWEDT). If there is a date, system puts the error message.

Please let me know if it helps.

Regards,

Madhusmita

[former_member627818]

Hi Madhusmita,

Sorry for the delayed reply. Let me go with an example. I am doing Goods Issue for Material no: 810 from Plant 0101 of a batch 0000000261 for a quantity of 9 (from 3 different - 3 from PIM, 3 from RR and 3 from N) and doing Goods Receipt on Plant 0105 for a quantity of 3(PIM). If I again try to receive a quantity from PIM, MIGO displays the error. This is the logic I need to know whether how does MIGO checks the issued and received relation?

Also if I do GI and GR for a quantity of 1 for 3 times individually (3 * 1 PIM), how do we relate the material documents created (other than time - As 1000s of receords will be issued and received in real time)?

Thanks for your time.

[former_member532753]

Have you tried debugging and checking the kind of validation that the SAP standard code is doing that causes it to log the message?

[former_member627818]

Hi Joseph, Sorry for the delayed response. I tried debugging "MIGO" transaction and unable to find anywhere regarding the reference.

[former_member627818]

Unable to find the reference link. Hence, implemented alternative custom solution in our custom program.