topic Re: BAPI_GOODSMVT_CREATE for 305 got problem in Application Development and Automation Discussions

BAPI_GOODSMVT_CREATE for 305 got problem

Former Member — Tue, 04 Sep 2007 05:53:44 GMT

Hi all,

We have a program, first to call BAPI_GOODSMVT_CREATE movement type=303, then execute BAPI_TRANSACTION_COMMIT. It's OK, but next, we call BAPI_GOODSMVT_CREATE using movement 305, the function return error message as following:PL Stock in transfer exceeded by 1 EAC : W78E58B-40 A23P, but open new session call mb1b is work. Don't know why 303 and 305 can't work together? Did anyone know how to solve this problem? Thanks!

Re: BAPI_GOODSMVT_CREATE for 305 got problem

Former Member — Tue, 04 Sep 2007 09:03:27 GMT

Hi,

Please put 2 second's wait between both the call.(303 and 305).

And let me know if it is working or not.

Regards,

Saroj

Re: BAPI_GOODSMVT_CREATE for 305 got problem

Former Member — Tue, 04 Sep 2007 09:40:23 GMT

Hi,

We try to wait over 100 seconds and also try dequeue_all, but dont' work.

It seem like can't get plant stock with do 305 movement. But using MM03 check, there are always have correct quantity at plant stock.

After BAPI_GOODSMVT_CREATE fail, we using MB1B is all done.

Don't know why 303+305 is fail?

Re: BAPI_GOODSMVT_CREATE for 305 got problem

Former Member — Sat, 21 Apr 2012 07:02:15 GMT

Dear Former Member,

Instead of BAPI_TRANSACTION_COMMIT go for COMMIT WORK AND WAIT.

This will wait for next step to execute until the previous process is not executed.

no need to go for dequeue_all.

With Regards,

Akshay

Re: BAPI_GOODSMVT_CREATE for 305 got problem

Former Member — Sat, 21 Apr 2012 07:28:37 GMT

Hi,

If you feel this a technical problem use function 'C14Z_WAIT_ON_COMMIT' after BAPI.. and commit BAPI.

Otherwise consult functional person.

Regards,

Phani.

Re: BAPI_GOODSMVT_CREATE for 305 got problem

pushkar_dhale — Sat, 21 Apr 2012 15:47:34 GMT

Hi Kate

The problem you faced to has a simple solution. Before calling every BAPI which causes asynchronous updates insert 'SET UPDATE TASK LOCAL' statement. It turns on local update mode upto next COMMIT statement. That is, all the updates will take place synchronously in the same task and after next COMMIT .

SET UPDATE TASK LOCAL.

CALL FUNCTION 'BAPI_GOODSMVT_CREATE'

......

COMMIT WORK.

Try this & let me know.

Regards,

Pushkar

Re: BAPI_GOODSMVT_CREATE for 305 got problem

former_member214878 — Sat, 21 Apr 2012 16:22:59 GMT

SET UPDATE TASK LOCAL.

is the solution .........