Implement Solution Manager Change Request Management following only the standard SAP configuration, standard workflow and documents is in most of the cases not enough to fulfill the customer needs. It’s very common to be requested to create new transaction types, partner, status, text and action profiles copying the standard objects, and adjust them. But in some cases only configuration does not solve all the gaps and a little bit of ABAP code is also necessary. In order to be able to enhance the standard Solution Manager programs related to ChaRM processes, there are some BadIs that can be used. Most of them are still usable in Solution Manager 7.1, but there are some BadIs related to workflow processing which will no longer work in 7.1 because they are SAP GUI specific and are not valid for CRM Web UI.
Below I show two lists of BadIs for ChaRM in Solution Manager 7.1, one related to workflow processing and another one for other general use, including retrofit. If you need to do enhancements in ChaRM, take a look at these BadIs and their implementations and you may find one which solves your problem.
WorkFlow processing:
BAdI | Function | Comment |
---|---|---|
EVAL_SCHEDCOND_PPF | PPF: Exit for Evaluation of Schedule Condition | Still valid |
EVAL_STARTCOND_PPF | PPF: Exit for Evaluation of Start Condition | Still valid |
EXEC_METHODCALL_PPF | PPF: BADI for Execution of Actions | Still valid |
COM_PARTNER_BADI | Business Add Ins for Partner Processing | Still valid |
CONTAINER_PPF | PPF: Complete Container Before Condition Evaluation | Still valid |
CRM_FIELD_AUTH_BADI | BAdI for Fieldcheck Tool | Not valid in 7.1 Web UI, specific for GUI |
CRM_DNO_LTEXT_FILTER | Add-In for Filter Function: Long Text history for Service Process | Still valid |
CRM_DNO_MONITOR | Enhancements for Service Process Monitor | Not valid in 7.1 Web UI, specific for GUI |
CRM_ORDER_AUTH_CHECK | Authorization Check: CRM Business | Still valid |
CRM_PARTNER_BADI | User Exits for the CRM Shell in Partner | Not valid in 7.1 Web UI, specific for GUI |
ORDER_SAVE BADI | CRM Order Save | Still valid |
SOCM_CHECK_CONDITION | Checks conditions for status transition | Still valid |
SOCM_PROCESS_ACTION | SOCM_PROCESS_ACTION | Still valid |
CRM_ORDER_STATUS | Influence the user status if it gets changed | Still valid |
AIC_CREATE_TRANSPORT_WINDOW | Influence the list of development systems in a project and the default system set in the dropdown | Valid in 7.1 SP8 ( and SP4-7 via SAP note 1772445) |
Other BadIs available in 7.1 and relevant for ChaRM scenario:
BAdI | Function |
---|---|
CRM_ORDER_FIELDCHECK | Business Add-In for Field Selection |
/TMWFLOW/SCMA_TASK | Enhanceability of Tasks in Task List |
/TMWFLOW/SCMA_TRANS_REQ_DESC | Get pre-filled description for new transport request |
/TMWFLOW/SCMA_TRORDER_IMPORT1 | Enhancement in Program /TMWFLOW/SCMA_TRORDER_IMPORT |
/TMWFLOW/SCMA_TRORDER_RELEASE1 | Enhancement in Program /TMWFLOW/SCMA_TRORDER_RELEASE |
/TMWFLOW/PHCTRL_COOP | BADI for Phase Model Participants |
/TMWFLOW/RETRO_RELEASE | BADI affects the retrofit functions during release (create retrofit data) |
/TMWFLOW/ RETRO_DURING_RETROFIT | BADI allows customers to install specified functions in retrofit |
/TMWFLOW/RETRO_AFTER_RETROFIT | BAdI performs the functionality after the retrofit |
If you know any other BadI relevant for ChaRM in SolMan 7.1, please let me know adding a comment.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
37 | |
10 | |
7 | |
5 | |
5 | |
4 | |
4 | |
3 | |
3 | |
3 |