SAP SIW_RFC_SYNTAX_CHECK Function Module for Perform Syntax Check on a given object









SIW_RFC_SYNTAX_CHECK is a standard siw rfc syntax check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Perform Syntax Check on a given object processing and below is the pattern details for this FM, 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 siw rfc syntax check FM, simply by entering the name SIW_RFC_SYNTAX_CHECK into the relevant SAP transaction such as SE37 or SE38.

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



Function SIW_RFC_SYNTAX_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 'SIW_RFC_SYNTAX_CHECK'"Perform Syntax Check on a given object
EXPORTING
I_OBJECT = "Object Type
I_OBJNAME = "Object Name in Object Directory
* I_METHODNAME = "

IMPORTING
E_STR_EXCEPTION = "Message/Exception
E_SYNTAXERROR = "
.



IMPORTING Parameters details for SIW_RFC_SYNTAX_CHECK

I_OBJECT - Object Type

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

I_OBJNAME - Object Name in Object Directory

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

I_METHODNAME -

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

EXPORTING Parameters details for SIW_RFC_SYNTAX_CHECK

E_STR_EXCEPTION - Message/Exception

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

E_SYNTAXERROR -

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

Copy and paste ABAP code example for SIW_RFC_SYNTAX_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_i_object  TYPE TADIR-OBJECT, "   
lv_e_str_exception  TYPE SIW_STR_MSG, "   
lv_i_objname  TYPE TADIR-OBJ_NAME, "   
lv_e_syntaxerror  TYPE STRING, "   
lv_i_methodname  TYPE SEOCPDNAME. "   

  CALL FUNCTION 'SIW_RFC_SYNTAX_CHECK'  "Perform Syntax Check on a given object
    EXPORTING
         I_OBJECT = lv_i_object
         I_OBJNAME = lv_i_objname
         I_METHODNAME = lv_i_methodname
    IMPORTING
         E_STR_EXCEPTION = lv_e_str_exception
         E_SYNTAXERROR = lv_e_syntaxerror
. " SIW_RFC_SYNTAX_CHECK




ABAP code using 7.40 inline data declarations to call FM SIW_RFC_SYNTAX_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.

"SELECT single OBJECT FROM TADIR INTO @DATA(ld_i_object).
 
 
"SELECT single OBJ_NAME FROM TADIR INTO @DATA(ld_i_objname).
 
 
 


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!