Problem with bapi BAPI_PRODORDCONF_CREATE_TT

[rudy_schmitz]

Hello Everybody,

I have a strange problem with the use of bapi BAPI_PRODORDCONF_CREATE_TT.

This bapi is used in a RFC function I wrote.

As the problem does not occur on the test platform, I can't check exactly its behaviour.

Anyway, it seems that, from time to time, the bapi returns a message telling the confirmation is saved, but in reality, it is not!!!

Unfortunately, I can't reproduce the case on our test platform.

Because I don't know what makes this happen.

I tried several times, but without success.

It only appears on the production platform, and only for several weeks ago.

In the past, I did not have this problem...

Have you already experienced this problem? And how did you solve it?

Thanks in advance for your help on this subject...

Regards,

Rudy

[Former Member]

Hi Rudy ,

Are u commting the work or not ?

check the return table of this BAPI based on that u need to commit the work ?

if return[] is initial.

commit work.

endif.

if u are doing like this , then u need to check what kind of errors u are getting in the return internal table.

regards

prabhu

[rudy_schmitz]

Thank you for your very fast reply Prabhu.

But yes, there is a commit work after the call to the bapi.

I don't know what is the error message given by the bapi.

The only thing I know is that the returned error type is not "A" or "E".

But is it possible to get another error type, with the bapi not recording the data?

I thought that the checking of error types "A" and "E" would be enough to know if the bapi worked successfully or not...

Can you provide me a way to get an error type different of "A" and "E", but with the bapi not saving the data successfully?

Strange...

Rudy

[Former Member]

HI ,

Strange...--->its common in SAP world, okay any how -->Are u running the transaction in Test Mode ?

rregards

prabhu

[Former Member]

hi,

do commit it will solve your problem...

use bapi_transaction_commit

[rudy_schmitz]

No, not in test mode.

But I tried to run it in the test platform, but I never got the problem!!