ECIR addon in SAP CRM (EN)
2018: BADI CRM_BADI_RF_Q1O_SEARCH
A solution to avoid the worst issue into SAP CRM has been created and given to you on our website:
forum SAP CRM (you have to subscribe to access to it, free and email not used).
2014: BADI ORDER_SAVE
If you use a SAP CRM solution you have to enhance the standard processes to meet your functionnal processes.
To enhance them you will use BADI.
In Standard ABAP coding way you will create several usage of your badi, 1 for each requirement.
In the previous screenshot we have created 4 BADI usage, 1 for each document type.
Inside 1 of this usage, by example for LEAD document, inside method CHECK_BEFORE_SAVE, you will call CRM_ORDER_READ function module to allow to know which document is currently checked.
The underlined coding line give you which document is concerned by this badi.
Solution for BADI ORDER_SAVE:
- 1 badi is used only
- function module will be called once
- No hard coded functional processes into your coding.
- regression tests will be easier to determine, more secure.
Transformation cost (done by using ECIR methodology and ECIR client:
1 day for 10 badi usage.
Solution for CRM_BADI_RF_Q1O_SEARCH:
20 days of thinking
7 days of ABAP
All issues coming from specific tables, specific requirements are showed by a real example. Even working on Hana.