SAP CS_CL_S_DBM_EXIST_CHECK Function Module for NOTRANSL: Prüft, ob zum Dokument Stückliste existiert









CS_CL_S_DBM_EXIST_CHECK is a standard cs cl s dbm exist 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 NOTRANSL: Prüft, ob zum Dokument Stückliste existiert 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 cs cl s dbm exist check FM, simply by entering the name CS_CL_S_DBM_EXIST_CHECK into the relevant SAP transaction such as SE37 or SE38.

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



Function CS_CL_S_DBM_EXIST_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 'CS_CL_S_DBM_EXIST_CHECK'"NOTRANSL: Prüft, ob zum Dokument Stückliste existiert
EXPORTING
I_DOKNR = "Document number
I_DOKAR = "Document Type
I_DOKTL = "Document Part
I_DOKVR = "Document Version

IMPORTING
E_FLG_DBM_EXISTS = "Single-Character Indicator
.



IMPORTING Parameters details for CS_CL_S_DBM_EXIST_CHECK

I_DOKNR - Document number

Data type: DOST-DOKNR
Optional: No
Call by Reference: Yes

I_DOKAR - Document Type

Data type: DOST-DOKAR
Optional: No
Call by Reference: Yes

I_DOKTL - Document Part

Data type: DOST-DOKTL
Optional: No
Call by Reference: Yes

I_DOKVR - Document Version

Data type: DOST-DOKVR
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for CS_CL_S_DBM_EXIST_CHECK

E_FLG_DBM_EXISTS - Single-Character Indicator

Data type: CSDATA-CHAR1
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CS_CL_S_DBM_EXIST_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_doknr  TYPE DOST-DOKNR, "   
lv_e_flg_dbm_exists  TYPE CSDATA-CHAR1, "   
lv_i_dokar  TYPE DOST-DOKAR, "   
lv_i_doktl  TYPE DOST-DOKTL, "   
lv_i_dokvr  TYPE DOST-DOKVR. "   

  CALL FUNCTION 'CS_CL_S_DBM_EXIST_CHECK'  "NOTRANSL: Prüft, ob zum Dokument Stückliste existiert
    EXPORTING
         I_DOKNR = lv_i_doknr
         I_DOKAR = lv_i_dokar
         I_DOKTL = lv_i_doktl
         I_DOKVR = lv_i_dokvr
    IMPORTING
         E_FLG_DBM_EXISTS = lv_e_flg_dbm_exists
. " CS_CL_S_DBM_EXIST_CHECK




ABAP code using 7.40 inline data declarations to call FM CS_CL_S_DBM_EXIST_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 DOKNR FROM DOST INTO @DATA(ld_i_doknr).
 
"SELECT single CHAR1 FROM CSDATA INTO @DATA(ld_e_flg_dbm_exists).
 
"SELECT single DOKAR FROM DOST INTO @DATA(ld_i_dokar).
 
"SELECT single DOKTL FROM DOST INTO @DATA(ld_i_doktl).
 
"SELECT single DOKVR FROM DOST INTO @DATA(ld_i_dokvr).
 


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!