Usage of IN UPDATE TASK in Update process

[Former Member]

Hi

I want to synchronize the Lock and Rollback process with respect to

addon table and FI document posting.Need to consider that many addon programs are accessing the table at same time and may be bulk records need to be udpated sometimes.So may be more time to execute. I am trying to execute below in 1LUW process. pls correct me if i am doing wrong here. below is my issue.

Pls correct me whether can i go with below process.

---------------------------------------
1)Check and prepare record for Update
2)If (No) record exists
  Display Error.
  Else
3)call Function Enqueue_XXXXX " (Lock the Updating doc record for table.)
4)Call Function 'UPDATE_ZMMT44' IN UPDATE TASK(Inside FM Update stmt is written)

-------------------------------
FI document standard Commit Work (hope this will release both table lock and BKPF lock)
FI standard Rollback Work
------------------------------------

Issue

1)Lock Release timing of Enqueue process?

Lock Release happens only at the end of FI document Posting. if batch update happens it will lead to long time freeze and no error can be displayed unfortunately. how to handle this?

2)How to handle SQL error(Update <table> stmt error)

I am not able to catch this error inside program. seems it goes to ST22 ...how to catch this inside program?

My earlier query is not clear and i did not get answer so i am post it again

regards

prince

Edited by: princeck on Nov 18, 2011 2:28 AM

[Former Member]

Hi

Regarding Issue1, I understand that I will look at BKPF lock and update the addon table record.

since at each transaction each LUW happens and standard releases the BKPF lock hope notthing to worry even at bulky records.

Regarding issue2, this is not solved, How to handle the SQL error when update record?

Now its going to SAP office and gives error. not showing error at same place.

Appreciate your help.

Regards

[SuhaSaha]

Hello Prince,

Regarding issue2, this is not solved, How to handle the SQL error when update record?
Now its going to SAP office and gives error. not showing error at same place.

This is the standard behavior when an "update"(processed via an Update WP) fails.

If you don't want this to happen you can opt for local updates(SET UPDATE TASK LOCAL). You would like to read the [behavior of messages in local updates|http://help.sap.com/abapdocu_702/en/abenabap_message_update.htm].

BR,

Suhas

[SuhaSaha]

Hello Prince,

My earlier query is not clear and i did not get answer so i am post it again

Please close the thread . If you think your query was not answered, please mark it as "unanswered".

BR,

Suhas