SAP ISP_BP_HIERARCHY_PATH_READ Function Module for IS-M/AM: BP Hierarchy: Read Paths
ISP_BP_HIERARCHY_PATH_READ is a standard isp bp hierarchy path read SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for IS-M/AM: BP Hierarchy: Read Paths 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 isp bp hierarchy path read FM, simply by entering the name ISP_BP_HIERARCHY_PATH_READ into the relevant SAP transaction such as SE37 or SE38.
Function Group: JJG3
Program Name: SAPLJJG3
Main Program: SAPLJJG3
Appliation area: J
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISP_BP_HIERARCHY_PATH_READ 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 'ISP_BP_HIERARCHY_PATH_READ'"IS-M/AM: BP Hierarchy: Read Paths.
EXPORTING
DATE_FROM = "
DATE_TO = "
GPNR_FROM = "Start Node
IN_HITYP = "
* GPNR_TO = ' ' "
* READ_DIRECTION = 'U' "
* IN_TREE = 0 "
TABLES
* ALL_ELEMENTS = "
PATHDIR = "
PATHS = "
EXCEPTIONS
NO_RELATIONS = 1 WRONG_DATE = 2
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLJJG3_001 IS-M/AM: BP Hierarchy Output Control
EXIT_SAPLJJG3_002 IS-M/AM: Output: Fill Communication Structure in BP Hierarchy
IMPORTING Parameters details for ISP_BP_HIERARCHY_PATH_READ
DATE_FROM -
Data type: JJTKS-GUELTIGABOptional: No
Call by Reference: No ( called with pass by value option)
DATE_TO -
Data type: JJTKS-GUELTIGBISOptional: No
Call by Reference: No ( called with pass by value option)
GPNR_FROM - Start Node
Data type: JGTGPNR-GPNROptional: No
Call by Reference: No ( called with pass by value option)
IN_HITYP -
Data type: TJJ69-HITYPOptional: No
Call by Reference: No ( called with pass by value option)
GPNR_TO -
Data type: JGTGPNR-GPNRDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
READ_DIRECTION -
Data type:Default: 'U'
Optional: Yes
Call by Reference: No ( called with pass by value option)
IN_TREE -
Data type: RJJY001-TREEOptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ISP_BP_HIERARCHY_PATH_READ
ALL_ELEMENTS -
Data type: RJJLG33Optional: Yes
Call by Reference: No ( called with pass by value option)
PATHDIR -
Data type: RJJLG32Optional: No
Call by Reference: No ( called with pass by value option)
PATHS -
Data type: RJJLG31Optional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_RELATIONS -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
WRONG_DATE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ISP_BP_HIERARCHY_PATH_READ 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_date_from | TYPE JJTKS-GUELTIGAB, " | |||
| lt_all_elements | TYPE STANDARD TABLE OF RJJLG33, " | |||
| lv_no_relations | TYPE RJJLG33, " | |||
| lv_date_to | TYPE JJTKS-GUELTIGBIS, " | |||
| lt_pathdir | TYPE STANDARD TABLE OF RJJLG32, " | |||
| lv_wrong_date | TYPE RJJLG32, " | |||
| lt_paths | TYPE STANDARD TABLE OF RJJLG31, " | |||
| lv_gpnr_from | TYPE JGTGPNR-GPNR, " | |||
| lv_in_hityp | TYPE TJJ69-HITYP, " | |||
| lv_gpnr_to | TYPE JGTGPNR-GPNR, " SPACE | |||
| lv_read_direction | TYPE JGTGPNR, " 'U' | |||
| lv_in_tree | TYPE RJJY001-TREE. " 0 |
|   CALL FUNCTION 'ISP_BP_HIERARCHY_PATH_READ' "IS-M/AM: BP Hierarchy: Read Paths |
| EXPORTING | ||
| DATE_FROM | = lv_date_from | |
| DATE_TO | = lv_date_to | |
| GPNR_FROM | = lv_gpnr_from | |
| IN_HITYP | = lv_in_hityp | |
| GPNR_TO | = lv_gpnr_to | |
| READ_DIRECTION | = lv_read_direction | |
| IN_TREE | = lv_in_tree | |
| TABLES | ||
| ALL_ELEMENTS | = lt_all_elements | |
| PATHDIR | = lt_pathdir | |
| PATHS | = lt_paths | |
| EXCEPTIONS | ||
| NO_RELATIONS = 1 | ||
| WRONG_DATE = 2 | ||
| . " ISP_BP_HIERARCHY_PATH_READ | ||
ABAP code using 7.40 inline data declarations to call FM ISP_BP_HIERARCHY_PATH_READ
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 GUELTIGAB FROM JJTKS INTO @DATA(ld_date_from). | ||||
| "SELECT single GUELTIGBIS FROM JJTKS INTO @DATA(ld_date_to). | ||||
| "SELECT single GPNR FROM JGTGPNR INTO @DATA(ld_gpnr_from). | ||||
| "SELECT single HITYP FROM TJJ69 INTO @DATA(ld_in_hityp). | ||||
| "SELECT single GPNR FROM JGTGPNR INTO @DATA(ld_gpnr_to). | ||||
| DATA(ld_gpnr_to) | = ' '. | |||
| DATA(ld_read_direction) | = 'U'. | |||
| "SELECT single TREE FROM RJJY001 INTO @DATA(ld_in_tree). | ||||
Search for further information about these or an SAP related objects