Problem in Migo BAdi

[Former Member]

Hi All...

I have written a BDC for MIGO for Transfer Posting (A08) , with Reference Document (R10)-Others and Movement Type 911.

First I go into the Tcode MIGO and set these parameters and come back.

Then I run the BDC , it runs properly.

But once I change these parameters one or all of them, the BDC does not run properly. It says that movement type does not exist.

While in my BDC , I have assigned the above parameters .So it should run properly for these parameters, but it still shows the error.

Can anyone please suggest me a solution .

Thanks in advance.

Sangeet.

[Former Member]

Hi All...

I have written a BDC for MIGO for Transfer Posting (A08) , with Reference Document (R10)-Others and Movement Type 911.

First I go into the Tcode MIGO and set these parameters and come back.

Then I run the BDC , it runs properly.

But once I change these parameters one or all of them, the BDC does not run properly. It says that movement type does not exist.

While in my BDC , I have assigned the above parameters .So it should run properly for these parameters, but it still shows the error.

Can anyone please suggest me a solution .

Thanks in advance.

Sangeet.

[RaymondGiuseppi]

Look at [Note 504936 - Batch input compatibility of new transactions|https://service.sap.com/sap/support/notes/504936]

With release 4.6B, SAP has delivered new enjoy transactions. Examples
are transactions MIGO, MEPO, VL01N, VL02N. These transactions are not
supported for batch input processing. For details please read notes
304122,381630 457925 and 491875.

or [Note 304122 - MIGO: Batch input and CATT not supported|https://service.sap.com/sap/support/notes/304122]

Reason and Prerequisites
The new goods movement transaction MIGO is not intended for use with batch input and CATT.
The reason for this is that batch input and CATT are based on the screen technique, the Enjoy transactions like MIGO (single screen transactions) work more and more with the control technique. Batch input and controls are not compatible.
Solution
There are two alternatives:
Use the following BAPIs to post goods movements in the background:
      Object name:  GoodsMovement
      Object type:  US2017
      Method:       Cancel (cancel goods movement)
                    CreateFromData (post goods movement)
The old goods movement transactions (MB01, MB0A, MB1A, MB1B, MB1C, MB31) are still supported. These transactions support batch input and CATT.

(BAPI refers to function module BAPI_GOODSMVT_CREATE)

Regards