Ansicht
Dokumentation

CRM_PS_DM_EA_STATUS - BAdI: Define Enforcement Action External Status

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

You use this Business Add-In (BAdI) during the processing of enforcement action (EA) to implement custom requirements to set or adjust the external status of the EA automatically. This custom logic overwrites the default logic for setting external statuses based on the Enforcement Action Types Configuration. This BAdI contains the following methods:

• GET_TRIGGERED_EXT_STATUS is called when EA internal status is changed. In some business scenarios, an internal status change automatically triggers an external status change. Based on the old and new internal status values and the header fields, you may set a new external status value. If you want default logic based on EA type configuration, copy IF_CRM_PS_DM_EA_STATUS~GET_TRIGGERED_EXT_STATUS code from the sample implementation.

Note: If you don't implement this BAdI, the default code is executed.

• ADJUST_EXT_STATUS is called during processing of EA external status, which happens after internal status is processed. Based on values of the previous external status, the new one, a value triggered by the internal status change, header fields, and header extensions, you may change the current external status value.

You activated the debt management switch, CRM_IPS_DBM_1.

This BAdI is not implemented in the standard system.

After you open the Customizing activity, enter the following in dialog box:

1. Enter a name for the enhancement implementation, short text, and composite enhancement implementation. If no composite exists, click Create.
2. Save your entries and assign the implementation to a development class.
3. Click on BAdI and select Create BAdI.
4. Enter BAdI definition, BAdI implementation, implementation class, and description, then click Enter.
5. On the next screen, expand the implementation node on the left panel and double-click Entry Class.
6. Place the cursor on the method and double-click to enter method processing.
7. Enter the code for the implementation between the statements method, ~, and end method.

Note: Sample implementation is copied automatically.

1. Save and activate all objects.

You may need to adjust the external status as an exception based on individual debtor characteristics.

For a sample implementation class, see CL_EXM_IM_CRM_PS_DM_EA_STATUS.

BAL_S_LOG - Application Log: Log header data   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

Length: 3417 Date: 20240523 Time: 154708     sap01-206 ( 48 ms )