topic Re: Not Updating Customized Table when System having Performance Issue in Application Development and Automation Discussions

Not Updating Customized Table when System having Performance Issue

Former Member — Mon, 09 Oct 2006 07:01:23 GMT

Hi,

This is actually the same topic as "Not Updating Customized Table when System having Performance Issue" which is posted last December by Leonard Tan regarding the user exit EXIT_SAPLMBMB_001.

Recently we changed the program function module z_mm_save_hide_qty to update task. However this causes more data not updated. Hence we put back the old version (without the update task). But now it is not working as it used to be (e.g. version 1 - 10 records not updated, version 2 with update task - 20 records not updated, back to version 1 - 20 records not updated).

I tried debugging the program, however whenever I debugged, there is nothing wrong and the data is updated correctly.

Please advise if anyone has any idea why is this happening. Many thanks.

Regards,

Janet

Re: Not Updating Customized Table when System having Performance Issue

Former Member — Mon, 09 Oct 2006 07:17:23 GMT

Hi Janet,

This could be because of no commit happening to the DB. So try putting an COMMIT WORK Statement after update.

Hope this could workout.

Thanks,

Prashanth

Re: Not Updating Customized Table when System having Performance Issue

Former Member — Mon, 09 Oct 2006 07:23:28 GMT

Hi,

Thanks for the reply. But I thought that it is not advisable to put in a commit work in this user exit as this might cause a rollback (if any) to fail.

Please advise if my concern is unfounded. Thanks.

Regards,

Janet

Re: Not Updating Customized Table when System having Performance Issue

Clemenss — Mon, 09 Oct 2006 09:16:40 GMT

Hi Janet,

you are right. This is a basic rule not to do any COMMIT or RFC calls in a user exit.

Have a look at SAP note 92550. Here they say that exit EXIT_SAPLMBMB_001 is called in the update routine MB_POST_DOCUMENT. And this routine is already called in UPDATE TASK from FUNCTION 'MB_UPDATE_TASKS' IN UPDATE TASK.

SAP also tells us not to do any updates on SAP system tables like MBEW, MARD, MSEG.

Before the exit is called, now they call 'MB_DOCUMENT_BADI' with methods MB_DOCUMENT_BEFORE_UPDATE and MB_DOCUMENT_UPDATE. Possibly you have more success implementing the BADI.

I don't know your situation and goal so this is all I can tell you now.

Good luck!

Regards,

Clemens

Re: Not Updating Customized Table when System having Performance Issue

Former Member — Tue, 10 Oct 2006 00:25:59 GMT

Hi,

Thanks for the info. Actually the goal is very simple, when it is posting the material document, it will update a customized table. However when the system is slow, the customized table is not updated.

Regards,

Janet

Re: Not Updating Customized Table when System having Performance Issue

suresh_datti — Tue, 10 Oct 2006 00:29:32 GMT

Hi Janet,

Place the code that updates the custom table in another Report program. SUBMIT that report from the User Exit. This will isolate the two workprocesses & avoid the UPDATE conflict.

~Suresh

Re: Not Updating Customized Table when System having Performance Issue

Former Member — Tue, 10 Oct 2006 01:09:28 GMT

Hi,

Sorry, need more information. Currently a function module is in the user exit. Inside the function module, after some validation, then there will be a insert/update statement. Is it better to put the whole function module in another report? or only the insert/update statments are to be put into another report?

Thanks in advance.

Regards,

Janet

Message was edited by: Janet Lee

Re: Not Updating Customized Table when System having Performance Issue

gopi_narendra — Tue, 10 Oct 2006 05:51:28 GMT

create a new report program with the update u wnated for the ztable.

and in the include of the function module write the submit report statement. for further details on submit use F1 Help.

Regards

- Gopi

Re: Not Updating Customized Table when System having Performance Issue

Former Member — Tue, 10 Oct 2006 05:57:36 GMT

Hi,

I have create a new program and a Submit statement in the user exit. However an error Update Terminated appeared. Via SM13, I checked the error log and it is saying that the Submit statment is not allowed in a update task. Any other ways? Thanks.

Regards,

Janet

Re: Not Updating Customized Table when System having Performance Issue

Former Member — Wed, 11 Oct 2006 09:20:19 GMT

The submit (and return) is done from the user-exit, and in the called program, the function module is called. But this function module does not need to be called in UPDATE TASK anymore.

When this called program is finished, the Logical Unit of Work is finished and a commit work is executed for the called program. Your data is then updated in the database. Then you're returned back to the User-Exit. The commit work should not affect the user-exit itself.

Re: Not Updating Customized Table when System having Performance Issue

Former Member — Thu, 12 Oct 2006 00:14:51 GMT

Hi,

Thanks. However I check the process and it seems that there are no other user exit that is suitable except the user exit (EXIT_SAPLMBMB_001) that is called in the update task (MB_UPDATE_TASKS). Please advise if otherwise. Thanks.

Regards,

Janet

Re: Not Updating Customized Table when System having Performance Issue

Former Member — Thu, 12 Oct 2006 05:39:24 GMT

I see the problem...

At the moment I have a similar issue but in a 'normal' user-exit. I can't update some data because a sales-order is locked.

I am going for a workflow solution. Trigger an event in the user-exit. In the workflow, it is possible to check if the lock on the object is released. If yes, then continue and make the changes. If not, try again in a minute...

Edit:

It works.

I've created a new business object, with event and method that contains the logic.

Also created a task to call the method, and a workflow with only that task.

Then, in the User Exit, I create an event with SWE_EVENT_CREATE and pass the paremeters to the event container. No commit work after the event create, of course...

The event is triggered, the created workflow started, and the task calls the method and the change is made.

Regards,

Edwin

Re: Not Updating Customized Table when System having Performance Issue

Former Member — Tue, 17 Oct 2006 17:56:52 GMT

I would suggest either solution via workflow or use "starting new task" addition to call your FM.

The goal is to separate main update task & your update.

You will need to put some logic like

- try to lock records you are going to update

- if lock fails - wait up to nnn seconds & try again

- if lock successfull - update your records.

I don't know how exactly you are updating your table but you can try to put some lock/wait logic into your FM which works in update task... It can cause delays for other updates if your FM is called in V1 update.

If you do not have requirement to fail whole transaction if your FM fails to update your table -> you can call your FM in async. update (change administration parameters of your FM).