SAP MD_PLDORD_DELETE_BAPI Function Module for NOTRANSL: BAPI: Löschen eines einzelnen Planauftrags
MD_PLDORD_DELETE_BAPI is a standard md pldord delete bapi 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: BAPI: Löschen eines einzelnen Planauftrags 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 pldord delete bapi FM, simply by entering the name MD_PLDORD_DELETE_BAPI into the relevant SAP transaction such as SE37 or SE38.
Function Group: M61O
Program Name: SAPLM61O
Main Program: SAPLM61O
Appliation area: C
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function MD_PLDORD_DELETE_BAPI 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_PLDORD_DELETE_BAPI'"NOTRANSL: BAPI: Löschen eines einzelnen Planauftrags.
EXPORTING
IV_PLNUM = "Planned Order Number
* BAPCO = "
* USE_COLLECTIVE_UPDATE = ' ' "Checkbox
* LAST_ORDER = ' ' "Checkbox
EXCEPTIONS
PLANNED_ORDER_DOESNOT_EXIST = 1 ENTRY_NOT_MADE = 2 FAILURE_IN_READING_PLANT = 3 NO_AUTHORITY = 4 ERROR_CALLING_FUNCTION = 5 CHANGES_NOT_ALLOWED = 6
IMPORTING Parameters details for MD_PLDORD_DELETE_BAPI
IV_PLNUM - Planned Order Number
Data type: PLAF-PLNUMOptional: No
Call by Reference: No ( called with pass by value option)
BAPCO -
Data type: CM61O-BAPCOOptional: Yes
Call by Reference: No ( called with pass by value option)
USE_COLLECTIVE_UPDATE - Checkbox
Data type: CM61O-COLUPDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
LAST_ORDER - Checkbox
Data type: CM61O-UPDATDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
PLANNED_ORDER_DOESNOT_EXIST - Planned order does not exist
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ENTRY_NOT_MADE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
FAILURE_IN_READING_PLANT -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_AUTHORITY - Error during authorization check
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ERROR_CALLING_FUNCTION - Error during function module call
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
CHANGES_NOT_ALLOWED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for MD_PLDORD_DELETE_BAPI 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: | ||||
| lv_iv_plnum | TYPE PLAF-PLNUM, " | |||
| lv_planned_order_doesnot_exist | TYPE PLAF, " | |||
| lv_bapco | TYPE CM61O-BAPCO, " | |||
| lv_entry_not_made | TYPE CM61O, " | |||
| lv_use_collective_update | TYPE CM61O-COLUP, " ' ' | |||
| lv_failure_in_reading_plant | TYPE CM61O, " | |||
| lv_last_order | TYPE CM61O-UPDAT, " ' ' | |||
| lv_no_authority | TYPE CM61O, " | |||
| lv_error_calling_function | TYPE CM61O, " | |||
| lv_changes_not_allowed | TYPE CM61O. " |
|   CALL FUNCTION 'MD_PLDORD_DELETE_BAPI' "NOTRANSL: BAPI: Löschen eines einzelnen Planauftrags |
| EXPORTING | ||
| IV_PLNUM | = lv_iv_plnum | |
| BAPCO | = lv_bapco | |
| USE_COLLECTIVE_UPDATE | = lv_use_collective_update | |
| LAST_ORDER | = lv_last_order | |
| EXCEPTIONS | ||
| PLANNED_ORDER_DOESNOT_EXIST = 1 | ||
| ENTRY_NOT_MADE = 2 | ||
| FAILURE_IN_READING_PLANT = 3 | ||
| NO_AUTHORITY = 4 | ||
| ERROR_CALLING_FUNCTION = 5 | ||
| CHANGES_NOT_ALLOWED = 6 | ||
| . " MD_PLDORD_DELETE_BAPI | ||
ABAP code using 7.40 inline data declarations to call FM MD_PLDORD_DELETE_BAPI
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 PLNUM FROM PLAF INTO @DATA(ld_iv_plnum). | ||||
| "SELECT single BAPCO FROM CM61O INTO @DATA(ld_bapco). | ||||
| "SELECT single COLUP FROM CM61O INTO @DATA(ld_use_collective_update). | ||||
| DATA(ld_use_collective_update) | = ' '. | |||
| "SELECT single UPDAT FROM CM61O INTO @DATA(ld_last_order). | ||||
| DATA(ld_last_order) | = ' '. | |||
Search for further information about these or an SAP related objects