SAP CBIH_LB05_SL_CHECK_EXIST Function Module for









CBIH_LB05_SL_CHECK_EXIST is a standard cbih lb05 sl check exist 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 cbih lb05 sl check exist FM, simply by entering the name CBIH_LB05_SL_CHECK_EXIST into the relevant SAP transaction such as SE37 or SE38.

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



Function CBIH_LB05_SL_CHECK_EXIST 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 'CBIH_LB05_SL_CHECK_EXIST'"
EXPORTING
I_WADOTYPE = "
I_WADONR = "
* I_ADDINF = "

IMPORTING
E_EXISTS = "

EXCEPTIONS
PARAMETER_ERROR = 1 KEY_NOT_UNIQUE = 2
.



IMPORTING Parameters details for CBIH_LB05_SL_CHECK_EXIST

I_WADOTYPE -

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

I_WADONR -

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

I_ADDINF -

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

EXPORTING Parameters details for CBIH_LB05_SL_CHECK_EXIST

E_EXISTS -

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

EXCEPTIONS details

PARAMETER_ERROR -

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

KEY_NOT_UNIQUE -

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

Copy and paste ABAP code example for CBIH_LB05_SL_CHECK_EXIST 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_e_exists  TYPE ESP1_BOOLEAN, "   
lv_i_wadotype  TYPE CCIHT_WADO-WADOTYPE, "   
lv_parameter_error  TYPE CCIHT_WADO, "   
lv_i_wadonr  TYPE CCIHT_WADO-WADONR, "   
lv_key_not_unique  TYPE CCIHT_WADO, "   
lv_i_addinf  TYPE RCGADDINF. "   

  CALL FUNCTION 'CBIH_LB05_SL_CHECK_EXIST'  "
    EXPORTING
         I_WADOTYPE = lv_i_wadotype
         I_WADONR = lv_i_wadonr
         I_ADDINF = lv_i_addinf
    IMPORTING
         E_EXISTS = lv_e_exists
    EXCEPTIONS
        PARAMETER_ERROR = 1
        KEY_NOT_UNIQUE = 2
. " CBIH_LB05_SL_CHECK_EXIST




ABAP code using 7.40 inline data declarations to call FM CBIH_LB05_SL_CHECK_EXIST

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 WADOTYPE FROM CCIHT_WADO INTO @DATA(ld_i_wadotype).
 
 
"SELECT single WADONR FROM CCIHT_WADO INTO @DATA(ld_i_wadonr).
 
 
 


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!