topic Re: performance tuning in Application Development and Automation Discussions

performance tuning

Rushikesh_Yeole — Thu, 26 Mar 2009 06:29:51 GMT

Please use more informative subject in future

IF NOT l_lock IS INITIAL.
  UPDATE marc FROM TABLE lt_marc.
  IF sy-subrc = 0.
* creation of change document - ZZACT
    PERFORM cd_call_mat_full.
    COMMIT WORK.
  ELSE.
    ROLLBACK WORK.
    CLEAR gt_return.
    gt_return-type = 'E'.
    gt_return-message = 'Problem with update entries in MARC !'(011).
    PERFORM log_message TABLES gt_mess_list
           USING gt_return gt_todo_list.
  ENDIF.

How can we improve the performance of program?? Any other better query which will replace UPDATE statement???

Edited by: Matt on Mar 26, 2009 9:54 AM

Re: performance tuning

Former Member — Thu, 26 Mar 2009 06:31:53 GMT

Hi,

if you are changing the MARC(standard table )....use the FMs instead of the MODIFY or update.

tyr to look with the FM CM_FV_MARC_UPDATE

or else try with

MODIFY marc FROM TABLE lt_marc.

Thanks!

Edited by: Prasanth on Mar 26, 2009 12:02 PM

Re: performance tuning

Former Member — Thu, 26 Mar 2009 06:32:57 GMT

HI,

Try to use modify statement instead of update.

Thanks.

Re: performance tuning

Sm1tje — Thu, 26 Mar 2009 06:50:11 GMT

First of all NEVER EVER update these standard tables yourself (See comment Prashant). So change that first and use the proper function modules (BAPI's) for this. Then, and only then see how to improve performance, if still necessary.

Edited by: Micky Oestreich on Mar 26, 2009 7:50 AM

Re: performance tuning

Former Member — Thu, 26 Mar 2009 07:26:40 GMT

Hi,

Do not commit work, the LUW will automatically commited at the run time. Use Commit only if you are reusing the table later in your program.

Regards,

Prashant.

Re: performance tuning

matt — Thu, 26 Mar 2009 08:56:01 GMT

Please use more informative subject in future

And don't update SAP tables directly. It's a good way of of invalidating your support agreement with SAP.