SAP DELIVERY_GET_COMPONENT_STATE Function Module for Delivers the release and the Support Package of a software component









DELIVERY_GET_COMPONENT_STATE is a standard delivery get component state SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Delivers the release and the Support Package of a software component 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 delivery get component state FM, simply by entering the name DELIVERY_GET_COMPONENT_STATE into the relevant SAP transaction such as SE37 or SE38.

Function Group: SUGU
Program Name: SAPLSUGU
Main Program:
Appliation area: S
Release date: 12-May-1999
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function DELIVERY_GET_COMPONENT_STATE 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_GET_COMPONENT_STATE'"Delivers the release and the Support Package of a software component
  EXPORTING
   IV_COMPNAME =  "Name of the software component
   IV_BUFFERED =  "Flag for buffered reading

 IMPORTING
   EV_COMPVERS =  "Software Component Release
   EV_COMPPALV =  "Support Package level of the software component
   EV_PUTSTATUS =  "Current upgrade status (PUTSTATUS)

EXCEPTIONS
   COMP_NOT_FOUND = 1
.



IMPORTING Parameters details for DELIVERY_GET_COMPONENT_STATE

IV_COMPNAME - Name of the software component

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

IV_BUFFERED - Flag for buffered reading

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

EXPORTING Parameters details for DELIVERY_GET_COMPONENT_STATE

EV_COMPVERS - Software Component Release

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

EV_COMPPALV - Support Package level of the software component

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

EV_PUTSTATUS - Current upgrade status (PUTSTATUS)

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

EXCEPTIONS details

COMP_NOT_FOUND - Unable to find software component

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

Copy and paste ABAP code example for DELIVERY_GET_COMPONENT_STATE 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_ev_compvers  TYPE CVERS-RELEASE, "   
lv_iv_compname  TYPE CVERS-COMPONENT, "   
lv_comp_not_found  TYPE CVERS, "   
lv_ev_comppalv  TYPE SUGU_PARA-COMPPALV, "   
lv_iv_buffered  TYPE SUGU_PARA-XBFLAG, "   
lv_ev_putstatus  TYPE UVERS-PUTSTATUS. "   

  CALL FUNCTION 'DELIVERY_GET_COMPONENT_STATE'  "Delivers the release and the Support Package of a software component
    EXPORTING
         IV_COMPNAME = lv_iv_compname
         IV_BUFFERED = lv_iv_buffered
    IMPORTING
         EV_COMPVERS = lv_ev_compvers
         EV_COMPPALV = lv_ev_comppalv
         EV_PUTSTATUS = lv_ev_putstatus
    EXCEPTIONS
        COMP_NOT_FOUND = 1
. " DELIVERY_GET_COMPONENT_STATE




ABAP code using 7.40 inline data declarations to call FM DELIVERY_GET_COMPONENT_STATE

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 RELEASE FROM CVERS INTO @DATA(ld_ev_compvers).
 
"SELECT single COMPONENT FROM CVERS INTO @DATA(ld_iv_compname).
 
 
"SELECT single COMPPALV FROM SUGU_PARA INTO @DATA(ld_ev_comppalv).
 
"SELECT single XBFLAG FROM SUGU_PARA INTO @DATA(ld_iv_buffered).
 
"SELECT single PUTSTATUS FROM UVERS INTO @DATA(ld_ev_putstatus).
 


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!