SAP CRS_CHECK_INTERFACE Function Module for









CRS_CHECK_INTERFACE is a standard crs check interface 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 crs check interface FM, simply by entering the name CRS_CHECK_INTERFACE into the relevant SAP transaction such as SE37 or SE38.

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



Function CRS_CHECK_INTERFACE 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 'CRS_CHECK_INTERFACE'"
EXPORTING
IV_FUNCNAME = "
* IV_CHECK_TYPE = "

TABLES
TO_PARAMETERS = "

EXCEPTIONS
FUNCTION_NOT_FOUND = 1 PARAMETER_MISMATCH = 2 TYPE_MISMATCH = 3
.



IMPORTING Parameters details for CRS_CHECK_INTERFACE

IV_FUNCNAME -

Data type: TFDIR-FUNCNAME
Optional: No
Call by Reference: Yes

IV_CHECK_TYPE -

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

TABLES Parameters details for CRS_CHECK_INTERFACE

TO_PARAMETERS -

Data type: RFC_FUNINT
Optional: No
Call by Reference: Yes

EXCEPTIONS details

FUNCTION_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

PARAMETER_MISMATCH -

Data type:
Optional: No
Call by Reference: Yes

TYPE_MISMATCH -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CRS_CHECK_INTERFACE 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_iv_funcname  TYPE TFDIR-FUNCNAME, "   
lt_to_parameters  TYPE STANDARD TABLE OF RFC_FUNINT, "   
lv_function_not_found  TYPE RFC_FUNINT, "   
lv_iv_check_type  TYPE BOOLEAN, "   
lv_parameter_mismatch  TYPE BOOLEAN, "   
lv_type_mismatch  TYPE BOOLEAN. "   

  CALL FUNCTION 'CRS_CHECK_INTERFACE'  "
    EXPORTING
         IV_FUNCNAME = lv_iv_funcname
         IV_CHECK_TYPE = lv_iv_check_type
    TABLES
         TO_PARAMETERS = lt_to_parameters
    EXCEPTIONS
        FUNCTION_NOT_FOUND = 1
        PARAMETER_MISMATCH = 2
        TYPE_MISMATCH = 3
. " CRS_CHECK_INTERFACE




ABAP code using 7.40 inline data declarations to call FM CRS_CHECK_INTERFACE

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 FUNCNAME FROM TFDIR INTO @DATA(ld_iv_funcname).
 
 
 
 
 
 


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!