Splitting the Print Run from the IDoc Run (SAP Library

Splitting the Print Run from the IDoc Run

Use

There are seven reports you can use to generate 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 in Customizing.

Reports Generating both IDocs and Print Versions for Assortment Lists

Message type	Report name	Transaction
Full version (initialize)	RWDBBINI	WDBI
Change version	RWDBBUPD	WDBU
Manual request	RWDBBMAN	WDBM

(See Assortment List Message Types for more information on these reports.)

Since retailers usually have a large volume of data to be processed in a short window of time, you may want to consider splitting the print run from the IDoc run. This provides a significant increase in throughput speed. 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.

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

Reports for Splitting IDoc and Print Runs

Message type	Report name	Transaction
Full version (initialize)	RWBBINI_HPR	WDBI_HPR
Change version	RWDBBUPD_HPR	WDBU_HPR
Manual request	RWDBBMAN_HPR	WDBM_HPR
Print run	RWBBVCRE_HPR	WBBV_HPR

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

Prerequisites

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

If you have previously used the combined IDoc/print reports previously 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, you must open three separate sessions and run one report in each screen. This improves efficiency by restricting analysis of change pointers to a given distribution chain. There is much less data through which the system has to search.

For performance reasons, 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-dependant IDoc segments (for example, price segments and listing segments).

Note

The older IDoc type WBBDLD03 permits only one price per article. So if you have school notebooks with a September price and a price change in October, the system would have to generate two article segments for the same article, each with a different price subsegment.

The newer IDoc type WBBDLD04 can handle multiple prices. In this case, the system would need to generate only one article segment for school notebooks, containing both price segments. This reduces the total number of IDoc segments that need to be transmitted and therefore the amount of time needed to run the assortment list.

The split reports contain most — but not all — of the same master data as the combined reports. This is sufficient for most retailers. However, if you require this missing data (specifically: classification data, old labeling data, and layout modules for space management), you must implement a user exit to include this additional data.