Solution : https://service.sap.com/sap/support/notes/524154 (SAP Service marketplace login required)
Summary :
This SAP Note identifies a problem with user exits not executing during collective processing of deliveries in various VL10 transactions (e.g., VL10A, VL10B). The affected user exits include USEREXIT_MOVE_FIELD_TO_LIKP, USEREXIT_MOVE_FIELD_TO_LIPS, USEREXIT_SAVE_DOCUMENT_PREPARE, among others. The creation of deliveries involves multiple parallel processes, causing breakpoints in user exits to be ineffective and the system field SY-TCODE not being consistently assigned. To address the issue, SAP advises against using SY-TCODE to identify the processing mode in user exits. A solution is provided for debugging collective processing by means of setting breakpoints strategically before function module SHP_VL10_DELIVERY_CREATE_PARA, and detailed debugging steps are outlined. Further insights are offered on actions within the SAP debugger for effective resolution of the problem.
Key words :
userexit_move_field_to_likp userexit_move_field_to_lips userexit_save_document_prepare userexit_save_document userexit_number_range userexit_batch_determination, flags v50agl-sammelgang = 'x', system field sy-tcode, parameter t180-tcode = 'vl04', parameter sy-tcode, t180-trtyp = 'h', stock transport orders, call include lv50r_viewf43, desired selection criteria, function module shp_vl10_delivery_create_para
Related Notes :
444078 | VL10: Debugging made easy |
415716 | User exits in delivery processing |
209846 | Use of SY-TCODE in delivery processing |