SAP J_7L_SUPPLIER_HIERARCHY_PATH Function Module for NOTRANSL: REA Ermitteln Lieferantenhierachie-Pfad









J_7L_SUPPLIER_HIERARCHY_PATH is a standard j 7l supplier hierarchy path SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: REA Ermitteln Lieferantenhierachie-Pfad 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 j 7l supplier hierarchy path FM, simply by entering the name J_7L_SUPPLIER_HIERARCHY_PATH into the relevant SAP transaction such as SE37 or SE38.

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



Function J_7L_SUPPLIER_HIERARCHY_PATH 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 'J_7L_SUPPLIER_HIERARCHY_PATH'"NOTRANSL: REA Ermitteln Lieferantenhierachie-Pfad
  EXPORTING
   I_HITYP =  "Hierarchy category: vendor hierarchy
   I_LIFNR =  "Account Number of Vendor
   I_EKORG =  "Purchasing Organization
*  I_DATAB = '00000000' "Valid-From Date
*  I_DATBI = '99991231' "Valid-To Date
   I_PARVW =  "Partner Function
*  I_DATUM = SY-DATUM "Date

 IMPORTING
   E_DATAB_MAX =  "Valid-From Date
   E_DATBI_MIN =  "Valid-To Date

TABLES
   T_I_HPATH =  "REA: Hiearchy Path Vendor Hierarchy for Splitting

EXCEPTIONS
   HITYP_NOT_EXIST = 1    NODE_NOT_EXIST = 2    PARVW_NOT_EXIST = 3
.



IMPORTING Parameters details for J_7L_SUPPLIER_HIERARCHY_PATH

I_HITYP - Hierarchy category: vendor hierarchy

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

I_LIFNR - Account Number of Vendor

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

I_EKORG - Purchasing Organization

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

I_DATAB - Valid-From Date

Data type: DATAB
Default: '00000000'
Optional: No
Call by Reference: Yes

I_DATBI - Valid-To Date

Data type: DATBI
Default: '99991231'
Optional: No
Call by Reference: Yes

I_PARVW - Partner Function

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

I_DATUM - Date

Data type: DATUM
Default: SY-DATUM
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for J_7L_SUPPLIER_HIERARCHY_PATH

E_DATAB_MAX - Valid-From Date

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

E_DATBI_MIN - Valid-To Date

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

TABLES Parameters details for J_7L_SUPPLIER_HIERARCHY_PATH

T_I_HPATH - REA: Hiearchy Path Vendor Hierarchy for Splitting

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

EXCEPTIONS details

HITYP_NOT_EXIST -

Data type:
Optional: No
Call by Reference: Yes

NODE_NOT_EXIST -

Data type:
Optional: No
Call by Reference: Yes

PARVW_NOT_EXIST -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for J_7L_SUPPLIER_HIERARCHY_PATH 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_i_hityp  TYPE HITYP_LH, "   
lt_t_i_hpath  TYPE STANDARD TABLE OF J_7LHPATH_LH, "   
lv_e_datab_max  TYPE DATAB, "   
lv_hityp_not_exist  TYPE DATAB, "   
lv_i_lifnr  TYPE LIFNR, "   
lv_e_datbi_min  TYPE DATBI, "   
lv_node_not_exist  TYPE DATBI, "   
lv_i_ekorg  TYPE EKORG, "   
lv_parvw_not_exist  TYPE EKORG, "   
lv_i_datab  TYPE DATAB, "   '00000000'
lv_i_datbi  TYPE DATBI, "   '99991231'
lv_i_parvw  TYPE PARVW, "   
lv_i_datum  TYPE DATUM. "   SY-DATUM

  CALL FUNCTION 'J_7L_SUPPLIER_HIERARCHY_PATH'  "NOTRANSL: REA Ermitteln Lieferantenhierachie-Pfad
    EXPORTING
         I_HITYP = lv_i_hityp
         I_LIFNR = lv_i_lifnr
         I_EKORG = lv_i_ekorg
         I_DATAB = lv_i_datab
         I_DATBI = lv_i_datbi
         I_PARVW = lv_i_parvw
         I_DATUM = lv_i_datum
    IMPORTING
         E_DATAB_MAX = lv_e_datab_max
         E_DATBI_MIN = lv_e_datbi_min
    TABLES
         T_I_HPATH = lt_t_i_hpath
    EXCEPTIONS
        HITYP_NOT_EXIST = 1
        NODE_NOT_EXIST = 2
        PARVW_NOT_EXIST = 3
. " J_7L_SUPPLIER_HIERARCHY_PATH




ABAP code using 7.40 inline data declarations to call FM J_7L_SUPPLIER_HIERARCHY_PATH

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.

 
 
 
 
 
 
 
 
 
DATA(ld_i_datab) = '00000000'.
 
DATA(ld_i_datbi) = '99991231'.
 
 
DATA(ld_i_datum) = SY-DATUM.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!