SAP BAPI_DSOURCE_HIER_CHANGE Function Module for Change Hierarchy DataSource
BAPI_DSOURCE_HIER_CHANGE is a standard bapi dsource hier change SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Change Hierarchy DataSource 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 bapi dsource hier change FM, simply by entering the name BAPI_DSOURCE_HIER_CHANGE into the relevant SAP transaction such as SE37 or SE38.
Function Group: RSDS_BAPI
Program Name: SAPLRSDS_BAPI
Main Program: SAPLRSDS_BAPI
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:
Function BAPI_DSOURCE_HIER_CHANGE 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 'BAPI_DSOURCE_HIER_CHANGE'"Change Hierarchy DataSource.
EXPORTING
DATASOURCE = "DataSource
SOURCESYSTEM = "Source System
* TIMEDEPENDENCY = 'S' "Indicator for time dependence of hierarchies
* VERSIONS_ALLOWED = 'X' "Hierarchies can have several versions
* INTERVALS_ALLOWED = 'X' "Intervals permitted in hierarchy
* SIGNS_ALLOWED = 'X' "Reverse Sign for Hierarchy Nodes
* SORTED_HIERARCHY = 'X' "Hierarchy transfer with sorted node(s)
IMPORTING
RETURN = "Return Parameter(s)
IMPORTING Parameters details for BAPI_DSOURCE_HIER_CHANGE
DATASOURCE - DataSource
Data type: BAPIDSHEADER-DATASOURCEOptional: No
Call by Reference: No ( called with pass by value option)
SOURCESYSTEM - Source System
Data type: BAPIDSHEADER-SOURCESYSTEMOptional: No
Call by Reference: No ( called with pass by value option)
TIMEDEPENDENCY - Indicator for time dependence of hierarchies
Data type: BAPIDSHIER-TIMEDEPENDENCYDefault: 'S'
Optional: Yes
Call by Reference: No ( called with pass by value option)
VERSIONS_ALLOWED - Hierarchies can have several versions
Data type: BAPIDSHIER-VERSIONS_ALLOWEDDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
INTERVALS_ALLOWED - Intervals permitted in hierarchy
Data type: BAPIDSHIER-INTERVALS_ALLOWEDDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
SIGNS_ALLOWED - Reverse Sign for Hierarchy Nodes
Data type: BAPIDSHIER-SIGNS_ALLOWEDDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
SORTED_HIERARCHY - Hierarchy transfer with sorted node(s)
Data type: BAPIDSHIER-SORTED_HIERARCHYDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BAPI_DSOURCE_HIER_CHANGE
RETURN - Return Parameter(s)
Data type: BAPIRET2Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BAPI_DSOURCE_HIER_CHANGE 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_return | TYPE BAPIRET2, " | |||
| lv_datasource | TYPE BAPIDSHEADER-DATASOURCE, " | |||
| lv_sourcesystem | TYPE BAPIDSHEADER-SOURCESYSTEM, " | |||
| lv_timedependency | TYPE BAPIDSHIER-TIMEDEPENDENCY, " 'S' | |||
| lv_versions_allowed | TYPE BAPIDSHIER-VERSIONS_ALLOWED, " 'X' | |||
| lv_intervals_allowed | TYPE BAPIDSHIER-INTERVALS_ALLOWED, " 'X' | |||
| lv_signs_allowed | TYPE BAPIDSHIER-SIGNS_ALLOWED, " 'X' | |||
| lv_sorted_hierarchy | TYPE BAPIDSHIER-SORTED_HIERARCHY. " 'X' |
| CALL FUNCTION 'BAPI_DSOURCE_HIER_CHANGE' "Change Hierarchy DataSource |
| EXPORTING | ||
| DATASOURCE | = lv_datasource | |
| SOURCESYSTEM | = lv_sourcesystem | |
| TIMEDEPENDENCY | = lv_timedependency | |
| VERSIONS_ALLOWED | = lv_versions_allowed | |
| INTERVALS_ALLOWED | = lv_intervals_allowed | |
| SIGNS_ALLOWED | = lv_signs_allowed | |
| SORTED_HIERARCHY | = lv_sorted_hierarchy | |
| IMPORTING | ||
| RETURN | = lv_return | |
| . " BAPI_DSOURCE_HIER_CHANGE | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_DSOURCE_HIER_CHANGE
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 DATASOURCE FROM BAPIDSHEADER INTO @DATA(ld_datasource). | ||||
| "SELECT single SOURCESYSTEM FROM BAPIDSHEADER INTO @DATA(ld_sourcesystem). | ||||
| "SELECT single TIMEDEPENDENCY FROM BAPIDSHIER INTO @DATA(ld_timedependency). | ||||
| DATA(ld_timedependency) | = 'S'. | |||
| "SELECT single VERSIONS_ALLOWED FROM BAPIDSHIER INTO @DATA(ld_versions_allowed). | ||||
| DATA(ld_versions_allowed) | = 'X'. | |||
| "SELECT single INTERVALS_ALLOWED FROM BAPIDSHIER INTO @DATA(ld_intervals_allowed). | ||||
| DATA(ld_intervals_allowed) | = 'X'. | |||
| "SELECT single SIGNS_ALLOWED FROM BAPIDSHIER INTO @DATA(ld_signs_allowed). | ||||
| DATA(ld_signs_allowed) | = 'X'. | |||
| "SELECT single SORTED_HIERARCHY FROM BAPIDSHIER INTO @DATA(ld_sorted_hierarchy). | ||||
| DATA(ld_sorted_hierarchy) | = 'X'. | |||
Search for further information about these or an SAP related objects