SAP SXIVERI_BPM_SCENARIO_EXEC_SYNC Function Module for
SXIVERI_BPM_SCENARIO_EXEC_SYNC is a standard sxiveri bpm scenario exec sync SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 sxiveri bpm scenario exec sync FM, simply by entering the name SXIVERI_BPM_SCENARIO_EXEC_SYNC into the relevant SAP transaction such as SE37 or SE38.
Function Group: SXIVERI_FRAMEWORK
Program Name: SAPLSXIVERI_FRAMEWORK
Main Program: SAPLSXIVERI_FRAMEWORK
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function SXIVERI_BPM_SCENARIO_EXEC_SYNC 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 'SXIVERI_BPM_SCENARIO_EXEC_SYNC'".
EXPORTING
BPM_MESSAGES = "
* DEBUG = ' ' "
IMPORTING
RETURN = "
EXCEPTIONS
TESTCASE_FAILED = 1
IMPORTING Parameters details for SXIVERI_BPM_SCENARIO_EXEC_SYNC
BPM_MESSAGES -
Data type: SXIVERI_BPM_MESSAGE_TABOptional: No
Call by Reference: No ( called with pass by value option)
DEBUG -
Data type: CHAR01Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SXIVERI_BPM_SCENARIO_EXEC_SYNC
RETURN -
Data type: BAPIRETTABOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
TESTCASE_FAILED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SXIVERI_BPM_SCENARIO_EXEC_SYNC 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_return | TYPE BAPIRETTAB, " | |||
| lv_bpm_messages | TYPE SXIVERI_BPM_MESSAGE_TAB, " | |||
| lv_testcase_failed | TYPE SXIVERI_BPM_MESSAGE_TAB, " | |||
| lv_debug | TYPE CHAR01. " ' ' |
|   CALL FUNCTION 'SXIVERI_BPM_SCENARIO_EXEC_SYNC' " |
| EXPORTING | ||
| BPM_MESSAGES | = lv_bpm_messages | |
| DEBUG | = lv_debug | |
| IMPORTING | ||
| RETURN | = lv_return | |
| EXCEPTIONS | ||
| TESTCASE_FAILED = 1 | ||
| . " SXIVERI_BPM_SCENARIO_EXEC_SYNC | ||
ABAP code using 7.40 inline data declarations to call FM SXIVERI_BPM_SCENARIO_EXEC_SYNC
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.| DATA(ld_debug) | = ' '. | |||
Search for further information about these or an SAP related objects