Batch Data Control - problem (success message/database is not updated)

[Former Member]

Hello

When executing a BDC via SM35 R3 will display a successful message stating that the BDC session is complete "Processing of Batch Input Session Complete". However the system fails to update the database but no error is ever displayed. R3 gives the impression that the BDC was successful when it fact nothing was updated.

I am able to manually execute transaction F-44 and successfully update the database and generate a valid posting document. So data and number ranges don't appear to be an issue.

I turned it over to the Basis group and they could not find/locate any evidence of locking or update failures.

Has anybody experienced or seen anything similar. Your help is greatly appreciated.

[Jelena_Perfiljeva]

How do you create the BDC sessions?

First of all, test thoroughly. Run the session in foreground, make sure to check the checkboxes for all additional functions except for "simulate background". Make sure that the fields in the session are correct and also try running the transaction with the same exact values. Maybe it just appears that it's working when in fact it does not do anything.

Second, see if there are any "gaps" in the document numbers. For example, if the last document number before the session is 99, after the session 101 and document # 100 does not exist, this would be a usual symptom of an update termination. Don't wait on Basis to do research and go to transaction SM13 yourself immediately. If there was an update termination, you'll see it there.

In some systems the update termination log might be deleted periodically and by the time when someone starts researching it's already too late. Also check transactionST22 (ABAP dumps), although those you would see on the screen...

Good luck!

[Former Member]

Hi

Thanks for replying. Yes, I have tested thoroughly. In addition to my program several other programs that were not recently modified also started to fail as well which led me down the Basis path. I suspected something had been changed in the environment. Not all BDC's are failing to process however. I did add my data manually field by field. R3 successfully updated. I plan to check if there are gaps in the number generation.

thanks

[Former Member]

Hi Joe,

Run your BDC in 'E' mode there you will find some errors which you might not find in 'A' mode.

The reason is when some fields are missing in BDC screen, SAP tend to give a success message rather than error message. So run it 'E' mode and check if it has any errors.

Hope this helps you.

Thanks,

Arun

[Former Member]

Hi Arun

We have tried that as well. The issue we are having involves several programs not just mine. And these other programs have not been modified recently. So it raised the question as to why did these programs suddenly start ti fail.

But all the programs that do fail within a BDC have one thing in common they all involve the finance transactions F-02 etc.Why does the BDC fail and not the online transaction?

I am in the process of identifying all the programs that have failed and on what clients etc. We don't know if a recent patch that was applied has created this problem as this patch may or may not have been transported to all boxes.

Thanks for your help.

[Jelena_Perfiljeva]

It seems obvious that something has changed in the transaction. If you have applied a support pack or a note, I guess it's a no-brainer that you need to look for the changes brought in by that implementation.

This is the main reason why BDC programs should be avoided - every time anything changes in the transaction, the program might fail and will have to be modified and re-tested.

[Former Member]

Mystery solved. First of all I want to thank those that spent the time to reply to my note. We discovered a recently modified user exit that has a commit work statement at the end of the exit. This caused R3 to behave differently online versus via the BDC. We removed the commit work and am now able to process all of our finance related BDC programs. The next problem is to address the user exit.

Thanks again,