This function allows you to create individual sales orders for the stores that have been entered in a multi-store order.

The break-down, or explosion, of a multi-store order simplifies processing of a multi-store order.

• You can execute the explosion process in the background.
• You can make changes in the individual orders. You can always call the basic multi-store order to check what the sold-to party originally ordered and which changes have been made to the order.
• You can communicate with the sold-to party and stores more easily. You only have to call the single document to be able to confirm delivery quantities, delivery dates, and prices for a store.

If your customer cancels the order, you can close the multi-store document in the explosion report as long as you have not exploded it completely.

You can run a simulation before you explode a multi-store order. The system checks whether the document is complete. If problems occur, you can check them using a special explosion log.

You can explode a multi-store order directly after it has been posted. However, for multi-store orders that contain a large number of stores, you should, for performance reasons, run the explosion in the background. There is a report for this purpose. To call the report, choose Logistics ® Sales and Distribution ® Sales ® Order ® Explode Multi-Store Order.

You decide which sales document type you want to use for MSO documents by making settings in Customizing.

• Whether you want to run a simulation before the actual explosion
• When you want the system to create the explosion log

When a multi-store order is exploded, the system transfers all the requirements that you had created via the MSO document to the individual orders.

The system creates an individual order for each store. If you have entered the store in the document several times in different multi-store order mixes, the system checks whether all the data is the same on store level. Only if this is the case does the system generate a single order for this store. The system copies the items, schedule lines, and quantities that were included in the MSO document for the store into this individual document.

If the system finds a store more than once in the MSO document, but with different data on store level (for example, with different order numbers, items etc.), it creates more than one individual document for this store in the MSO explosion.

You use copy routines in Customizing to define which data you want the system to copy apart from store numbers, materials, and quantities. In the standard release the system transfers the following data:

• Purchase order number at the level of the store or sold-to party

• Department at the level of the store or sold-to party

• Cancellation date for document or individual items

• Partners

Under certain circumstances it may be advantageous to close an MSO document without exploding it (completely).

This may be the case, for example, if your customer cancels the order or wants it to be changed to such an extent that it is easier for you to create the order again.

You never process a MSO document further yourself. If the system cannot explode the MSO document completely, you have to close the document manually. As long as the MFA document is not completely exploded, it is relevant to requirements. When you close it, you reset these requirements.

You close an MSO document using an explosion report. Different statuses allow you to inform the system how you want it to handle closing MSO documents with individual orders that may have already been created.