SAP SWD_API_WORKFLOW_PROTOCOL_GET Function Module for









SWD_API_WORKFLOW_PROTOCOL_GET is a standard swd api workflow protocol get 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 swd api workflow protocol get FM, simply by entering the name SWD_API_WORKFLOW_PROTOCOL_GET into the relevant SAP transaction such as SE37 or SE38.

Function Group: SWDN
Program Name: SAPLSWDN
Main Program: SAPLSWDN
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function SWD_API_WORKFLOW_PROTOCOL_GET 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 'SWD_API_WORKFLOW_PROTOCOL_GET'"
EXPORTING
* WI_ID = "Work Item ID
* LANGU = SY-LANGU "SAP R/3 System, Current Language
* VIEW = ' ' "Workflow Builder view
* STEPS_HIDE = 'X' "Internal
* TASK = "
* USE_BUFFER = ' ' "Checkbox Field

IMPORTING
PROTOCOL = "Structure for XML Output of Workflow Log
.



IMPORTING Parameters details for SWD_API_WORKFLOW_PROTOCOL_GET

WI_ID - Work Item ID

Data type: SWWWIHEAD-WI_ID
Optional: Yes
Call by Reference: No ( called with pass by value option)

LANGU - SAP R/3 System, Current Language

Data type: SY-LANGU
Default: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)

VIEW - Workflow Builder view

Data type: SWD_VIEW
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

STEPS_HIDE - Internal

Data type: SYINPUT
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

TASK -

Data type: SWD_STEP_T
Optional: Yes
Call by Reference: No ( called with pass by value option)

USE_BUFFER - Checkbox Field

Data type: SYINPUT
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for SWD_API_WORKFLOW_PROTOCOL_GET

PROTOCOL - Structure for XML Output of Workflow Log

Data type: SWD_APIXML
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for SWD_API_WORKFLOW_PROTOCOL_GET 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_wi_id  TYPE SWWWIHEAD-WI_ID, "   
lv_protocol  TYPE SWD_APIXML, "   
lv_langu  TYPE SY-LANGU, "   SY-LANGU
lv_view  TYPE SWD_VIEW, "   SPACE
lv_steps_hide  TYPE SYINPUT, "   'X'
lv_task  TYPE SWD_STEP_T, "   
lv_use_buffer  TYPE SYINPUT. "   SPACE

  CALL FUNCTION 'SWD_API_WORKFLOW_PROTOCOL_GET'  "
    EXPORTING
         WI_ID = lv_wi_id
         LANGU = lv_langu
         VIEW = lv_view
         STEPS_HIDE = lv_steps_hide
         TASK = lv_task
         USE_BUFFER = lv_use_buffer
    IMPORTING
         PROTOCOL = lv_protocol
. " SWD_API_WORKFLOW_PROTOCOL_GET




ABAP code using 7.40 inline data declarations to call FM SWD_API_WORKFLOW_PROTOCOL_GET

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 WI_ID FROM SWWWIHEAD INTO @DATA(ld_wi_id).
 
 
"SELECT single LANGU FROM SY INTO @DATA(ld_langu).
DATA(ld_langu) = SY-LANGU.
 
DATA(ld_view) = ' '.
 
DATA(ld_steps_hide) = 'X'.
 
 
DATA(ld_use_buffer) = ' '.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!