Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

BAPI_GOODSMVT_CREATE Issue

Former Member
0 Likes
773

I execute the BAPI and get a material docno and a material doc year. No errors. I do an MB51 and it says the doc does not exist?

What should I check?

Thank-You.

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
746

You need a commit work after the BAPI call.

6 REPLIES 6
Read only

Former Member
0 Likes
747

You need a commit work after the BAPI call.

Read only

0 Likes
746

So I assume from your response that a test run of the BAPI will not do a commit work? It must put it in code and "COMMIT WORK"?

Thank-You.

Read only

0 Likes
746

Yep. Although you can get the BAPI COMMIT WORK to run in test mode but I cannot remember how to using SE37.

Read only

0 Likes
746

Yes Tom.

YOu are right.

Here is an excerpt from the BAPI FM's documentation in SE37:

"Transaction control is not implemented. The calling program therefore

has to execute the Commit Work itself after this method has been

successfully called (in other words, if no errors were reported in the

Return parameter)."

Read only

0 Likes
746

I think the path changed innext versions and this is a rough translation. but...

In se37 go to menu function module->Verify->Sequential test.

You put the bapi you want to use and bapi_commit_work. After the first bapi when you try to return you'll get to the second function to commit

Read only

Former Member
0 Likes
746

Hi Tom,

Do you call the BAPI : 'BAPI_TRANSACTION_COMMIT' after your call to BAPI_GOODSMVT_CREATE?

Kind Regards