SAP UJW_API_GET_WORKSTATUS Function Module for Work Status - Get Work Status
UJW_API_GET_WORKSTATUS is a standard ujw api get workstatus SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Work Status - Get Work Status 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 ujw api get workstatus FM, simply by entering the name UJW_API_GET_WORKSTATUS into the relevant SAP transaction such as SE37 or SE38.
Function Group: UJW0
Program Name: SAPLUJW0
Main Program: SAPLUJW0
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function UJW_API_GET_WORKSTATUS 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 'UJW_API_GET_WORKSTATUS'"Work Status - Get Work Status.
EXPORTING
IS_USER = "BPC: User Login Info
I_APPSET = "BPC: AppSet ID
IMPORTING
ET_WORKSTATUS_TABLE = "BPC: Work Status - Status Code Table Type
ET_MESSAGE_LINES = "BPC: Messages
EXCEPTIONS
SYSTEM_FAILURE = 1 COMMUNICATION_FAILURE = 2
IMPORTING Parameters details for UJW_API_GET_WORKSTATUS
IS_USER - BPC: User Login Info
Data type: UJ0_S_USEROptional: No
Call by Reference: No ( called with pass by value option)
I_APPSET - BPC: AppSet ID
Data type: UJ_APPSET_IDOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for UJW_API_GET_WORKSTATUS
ET_WORKSTATUS_TABLE - BPC: Work Status - Status Code Table Type
Data type: UJW_T_STATCODEOptional: No
Call by Reference: No ( called with pass by value option)
ET_MESSAGE_LINES - BPC: Messages
Data type: UJ0_T_MESSAGEOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
SYSTEM_FAILURE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
COMMUNICATION_FAILURE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for UJW_API_GET_WORKSTATUS 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_is_user | TYPE UJ0_S_USER, " | |||
| lv_system_failure | TYPE UJ0_S_USER, " | |||
| lv_et_workstatus_table | TYPE UJW_T_STATCODE, " | |||
| lv_i_appset | TYPE UJ_APPSET_ID, " | |||
| lv_et_message_lines | TYPE UJ0_T_MESSAGE, " | |||
| lv_communication_failure | TYPE UJ0_T_MESSAGE. " |
|   CALL FUNCTION 'UJW_API_GET_WORKSTATUS' "Work Status - Get Work Status |
| EXPORTING | ||
| IS_USER | = lv_is_user | |
| I_APPSET | = lv_i_appset | |
| IMPORTING | ||
| ET_WORKSTATUS_TABLE | = lv_et_workstatus_table | |
| ET_MESSAGE_LINES | = lv_et_message_lines | |
| EXCEPTIONS | ||
| SYSTEM_FAILURE = 1 | ||
| COMMUNICATION_FAILURE = 2 | ||
| . " UJW_API_GET_WORKSTATUS | ||
ABAP code using 7.40 inline data declarations to call FM UJW_API_GET_WORKSTATUS
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