SAP SALW_TEST_ALL_FUNCTIONS Function Module for









SALW_TEST_ALL_FUNCTIONS is a standard salw test all functions 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 salw test all functions FM, simply by entering the name SALW_TEST_ALL_FUNCTIONS into the relevant SAP transaction such as SE37 or SE38.

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



Function SALW_TEST_ALL_FUNCTIONS 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 'SALW_TEST_ALL_FUNCTIONS'"
EXPORTING
* TEST1_PARAMETERS = ' ' "
* LONGSALW = "
* VARIANTE = "
* NEW_VARIANT_NAME = "
* NEW_SHORT_TEXT = "
* NEW_PARENT_VARIANT = "
* NEW_OWNER = "
* MONITOR = "
* TID_SPECIFIC = ' ' "
* TEST2_PARAMETERS = 'X' "
* LONGBAPI = "

IMPORTING
SHORT_TEXT = "
PARENT_VARIANT = "
OWNER = "

TABLES
* BAPIRETURNS = "
.



IMPORTING Parameters details for SALW_TEST_ALL_FUNCTIONS

TEST1_PARAMETERS -

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

LONGSALW -

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

VARIANTE -

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

NEW_VARIANT_NAME -

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

NEW_SHORT_TEXT -

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

NEW_PARENT_VARIANT -

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

NEW_OWNER -

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

MONITOR -

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

TID_SPECIFIC -

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

TEST2_PARAMETERS -

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

LONGBAPI -

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

EXPORTING Parameters details for SALW_TEST_ALL_FUNCTIONS

SHORT_TEXT -

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

PARENT_VARIANT -

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

OWNER -

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

TABLES Parameters details for SALW_TEST_ALL_FUNCTIONS

BAPIRETURNS -

Data type: BAPIRET2
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for SALW_TEST_ALL_FUNCTIONS 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_short_text  TYPE ALCUSSETTX, "   
lt_bapireturns  TYPE STANDARD TABLE OF BAPIRET2, "   
lv_test1_parameters  TYPE C, "   ' '
lv_longsalw  TYPE ALMTFULLNM, "   
lv_variante  TYPE ALCUSSETNM, "   
lv_parent_variant  TYPE ALCUSSETNM, "   
lv_new_variant_name  TYPE ALCUSSETNM, "   
lv_owner  TYPE XMILOGCOMP, "   
lv_new_short_text  TYPE ALCUSSETTX, "   
lv_new_parent_variant  TYPE ALCUSSETNM, "   
lv_new_owner  TYPE XMILOGCOMP, "   
lv_monitor  TYPE ALMONINAME, "   
lv_tid_specific  TYPE C, "   ' '
lv_test2_parameters  TYPE C, "   'X'
lv_longbapi  TYPE ALMTFULLNM. "   

  CALL FUNCTION 'SALW_TEST_ALL_FUNCTIONS'  "
    EXPORTING
         TEST1_PARAMETERS = lv_test1_parameters
         LONGSALW = lv_longsalw
         VARIANTE = lv_variante
         NEW_VARIANT_NAME = lv_new_variant_name
         NEW_SHORT_TEXT = lv_new_short_text
         NEW_PARENT_VARIANT = lv_new_parent_variant
         NEW_OWNER = lv_new_owner
         MONITOR = lv_monitor
         TID_SPECIFIC = lv_tid_specific
         TEST2_PARAMETERS = lv_test2_parameters
         LONGBAPI = lv_longbapi
    IMPORTING
         SHORT_TEXT = lv_short_text
         PARENT_VARIANT = lv_parent_variant
         OWNER = lv_owner
    TABLES
         BAPIRETURNS = lt_bapireturns
. " SALW_TEST_ALL_FUNCTIONS




ABAP code using 7.40 inline data declarations to call FM SALW_TEST_ALL_FUNCTIONS

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.

 
 
DATA(ld_test1_parameters) = ' '.
 
 
 
 
 
 
 
 
 
 
DATA(ld_tid_specific) = ' '.
 
DATA(ld_test2_parameters) = '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!