SAP SWD_STEP_SET Function Module for Fill step which is currently being processed









SWD_STEP_SET is a standard swd step set SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Fill step which is currently being processed 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 swd step set FM, simply by entering the name SWD_STEP_SET into the relevant SAP transaction such as SE37 or SE38.

Function Group: SWDD
Program Name: SAPLSWDD
Main Program: SAPLSWDD
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function SWD_STEP_SET 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_STEP_SET'"Fill step which is currently being processed
  EXPORTING
*  STEP =  "API: Step Definition
*  PROPTS =  "Properties
*  CONTAINERS =  "Container

TABLES
*  CASE_DECISION =  "
*  CONDITION =  "
*  TASKS =  "
*  IF_DECISION =  "
*  UNTIL_DECISION =  "
*  BINDING =  "
*  DEADLINE =  "
*  EXCEPT =  "
*  METHOD =  "
*  RESULT =  "
*  DECISION =  "
.



IMPORTING Parameters details for SWD_STEP_SET

STEP - API: Step Definition

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

PROPTS - Properties

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

CONTAINERS - Container

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

TABLES Parameters details for SWD_STEP_SET

CASE_DECISION -

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

CONDITION -

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

TASKS -

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

IF_DECISION -

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

UNTIL_DECISION -

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

BINDING -

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

DEADLINE -

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

EXCEPT -

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

METHOD -

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

RESULT -

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

DECISION -

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

Copy and paste ABAP code example for SWD_STEP_SET 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_step  TYPE SWD_ASTEP, "   
lt_case_decision  TYPE STANDARD TABLE OF SWD_CASE, "   
lt_condition  TYPE STANDARD TABLE OF SWD_CONDEF, "   
lt_tasks  TYPE STANDARD TABLE OF SWD_ITASKS, "   
lv_propts  TYPE SWDTIPROPTS, "   
lt_if_decision  TYPE STANDARD TABLE OF SWD_IF, "   
lv_containers  TYPE SWDTACONT, "   
lt_until_decision  TYPE STANDARD TABLE OF SWD_IF, "   
lt_binding  TYPE STANDARD TABLE OF SWD_STBIND, "   
lt_deadline  TYPE STANDARD TABLE OF SWD_DEADLN, "   
lt_except  TYPE STANDARD TABLE OF SWD_EXCEPT, "   
lt_method  TYPE STANDARD TABLE OF SWD_IMETHD, "   
lt_result  TYPE STANDARD TABLE OF SWD_RESULT, "   
lt_decision  TYPE STANDARD TABLE OF SWD_DECSN. "   

  CALL FUNCTION 'SWD_STEP_SET'  "Fill step which is currently being processed
    EXPORTING
         STEP = lv_step
         PROPTS = lv_propts
         CONTAINERS = lv_containers
    TABLES
         CASE_DECISION = lt_case_decision
         CONDITION = lt_condition
         TASKS = lt_tasks
         IF_DECISION = lt_if_decision
         UNTIL_DECISION = lt_until_decision
         BINDING = lt_binding
         DEADLINE = lt_deadline
         EXCEPT = lt_except
         METHOD = lt_method
         RESULT = lt_result
         DECISION = lt_decision
. " SWD_STEP_SET




ABAP code using 7.40 inline data declarations to call FM SWD_STEP_SET

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



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!