You can execute order allocation run (ARun) both in the background and online. For more information about about executing ARun in the background, see Background Processing (Batch ARUN) Background Processing of ARun.

An allocation type controls every allocation run. All the rules that influence the allocation run are grouped in the allocation type. The individual rules (selection, requirement check, grouping, sorting, allocation, release check, and log) are individually defined in Customizing for the allocation run and entered in the corresponding allocation type. Since you can define any number of allocation types, you can map a wide variety of business processes in the system. For example, you can create special allocation types with specific settings for certain customers. In this way, you can make sure that those special requests can be mapped by the system during the order processing.

Whenever you start an order allocation run, you can decide whether to run it in normal mode or simulation mode.

In normal mode, the assignments between the requirement and stock are posted and the order is updated. The stock is then assigned to this order and can be delivered in the next step.

In simulation mode, processing is similar, but the system does not update orders and the requirements are not assigned to a certain stock. You can use this mode to simulate and test results.

You can display and edit the results of a saved allocation run using ARun Workbench and log files. You can use log rules to check where the log files (containing exceptions) for order allocation run (ARun) are saved in the database.