Ansicht
Dokumentation

CRM_PS_SUPR_BADI - BAdI: Define Processes of Successor Processing

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

This Business Add-In (BAdI) is used in the Social Services component for creation processing and change processing during successor processing (SuPr).

Implementing this BAdI is a Customizing setting for successor processing on the basis of Web request-based predecessor business transactions. In such cases, you need to create a relevant BAdI implementation for each Web request category.

Creation Processing Mode

The method DEFINE_PARAMETER_CREATION_MODE is run to create a new successor social service plan on the basis of a Web request-based predecessor business transaction.

The following functions are controlled by the BAdI creation method:

• Access Request Form Data

The BAdI creation method provides the request form data as a parameter in the XML structure IT_PATH_VALUE. This means that you can access request data, and adjust the contents of the successor business transactions to meet your requirements on the basis of this data.

• Control Options for Successor Processing

You can use the parameter CS_SUPP to control how successor processing is to continue. The system enters the values defined in Customizing in the structure CRMT_PS_SUP_P as a default setting. If you do not want to make any changes to this successor processing profile data, you do not need to do anything else here.

You can use the parameters CV_SUCC_START_DATE and CV_SUCC_END_DATE to create the decision start and decision end date (CONTSTART, CONTEND) for the SSP version. The system enters the header start and end dates of the current social application in the parameters. You only need to change the parameters if you want to use different start and end dates in the new SSP version.

• Creation of Manual Decision Units

If you are using the composite calculation function, you can use the exporting parameter ET_MANUAL_DECISION_UNITS to create manual decision units.

Change Processing Mode

The method DEFINE_FURTHER_PROCESSING is run to make a change, if a related existing successor social service plan (SSP) has to be updated when the application form data of the predecessor business transaction is changed. At runtime, the BAdI supports the selection of the change processes dependent on the contents of the Web request form, and enables the further successor processing of the current SSP to be influenced.

The following functions are controlled by the BAdI change method:

• Selection of the Change Processes

The change processes assigned in the change processing profile are read, or can be determined and assigned at runtime based on the form data.

Note:
So that change processes can be processed by the Change Process Engine (CPE), the relevant data structures must be filled in the internal table ET_CPC_DATA and/or the structure CS_GCP_DATA and specified along with the GUIDs (handle) of the successor SSP to be changed or its items. This applies for the change processes of the change process chain (CPC) and/or for the global change process (GCP).
(By default, the system fills the structure CS_GCP_DATA with the GUID of the current successor SSP and the GCP defined in Customizing. This means that if you want to change the current successor SSP with the GCP, you need take no action. The same is done for change process chains (CPC) if they are defined as header change processes. The internal table CT_CPC_DATA is filled accordingly.)

Some change processes are not permitted in the change process chain; their execution would be terminated by the CPE and an error message would be displayed (For example only inbound change processes are allowed to be processed by SuPr). The method CHECK_FOR_CHAIN enables you to check at runtime whether this applies for one of your change processes also.

SuPr supports the following special cases:
If you specified a global change process in the change processing profile, but the SuPr BAdI is not implemented, the system automatically uses the GUID of the current successor SSP for the global change process. It is not necessary to implement the SuPr BAdI for simple requests (social applications) that only need one change process (and a global change process thus meets all requirements) The same is true for header change processes defined in a change process chain.

• Access Request Form Data

The SuPr BAdI provides the request form data as a parameter in the XML structure IT_PATH_VALUE. This means that you can access request data, and, on this basis, determine different change processing profiles or adjust the contents of a change processing profile to satisfy your requirements.

• Control Options for Successor Processing

You can use the structure CS_CPP_DEF to control how successor processing is to continue. For example, you can change the item copy strategy (ICS) or parameters of the item copy.
(By default, the system fills the structure CS_CPP_DEF with the values of the first change processing profile that is valid for the current Web request category. If you do not want to make any changes to this CPP data, you need take no action).

By way of additional support, the SuPr BAdI provides access to the successor processing profiles and change processing profiles defined in Customizing, to the GUIDs of the predecessor and successor transactions and to the related item GUIDs.

You can use the parameters CV_SUCC_START_DATE and CV_SUCC_END_DATE to change the decision start and decision end date (CONTSTART, CONTEND) of the SSP version that is created as result of the current run of SuPr. The parameters are pre-filled with the header start and end dates of the current social application. You only need to change the parameters if you want different start and end dates for the new SSP version.

You can use the parameter CV_SUCC_PROC_TYPE to change the transaction type for the SSP version that is created by the current run of SuPr. The system enters the transaction type of the previous SSP version in the parameter as a default setting. You only need to change the parameter if the SSP transaction type of the new version needs to be different from the previous version.

You can use multiple successor processing profiles and change processing profiles for a social application. For example, to predefine change process chains for several possible process flow variants. If you have defined multiple profiles, you need to select one profile as the relevant one in each case, in the SuPr BAdI at runtime.

For information about the implementation of BAdIs in the context of the Enhancement Concept, see SAP Library for SAP NetWeaver under BAdIs - Embedding in the Enhancement Framework.

The delivered sample implementation shows how the SuPr BAdI is used in the change mode.

Addresses (Business Address Services)   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

Length: 9756 Date: 20240523 Time: 160710     sap01-206 ( 187 ms )