SAP UPG_GET_SINGLE_COMPREL Function Module for Reading a single component release

Search SAP Function Modules

UPG_GET_SINGLE_COMPREL is a standard upg get single comprel SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Reading a single component release 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 upg get single comprel FM, simply by entering the name UPG_GET_SINGLE_COMPREL into the relevant SAP transaction such as SE37 or SE38.

Function Group: SUGS
Program Name: SAPLSUGS
Main Program: SAPLSUGS
Appliation area: S
Release date: 12-May-1999
Mode(Normal, Remote etc): Normal Function Module
Update:

Function UPG_GET_SINGLE_COMPREL 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 'UPG_GET_SINGLE_COMPREL'"Reading a single component release
  EXPORTING
*  IV_COMPONENT = 'SAP_BASIS' "Component description
*  IV_BUFFERED = 'X' "Reading using table buffer ('X' = yes)

 IMPORTING
   EV_VERSION =  "Component version has been read
   EV_BASISSTATE =  "Basis status (SVERS <-> CVERS)

EXCEPTIONS
   NO_RELEASE_FOUND = 1    COMPONENT_RELEASE_NOT_FOUND = 2    INVALID_COMPONENT_NAME = 3 

.

IMPORTING Parameters details for UPG_GET_SINGLE_COMPREL

IV_COMPONENT - Component description

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

IV_BUFFERED - Reading using table buffer ('X' = yes)

Data type: SUGS_FPARA-BOOL
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for UPG_GET_SINGLE_COMPREL

EV_VERSION - Component version has been read

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

EV_BASISSTATE - Basis status (SVERS <-> CVERS)

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

EXCEPTIONS details

NO_RELEASE_FOUND - Unable to find release for any component

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

COMPONENT_RELEASE_NOT_FOUND - Unable to find the release for IV_COMPONENT

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

INVALID_COMPONENT_NAME - Component name is invalid ('*' for example)

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

Copy and paste ABAP code example for UPG_GET_SINGLE_COMPREL 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.

ABAP code using 7.40 inline data declarations to call FM UPG_GET_SINGLE_COMPREL

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