SAP MPOP_ARRAY_UPDATE Function Module for NOTRANSL: Fortschreiben der Prognose-Daten vom Puffer in die Datenbank
MPOP_ARRAY_UPDATE is a standard mpop array update 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: Fortschreiben der Prognose-Daten vom Puffer in die Datenbank 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 mpop array update FM, simply by entering the name MPOP_ARRAY_UPDATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: MG32
Program Name: SAPLMG32
Main Program: SAPLMG32
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function MPOP_ARRAY_UPDATE 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 'MPOP_ARRAY_UPDATE'"NOTRANSL: Fortschreiben der Prognose-Daten vom Puffer in die Datenbank.
EXPORTING
* FLG_AEN_KNOWN = ' ' "Indicator: Changes Already Determined
IMPORTING
FLGAEN = "Change Flag (U/I/X)
EXCEPTIONS
MPOP_UPDATE_ERROR = 1 MPOP_INSERT_ERROR = 2
IMPORTING Parameters details for MPOP_ARRAY_UPDATE
FLG_AEN_KNOWN - Indicator: Changes Already Determined
Data type: SY-DATARDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for MPOP_ARRAY_UPDATE
FLGAEN - Change Flag (U/I/X)
Data type: SY-DATAROptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
MPOP_UPDATE_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
MPOP_INSERT_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for MPOP_ARRAY_UPDATE 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_flgaen | TYPE SY-DATAR, " | |||
lv_flg_aen_known | TYPE SY-DATAR, " ' ' | |||
lv_mpop_update_error | TYPE SY, " | |||
lv_mpop_insert_error | TYPE SY. " |
  CALL FUNCTION 'MPOP_ARRAY_UPDATE' "NOTRANSL: Fortschreiben der Prognose-Daten vom Puffer in die Datenbank |
EXPORTING | ||
FLG_AEN_KNOWN | = lv_flg_aen_known | |
IMPORTING | ||
FLGAEN | = lv_flgaen | |
EXCEPTIONS | ||
MPOP_UPDATE_ERROR = 1 | ||
MPOP_INSERT_ERROR = 2 | ||
. " MPOP_ARRAY_UPDATE |
ABAP code using 7.40 inline data declarations to call FM MPOP_ARRAY_UPDATE
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."SELECT single DATAR FROM SY INTO @DATA(ld_flgaen). | ||||
"SELECT single DATAR FROM SY INTO @DATA(ld_flg_aen_known). | ||||
DATA(ld_flg_aen_known) | = ' '. | |||
Search for further information about these or an SAP related objects