In addition to creating markdown plans manually, you can have R/3 analyze sales data and let you know when a markdown is advisable. For example, you can create an exception report that lists the 100 articles with the lowest sales revenue for the previous month. When the analysis is run, Workflow will send a work item to the person responsible for markdown planning, who can then examine the results and determine whether price reductions are warranted. If so, R/3 will create the markdown plans automatically.

• In subsequent processing for the exception, specify that the data is to be transferred to Workflow as a table.
• Define article and store as characteristics, and define sales revenue as a condition.

2. Assign the exception analysis to the standard event MarkdownCreate (business object MCYA) using transaction AWUW. Set the event coupling to the exception as active.

3. Define the organizational data and assign it to Workflow task TS20000675. Then activate the event coupling to Workflow.

4. Execute the exception analysis in batch mode.

5. The person responsible receives a Workflow message. Based on the exception data, he or she then determines whether or not to proceed with markdowns. If so, R/3 will create the markdown plans automatically.