SAP /SAPAPO/CBM_DM_VERSION_EXISTS Function Module for Check Whether Version (Batch) Exists









/SAPAPO/CBM_DM_VERSION_EXISTS is a standard /sapapo/cbm dm version exists SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check Whether Version (Batch) Exists 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 /sapapo/cbm dm version exists FM, simply by entering the name /SAPAPO/CBM_DM_VERSION_EXISTS into the relevant SAP transaction such as SE37 or SE38.

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



Function /SAPAPO/CBM_DM_VERSION_EXISTS 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 '/SAPAPO/CBM_DM_VERSION_EXISTS'"Check Whether Version (Batch) Exists
EXPORTING
IS_VERSION = "Schlüssel für Version (Charge) im APO
* IV_IGNORE_NEGBUFFER = "Ignore negative buffer

IMPORTING
EV_VERSION_ON_DB = "Feld zum Ankreuzen

EXCEPTIONS
VERSION_NOT_EXIST = 1
.



IMPORTING Parameters details for /SAPAPO/CBM_DM_VERSION_EXISTS

IS_VERSION - Schlüssel für Version (Charge) im APO

Data type: /SAPAPO/CBM_KEY
Optional: No
Call by Reference: Yes

IV_IGNORE_NEGBUFFER - Ignore negative buffer

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

EXPORTING Parameters details for /SAPAPO/CBM_DM_VERSION_EXISTS

EV_VERSION_ON_DB - Feld zum Ankreuzen

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

EXCEPTIONS details

VERSION_NOT_EXIST - Version (Charge) ist nicht vorhanden

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

Copy and paste ABAP code example for /SAPAPO/CBM_DM_VERSION_EXISTS 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_is_version  TYPE /SAPAPO/CBM_KEY, "   
lv_ev_version_on_db  TYPE XFELD, "   
lv_version_not_exist  TYPE XFELD, "   
lv_iv_ignore_negbuffer  TYPE BOOLE_D. "   

  CALL FUNCTION '/SAPAPO/CBM_DM_VERSION_EXISTS'  "Check Whether Version (Batch) Exists
    EXPORTING
         IS_VERSION = lv_is_version
         IV_IGNORE_NEGBUFFER = lv_iv_ignore_negbuffer
    IMPORTING
         EV_VERSION_ON_DB = lv_ev_version_on_db
    EXCEPTIONS
        VERSION_NOT_EXIST = 1
. " /SAPAPO/CBM_DM_VERSION_EXISTS




ABAP code using 7.40 inline data declarations to call FM /SAPAPO/CBM_DM_VERSION_EXISTS

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.

 
 
 
 


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!