SAP SW_CREATE_VERSION Function Module for Create new SW-Project version









SW_CREATE_VERSION is a standard sw create version SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Create new SW-Project version 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 sw create version FM, simply by entering the name SW_CREATE_VERSION into the relevant SAP transaction such as SE37 or SE38.

Function Group: CAD_SRV_ECTR_SW
Program Name: SAPLCAD_SRV_ECTR_SW
Main Program: SAPLCAD_SRV_ECTR_SW
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function SW_CREATE_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 'SW_CREATE_VERSION'"Create new SW-Project version
EXPORTING
IV_PROJECT_KEY = "DB_KEY of SW-Project
IV_SW_VERSION = "External Version ID for Software
IV_BUILD_URL = "Navigation URL of Software Build in ALM
IV_BUILD_CNT = "Number of Software Project Builds
IV_BUILD_TIMESTMP = "Time of Software Project Build (YYYYMMDDhhmmss)
* IV_MAND_UPDATE_FLG = ABAP_FALSE "At Least One Update Required
* IS_DOC_KEY = "BAPIS DMS: document key
* IV_DESCRIPTION = "Description in logon-language

IMPORTING
ES_VERSION = "Attribute data of SW-project version
EV_RUNTIME = "Runtime in milliseconds
ES_RETURN = "Return Parameter

TABLES
* ET_RETURN = "Return Parameter
.



IMPORTING Parameters details for SW_CREATE_VERSION

IV_PROJECT_KEY - DB_KEY of SW-Project

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

IV_SW_VERSION - External Version ID for Software

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

IV_BUILD_URL - Navigation URL of Software Build in ALM

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

IV_BUILD_CNT - Number of Software Project Builds

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

IV_BUILD_TIMESTMP - Time of Software Project Build (YYYYMMDDhhmmss)

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

IV_MAND_UPDATE_FLG - At Least One Update Required

Data type: /PLMB/SW_MAND_UPDATE_FLG
Default: ABAP_FALSE
Optional: Yes
Call by Reference: No ( called with pass by value option)

IS_DOC_KEY - BAPIS DMS: document key

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

IV_DESCRIPTION - Description in logon-language

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

EXPORTING Parameters details for SW_CREATE_VERSION

ES_VERSION - Attribute data of SW-project version

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

EV_RUNTIME - Runtime in milliseconds

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

ES_RETURN - Return Parameter

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

TABLES Parameters details for SW_CREATE_VERSION

ET_RETURN - Return Parameter

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

Copy and paste ABAP code example for SW_CREATE_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:
lt_et_return  TYPE STANDARD TABLE OF BAPIRET2, "   
lv_es_version  TYPE CAD_SRV_ECTR_SW_VERSION, "   
lv_iv_project_key  TYPE SYSUUID_C32, "   
lv_ev_runtime  TYPE CAD_SRV_RUNTIME_C, "   
lv_iv_sw_version  TYPE /PLMB/SW_VERSION, "   
lv_es_return  TYPE BAPIRET2, "   
lv_iv_build_url  TYPE /PLMB/SW_BUILD_URL, "   
lv_iv_build_cnt  TYPE /PLMB/SW_BUILD_CNT, "   
lv_iv_build_timestmp  TYPE TIMESTAMP, "   
lv_iv_mand_update_flg  TYPE /PLMB/SW_MAND_UPDATE_FLG, "   ABAP_FALSE
lv_is_doc_key  TYPE BAPI_DOC_KEYS, "   
lv_iv_description  TYPE TEXT60. "   

  CALL FUNCTION 'SW_CREATE_VERSION'  "Create new SW-Project version
    EXPORTING
         IV_PROJECT_KEY = lv_iv_project_key
         IV_SW_VERSION = lv_iv_sw_version
         IV_BUILD_URL = lv_iv_build_url
         IV_BUILD_CNT = lv_iv_build_cnt
         IV_BUILD_TIMESTMP = lv_iv_build_timestmp
         IV_MAND_UPDATE_FLG = lv_iv_mand_update_flg
         IS_DOC_KEY = lv_is_doc_key
         IV_DESCRIPTION = lv_iv_description
    IMPORTING
         ES_VERSION = lv_es_version
         EV_RUNTIME = lv_ev_runtime
         ES_RETURN = lv_es_return
    TABLES
         ET_RETURN = lt_et_return
. " SW_CREATE_VERSION




ABAP code using 7.40 inline data declarations to call FM SW_CREATE_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.

 
 
 
 
 
 
 
 
 
DATA(ld_iv_mand_update_flg) = ABAP_FALSE.
 
 
 


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!