SAP MD_PLANNED_ORDER_CHANGE Function Module for Change Planned Order

Search SAP Function Modules

MD_PLANNED_ORDER_CHANGE is a standard md planned order change SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Change Planned Order 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 md planned order change FM, simply by entering the name MD_PLANNED_ORDER_CHANGE into the relevant SAP transaction such as SE37 or SE38.

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

Function MD_PLANNED_ORDER_CHANGE 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 'MD_PLANNED_ORDER_CHANGE'"Change Planned Order
  EXPORTING
*  ECM61O =  "Common work area for planned order functions
   EPLAF =  "Planned Order
*  ECM61S =  "Processing planned orders: scheduling parameters (input)

 IMPORTING
   IPLAF =  "Planned Order
   ICM61O =  "Common work area for planned order functions
   ICM61T =  "Processing planned orders: scheduling return value (output)
   ISCHED =  "Checkbox
   IBOMCH =  "Checkbox

TABLES
*  CM61FX =  "Interface table for function codes

EXCEPTIONS
   LOCKED = 1    LOCKING_ERROR = 2 

.

IMPORTING Parameters details for MD_PLANNED_ORDER_CHANGE

ECM61O - Common work area for planned order functions

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

EPLAF - Planned Order

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

ECM61S - Processing planned orders: scheduling parameters (input)

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

EXPORTING Parameters details for MD_PLANNED_ORDER_CHANGE

IPLAF - Planned Order

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

ICM61O - Common work area for planned order functions

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

ICM61T - Processing planned orders: scheduling return value (output)

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

ISCHED - Checkbox

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

IBOMCH - Checkbox

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

TABLES Parameters details for MD_PLANNED_ORDER_CHANGE

CM61FX - Interface table for function codes

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

EXCEPTIONS details

LOCKED -

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

LOCKING_ERROR -

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

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

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