SAP CRM_EOP_SIMULATE_SAVE_EOB Function Module for Data Privacy: Simulate an End of Business calculation (no save to DB)
CRM_EOP_SIMULATE_SAVE_EOB is a standard crm eop simulate save eob SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Data Privacy: Simulate an End of Business calculation (no save to DB) processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.
See here to view full function module documentation and code listing for crm eop simulate save eob FM, simply by entering the name CRM_EOP_SIMULATE_SAVE_EOB into the relevant SAP transaction such as SE37 or SE38.
Function Group: CRM_DPP_EOP
Program Name: SAPLCRM_DPP_EOP
Main Program: SAPLCRM_DPP_EOP
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CRM_EOP_SIMULATE_SAVE_EOB pattern details
In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.CALL FUNCTION 'CRM_EOP_SIMULATE_SAVE_EOB'"Data Privacy: Simulate an End of Business calculation (no save to DB).
EXPORTING
IT_PARTNERS_AND_OBJECTS = "Data Privacy: Table type for Partner GUID and Object GUID
IMPORTING
ET_RECORDS_TO_MODIFY = "Data Privacy: table table for CRM_EOB_BP_UPDATE_DU
ET_PARS_AND_OBJS_WITH_ERR_MICU = "Data Privacy: Table type for Partner GUID and Object GUID
ET_PARS_AND_OBJS_WITH_ERR_CALC = "Data Privacy: Table type for Partner GUID and Object GUID
EXCEPTIONS
INSTANTIATION_FAILED = 1
IMPORTING Parameters details for CRM_EOP_SIMULATE_SAVE_EOB
IT_PARTNERS_AND_OBJECTS - Data Privacy: Table type for Partner GUID and Object GUID
Data type: CRMT_EOP_CHECK_PGUID_OGUID_TTOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for CRM_EOP_SIMULATE_SAVE_EOB
ET_RECORDS_TO_MODIFY - Data Privacy: table table for CRM_EOB_BP_UPDATE_DU
Data type: CRMT_EOB_FOR_BP_TTOptional: No
Call by Reference: No ( called with pass by value option)
ET_PARS_AND_OBJS_WITH_ERR_MICU - Data Privacy: Table type for Partner GUID and Object GUID
Data type: CRMT_EOP_CHECK_PGUID_OGUID_TTOptional: No
Call by Reference: No ( called with pass by value option)
ET_PARS_AND_OBJS_WITH_ERR_CALC - Data Privacy: Table type for Partner GUID and Object GUID
Data type: CRMT_EOP_CHECK_PGUID_OGUID_TTOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
INSTANTIATION_FAILED - Instantiation of the central EoP check class failed
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for CRM_EOP_SIMULATE_SAVE_EOB Function Module
The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.| DATA: | ||||
| lv_et_records_to_modify | TYPE CRMT_EOB_FOR_BP_TT, " | |||
| lv_instantiation_failed | TYPE CRMT_EOB_FOR_BP_TT, " | |||
| lv_it_partners_and_objects | TYPE CRMT_EOP_CHECK_PGUID_OGUID_TT, " | |||
| lv_et_pars_and_objs_with_err_micu | TYPE CRMT_EOP_CHECK_PGUID_OGUID_TT, " | |||
| lv_et_pars_and_objs_with_err_calc | TYPE CRMT_EOP_CHECK_PGUID_OGUID_TT. " |
|   CALL FUNCTION 'CRM_EOP_SIMULATE_SAVE_EOB' "Data Privacy: Simulate an End of Business calculation (no save to DB) |
| EXPORTING | ||
| IT_PARTNERS_AND_OBJECTS | = lv_it_partners_and_objects | |
| IMPORTING | ||
| ET_RECORDS_TO_MODIFY | = lv_et_records_to_modify | |
| ET_PARS_AND_OBJS_WITH_ERR_MICU | = lv_et_pars_and_objs_with_err_micu | |
| ET_PARS_AND_OBJS_WITH_ERR_CALC | = lv_et_pars_and_objs_with_err_calc | |
| EXCEPTIONS | ||
| INSTANTIATION_FAILED = 1 | ||
| . " CRM_EOP_SIMULATE_SAVE_EOB | ||
ABAP code using 7.40 inline data declarations to call FM CRM_EOP_SIMULATE_SAVE_EOB
The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.Search for further information about these or an SAP related objects