SAP PVSU2_MAP_CHANGE Function Module for NOTRANSL: liest map Eintrag









PVSU2_MAP_CHANGE is a standard pvsu2 map 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 NOTRANSL: liest map Eintrag 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 change FM, simply by entering the name PVSU2_MAP_CHANGE 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_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 'PVSU2_MAP_CHANGE'"NOTRANSL: liest map Eintrag
EXPORTING
* IM_MSG_HANDLING = 'A' "
IM_TREE_ID = "ALV Tree Control: Node Key
IM_NODE_KEY = "ALV Tree Control: Node Key
IM_MAP = "
IM_FLG_EXPANDER = "Single-Character Flag
IM_FLG_IS_NEW = "Single-Character Flag
IM_FLG_ISFOLDER = "Single-Character Flag
* IM_OBJ_ID_INT = "DE-EN-LANG-SWITCH-NO-TRANSLATION
* IM_PARENT_KEY = ' ' "ALV Tree Control: Node Key

EXCEPTIONS
NO_TREE_ID = 1 NO_NODE = 2 NOT_EXIST = 3
.



IMPORTING Parameters details for PVSU2_MAP_CHANGE

IM_MSG_HANDLING -

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

IM_TREE_ID - ALV Tree Control: Node Key

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_MAP -

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

IM_FLG_EXPANDER - Single-Character Flag

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

IM_FLG_IS_NEW - Single-Character Flag

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

IM_FLG_ISFOLDER - Single-Character Flag

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

IM_OBJ_ID_INT - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

IM_PARENT_KEY - ALV Tree Control: Node Key

Data type: LVC_NKEY
Default: ' '
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

NO_TREE_ID - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

NO_NODE - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

NOT_EXIST - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

Copy and paste ABAP code example for PVSU2_MAP_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_no_tree_id  TYPE STRING, "   
lv_im_msg_handling  TYPE PPET_MSG_OPT, "   'A'
lv_no_node  TYPE PPET_MSG_OPT, "   
lv_im_tree_id  TYPE PPET0_TREE_ID, "   
lv_not_exist  TYPE PPET0_TREE_ID, "   
lv_im_node_key  TYPE LVC_NKEY, "   
lv_im_map  TYPE PPET0_IPPE_MAP_TYPE, "   
lv_im_flg_expander  TYPE CHAR1, "   
lv_im_flg_is_new  TYPE CHAR1, "   
lv_im_flg_isfolder  TYPE CHAR1, "   
lv_im_obj_id_int  TYPE PPET0_OID_INT_TYPE, "   
lv_im_parent_key  TYPE LVC_NKEY. "   ' '

  CALL FUNCTION 'PVSU2_MAP_CHANGE'  "NOTRANSL: liest map Eintrag
    EXPORTING
         IM_MSG_HANDLING = lv_im_msg_handling
         IM_TREE_ID = lv_im_tree_id
         IM_NODE_KEY = lv_im_node_key
         IM_MAP = lv_im_map
         IM_FLG_EXPANDER = lv_im_flg_expander
         IM_FLG_IS_NEW = lv_im_flg_is_new
         IM_FLG_ISFOLDER = lv_im_flg_isfolder
         IM_OBJ_ID_INT = lv_im_obj_id_int
         IM_PARENT_KEY = lv_im_parent_key
    EXCEPTIONS
        NO_TREE_ID = 1
        NO_NODE = 2
        NOT_EXIST = 3
. " PVSU2_MAP_CHANGE




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

 
DATA(ld_im_msg_handling) = 'A'.
 
 
 
 
 
 
 
 
 
 
DATA(ld_im_parent_key) = ' '.
 


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!