SAP RM_AGGREGATE_REQUIREMENTS Function Module for NOTRANSL: Aggregation von Sekundärbedarfen in zentraler Tabelle P_AGREQ
RM_AGGREGATE_REQUIREMENTS is a standard rm aggregate requirements 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: Aggregation von Sekundärbedarfen in zentraler Tabelle P_AGREQ 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 rm aggregate requirements FM, simply by entering the name RM_AGGREGATE_REQUIREMENTS into the relevant SAP transaction such as SE37 or SE38.
Function Group: RMAG
Program Name: SAPLRMAG
Main Program: SAPLRMAG
Appliation area: C
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RM_AGGREGATE_REQUIREMENTS 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 'RM_AGGREGATE_REQUIREMENTS'"NOTRANSL: Aggregation von Sekundärbedarfen in zentraler Tabelle P_AGREQ.
EXPORTING
P_PLAF = "Planned Order
* P_IGDKZ = "New Input Values
TABLES
P_MDPMX = "View of Material Components in the Planned Order
P_AGREQ = "
IMPORTING Parameters details for RM_AGGREGATE_REQUIREMENTS
P_PLAF - Planned Order
Data type: PLAFOptional: No
Call by Reference: No ( called with pass by value option)
P_IGDKZ - New Input Values
Data type: AMRPC-FLG01Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for RM_AGGREGATE_REQUIREMENTS
P_MDPMX - View of Material Components in the Planned Order
Data type: MDPMOptional: No
Call by Reference: No ( called with pass by value option)
P_AGREQ -
Data type: BARM_TYPE_TAB_AGREQOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RM_AGGREGATE_REQUIREMENTS 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_p_plaf | TYPE PLAF, " | |||
| lt_p_mdpmx | TYPE STANDARD TABLE OF MDPM, " | |||
| lt_p_agreq | TYPE STANDARD TABLE OF BARM_TYPE_TAB_AGREQ, " | |||
| lv_p_igdkz | TYPE AMRPC-FLG01. " |
|   CALL FUNCTION 'RM_AGGREGATE_REQUIREMENTS' "NOTRANSL: Aggregation von Sekundärbedarfen in zentraler Tabelle P_AGREQ |
| EXPORTING | ||
| P_PLAF | = lv_p_plaf | |
| P_IGDKZ | = lv_p_igdkz | |
| TABLES | ||
| P_MDPMX | = lt_p_mdpmx | |
| P_AGREQ | = lt_p_agreq | |
| . " RM_AGGREGATE_REQUIREMENTS | ||
ABAP code using 7.40 inline data declarations to call FM RM_AGGREGATE_REQUIREMENTS
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 FLG01 FROM AMRPC INTO @DATA(ld_p_igdkz). | ||||
Search for further information about these or an SAP related objects