PlannedOrder

The business object Planned order is a request created in the
planning run for a plant to trigger the procurement of a plant material for a certain quantity for a specific date.


Structure
The procurement type can be either in-house production or external procurement.

In in-house production, the planned order triggers the creation of
dependent requirements for the material components. These are the BOM
components of the material to be procured. The required quantities and
dates for these components are planned using the BOM and routing of the material to be procured.

The capacity requirements at the work center can be calculated using the appropriate routing for in-house production.


Integration
For in-house production, the planned order can be converted into a
production order or a process order. For external procurement, the planned order can be converted into a purchase requisition.

A planned order can be used to plan the production of the material
requested in a sales order. The production date is based on the date specified in the schedule line of the sales order.

Available Methods

• Change : Change Planned Order [ BAPI_PLANNEDORDER_CHANGE ]
  
• Create : Create Planned Order [ BAPI_PLANNEDORDER_CREATE ]
  
• Delete : Delete Planned Order [ BAPI_PLANNEDORDER_DELETE ]
  
• ExistenceCheck : Check Existence of Object [ BAPI_PLANNEDORDER_EXIST_CHECK ]
  
• GetDetail : Get Details for Planned Order [ BAPI_PLANNEDORDER_GET_DETAIL ]
  
• GetDetailedList : GetDetailedList [ BAPI_PLANNEDORDER_GET_DET_LIST ]
  

Change

This method can be used to change the header data of a planned order.

For example, you can change the order quantity of a planned order.Using this method, changing the values in the header data always willtrigger rescheduling and re-explosion of the Bill of Material for the planned order.

To help you understand how the method can be used, test transaction"MDBA" is available. It has integrated all 6 planned order methods (R/3release 4.5A) into a transaction to deal with planned orders. For moreinformation, please refer to the program documentation on this transaction. The name of the program is "MDBAPI01".

Restriction:

Please note that this method can not be used to change the material components of a planned order.

Notes

Authorization checks:

The following authorization objects are checked with the activity V (change):

Parameter interdependencies:

Parameter "HEADERDATA" and "HEADERDATAX have the following interdependencies:
"HEADERDATA" is used to enter the values to change a planned order, andthe corresponding fields in "HEADERDATAX" must be filled if you want to
make the entry in "HEADERDATA" valid. The two parameters consist of the same fields with the same names.

Further methods:

If you have decided that the changes made by this method are to be saved in the database, you have to call up the method
CommitWork. If you decide not to save the data to the database, you can call the method RollbackWork instead.
You can find more information in the parameter documentation of the parameters below.

Confirmations:

Messages are received back in the parameter 'Return'. You can find
return values and their meaning in this parameter documentation.

Create

This method can be used to create planned orders with BoM explosion or with manual entry of components.

To help you to understand how the method can be used, test transaction"MDBA" is available. It has integrated all 6 planned order methods (R/3Release 4.A) into a transaction to deal with planned orders. For more
information, please refer to the program documentation on this transaction. The name of the program is 'MDBAPI01'.

Notes

The following authorization objects are checked with the activity H (Create):

Transfer:

You have to pass on the header data of the planned order together with the component data (optional).

Further methods:

If you have decided that the planned orders created using this method
are to be saved to the database, you have to call up the method CommitWork. You can find moreinformation in the parameter documentation of the parameters below.

Confirmation:

Messages are received back in the parameter 'Return'. You can find
return values and their meaning in this parameter documentation.

Delete

This method can be used to delete a planned order from the database. Itwill delete all corresponding data such as capacity and components when it 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 (R/3
Release 4.5A) into a transaction to deal with planned orders. For moreinformation, please refer to the program documentation on this transaction. The name of the program is 'MDBAPI01'.

Notes

Authorization checks:

The following authorization objects are checked with the activity V (Change):

Further methods:

When you have decided to save the changes (deletion, in this case) to the database, you must call the method CommitWork
. If you decide not to save the data in the database, you can call the method RollbackWork instead.

You can find more information in the parameter documentation of the parameters below.

Confirmation:

Messages are received back in the parameter 'Return'. You can find
return values and their meaning in this parameter documentation.

ExistenceCheck

This method can be used to check if a specific planned order exists in the database.

To help you understand how the method can be used, test transaction"MDBA" is available. It has integrated all 6 planned order methods (R/3Release 4.5A) into a transaction to deal with planned orders. For more
information, please refer to the program documentation on this transaction. The name of the program is 'MDBAPI01'.

Notes

Authorization checks:

The following authorization objects are checked with the activity A (Display):

You can find more information in the parameter documentation of the parameters below.

Confirmations:

Messages are received back in the parameter 'Return'. You can findreturn values and their meaning in this parameter documentation.

GetDetail

This method can be used to obtain the details of a planned order. Thedetails include the header data, material components, capacity headerdata, capacity data. Please note that this method reads data from thedatabase. This means that you will not be able to obtain the detailed
information of a planned order that is not saved yet to the database.For example, if you have just created a planned order with method PlannedOrder.Create, you can onlyget the details of this planned order after saving it to the database using such method as CommitWork.

To help you understand how the method can be used, test transaction"MDBA" is available. It has integrated all 6 planned order methods (R/3Release 4.5A) into a transaction to deal with planned orders.

For more information, please refer to the program documentation on this transaction. The name of the program is 'MDBAPI01'.

Notes

Authorization checks:

The following authorization objects are checked with the activity A (Display):

Confirmations:

Messages are received back in the parameter 'Return'. You can findreturn values and their meaning in this parameter documentation.

GetDetailedList

This method can be used to obtain a "detailed" list of planned ordersthat are selected using the selection criterias given as an import parameter to the method.

Please note that only the planned orders that are saved in the database will be selected.

To help you understand how the method can be used, test transaction"MDBA" is available. It has integrated all 6 planned order methods (R/3Release 4.5A) into a transaction to deal with planned orders.

For more information, please refer to the program documentation on this transaction. The name of the program is 'MDBAPI01'.

Notes

Authorization checks:

The following authorization objects are checked with the activity V (Change):

You can find more information in the parameter documentation of the parameters below.

Confirmations:

Messages are received back in the parameter 'Return'. You can findreturn values and their meaning in this parameter documentation.