SAP DELIVERY_UPGRADE_COMPONENT Function Module for









DELIVERY_UPGRADE_COMPONENT is a standard delivery upgrade component 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 delivery upgrade component FM, simply by entering the name DELIVERY_UPGRADE_COMPONENT into the relevant SAP transaction such as SE37 or SE38.

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



Function DELIVERY_UPGRADE_COMPONENT 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 'DELIVERY_UPGRADE_COMPONENT'"
  EXPORTING
   IV_COMPNAME =  "Name of the software component
*  IV_COMPTYPE = ' ' "
   IV_COMPVERS =  "Software Component Release
*  IV_COMPPALV = 0 "Support Package Level of Software Component
*  IV_DESC_TEXT = ' ' "
*  IV_LANGUAGE = SY-LANGU "

EXCEPTIONS
   COMP_NOT_FOUND = 1    COMP_PROTECTED = 2    COMP_WRONG_VERSION = 3    COMP_WRONG_PATCH_LEVEL = 4    COMP_WRONG_TYPE = 5    UPDATE_FAILED = 6    NOT_PREPARED = 7
.



IMPORTING Parameters details for DELIVERY_UPGRADE_COMPONENT

IV_COMPNAME - Name of the software component

Data type: CVERS-COMPONENT
Optional: No
Call by Reference: Yes

IV_COMPTYPE -

Data type: CVERS-COMP_TYPE
Default: SPACE
Optional: Yes
Call by Reference: Yes

IV_COMPVERS - Software Component Release

Data type: CVERS-RELEASE
Optional: No
Call by Reference: Yes

IV_COMPPALV - Support Package Level of Software Component

Data type: SUGU_PARA-COMPPALV
Optional: Yes
Call by Reference: Yes

IV_DESC_TEXT -

Data type: CVERS_REF-DESC_TEXT
Default: SPACE
Optional: Yes
Call by Reference: Yes

IV_LANGUAGE -

Data type: CVERS_REF-LANGU
Default: SY-LANGU
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

COMP_NOT_FOUND - Unable to find software component

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

COMP_PROTECTED -

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

COMP_WRONG_VERSION -

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

COMP_WRONG_PATCH_LEVEL -

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

COMP_WRONG_TYPE -

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

UPDATE_FAILED -

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

NOT_PREPARED -

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

Copy and paste ABAP code example for DELIVERY_UPGRADE_COMPONENT 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_iv_compname  TYPE CVERS-COMPONENT, "   
lv_comp_not_found  TYPE CVERS, "   
lv_iv_comptype  TYPE CVERS-COMP_TYPE, "   SPACE
lv_comp_protected  TYPE CVERS, "   
lv_iv_compvers  TYPE CVERS-RELEASE, "   
lv_comp_wrong_version  TYPE CVERS, "   
lv_iv_comppalv  TYPE SUGU_PARA-COMPPALV, "   0
lv_comp_wrong_patch_level  TYPE SUGU_PARA, "   
lv_iv_desc_text  TYPE CVERS_REF-DESC_TEXT, "   SPACE
lv_comp_wrong_type  TYPE CVERS_REF, "   
lv_iv_language  TYPE CVERS_REF-LANGU, "   SY-LANGU
lv_update_failed  TYPE CVERS_REF, "   
lv_not_prepared  TYPE CVERS_REF. "   

  CALL FUNCTION 'DELIVERY_UPGRADE_COMPONENT'  "
    EXPORTING
         IV_COMPNAME = lv_iv_compname
         IV_COMPTYPE = lv_iv_comptype
         IV_COMPVERS = lv_iv_compvers
         IV_COMPPALV = lv_iv_comppalv
         IV_DESC_TEXT = lv_iv_desc_text
         IV_LANGUAGE = lv_iv_language
    EXCEPTIONS
        COMP_NOT_FOUND = 1
        COMP_PROTECTED = 2
        COMP_WRONG_VERSION = 3
        COMP_WRONG_PATCH_LEVEL = 4
        COMP_WRONG_TYPE = 5
        UPDATE_FAILED = 6
        NOT_PREPARED = 7
. " DELIVERY_UPGRADE_COMPONENT




ABAP code using 7.40 inline data declarations to call FM DELIVERY_UPGRADE_COMPONENT

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 COMPONENT FROM CVERS INTO @DATA(ld_iv_compname).
 
 
"SELECT single COMP_TYPE FROM CVERS INTO @DATA(ld_iv_comptype).
DATA(ld_iv_comptype) = ' '.
 
 
"SELECT single RELEASE FROM CVERS INTO @DATA(ld_iv_compvers).
 
 
"SELECT single COMPPALV FROM SUGU_PARA INTO @DATA(ld_iv_comppalv).
 
 
"SELECT single DESC_TEXT FROM CVERS_REF INTO @DATA(ld_iv_desc_text).
DATA(ld_iv_desc_text) = ' '.
 
 
"SELECT single LANGU FROM CVERS_REF INTO @DATA(ld_iv_language).
DATA(ld_iv_language) = SY-LANGU.
 
 
 


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!