POS Outbound Reports for Assortment Lists 
POS Outbound Reports for Assortment Lists
Use
There is a central group report that you can run to analyze data for generating assortment lists via POS outbound processing. It comprises several individual reports. If you execute the central group, it runs all the associated reports for a full analysis. Alternatively, you can run the individual reports independently or in any combination you desire.
You can select reports from an online transaction.
The individual reports are:
This report checks the IDoc types to be exported via POS outbound processing and determines whether the program will encounter any errors. You can target this report to specific sites and/or articles.
If the RWDPOSRS report fails to complete a reorganization run for some reason, you can run this troubleshooting report to determine possible causes.
Initializing assortment data for a new store can be time-consuming since so much data is involved. However, the previously existing analysis report could only be run after the initialization run takes place. Troubleshooting the data before actually performing the initialization can save time by uncovering possible problems. To meet this need, the dummy initialization report simulates an initialization run and analyzes the results so that you can address any problems. This helps ensure that you will have a clean initialization run.
No data is actually sent or processed by the dummy initialization report.
It often happens that you need to find a specific object among thousands of IDocs. This report provides a quick and easy way to search for such an object. (See also transaction WE09.)
Standard ALE report RBDCPCLR enables you to delete change pointers, but it does not provide any suitable navigation features for retail. This new report interfaces with RBDCPCLR to make it easier to use for the retail area.
Similar to the Change Pointer Deletion report above, this report interfaces with report RWDPOSRS to make it easier to use for the retail area.
When troubleshooting, you need to be able to reproduce errors so you can determine how to fix them. This report allows you to do a test rerun using the same change pointers that were handled in the previous download. However, there is usually some time delay (perhaps a few days) between the POS run and the analysis, during which time the system may detect new change pointers. This may cause the reprocessing report to include more articles than the original download. This new data is in addition to all the previous data. None of the previous data will be omitted.
This report will not work if the change pointers were already deleted after the previous run.
Integration
These reports are usually executed after a POS Outbound Processing run, and are intended for troubleshooting purposes.
No Customizing settings are necessary.