cancel
Showing results for 
Search instead for 
Did you mean: 

Auto Transfer Posting from MIGO transaction code

Former Member
0 Kudos

Friends Help Pls

Whenever goods receipt happens with movement type 101 for material XXXXX in MIGO transaction code, the system should trigger auto transfer posting with movement type 309 for material yyyyy in the background. So that material xxxxx will be auto transfer posted to material yyyyyyy.

could you please mention exit names (customer exit or user exit names ) which can be called from MIGO transaction code while creating a receipt with movement type 101 in order to automatically trigger transfer posting with movement type 309 in the background f?.

Accepted Solutions (1)

Accepted Solutions (1)

JL23
Active Contributor
0 Kudos

The BAPI can be called from a Z-report that runs every x minutes or just triggered by an event.

The report does its checks whether an extra movement is needed and fills the BAPI structures and starts the BAPI

Former Member
0 Kudos

Great Thank You !

former_member183424
Active Contributor
0 Kudos

If your question is answered then please accept the answer and close the question.

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi,

We have done similar requirement using output type concept. Output type will have driver program where you have to call standard BAPI for goods posting. Output type trigger can be constrained based on your requirement.

Regards,

Sundaresan.K

Former Member
0 Kudos

Great to know output type option, Thank you so much.

Former Member
0 Kudos

Thanks for your reply. Before I speak to my technical people. I have another short question here.

How can we call this BAPI'BAPI_GOODSMVT_CREATE' from MIGO immediately after saving the receipt to create to create transfer posting?

Thanks

JL23
Active Contributor
0 Kudos

An exit is executed before the data is actually saved, hence you cannot execute a transfer posting from here as the stock is not yet posted at this very moment.

Also kindly search before asking as this has been discussed several times before e.g. here and here