SAP IWB_PARSE_AND_MODIFY Function Module for









IWB_PARSE_AND_MODIFY is a standard iwb parse and modify 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 iwb parse and modify FM, simply by entering the name IWB_PARSE_AND_MODIFY into the relevant SAP transaction such as SE37 or SE38.

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



Function IWB_PARSE_AND_MODIFY 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 'IWB_PARSE_AND_MODIFY'"
EXPORTING
* PV_INPUTTYPE = ' ' "
PV_SEARCH_STR = "Search String
* PV_REPLACE_STR = ' ' "
* PV_STRING_IN = "Input String
* PV_BINFILE_LEN_IN = "
* PT_BIN_FILE_IN = "
* PT_ASCII_FILE_IN = "

IMPORTING
PV_STRING_OUT = "Output String
PV_BINFILE_LEN_OUT = "
PT_BIN_FILE_OUT = "
PT_ASCII_FILE_OUT = "
PV_HITS = "Number of Hits

EXCEPTIONS
NO_SEARCH_STR = 1 NO_VALID_TYPE = 2 BIN_TO_STRING_ERROR = 3 STRING_TO_XSTRING_ERROR = 4
.



IMPORTING Parameters details for IWB_PARSE_AND_MODIFY

PV_INPUTTYPE -

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

PV_SEARCH_STR - Search String

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

PV_REPLACE_STR -

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

PV_STRING_IN - Input String

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

PV_BINFILE_LEN_IN -

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

PT_BIN_FILE_IN -

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

PT_ASCII_FILE_IN -

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

EXPORTING Parameters details for IWB_PARSE_AND_MODIFY

PV_STRING_OUT - Output String

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

PV_BINFILE_LEN_OUT -

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

PT_BIN_FILE_OUT -

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

PT_ASCII_FILE_OUT -

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

PV_HITS - Number of Hits

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

EXCEPTIONS details

NO_SEARCH_STR -

Data type:
Optional: No
Call by Reference: Yes

NO_VALID_TYPE -

Data type:
Optional: No
Call by Reference: Yes

BIN_TO_STRING_ERROR -

Data type:
Optional: No
Call by Reference: Yes

STRING_TO_XSTRING_ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for IWB_PARSE_AND_MODIFY 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_pv_inputtype  TYPE IWPARAMS-FLAG, "   SPACE
lv_no_search_str  TYPE IWPARAMS, "   
lv_pv_string_out  TYPE STRING, "   
lv_no_valid_type  TYPE STRING, "   
lv_pv_search_str  TYPE STRING, "   
lv_pv_binfile_len_out  TYPE I, "   
lv_pv_replace_str  TYPE STRING, "   SPACE
lv_pt_bin_file_out  TYPE SDOKCNTBINS, "   
lv_bin_to_string_error  TYPE SDOKCNTBINS, "   
lv_pv_string_in  TYPE STRING, "   
lv_pt_ascii_file_out  TYPE HTMLTABLE, "   
lv_string_to_xstring_error  TYPE HTMLTABLE, "   
lv_pv_hits  TYPE I, "   
lv_pv_binfile_len_in  TYPE I, "   
lv_pt_bin_file_in  TYPE SDOKCNTBINS, "   
lv_pt_ascii_file_in  TYPE HTMLTABLE. "   

  CALL FUNCTION 'IWB_PARSE_AND_MODIFY'  "
    EXPORTING
         PV_INPUTTYPE = lv_pv_inputtype
         PV_SEARCH_STR = lv_pv_search_str
         PV_REPLACE_STR = lv_pv_replace_str
         PV_STRING_IN = lv_pv_string_in
         PV_BINFILE_LEN_IN = lv_pv_binfile_len_in
         PT_BIN_FILE_IN = lv_pt_bin_file_in
         PT_ASCII_FILE_IN = lv_pt_ascii_file_in
    IMPORTING
         PV_STRING_OUT = lv_pv_string_out
         PV_BINFILE_LEN_OUT = lv_pv_binfile_len_out
         PT_BIN_FILE_OUT = lv_pt_bin_file_out
         PT_ASCII_FILE_OUT = lv_pt_ascii_file_out
         PV_HITS = lv_pv_hits
    EXCEPTIONS
        NO_SEARCH_STR = 1
        NO_VALID_TYPE = 2
        BIN_TO_STRING_ERROR = 3
        STRING_TO_XSTRING_ERROR = 4
. " IWB_PARSE_AND_MODIFY




ABAP code using 7.40 inline data declarations to call FM IWB_PARSE_AND_MODIFY

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 FLAG FROM IWPARAMS INTO @DATA(ld_pv_inputtype).
DATA(ld_pv_inputtype) = ' '.
 
 
 
 
 
 
DATA(ld_pv_replace_str) = ' '.
 
 
 
 
 
 
 
 
 
 


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!