SAP PVSU2_MAPTAB_READ_EXOBJ_ID Function Module for NOTRANSL: liest externes Objekt

Search SAP Function Modules

PVSU2_MAPTAB_READ_EXOBJ_ID is a standard pvsu2 maptab read exobj id 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 externes Objekt 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 maptab read exobj id FM, simply by entering the name PVSU2_MAPTAB_READ_EXOBJ_ID 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_MAPTAB_READ_EXOBJ_ID 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_MAPTAB_READ_EXOBJ_ID'"NOTRANSL: liest externes Objekt
  EXPORTING
   IM_MSG_OPT =  "
   IM_TREE_ID =  "Identification of the ALV Tree on the iPPE User Interface
   IM_OTYPE =  "iPPE Object Type
   IM_EXOBJ_ID =  "Identification for External Objects

CHANGING
   CH_MAP_EXT =  "

EXCEPTIONS
   INVALID_INPUT = 1 

.

IMPORTING Parameters details for PVSU2_MAPTAB_READ_EXOBJ_ID

IM_MSG_OPT -

Data type: PPET_MSG_OPT
Optional: No
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_OTYPE - iPPE Object Type

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

IM_EXOBJ_ID - Identification for External Objects

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

CHANGING Parameters details for PVSU2_MAPTAB_READ_EXOBJ_ID

CH_MAP_EXT -

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

EXCEPTIONS details

INVALID_INPUT - Invalid Entries

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for PVSU2_MAPTAB_READ_EXOBJ_ID 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_MAPTAB_READ_EXOBJ_ID

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