SAP PVSU2_MAP_ADD Function Module for NOTRANSL: legt map Eintrag an

Search SAP Function Modules

PVSU2_MAP_ADD is a standard pvsu2 map add 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: legt map Eintrag an 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 add FM, simply by entering the name PVSU2_MAP_ADD 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_ADD 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_ADD'"NOTRANSL: legt map Eintrag an
  EXPORTING
*  IM_MSG_HANDLING = 'A' "
   IM_MAP =  "
*  IM_PAR_OBJ_ID =  "ALV Tree Control: Node Key
   IM_OID_INT_TAB =  "
*  IM_EXOBJ_ID =  "Identification for External Objects
*  IM_QUANT =  "Quantity (in Component Variant)
*  IM_DMUCNT =  "Count parameters
*  IM_INSCNT =  "Count parameters

CHANGING
*  CH_OBJ_ID =  "ALV Tree Control: Node Key

EXCEPTIONS
   PARENT_NOT_FOUND = 1    ERROR = 2    OBJ_ID_NOT_ADDED = 3 

.

IMPORTING Parameters details for PVSU2_MAP_ADD

IM_MSG_HANDLING -

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

IM_MAP -

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

IM_PAR_OBJ_ID - ALV Tree Control: Node Key

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

IM_OID_INT_TAB -

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

IM_EXOBJ_ID - Identification for External Objects

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

IM_QUANT - Quantity (in Component Variant)

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

IM_DMUCNT - Count parameters

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

IM_INSCNT - Count parameters

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

CHANGING Parameters details for PVSU2_MAP_ADD

CH_OBJ_ID - ALV Tree Control: Node Key

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

EXCEPTIONS details

PARENT_NOT_FOUND - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

ERROR - Internal error

Data type:
Optional: No
Call by Reference: Yes

OBJ_ID_NOT_ADDED - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for PVSU2_MAP_ADD 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_ADD

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