SAP SAP_WAPI_GET_OBJECTS Function Module for Workflow Interfaces: Read Work Item Objects
SAP_WAPI_GET_OBJECTS is a standard sap wapi get objects 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: Read Work Item Objects 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 get objects FM, simply by entering the name SAP_WAPI_GET_OBJECTS 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_GET_OBJECTS 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_GET_OBJECTS'"Workflow Interfaces: Read Work Item Objects.
EXPORTING
WORKITEM_ID = "Work Item ID
* LANGUAGE = SY-LANGU "SAP System, Current Language
* USER = SY-UNAME "ABAP System, User Logon Name
* BUFFERED_ACCESS = 'X' "Determine Data from Buffer
IMPORTING
LEADING_OBJECT = "Object
RETURN_CODE = "Return Code (0, 1, 999)
LEADING_OBJECT_2 = "Local Persistent Object Reference - BOR Compatible
TABLES
* OBJECTS = "Added Objects
* MESSAGE_LINES = "Message Lines
* MESSAGE_STRUCT = "Message Structure
* OBJECTS_2 = "WAPI: Generic Structure for Objects (After 4.6)
IMPORTING Parameters details for SAP_WAPI_GET_OBJECTS
WORKITEM_ID - Work Item ID
Data type: SWR_STRUCT-WORKITEMIDOptional: No
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)
USER - ABAP System, User Logon Name
Data type: SYUNAMEDefault: SY-UNAME
Optional: Yes
Call by Reference: No ( called with pass by value option)
BUFFERED_ACCESS - Determine Data from Buffer
Data type: XFELDDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SAP_WAPI_GET_OBJECTS
LEADING_OBJECT - Object
Data type: SWR_OBJECTOptional: No
Call by Reference: No ( called with pass by value option)
RETURN_CODE - Return Code (0, 1, 999)
Data type: SY-SUBRCOptional: No
Call by Reference: No ( called with pass by value option)
LEADING_OBJECT_2 - Local Persistent Object Reference - BOR Compatible
Data type: SWR_OBJ_2Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for SAP_WAPI_GET_OBJECTS
OBJECTS - Added Objects
Data type: SWR_OBJECTOptional: Yes
Call by Reference: No ( called with pass by value option)
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)
OBJECTS_2 - WAPI: Generic Structure for Objects (After 4.6)
Data type: SWR_OBJ_2Optional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for SAP_WAPI_GET_OBJECTS 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: | ||||
| lt_objects | TYPE STANDARD TABLE OF SWR_OBJECT, " | |||
| lv_workitem_id | TYPE SWR_STRUCT-WORKITEMID, " | |||
| lv_leading_object | TYPE SWR_OBJECT, " | |||
| lv_language | TYPE SYLANGU, " SY-LANGU | |||
| lv_return_code | TYPE SY-SUBRC, " | |||
| lt_message_lines | TYPE STANDARD TABLE OF SWR_MESSAG, " | |||
| lv_user | TYPE SYUNAME, " SY-UNAME | |||
| lt_message_struct | TYPE STANDARD TABLE OF SWR_MSTRUC, " | |||
| lv_leading_object_2 | TYPE SWR_OBJ_2, " | |||
| lt_objects_2 | TYPE STANDARD TABLE OF SWR_OBJ_2, " | |||
| lv_buffered_access | TYPE XFELD. " 'X' |
|   CALL FUNCTION 'SAP_WAPI_GET_OBJECTS' "Workflow Interfaces: Read Work Item Objects |
| EXPORTING | ||
| WORKITEM_ID | = lv_workitem_id | |
| LANGUAGE | = lv_language | |
| USER | = lv_user | |
| BUFFERED_ACCESS | = lv_buffered_access | |
| IMPORTING | ||
| LEADING_OBJECT | = lv_leading_object | |
| RETURN_CODE | = lv_return_code | |
| LEADING_OBJECT_2 | = lv_leading_object_2 | |
| TABLES | ||
| OBJECTS | = lt_objects | |
| MESSAGE_LINES | = lt_message_lines | |
| MESSAGE_STRUCT | = lt_message_struct | |
| OBJECTS_2 | = lt_objects_2 | |
| . " SAP_WAPI_GET_OBJECTS | ||
ABAP code using 7.40 inline data declarations to call FM SAP_WAPI_GET_OBJECTS
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 WORKITEMID FROM SWR_STRUCT INTO @DATA(ld_workitem_id). | ||||
| DATA(ld_language) | = SY-LANGU. | |||
| "SELECT single SUBRC FROM SY INTO @DATA(ld_return_code). | ||||
| DATA(ld_user) | = SY-UNAME. | |||
| DATA(ld_buffered_access) | = 'X'. | |||
Search for further information about these or an SAP related objects