SAP TEST_SCHEDULE_COMPENSATE Function Module for capsulation for call by serviceuser
TEST_SCHEDULE_COMPENSATE is a standard test schedule compensate SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for capsulation for call by serviceuser 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 test schedule compensate FM, simply by entering the name TEST_SCHEDULE_COMPENSATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: SEQUENCE_MANAGER_TEST
Program Name: SAPLSEQUENCE_MANAGER_TEST
Main Program: SAPLSEQUENCE_MANAGER_TEST
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function TEST_SCHEDULE_COMPENSATE 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 'TEST_SCHEDULE_COMPENSATE'"capsulation for call by serviceuser.
EXPORTING
* PERSIST_ID = "WSRM: Persistent Identifier
IMPORTING Parameters details for TEST_SCHEDULE_COMPENSATE
PERSIST_ID - WSRM: Persistent Identifier
Data type: WSRM_PERSIST_IDOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for TEST_SCHEDULE_COMPENSATE 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_persist_id | TYPE WSRM_PERSIST_ID. " |
|   CALL FUNCTION 'TEST_SCHEDULE_COMPENSATE' "capsulation for call by serviceuser |
| EXPORTING | ||
| PERSIST_ID | = lv_persist_id | |
| . " TEST_SCHEDULE_COMPENSATE | ||
ABAP code using 7.40 inline data declarations to call FM TEST_SCHEDULE_COMPENSATE
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