SAP MD_POST_PLANNED_ORDERS Function Module for NOTRANSL: Planauftraege verbuchen









MD_POST_PLANNED_ORDERS is a standard md post planned orders 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: Planauftraege verbuchen 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 post planned orders FM, simply by entering the name MD_POST_PLANNED_ORDERS 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_POST_PLANNED_ORDERS 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_POST_PLANNED_ORDERS'"NOTRANSL: Planauftraege verbuchen
EXPORTING
* NCOMM = ' ' "
* KDAUF = ' ' "
* MONTX = ' ' "
* NO_UPD_TASK = ' ' "

TABLES
* CUOBX = "
* TECHS = "Effectivity - technical status (TECHS) - temp. / new
.



IMPORTING Parameters details for MD_POST_PLANNED_ORDERS

NCOMM -

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

KDAUF -

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

MONTX -

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

NO_UPD_TASK -

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

TABLES Parameters details for MD_POST_PLANNED_ORDERS

CUOBX -

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

TECHS - Effectivity - technical status (TECHS) - temp. / new

Data type: TECHSNR
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for MD_POST_PLANNED_ORDERS 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:
lt_cuobx  TYPE STANDARD TABLE OF CONFNR, "   
lv_ncomm  TYPE AF61O-FLG01, "   SPACE
lv_kdauf  TYPE PLAF-KDAUF, "   SPACE
lt_techs  TYPE STANDARD TABLE OF TECHSNR, "   
lv_montx  TYPE AF61O-FLG01, "   SPACE
lv_no_upd_task  TYPE AF61O-FLG01. "   SPACE

  CALL FUNCTION 'MD_POST_PLANNED_ORDERS'  "NOTRANSL: Planauftraege verbuchen
    EXPORTING
         NCOMM = lv_ncomm
         KDAUF = lv_kdauf
         MONTX = lv_montx
         NO_UPD_TASK = lv_no_upd_task
    TABLES
         CUOBX = lt_cuobx
         TECHS = lt_techs
. " MD_POST_PLANNED_ORDERS




ABAP code using 7.40 inline data declarations to call FM MD_POST_PLANNED_ORDERS

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 AF61O INTO @DATA(ld_ncomm).
DATA(ld_ncomm) = ' '.
 
"SELECT single KDAUF FROM PLAF INTO @DATA(ld_kdauf).
DATA(ld_kdauf) = ' '.
 
 
"SELECT single FLG01 FROM AF61O INTO @DATA(ld_montx).
DATA(ld_montx) = ' '.
 
"SELECT single FLG01 FROM AF61O INTO @DATA(ld_no_upd_task).
DATA(ld_no_upd_task) = ' '.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!