on 01-08-2014 4:49 AM
Hi Experts,
I have a question regarding update to custom table (rapid application).
Currently there's code to prevent update to the custom table in method EH_ONSAVE (when save button is clicked - error is displayed and changes will not be saved).
The issue is when Back button is clicked, pop up is shown asking whether to save the changes (standard CRM behavior). Changes is saved when Yes is clicked. ORDER_SAVE badi is not useful in this case, does anyone know how to stop it from saving?
Thanks,
Jacinth.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Another approach can be, using AET instead of rapid application to extend the one order model (let's say CRMD_ORDERADM_H or CRMD_ORDERADM_I) and then use the BADI ORDER_SAVE getting the infromation from CRM_ORDER_READ - et_extension2 and raising the exception DO_NOT_SAVE.
Without knowing your requirement I would went for this approach as rapid application doesn't support RAW types so it will be hard/not supported to embed your view to the standard component.
Cheers!
Luis
Hi,
Data loss popup will be raised in class CL_CRM_UI_FRAME_APP_CONTROLLER method LAUNCH_DATALOSS_DIALOG
Process for yes_no_cancel will be done in class CL_CRM_UI_CORE_APPL_CONTROLLER method PROCESS_DATALOSS.
Check this class methods you will get some idea. You should enhance these classes for your requirement. This methods will be called for all data loss popup cases.
Regards,
Deepika.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
7 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.