SAP MAP2I_BAPIQPGR_QPGT_TO_QPGT Function Module for NOTRANSL: bapiqpgr_qpgt -> qpgt
MAP2I_BAPIQPGR_QPGT_TO_QPGT is a standard map2i bapiqpgr qpgt to qpgt 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: bapiqpgr_qpgt -> qpgt 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 map2i bapiqpgr qpgt to qpgt FM, simply by entering the name MAP2I_BAPIQPGR_QPGT_TO_QPGT into the relevant SAP transaction such as SE37 or SE38.
Function Group: QPGR
Program Name: SAPLQPGR
Main Program: SAPLQPGR
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
![](https://www.se80.co.uk/training-education/wp-content/uploads/2019/07/normal-function-module.png)
Function MAP2I_BAPIQPGR_QPGT_TO_QPGT 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 'MAP2I_BAPIQPGR_QPGT_TO_QPGT'"NOTRANSL: bapiqpgr_qpgt -> qpgt.
EXPORTING
BAPIQPGR_QPGT = "
CHANGING
QPGT = "
EXCEPTIONS
ERROR_CONVERTING_ISO_CODE = 1
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLQPGR_021 Customizing Exit Extension Parameters ALE Interface for Code Groups
EXIT_SAPLQPGR_022 Customizing Exit Extension Parameters ALE Interface for Code Groups
IMPORTING Parameters details for MAP2I_BAPIQPGR_QPGT_TO_QPGT
BAPIQPGR_QPGT -
Data type: BAPIQPGR_QPGTOptional: No
Call by Reference: Yes
CHANGING Parameters details for MAP2I_BAPIQPGR_QPGT_TO_QPGT
QPGT -
Data type: QPGTOptional: No
Call by Reference: Yes
EXCEPTIONS details
ERROR_CONVERTING_ISO_CODE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for MAP2I_BAPIQPGR_QPGT_TO_QPGT 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_qpgt | TYPE QPGT, " | |||
lv_bapiqpgr_qpgt | TYPE BAPIQPGR_QPGT, " | |||
lv_error_converting_iso_code | TYPE BAPIQPGR_QPGT. " |
  CALL FUNCTION 'MAP2I_BAPIQPGR_QPGT_TO_QPGT' "NOTRANSL: bapiqpgr_qpgt -> qpgt |
EXPORTING | ||
BAPIQPGR_QPGT | = lv_bapiqpgr_qpgt | |
CHANGING | ||
QPGT | = lv_qpgt | |
EXCEPTIONS | ||
ERROR_CONVERTING_ISO_CODE = 1 | ||
. " MAP2I_BAPIQPGR_QPGT_TO_QPGT |
ABAP code using 7.40 inline data declarations to call FM MAP2I_BAPIQPGR_QPGT_TO_QPGT
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