SAP SWW_WI_ENABLE Function Module for Remove Lock Against Execution for Work Item









SWW_WI_ENABLE is a standard sww wi enable SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Remove Lock Against Execution for 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 sww wi enable FM, simply by entering the name SWW_WI_ENABLE into the relevant SAP transaction such as SE37 or SE38.

Function Group: SWWA
Program Name: SAPLSWWA
Main Program: SAPLSWWA
Appliation area:
Release date: 02-Jul-1998
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function SWW_WI_ENABLE 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 'SWW_WI_ENABLE'"Remove Lock Against Execution for Work Item
EXPORTING
WI_ID = "Work Item ID
* DO_COMMIT = 'X' "Indicator for Control of Commit Logic
* AUTHORIZATION_CHECKED = ' ' "Flag for Control of Authorization Check
* PRECONDITIONS_CHECKED = ' ' "Indicator for Control of Status and Type Check
* DO_SYNC_CALLBACK = ' ' "Indicator for Control of Callback to WFM
* INCLUDING_SUBWORKITEMS = 'X' "Indicator for Control of Recursion

EXCEPTIONS
UPDATE_FAILED = 1 NO_AUTHORIZATION = 2 INVALID_TYPE = 3
.



IMPORTING Parameters details for SWW_WI_ENABLE

WI_ID - Work Item ID

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

DO_COMMIT - Indicator for Control of Commit Logic

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

AUTHORIZATION_CHECKED - Flag for Control of Authorization Check

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

PRECONDITIONS_CHECKED - Indicator for Control of Status and Type Check

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

DO_SYNC_CALLBACK - Indicator for Control of Callback to WFM

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

INCLUDING_SUBWORKITEMS - Indicator for Control of Recursion

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

EXCEPTIONS details

UPDATE_FAILED - Work Item Cannot Be Updated

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

NO_AUTHORIZATION - User Has No Authorization for this Action

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

INVALID_TYPE - Method Not Allowed for this Type

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

Copy and paste ABAP code example for SWW_WI_ENABLE 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_update_failed  TYPE SWWWIHEAD, "   
lv_do_commit  TYPE SWWCOMMIT-COMMITFLAG, "   'X'
lv_no_authorization  TYPE SWWCOMMIT, "   
lv_invalid_type  TYPE SWWCOMMIT, "   
lv_authorization_checked  TYPE SWWCOMMIT-AUTHCKFLAG, "   SPACE
lv_preconditions_checked  TYPE SWWCOMMIT-CHECKFLAG, "   SPACE
lv_do_sync_callback  TYPE SWWCOMMIT-SYNCFLAG, "   SPACE
lv_including_subworkitems  TYPE SWWCOMMIT-SUBWIFLAG. "   'X'

  CALL FUNCTION 'SWW_WI_ENABLE'  "Remove Lock Against Execution for Work Item
    EXPORTING
         WI_ID = lv_wi_id
         DO_COMMIT = lv_do_commit
         AUTHORIZATION_CHECKED = lv_authorization_checked
         PRECONDITIONS_CHECKED = lv_preconditions_checked
         DO_SYNC_CALLBACK = lv_do_sync_callback
         INCLUDING_SUBWORKITEMS = lv_including_subworkitems
    EXCEPTIONS
        UPDATE_FAILED = 1
        NO_AUTHORIZATION = 2
        INVALID_TYPE = 3
. " SWW_WI_ENABLE




ABAP code using 7.40 inline data declarations to call FM SWW_WI_ENABLE

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 COMMITFLAG FROM SWWCOMMIT INTO @DATA(ld_do_commit).
DATA(ld_do_commit) = 'X'.
 
 
 
"SELECT single AUTHCKFLAG FROM SWWCOMMIT INTO @DATA(ld_authorization_checked).
DATA(ld_authorization_checked) = ' '.
 
"SELECT single CHECKFLAG FROM SWWCOMMIT INTO @DATA(ld_preconditions_checked).
DATA(ld_preconditions_checked) = ' '.
 
"SELECT single SYNCFLAG FROM SWWCOMMIT INTO @DATA(ld_do_sync_callback).
DATA(ld_do_sync_callback) = ' '.
 
"SELECT single SUBWIFLAG FROM SWWCOMMIT INTO @DATA(ld_including_subworkitems).
DATA(ld_including_subworkitems) = 'X'.
 


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!