Executing the Source Allocation Run in the Background (SAP Library

Executing the Source Allocation Run in the Background

Use

You can execute the source allocation in the background with and without rescheduling. To do so, you first specify the sort and vendor ranking criteria for a version of your source allocation run. Then you trigger a simulation run, which is executed in the background.

Procedure

To execute a source allocation run as a simulation in the background, choose Logistics ® Materials Management ® Source Allocation ® Lists and Reports.

Execute the simulation run.

Choose Source Allocation - Simulation Run.
Enter the name and the version description of the simulation in the selection screen.
If at a later time you want to evaluate the AFS quotas and capacity situations before and after the simulation run and compare several versions of your simulation run according to these criteria , set the indicator save quota data and save capacity data. If you want to save any warning and error messages that appear during the source allocation run, activate the indicator save vendor reason code data.

Choose Execute to start the batch run. Leave the selection screen.

Query the results in various simulation reports.
If you have executed different versions of a batch run based on different sort and vendor ranking criteria, you can compare these versions and use the simulation reports to decide which version runs lead to the results that are best for you.

Select the optimal version of your source allocation run.
To select the versions that should be used in conclusion for the assignment of vendors, choose Select Version for Update.

Enter the name of the simulation run and execute the program.
Select a maximum of one version per update run and save it.

Assign the optimal vendors to your purchase requisitions.
To trigger the update of the purchase requisitions at database level for selected versions, choose Report for Update. A traffic light informs you of the status of the updated source allocation runs. Error messages and unexpectedly non-allocated purchase requisitions are displayed here.

Note

After an allocation run has been updated, you can use the additional report Neutralization of assigned P.R. to remove vendors from purchase requisitions in which they were written as fixed vendors and then reset the assignment that had been made.

Delete unnecessary versions.
To delete the unnecessary versions (simulations) after the last update run, choose Delete Simulation Data. The performance of the database is not affected.