‎2009 Mar 26 6:29 AM
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
‎2009 Mar 26 6:31 AM
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
‎2009 Mar 26 6:31 AM
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
‎2009 Mar 26 6:32 AM
HI,
Try to use modify statement instead of update.
Thanks.
‎2009 Mar 26 6:50 AM
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
‎2009 Mar 26 7:26 AM
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.
‎2009 Mar 26 8:56 AM
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.