Solution : https://service.sap.com/sap/support/notes/810477 (SAP Service marketplace login required)
Summary :
When using ORDER_SAVE BAdI's PREPARE method in SAPGUI to validate field inputs, triggering DO_NOT_SAVE halts the SAVE method call, which normally checks if the document is savable post-modification. This can leave the document unsaved without user notification when navigating away, risking data loss. To address this, create a function module CRM_ORDER_CHECK_BEFORE_SAVE_OW in SE37 with necessary parameters for proactive validation. Additionally, define a CHECK_BEFORE,SAVE method in BAdi ORDER_SAVE, ensuring it captures all user input validations adequately. These enhancements permit multiple validation calls and integrate seamlessly across PC-UI and CRM Web UI.
Key words :
iv_guid importing type crmt_object_guidcv_own_message changing type crmt_boolean optionalexception, iv_order_guid type crmt_object_guidiv_log_handle type balloghndl optionalexceptions, data loss popup check_before_save reason, class cl_crm_bsp_pm_generic_1o method if_crm_bsp_process_il~save, data loss pop, called multiple times, crm web ui, source code corrections, save method anymore, function group crm_order_ow
Related Notes :
| 500205 | BAdI prior to saving |