SAP REQUIREMENTS_MAINTAIN Function Module for NOTRANSL: Pflege von mehreren Planprimärbedarfen Batch/Dialog

Search SAP Function Modules

REQUIREMENTS_MAINTAIN is a standard requirements maintain 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: Pflege von mehreren Planprimärbedarfen Batch/Dialog 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 requirements maintain FM, simply by entering the name REQUIREMENTS_MAINTAIN into the relevant SAP transaction such as SE37 or SE38.

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

Function REQUIREMENTS_MAINTAIN 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_MAINTAIN'"NOTRANSL: Pflege von mehreren Planprimärbedarfen Batch/Dialog
  EXPORTING
*  ECM60R = ' ' "Common work area for planned indep. requirements functions
*  ECM60A = ' ' "Structure for planned independent requirements display
*  EPRASTA =  "Period split

TABLES
   EPBPT =  "Table of ind. requirements item data
*  EPBET =  "Table for splitting data for ind. reequirements
*  EPBCH =  "Direct input for characteristic values in demand management
*  IPROTO =  "Internal structure for collecting messages (indep reqmts)
*  ITEM_OUT =  "Table of ind. requirements item data
*  SCHEDULE_OUT =  "Table for splitting data for ind. reequirements

EXCEPTIONS
   ERROR = 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_SAPLM60E_001 User Exit for Planned Independent Requirements Management
EXIT_SAPLM60E_002 USER-EXIT at End of Planned Independent Requirement Maintenance

IMPORTING Parameters details for REQUIREMENTS_MAINTAIN

ECM60R - Common work area for planned indep. requirements functions

Data type: CM60R
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

ECM60A - Structure for planned independent requirements display

Data type: CM60A
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EPRASTA - Period split

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

TABLES Parameters details for REQUIREMENTS_MAINTAIN

EPBPT - Table of ind. requirements item data

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

EPBET - Table for splitting data for ind. reequirements

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

EPBCH - Direct input for characteristic values in demand management

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

IPROTO - Internal structure for collecting messages (indep reqmts)

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

ITEM_OUT - Table of ind. requirements item data

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

SCHEDULE_OUT - Table for splitting data for ind. reequirements

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

EXCEPTIONS details

ERROR -

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

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

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