04-22-2009 5:10 AM
Hi,
We are calling BAPI_TRANSACTION_COMMIT with value 'X' for the wait parameter after we call the BAPI_REQUISITION_DELETE. However, when we looked at our data most of the line items are not deleted. But when we explicitly added the wait up to 1 seconds command, the program worked.
Edited by: Jackie Fiesta on Apr 22, 2009 12:15 PM
04-22-2009 5:24 AM
Hi,
In BAPI_TRANSACTION_COMMIT, if you are not giving any value to wait parameter, it will execute only commit work, if you give value 'X' it executes the command commit work and wait. so there is nothing like how much time it has to wait.
Sometimes because of the huge data it will take more time, that is why when you are using exclusively wait up to 1 sec which is sufficient time to delete all the records.
04-22-2009 5:24 AM
Hi,
In BAPI_TRANSACTION_COMMIT, if you are not giving any value to wait parameter, it will execute only commit work, if you give value 'X' it executes the command commit work and wait. so there is nothing like how much time it has to wait.
Sometimes because of the huge data it will take more time, that is why when you are using exclusively wait up to 1 sec which is sufficient time to delete all the records.
04-22-2009 5:30 AM
Dear ,
this happen due to database updation take place .
bapi_commit give the sleep of some seconds and then commit the task which is updated by BAPI call function.
regds ankit
04-22-2009 5:54 AM
Hi jackie,
In BAPI_TRANSACTION_COMMIT u can specify the wait parameter.
Regards,
Anil N.
04-22-2009 6:09 AM
hi,
it depend upon load on the data base so ,
u can use BAPI_TRANSACTION_COMMIT with wait parameter.
~linganna
05-05-2009 7:23 AM
Hi all,
I would like to bring back my question before. We have encountered again a problem with database updating using bapi_transaction_commit. We have already issue bapi_transaction_commit with wait parameter set to 'X' but when we tried to query the content of the table, it doesn't give us the updated one. Could this be a bug?
05-05-2009 7:55 AM
HI,
it is not a bug , as the records are not updated in data base it will not reflect immediately , so there has to be time gap u can add wait up to n seconds and then query it u will get right results
if solve close the thread
05-05-2009 8:35 AM
Hi mohammad afzal,
We have already implemented the up to n seconds. however n seems to be a variable. for some pcs 3 seconds works. for some 5 seconds work. with this, it's hard to estimate how long will be the waiting part.