Splitting the Print Run from the IDoc Run 

Use

Since retailers usually have a large volume of data to be processed in a short period of time, you may want to consider splitting the print run from the IDoc run. This increases throughput speed significantly.

If you only require the assortment list for perishables, for visual purposes or for SAP Retail Store, you no longer have to take the step of creating IDocs when you do not require them. In this case you also do not have to delete the IDocs regularly.

Prerequisites

The following requirements apply if you are splitting the IDoc and print runs:

·         If you have previously used the combined IDoc/print reports and want to start using the split runs, you must run a migration report (RWDBBMIG) once only, prior to using the new change version report. The migration report builds the conditions index (database table WIND) from the change pointers for the assortment list, along with performing other necessary data conversions.

·         All stores for which you want to generate assortment lists must belong to the same distribution chain. If you want to include stores in three different distribution chains, for example, open three separate sessions and run one report in each session. This improves efficiency by restricting analysis of change pointers to a given distribution chain. The system has to search through far less data.

·         All stores within a report run must use the same IDoc reduction settings in the assortment list profile.

·         You must use IDoc type WBBDLD04 to allow repetition of time-dependent IDoc segments (for example, price segments and listing segments).

Features

Seven reports are available for generating assortment lists.

The following three reports can generate the lists in both electronic form (IDocs) and report form (for display and/or printing), if you so specify inCustomizing.

 Reports Generating both IDocs and Print Versions for Assortment Lists

Report Type	Report Name	Transaction
Full version (initialization)	RWDBBINI	WDBI
Change version	RWDBBUPB	WDBU
Manual request	RWDBBMAN	WDBM

 

(For more information about this report, see Assortment List Message Types.)

You still get IDocs automatically, but you can choose whether or not you want to generate the report as well. You can even decide to generate a print version several days after generating the IDocs, perhaps at a time when system processing demands are light.

Internal parallel processing guarantees efficient capacity utilization of the available hardware.

 

The first three reports in the following table are similar to those in the table above. However, they only generate IDocs. To generate the print version at a subsequent point in time, you run the fourth report (RWBBVCRE_HPR).

Reports for Splitting IDoc and Print Runs

The selection screens for these reports have a few additional fields.

Report Type	Report Name	Transaction
Full version (initialization)	RWDBBINI	WDBI_HPR
Change version	RWDBBUPB	WDBU_HPR
Manual request	RWDBBMAN	WDBM_HPR
Print version generation	RWBBVCRE_HPR	WBBV_HPR