SAP MD_LOESCHEN_PLANAUFTRAG Function Module for NOTRANSL: Loeschen eines Planauftrages durch Umsetzung in einen Fertigungs









MD_LOESCHEN_PLANAUFTRAG is a standard md loeschen planauftrag 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: Loeschen eines Planauftrages durch Umsetzung in einen Fertigungs 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 loeschen planauftrag FM, simply by entering the name MD_LOESCHEN_PLANAUFTRAG into the relevant SAP transaction such as SE37 or SE38.

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



Function MD_LOESCHEN_PLANAUFTRAG 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_LOESCHEN_PLANAUFTRAG'"NOTRANSL: Loeschen eines Planauftrages durch Umsetzung in einen Fertigungs
EXPORTING
* APO_PROC = "Processing Indicator for BAPI Call

TABLES
IPLAF = "Planned Order

EXCEPTIONS
PLAF_LOCKED = 1 PLAF_CHANGED = 2
.



IMPORTING Parameters details for MD_LOESCHEN_PLANAUFTRAG

APO_PROC - Processing Indicator for BAPI Call

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

TABLES Parameters details for MD_LOESCHEN_PLANAUFTRAG

IPLAF - Planned Order

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

EXCEPTIONS details

PLAF_LOCKED -

Data type:
Optional: No
Call by Reference: Yes

PLAF_CHANGED -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for MD_LOESCHEN_PLANAUFTRAG 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_iplaf  TYPE STANDARD TABLE OF PLAF, "   
lv_apo_proc  TYPE CM61O-BAPCO, "   
lv_plaf_locked  TYPE CM61O, "   
lv_plaf_changed  TYPE CM61O. "   

  CALL FUNCTION 'MD_LOESCHEN_PLANAUFTRAG'  "NOTRANSL: Loeschen eines Planauftrages durch Umsetzung in einen Fertigungs
    EXPORTING
         APO_PROC = lv_apo_proc
    TABLES
         IPLAF = lt_iplaf
    EXCEPTIONS
        PLAF_LOCKED = 1
        PLAF_CHANGED = 2
. " MD_LOESCHEN_PLANAUFTRAG




ABAP code using 7.40 inline data declarations to call FM MD_LOESCHEN_PLANAUFTRAG

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 BAPCO FROM CM61O INTO @DATA(ld_apo_proc).
 
 
 


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!