SAP REQUIREMENTS_AGGREGATION Function Module for

Search SAP Function Modules

REQUIREMENTS_AGGREGATION is a standard requirements aggregation SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 requirements aggregation FM, simply by entering the name REQUIREMENTS_AGGREGATION into the relevant SAP transaction such as SE37 or SE38.

Function Group: M60S
Program Name: SAPLM60S
Main Program: SAPLM60S
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function REQUIREMENTS_AGGREGATION 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 'REQUIREMENTS_AGGREGATION'"
  EXPORTING
   IWERKS =  "Plant
   IAGGKZ =  "Date type (day, week, month, interval)
*  IMRPPP =  "PPC planning calendar
*  IPERIV =  "Fiscal Year Variant

TABLES
   IWPBEX =  "Indep. reqmts value table structure - see WPBET for FM
   AWPBET =  "Indep. reqmts value table structure - see WPBET for FM

EXCEPTIONS
   CALENDAR_ID_MISSING = 1    CALENDAR_NOT_FOUND = 2    DATE_AFTER_RANGE = 3    DATE_BEFORE_RANGE = 4    DATE_INVALID = 5    DATE_OPTION_INVALID = 6    T009B_NOT_FOUND = 7 

.

IMPORTING Parameters details for REQUIREMENTS_AGGREGATION

IWERKS - Plant

Data type: PBPT-WERKS
Optional: No
Call by Reference: No ( called with pass by value option)

IAGGKZ - Date type (day, week, month, interval)

Data type: HM60X-ENTLI
Optional: No
Call by Reference: No ( called with pass by value option)

IMRPPP - PPC planning calendar

Data type: T439I-MRPPP
Optional: Yes
Call by Reference: No ( called with pass by value option)

IPERIV - Fiscal Year Variant

Data type: PBPT-PERIV
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for REQUIREMENTS_AGGREGATION

IWPBEX - Indep. reqmts value table structure - see WPBET for FM

Data type: PBEW
Optional: No
Call by Reference: No ( called with pass by value option)

AWPBET - Indep. reqmts value table structure - see WPBET for FM

Data type: PBEW
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

CALENDAR_ID_MISSING -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

CALENDAR_NOT_FOUND -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

DATE_AFTER_RANGE -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

DATE_BEFORE_RANGE -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

DATE_INVALID -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

DATE_OPTION_INVALID -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

T009B_NOT_FOUND -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

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

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