SAP TR_GET_DLVUNIT_RELEASE Function Module for Get Software Component Release Using Package
TR_GET_DLVUNIT_RELEASE is a standard tr get dlvunit release SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get Software Component Release Using Package 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 tr get dlvunit release FM, simply by entering the name TR_GET_DLVUNIT_RELEASE into the relevant SAP transaction such as SE37 or SE38.
Function Group: SGTA
Program Name: SAPLSGTA
Main Program: SAPLSGTA
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function TR_GET_DLVUNIT_RELEASE 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 'TR_GET_DLVUNIT_RELEASE'"Get Software Component Release Using Package.
EXPORTING
* IS_DEVCLASS = "Package
* IS_DLVUNIT = "Software component
IMPORTING
ES_DLVUNIT = "Software component
ES_RELEASE = "R/3 Release
EXCEPTIONS
DEVCLASS_NOT_FOUND = 1 NO_INPUT = 2 TRLAYER_NOT_FOUND = 3 ADD_ON_NOT_EXIST = 4 DEV_REL_NOT_FOUND = 5 LOGICAL_DLVUNIT_NOT_FOUND = 6
IMPORTING Parameters details for TR_GET_DLVUNIT_RELEASE
IS_DEVCLASS - Package
Data type: TDEVC-DEVCLASSOptional: Yes
Call by Reference: No ( called with pass by value option)
IS_DLVUNIT - Software component
Data type: DLVUNITOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for TR_GET_DLVUNIT_RELEASE
ES_DLVUNIT - Software component
Data type: DLVUNITOptional: No
Call by Reference: No ( called with pass by value option)
ES_RELEASE - R/3 Release
Data type: SAPRELEASEOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
DEVCLASS_NOT_FOUND - Package not found
Data type:Optional: No
Call by Reference: Yes
NO_INPUT - No input given
Data type:Optional: No
Call by Reference: Yes
TRLAYER_NOT_FOUND - Transport layer not found
Data type:Optional: No
Call by Reference: Yes
ADD_ON_NOT_EXIST - Add-on not defined in system
Data type:Optional: No
Call by Reference: Yes
DEV_REL_NOT_FOUND - No entry found in connection table
Data type:Optional: No
Call by Reference: Yes
LOGICAL_DLVUNIT_NOT_FOUND - Cannot get logical DLVUNIT
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for TR_GET_DLVUNIT_RELEASE 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_es_dlvunit | TYPE DLVUNIT, " | |||
| lv_is_devclass | TYPE TDEVC-DEVCLASS, " | |||
| lv_devclass_not_found | TYPE TDEVC, " | |||
| lv_no_input | TYPE TDEVC, " | |||
| lv_es_release | TYPE SAPRELEASE, " | |||
| lv_is_dlvunit | TYPE DLVUNIT, " | |||
| lv_trlayer_not_found | TYPE DLVUNIT, " | |||
| lv_add_on_not_exist | TYPE DLVUNIT, " | |||
| lv_dev_rel_not_found | TYPE DLVUNIT, " | |||
| lv_logical_dlvunit_not_found | TYPE DLVUNIT. " |
|   CALL FUNCTION 'TR_GET_DLVUNIT_RELEASE' "Get Software Component Release Using Package |
| EXPORTING | ||
| IS_DEVCLASS | = lv_is_devclass | |
| IS_DLVUNIT | = lv_is_dlvunit | |
| IMPORTING | ||
| ES_DLVUNIT | = lv_es_dlvunit | |
| ES_RELEASE | = lv_es_release | |
| EXCEPTIONS | ||
| DEVCLASS_NOT_FOUND = 1 | ||
| NO_INPUT = 2 | ||
| TRLAYER_NOT_FOUND = 3 | ||
| ADD_ON_NOT_EXIST = 4 | ||
| DEV_REL_NOT_FOUND = 5 | ||
| LOGICAL_DLVUNIT_NOT_FOUND = 6 | ||
| . " TR_GET_DLVUNIT_RELEASE | ||
ABAP code using 7.40 inline data declarations to call FM TR_GET_DLVUNIT_RELEASE
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 DEVCLASS FROM TDEVC INTO @DATA(ld_is_devclass). | ||||
Search for further information about these or an SAP related objects