Ansicht
Dokumentation

CRM_MI_PROC_DETER - BAdI: Determination of Work Item Recipients

Fill RESBD Structure from EBP Component Structure   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

This Business Add-In (BAdI) is used in the Basic Functions for Business Transactions component (CRM-BTX-BF) and serves the following two purposes:

• This BAdI determines the recipients for a newly-generated work item. It is assumed that there is a known agent group, which is transferred to the BAdI as an IMPORTING parameter.

For the analysis processing level, this comes about because the agent group must already be defined before the workflow can even be started. The business rules for triggering investigations sets the system status I2212, and also sets the identification code for the analysis agent group that identify it as being responsible for the investigation process. This could happen, for example, by accessing a customer-specific table that may contain key fields such as transaction type, item category, or product.

For security reasons, at the start of the workflow, the system checks whether an agent group analysis was defined by the rule. If this is not the case, the workflow itself defines this agent group by accessing the first analysis agent group that you defined.

The research agent group is normally defined manually by the agent responsible for analysis, by using the Consult Researchers decision function.
Exception: By choosing Direct to Research in Implementation Guide (IMG) activity Set "Direct to Research", the receiving agent groups in research are already defined by rules before the workflow starts. Then, similar to analysis level, the rules enter the corresponding identification codes in the item.

Agent group approval is determined dynamically, if necessary. The BAdI: Check Whether Approval Is Required BAdI is provided for this purpose.

• This method determines a CRM business transaction item for the current globally unique identifier (GUID), and an agent group in the Investigation application for the current user (SY-UNAME).

This BAdI is activated in the standard system. The default coding is automatically executed.

This BAdI is not reusable.

This BAdI is filter-dependent. The processing level is the filter value.

After you have called the IMG activity, proceed as follows:

1. In the following dialog box, enter in the field "Implementation" a name for the BAdI implementation and choose Copy.

If implementations have already been created for the BAdI, a dialog box with the existing implementations will be displayed. In this dialog box, choose Create.

1. In the corresponding field, enter a short text for implementation .
2. In the tab Propertiesenter filter properties - if this is a filter-dependent BAdI.
3. Choose the tab Interface.

The name of the implementing class is generated by the system based on the name of your impmlementation. You can change the name.

If the BAdI is a menu exit, the tab FCodes also appears.Enter a function here and, if necessary, additional data.

1. Save your entries and assign a package.
2. Position the cursor on a method. Call up the Class Builder by double-clicking it.
3. Between the statements method <Interface-Name>~<Name of Method>. and endmethod, enter the coding you request for the implementation.
4. Save and activate your coding, and navigate back to the screen Change Implementation.
5. Save on the screen Change Implementation.

Note: You can first create an implementation for the BAdI and then activate this later on. In this case, close the processing function at this time.

1. Choose Activate.

When the application program is executed, the coding you have created will be run.

BAL_S_LOG - Application Log: Log header data   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Length: 4909 Date: 20240523 Time: 153152     sap01-206 ( 87 ms )