SAP BBP_PDH_RELEASE_GET Function Module for Liefert EBP-Release

Search SAP Function Modules

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

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

Function BBP_PDH_RELEASE_GET 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 'BBP_PDH_RELEASE_GET'"Liefert EBP-Release
  EXPORTING
*  IV_COMPONENT = 'SAP_BASIS' "Softwarekomponente

 IMPORTING
   EV_BBP_RELEASE =  "BBP R/3 Release
   EV_BBP_EXTRELEASE =  "BBP Patch-Level einer Softwarekomponente
   EV_BASIS_RELEASE =  "Basis R/3 Release
   EV_BASIS_EXTRELEASE =  "Basis Patch-Level einer Softwarekomponente
   EV_ABA_RELEASE =  "ABA R/3 Release
   EV_ABA_EXTRELEASE =  "ABA Patch-Level einer Softwarekomponente
   EV_VERSION =  "Releasestände der im System vorhandenen Softwarekomponenten
   EV_BASISSTATE =  "Status des Basisreleases

EXCEPTIONS
   NO_RELEASE_FOUND = 1    COMPONENT_RELEASE_NOT_FOUND = 2    INVALID_COMPONENT_NAME = 3 

.

IMPORTING Parameters details for BBP_PDH_RELEASE_GET

IV_COMPONENT - Softwarekomponente

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

EXPORTING Parameters details for BBP_PDH_RELEASE_GET

EV_BBP_RELEASE - BBP R/3 Release

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

EV_BBP_EXTRELEASE - BBP Patch-Level einer Softwarekomponente

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

EV_BASIS_RELEASE - Basis R/3 Release

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

EV_BASIS_EXTRELEASE - Basis Patch-Level einer Softwarekomponente

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

EV_ABA_RELEASE - ABA R/3 Release

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

EV_ABA_EXTRELEASE - ABA Patch-Level einer Softwarekomponente

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

EV_VERSION - Releasestände der im System vorhandenen Softwarekomponenten

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

EV_BASISSTATE - Status des Basisreleases

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

EXCEPTIONS details

NO_RELEASE_FOUND - Fuer keine komponente wurde ein Release gefunden

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

COMPONENT_RELEASE_NOT_FOUND - Release fuer IV_COMPONENT wurde nicht gefunden

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

INVALID_COMPONENT_NAME - Komponentenname ungueltig (z.B. '*')

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

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

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