diff between MIGO and MB01 tcode.

[#1]

Dear all

Whats is the difference between cancelling GR from MIGO tcode and MB01 tcode.

Actually I got problem when GR was cancelled by using tcode MB01 (movt. type- 102). After that when i tried to cancel the part2 excise (tcode- J1IEX) i got the message "No Part I exists for availing credit in excise invoice 68150 2009". But I created the same scenario and cancelled the GR using migo then there was no problem. Still I couldn know the difference.......

With regards

Pardeep Sharma

[Former Member]

Dear Pradeep ,

MIGO is the single T code that gives the facility to carryout various inventory management transactions .

Each an every transaction carried out in MIGO also has a separate TCODE.

In your case as per the sys the material document should be cancelled .

While doing it through MIGO u have selected the right options & cancelled the material document .

But in MB01 u have not cacelled but carried out a ggods receipt in reverse direction . If not

using MIGO , u should have used MBST instead of MB01 .

Pls try with MBST and it would work fine.

Hope it is helpful .

Regards

Anis

[Former Member]

thnks for ur replies..

Her in this case part2 has been updated and then I did 102 in mb01. But if i do mb01 for 102 movement type then it gives me the error in J1iex. If i do migo for reversal of GR then i am able to cancel the part2 also. Is there any solution where mb01 has been done for 102 and after that i could use J1iex tcode for cancelling part2 CENVAT.

with regards

Pardeep Sharma

[Former Member]

Hi pradeep

why you r doing MB01 For 102 movement type where you have like for the 101 Movement document in that transaction code

either you can do cancellation in MBST or in MIGO.

And excise process i already told you in the above explanation

with regards

shrinivas gangoor

[Former Member]

OF COURSE SIR YOU ARE RIGHT.....

but things have happened in application server thats why i am looking for remedy......

I have discussed with the enduser to not to use mb01 in future.

with regards

Pardeep Sharma