|
Functionality
This method can be used to delete a planned order from the database. Itwill delete all corresponding data such as capacity and components whenit is executed.
To help you understand how the method can be used, test transaction"MDBA" is available. It has integrated all 6 planned order methods intoa transaction to deal with planned orders. For more information, pleaserefer to the program documentation on this transaction. The name of theprogram is 'MDBAPI01'. Example Notes Authorization checks:
The following authorization objects are checked with the activity V(Change):
- M_PLAF_ORG
- M_LFPL_ORG
Further methods:
- CommitWork
- RollbackWork
When you have decided to save the changes (deletion, in this case) tothe database, you must call the methodCommitWork. If you decide not to savethe data in the database, you can call the methodRollbackWork instead.
You can find more information in the parameter documentation of theparameters below.Confirmation:
Messages are received back in the parameter 'Return'. You can findreturn values and their meaning in this parameter documentation. Description
INCLUDE BAPI_TABLE Value range Error messages Type ID Number Message
E MD 652 Planned order number has notbeen entered
E 61 003 Planned order & does not exist
E 61 400 No authorization for & inplant & and MRP controller &
E MD 130 You do not have thenecess.authorization for this function (see long txt)
E 61 047 Planned order cannot bechanged manually in collective orderSuccess messages
S 61 012 Planned order & will be deleted
Description
You can find information on the meaning of the planned order number inthe data element documentation:
planned order number
INCLUDE BAPI_KEYFIELDDefault Description
Indicator: Collective update of planning file entries during massprocessing of planned orders via BAPIs.
During mass processing of planned orders, you can execute a collectiveupdate of planning file entries. You can activate the collective updateby setting USE_COLL_UPDATE. However, you must ensure that theindicator LAST_ORDER is set for the last call of the BAPI methodDELETE. Only then does the system transfer all of the planningfile entries collected up to then to the database table.
For additional information, see the documentation on data elementBAPI: Collective Update of Planning File Entries
|