SAP DPR_BW_GET_VERSIONS Function Module for Represent Hierarchy from cProjects for Transfer to BW

Search SAP Function Modules

DPR_BW_GET_VERSIONS is a standard dpr bw get versions SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Represent Hierarchy from cProjects for Transfer to BW 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 dpr bw get versions FM, simply by entering the name DPR_BW_GET_VERSIONS into the relevant SAP transaction such as SE37 or SE38.

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

Function DPR_BW_GET_VERSIONS 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 'DPR_BW_GET_VERSIONS'"Represent Hierarchy from cProjects for Transfer to BW
  EXPORTING
   I_REQUNR =  "
*  I_CHABASNM =  "
*  I_MAXSIZE =  "
*  I_INITFLAG =  "
*  I_UPDMODE =  "
*  I_DATAPAKID =  "
*  I_S_TIMEINT =  "

 IMPORTING
   E_PACKAGES =  "

TABLES
*  I_T_SELECT =  "
*  I_T_FIELDS =  "
*  E_T_DPR_BW_VRSN_ATTR =  "Dev. Projects: Version Attributes
*  E_T_DPR_BW_TEXTS_VERSIONS =  "Dev. Projects: Version Texts

EXCEPTIONS
   NO_MORE_DATA = 1    ERROR_PASSED_TO_MESS_HANDLER = 2 

.

IMPORTING Parameters details for DPR_BW_GET_VERSIONS

I_REQUNR -

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

I_CHABASNM -

Data type: SBIWA_S_INTERFACE-CHABASNM
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_MAXSIZE -

Data type: SBIWA_S_INTERFACE-MAXSIZE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_INITFLAG -

Data type: SBIWA_S_INTERFACE-INITFLAG
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_UPDMODE -

Data type: SBIWA_S_INTERFACE-UPDMODE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_DATAPAKID -

Data type: SBIWA_S_INTERFACE-DATAPAKID
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_S_TIMEINT -

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

EXPORTING Parameters details for DPR_BW_GET_VERSIONS

E_PACKAGES -

Data type: SBIWA_FLAG
Optional: No
Call by Reference: Yes

TABLES Parameters details for DPR_BW_GET_VERSIONS

I_T_SELECT -

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

I_T_FIELDS -

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

E_T_DPR_BW_VRSN_ATTR - Dev. Projects: Version Attributes

Data type: DPR_BW_VRSN_ATTR
Optional: Yes
Call by Reference: Yes

E_T_DPR_BW_TEXTS_VERSIONS - Dev. Projects: Version Texts

Data type: DPR_BW_TEXTS_VERSIONS
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

NO_MORE_DATA - Data Was Completely Transferred

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

ERROR_PASSED_TO_MESS_HANDLER - Exit Due to Error; Message in Message Handler

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

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

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