SAP PVSU2_MAP_GET_PATH Function Module for NOTRANSL: sucht Instanzen- bzw. Obj_id-Pfad nach oben

Search SAP Function Modules

PVSU2_MAP_GET_PATH is a standard pvsu2 map get 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: sucht Instanzen- bzw. Obj_id-Pfad nach oben 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 pvsu2 map get path FM, simply by entering the name PVSU2_MAP_GET_PATH into the relevant SAP transaction such as SE37 or SE38.

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

Function PVSU2_MAP_GET_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 'PVSU2_MAP_GET_PATH'"NOTRANSL: sucht Instanzen- bzw. Obj_id-Pfad nach oben
  EXPORTING
*  IM_MSG_HANDLING = 'A' "
   IM_TREE_ID =  "Identification of the ALV Tree on the iPPE User Interface
   IM_NODE_KEY =  "ALV Tree Control: Node Key
   IM_OTYPE =  "iPPE Object Type

 IMPORTING
   EX_INST_TAB =  "
   EX_PV_TAB =  "
   EX_OBJ_ID_TAB =  "
   EX_LEAF_INST_TAB =  "

EXCEPTIONS
   NODE_NOT_FOUND = 1    INVALID_OTYPE = 2    OBJ_ID_ERROR = 3    INST_ERROR = 4    DOC_ERROR = 5    ERROR = 6 

.

IMPORTING Parameters details for PVSU2_MAP_GET_PATH

IM_MSG_HANDLING -

Data type: PPET_MSG_OPT
Default: 'A'
Optional: Yes
Call by Reference: Yes

IM_TREE_ID - Identification of the ALV Tree on the iPPE User Interface

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

IM_NODE_KEY - ALV Tree Control: Node Key

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

IM_OTYPE - iPPE Object Type

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

EXPORTING Parameters details for PVSU2_MAP_GET_PATH

EX_INST_TAB -

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

EX_PV_TAB -

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

EX_OBJ_ID_TAB -

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

EX_LEAF_INST_TAB -

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

EXCEPTIONS details

NODE_NOT_FOUND - No Node

Data type:
Optional: No
Call by Reference: Yes

INVALID_OTYPE - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

OBJ_ID_ERROR - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

INST_ERROR - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

DOC_ERROR - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

ERROR - Error

Data type:
Optional: No
Call by Reference: Yes

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

ABAP code using 7.40 inline data declarations to call FM PVSU2_MAP_GET_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.

Search for further information about these or an SAP related objects