Problem with migo

[Former Member]

Hi,

i have a big problem with migo since 2-3 weeks. For the same material i must book a good receipt to an outbound delivery (we are usinf intercompany deliveries with our head-quarters). I either get Error Code 4 - delivery does not exist or i can choose the outbound delivery, mark the position ok, get a material document number but in MB51 nothing appears, the stock isn't modified and i get on screen and in mb03 the document numer doesn't exist.... i also get a commical message - material booking stopped by userxxxxx and when i choose step into position SAP throws me to SO01- but i havn't any rights.

I've cheked the MM02 settings nothing changed in the last 6 months, the IC delivery plan is the same.

Maybe someone knows what happens...

Many thanks,

Bianca

[Former Member · Accepted solution]

Hi,

Please check the if Outbound delivery happen (VL10B). then received Outbound delivery number.

then you have done PGI (VL02N)

If yes..

please check the acconting entries happen or Not (MIGO/MB03).

SAM

Edited by: Saminathan Gopalan on Jun 23, 2010 2:32 PM

[Former Member · Accepted solution]

hi,

after i book migo to the delivery i get a material document number f.ex. 5000015407 - at the bottom of the screen appears the message "Material document number 5000015407 was booked ok" - colour green.

In the MB03 i get error that this document number doesn't exist........

in the MB51 i can't find it either but in MR51 i find the quantity the stock doesn't the change the quantity after booking in MB52 but in accounting there is a value increase....

[JL23 · Accepted solution]

the message with the document number is issued before the program technically finished its job.

Storing the values in the database tables comes after this message.

If there is a failure at this stage, then the user usually gets an express message informing him about a posting failure.

However, this express message is not really to understand from a user. he should contact the local helpdesk if such happens.

the local help desk can then check in SM13 (select the posting failure and click header icon) what the error is that caused the posting faiilure.

[Former Member · Accepted solution]

Hi Juergen,

many thanks. With SM13 we found out what it was - different ZPIC price from the netto price in the delivery plan and from there the conflict.

Thanks again.

Bianca

[Former Member]

Hi,

This is cross company stock transfer.

Please note have you done PGI (Post goods Issue) for the delivery created?

Cheers,

Satish Purandare

[Former Member]

Hello,

yes, for the delivery from our head-quarters the post goods issue was made. That's why we can't figure out what happens.

Bianca

[Former Member]

Give the details of Movement type You have assigned for the both the COCD

Regards

Iqbal

[Former Member]

the cross company delivey has movement type 643 and my receipt of goods to an PO m. type 101.