SAP SCWB_GET_VERSION Function Module for









SCWB_GET_VERSION is a standard scwb get version 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 scwb get version FM, simply by entering the name SCWB_GET_VERSION into the relevant SAP transaction such as SE37 or SE38.

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



Function SCWB_GET_VERSION 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 'SCWB_GET_VERSION'"
  EXPORTING
   IS_HEADER =  "

 IMPORTING
   ES_OBJECT =  "
   ES_XOBJECT =  "

EXCEPTIONS
   ERROR = 1    RFC_ERROR = 2    NO_VERSION = 3
.



IMPORTING Parameters details for SCWB_GET_VERSION

IS_HEADER -

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

EXPORTING Parameters details for SCWB_GET_VERSION

ES_OBJECT -

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

ES_XOBJECT -

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

EXCEPTIONS details

ERROR -

Data type:
Optional: No
Call by Reference: Yes

RFC_ERROR -

Data type:
Optional: No
Call by Reference: Yes

NO_VERSION -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SCWB_GET_VERSION 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_error  TYPE STRING, "   
lv_es_object  TYPE SVRS2_VERSIONABLE_OBJECT, "   
lv_is_header  TYPE BCWBD_VERSION_HEADER, "   
lv_rfc_error  TYPE BCWBD_VERSION_HEADER, "   
lv_es_xobject  TYPE SVRS2_XVERSIONABLE_OBJECT, "   
lv_no_version  TYPE SVRS2_XVERSIONABLE_OBJECT. "   

  CALL FUNCTION 'SCWB_GET_VERSION'  "
    EXPORTING
         IS_HEADER = lv_is_header
    IMPORTING
         ES_OBJECT = lv_es_object
         ES_XOBJECT = lv_es_xobject
    EXCEPTIONS
        ERROR = 1
        RFC_ERROR = 2
        NO_VERSION = 3
. " SCWB_GET_VERSION




ABAP code using 7.40 inline data declarations to call FM SCWB_GET_VERSION

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!