SAP SAPWLN3_PARAMETER_DELETE Function Module for









SAPWLN3_PARAMETER_DELETE is a standard sapwln3 parameter delete 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 sapwln3 parameter delete FM, simply by entering the name SAPWLN3_PARAMETER_DELETE into the relevant SAP transaction such as SE37 or SE38.

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



Function SAPWLN3_PARAMETER_DELETE 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 'SAPWLN3_PARAMETER_DELETE'"
  EXPORTING
   CONSUMER_TYPE =  "
*  CONSUMER_NAME =  "
   PARAMETER_NAME =  "
*  MONITORING_SYSTEM =  "

EXCEPTIONS
   PARAMETER_NOT_FOUND = 1    DATABASE_PROBLEMS = 2    CONSUMER_NAME_MISSING = 3    RFC_PROBLEMS_DETECTED = 4    FUNCMODULE_NOT_FOUND_IN_MONSYS = 5    INTERNAL_ERROR = 6    AUTHORISATION_MISSING = 7    COULD_NOT_LOCK_PARAMETER_TABLE = 8
.



IMPORTING Parameters details for SAPWLN3_PARAMETER_DELETE

CONSUMER_TYPE -

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

CONSUMER_NAME -

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

PARAMETER_NAME -

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

MONITORING_SYSTEM -

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

EXCEPTIONS details

PARAMETER_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

DATABASE_PROBLEMS -

Data type:
Optional: No
Call by Reference: Yes

CONSUMER_NAME_MISSING -

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

RFC_PROBLEMS_DETECTED -

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

FUNCMODULE_NOT_FOUND_IN_MONSYS -

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

INTERNAL_ERROR -

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

AUTHORISATION_MISSING -

Data type:
Optional: No
Call by Reference: Yes

COULD_NOT_LOCK_PARAMETER_TABLE -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SAPWLN3_PARAMETER_DELETE 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_consumer_type  TYPE SWLN3PCTYP, "   
lv_parameter_not_found  TYPE SWLN3PCTYP, "   
lv_consumer_name  TYPE SWLN3PCNAM, "   
lv_database_problems  TYPE SWLN3PCNAM, "   
lv_parameter_name  TYPE SAPWLPARNM, "   
lv_consumer_name_missing  TYPE SAPWLPARNM, "   
lv_monitoring_system  TYPE RFCDEST, "   
lv_rfc_problems_detected  TYPE RFCDEST, "   
lv_funcmodule_not_found_in_monsys  TYPE RFCDEST, "   
lv_internal_error  TYPE RFCDEST, "   
lv_authorisation_missing  TYPE RFCDEST, "   
lv_could_not_lock_parameter_table  TYPE RFCDEST. "   

  CALL FUNCTION 'SAPWLN3_PARAMETER_DELETE'  "
    EXPORTING
         CONSUMER_TYPE = lv_consumer_type
         CONSUMER_NAME = lv_consumer_name
         PARAMETER_NAME = lv_parameter_name
         MONITORING_SYSTEM = lv_monitoring_system
    EXCEPTIONS
        PARAMETER_NOT_FOUND = 1
        DATABASE_PROBLEMS = 2
        CONSUMER_NAME_MISSING = 3
        RFC_PROBLEMS_DETECTED = 4
        FUNCMODULE_NOT_FOUND_IN_MONSYS = 5
        INTERNAL_ERROR = 6
        AUTHORISATION_MISSING = 7
        COULD_NOT_LOCK_PARAMETER_TABLE = 8
. " SAPWLN3_PARAMETER_DELETE




ABAP code using 7.40 inline data declarations to call FM SAPWLN3_PARAMETER_DELETE

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!