SAP SKWR_INDEX_CHANGE Function Module for









SKWR_INDEX_CHANGE is a standard skwr index change 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 skwr index change FM, simply by entering the name SKWR_INDEX_CHANGE into the relevant SAP transaction such as SE37 or SE38.

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



Function SKWR_INDEX_CHANGE 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 'SKWR_INDEX_CHANGE'"
EXPORTING
INDEX_ID = "GUID in 'CHAR' Format in Uppercase
X_TRAINING = "

EXCEPTIONS
INDEX_DOESNT_EXIST = 1 COMMUNICATION_FAILED = 2 XML_ERROR = 3 LOCKING_INDEX_FAILED = 4 FAILED = 5
.



IMPORTING Parameters details for SKWR_INDEX_CHANGE

INDEX_ID - GUID in 'CHAR' Format in Uppercase

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

X_TRAINING -

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

EXCEPTIONS details

INDEX_DOESNT_EXIST -

Data type:
Optional: No
Call by Reference: Yes

COMMUNICATION_FAILED -

Data type:
Optional: No
Call by Reference: Yes

XML_ERROR -

Data type:
Optional: No
Call by Reference: Yes

LOCKING_INDEX_FAILED -

Data type:
Optional: No
Call by Reference: Yes

FAILED -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SKWR_INDEX_CHANGE 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_index_id  TYPE GUID_32, "   
lv_index_doesnt_exist  TYPE GUID_32, "   
lv_x_training  TYPE XFELD, "   
lv_communication_failed  TYPE XFELD, "   
lv_xml_error  TYPE XFELD, "   
lv_locking_index_failed  TYPE XFELD, "   
lv_failed  TYPE XFELD. "   

  CALL FUNCTION 'SKWR_INDEX_CHANGE'  "
    EXPORTING
         INDEX_ID = lv_index_id
         X_TRAINING = lv_x_training
    EXCEPTIONS
        INDEX_DOESNT_EXIST = 1
        COMMUNICATION_FAILED = 2
        XML_ERROR = 3
        LOCKING_INDEX_FAILED = 4
        FAILED = 5
. " SKWR_INDEX_CHANGE




ABAP code using 7.40 inline data declarations to call FM SKWR_INDEX_CHANGE

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!