SAP SAP_WAPI_FORWARD_WORKITEM Function Module for Workflow Interfaces: Forward Work Item
SAP_WAPI_FORWARD_WORKITEM is a standard sap wapi forward workitem SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Workflow Interfaces: Forward Work Item 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 sap wapi forward workitem FM, simply by entering the name SAP_WAPI_FORWARD_WORKITEM into the relevant SAP transaction such as SE37 or SE38.
Function Group: SWRC
Program Name: SAPLSWRC
Main Program: SAPLSWRC
Appliation area: S
Release date: 05-Aug-1999
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function SAP_WAPI_FORWARD_WORKITEM 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 'SAP_WAPI_FORWARD_WORKITEM'"Workflow Interfaces: Forward Work Item.
EXPORTING
WORKITEM_ID = "Work Item ID
* USER_ID = "User ID
* LANGUAGE = SY-LANGU "SAP System, Current Language
* DO_COMMIT = 'X' "Execute Commit
* CURRENT_USER = SY-UNAME "Forwarding User
IMPORTING
RETURN_CODE = "Return Code (0 - 2, 999)
NEW_STATUS = "Workflow Interfaces: Work Item Status
TABLES
* MESSAGE_LINES = "Message Lines
* MESSAGE_STRUCT = "Message Structure
* USER_IDS = "User
IMPORTING Parameters details for SAP_WAPI_FORWARD_WORKITEM
WORKITEM_ID - Work Item ID
Data type: SWR_STRUCT-WORKITEMIDOptional: No
Call by Reference: No ( called with pass by value option)
USER_ID - User ID
Data type: SY-UNAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
LANGUAGE - SAP System, Current Language
Data type: SYLANGUDefault: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)
DO_COMMIT - Execute Commit
Data type: XFELDDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
CURRENT_USER - Forwarding User
Data type: SYUNAMEDefault: SY-UNAME
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SAP_WAPI_FORWARD_WORKITEM
RETURN_CODE - Return Code (0 - 2, 999)
Data type: SY-SUBRCOptional: No
Call by Reference: No ( called with pass by value option)
NEW_STATUS - Workflow Interfaces: Work Item Status
Data type: SWR_WISTATOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for SAP_WAPI_FORWARD_WORKITEM
MESSAGE_LINES - Message Lines
Data type: SWR_MESSAGOptional: Yes
Call by Reference: No ( called with pass by value option)
MESSAGE_STRUCT - Message Structure
Data type: SWR_MSTRUCOptional: Yes
Call by Reference: No ( called with pass by value option)
USER_IDS - User
Data type: SWRAGENTOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for SAP_WAPI_FORWARD_WORKITEM 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_code | TYPE SY-SUBRC, " | |||
| lv_workitem_id | TYPE SWR_STRUCT-WORKITEMID, " | |||
| lt_message_lines | TYPE STANDARD TABLE OF SWR_MESSAG, " | |||
| lv_user_id | TYPE SY-UNAME, " | |||
| lv_new_status | TYPE SWR_WISTAT, " | |||
| lt_message_struct | TYPE STANDARD TABLE OF SWR_MSTRUC, " | |||
| lv_language | TYPE SYLANGU, " SY-LANGU | |||
| lt_user_ids | TYPE STANDARD TABLE OF SWRAGENT, " | |||
| lv_do_commit | TYPE XFELD, " 'X' | |||
| lv_current_user | TYPE SYUNAME. " SY-UNAME |
|   CALL FUNCTION 'SAP_WAPI_FORWARD_WORKITEM' "Workflow Interfaces: Forward Work Item |
| EXPORTING | ||
| WORKITEM_ID | = lv_workitem_id | |
| USER_ID | = lv_user_id | |
| LANGUAGE | = lv_language | |
| DO_COMMIT | = lv_do_commit | |
| CURRENT_USER | = lv_current_user | |
| IMPORTING | ||
| RETURN_CODE | = lv_return_code | |
| NEW_STATUS | = lv_new_status | |
| TABLES | ||
| MESSAGE_LINES | = lt_message_lines | |
| MESSAGE_STRUCT | = lt_message_struct | |
| USER_IDS | = lt_user_ids | |
| . " SAP_WAPI_FORWARD_WORKITEM | ||
ABAP code using 7.40 inline data declarations to call FM SAP_WAPI_FORWARD_WORKITEM
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.| "SELECT single SUBRC FROM SY INTO @DATA(ld_return_code). | ||||
| "SELECT single WORKITEMID FROM SWR_STRUCT INTO @DATA(ld_workitem_id). | ||||
| "SELECT single UNAME FROM SY INTO @DATA(ld_user_id). | ||||
| DATA(ld_language) | = SY-LANGU. | |||
| DATA(ld_do_commit) | = 'X'. | |||
| DATA(ld_current_user) | = SY-UNAME. | |||
Search for further information about these or an SAP related objects