SAP SKWF_NMSPC_IO_RENAME_CHECK Function Module for
SKWF_NMSPC_IO_RENAME_CHECK is a standard skwf nmspc io rename check 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 skwf nmspc io rename check FM, simply by entering the name SKWF_NMSPC_IO_RENAME_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: SKWF_NAMESPACE
Program Name: SAPLSKWF_NAMESPACE
Main Program: SAPLSKWF_NAMESPACE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:
Function SKWF_NMSPC_IO_RENAME_CHECK 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 'SKWF_NMSPC_IO_RENAME_CHECK'".
EXPORTING
IO = "Directory
URL_PART = "
IMPORTING
ERROR = "Error Object
IMPORTING Parameters details for SKWF_NMSPC_IO_RENAME_CHECK
IO - Directory
Data type: SKWF_IOOptional: No
Call by Reference: No ( called with pass by value option)
URL_PART -
Data type: SKWF_URLPOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SKWF_NMSPC_IO_RENAME_CHECK
ERROR - Error Object
Data type: SKWF_ERROROptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SKWF_NMSPC_IO_RENAME_CHECK 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_io | TYPE SKWF_IO, " | |||
lv_error | TYPE SKWF_ERROR, " | |||
lv_url_part | TYPE SKWF_URLP. " |
  CALL FUNCTION 'SKWF_NMSPC_IO_RENAME_CHECK' " |
EXPORTING | ||
IO | = lv_io | |
URL_PART | = lv_url_part | |
IMPORTING | ||
ERROR | = lv_error | |
. " SKWF_NMSPC_IO_RENAME_CHECK |
ABAP code using 7.40 inline data declarations to call FM SKWF_NMSPC_IO_RENAME_CHECK
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