The program /osa/dispatch
is used to trigger the processing steps. This report has to be performed separately for each step of the On-Shelf Availability algorithm. This is because SAP recommends that you perform each step with a different frequency:
Intra-week pattern: Once per week at the start of the week, and as soon as all sales transactions of last week are available.
Estimation: Every day, or at least once per week after the intra-week pattern step has been performed.
Monitoring: Several times a day during opening hours of the store, and as often as the out-of-shelf alerts can be checked by the store personnel
Analysis: Your business needs determine how often the analytical run of the On-Shelf Availability processing is needed.
Note
In On-Shelf Availability, the current stock cannot be considered. The current stock could explain an out-of-shelf situation (stock is zero), which means stock personnel do not have to check the shelf. An out-of-shelf alert together with a zero stock situation could therefore be ignored in the regular monitoring run. For reporting, it could be an automatic explanation for the detected out-out-shelf situation.
To call the program /osa/dispatch
, use the transaction /OSA/DISPATCH
or execute the report /OSA/DISPATCHER
.
To execute the dispatcher, you can define the following settings:
A range or a list of stores: This allows you to schedule and run the dispatcher differently for each set of stores.
A range or a list of sub-departments: This allows you to schedule and run the dispatcher differently for each set of sub-departments.
With the /OSA/SUBDEPARTMENT_ACCESS
(Retrieve Sub-Department Data
) Business Add-In (BAdI) , the relevant product clustering can be defined. The program /osa/dispatch
uses this product clustering as a sub-department.
Time period: The intra-week pattern has to be determined based on a start date and end date.
This setting is required only for analytical business cases, not for regular monitoring.
Configuration profile: You can define several configuration sets for the OSA calculation.
You do this in Customizing under
.Parallel processing parameters: If On-Shelf Availability processing is performed for several stores, SAP recommends using parallel processing.
Processing log: You can activate logging, and choose whether you want to save the log in the database.
Even if the program /osa/dispatch
can be executed manually, SAP recommends a scheduled execution in the productive operation of the system. This ensures that the data in the system is continuously up to date. To regularly execute a step, define a corresponding job in the SAP NetWeaver scheduler. Specify /OSA/DISPATCHER
as program name and choose the appropriate variant that defines the desired step and the associated settings.