Slow system performance caused standard table update delay

[Former Member]

I have a program which updates a custom table depends on the values in the standard table which will be updated by submitting standard transaction in the same program. Due to slow system performance, there is a delay on the standard table being updated. For this reason, when the update statement for the custom table is executed, the standard table has not been updated yet, causing the incorrect value in the custom table. Try to use the "wait up to xx seconds" statement but don't think this is the best solution. Also tried commit work after the standard transaction is called, won't work. Does anyone know how to track or commit the database update?

[Former Member]

I have a program which updates a custom table depends on the values in the standard table which will be updated by submitting standard transaction in the same program. Due to slow system performance, there is a delay on the standard table being updated. For this reason, when the update statement for the custom table is executed, the standard table has not been updated yet, causing the incorrect value in the custom table. Try to use the "wait up to xx seconds" statement but don't think this is the best solution. Also tried commit work after the standard transaction is called, won't work. Does anyone know how to track or commit the database update?

[Former Member]

Are you running the standard table update in a synchronous or asynchronous process? You will want to make sure that it run synchronous.

This will prevent the custom table from being updated UNTIL the standard processing is completed.

[Former Member]

I had just about the same problem. I sent it to OSS and their solution was "wait up to xx seconds".

I haven't tried it, but a "COMMIT WORK AND WAIT" might also work.

Rob

[Former Member]

Its a know problem in SAP. I have faced this kind of problem many times and used either "WAIT UPTO XX SECONDS" or "COMMIT WORK AND WAIT".

Also, if you are updating the custom table in the same program where the standard table is being updated, you will not read the updated entry in the standard table ( once the commit work command has been executed ) because the LUW is not completed.

Try to use "WAIT UPTO XX SECONDS" or "COMMIT WORK AND WAIT" and see if it works. Also let me know how exactly the standard table is being updated ( which transaction ) and how you want to update the custom table. May be i can help.

Thanks,

Pal

[Former Member]

Hi minami,

Such problems are not caused

by slow performance of the system,

rather,

they are caused when

we do not have control

over LUW concept of SAP.

1. submitting standard transaction

2. which transaction are u submiting?

are u using call transaction ?

or submit programname ?

regards,

amit m.

[Former Member]

The standard transaction that I am called is a series of Product cost run: e.g. CK64, CK66, CK68. These transactions are called by SUBMIT JOB. Once the job is finished, the main program (custom program) will perform the update to several customized tables.

I tried the COMMIT WORK AND WAIT. Did not work. The standard tables KEKO and CKIS are still updated later than the update perform routing for the custom tables. So far only WAIT UPTO XX seconds work however, won't the XX value be changing depends on the number of records need to be updated in production system? That is my issue. I do not know how long should I put the wait for.

[Former Member]

I'm not sure that the delay will really depend on the number of inserts. (You're waiting for the commit to finish, not the inserts.) We found that our QA system (which is a regularly copied version of the production system) gave us a good indication of how long to wait.

I would suggest making XX = 1 and see how that works; if it does, fine, if not, increase it until it does work.

Rob