The report Automatic Relisting Using Change Documents (WSM4L) enables you to automatically analyze changes that have occurred whilst maintaining layout-relevant data and then automatically update the listing conditions accordingly.

The changes are logged by the relevant applications in the form of change documents. You can access these later.

When a new layout is created it is stored in table TWGV. This table is not relevant for listing conditions, however.

Any changes are updated using the change document object WRS1.

You make changes to the assignment of layouts to departments within site maintenance. Layouts are assigned to departments using entries in the LAYVR field of table WRF4.

Any changes are updated using the change document object BETRIEB.

If you reassign a layout module or delete or change an existing assignment, a change document is generated. These assignments are recorded in table TWGLV.

These changes to assignments are updated in the change document object LAYOUT.

When you create a new layout module it is stored in tables TWML and WLMV (an entry with version 0000 is created in the tables). Creating new layout modules has no effect on listing conditions. Deleting them also has no effect, as the assignments have to be deleted first.

When you change the validity of a layout module version, create or delete a layout module version or change the status, table WLMV is updated. A change document is generated. All changes are relevant for listing conditions.

These version changes are updated to the change document object LAYOUT_MOD.

If you assign an article to a layout module version, delete the assignment or change the facing, table MALG is updated.

These changes are updated to the change document object MAT_FULL.

Note that deleting a single field statement causes the number of change documents to increase.

If you include or delete an article in a variant, this change is also updated to table MALG. These changes are updated to the change document object MAT_FULL.

If you assign an article from a store to the variant, this change is updated to table WLVA. If the variant in which the article is found changes, field MALG-LMVAR needs to be considered. These changes are updated to the change document object LAYOUT_MOD.

Select the start time.

If you do not select a start time the start time and date are read from the application log in which the last run is recorded. Logical checks then run. If these checks do not find any errors, an entry is made in the application log (function module APPL_LOG_WRITE_DB). According to the assortments you selected, the listing conditions (table WLK1) are then locked.

Each change document object affected is encapsulated in an Include during processing. In each of these Includes, the corresponding change document object is read (function module CHANGEDOCUMENT_READ). The change documents that are not relevant are then removed.

The time taken to run the change documents should also be noted.

A change that has then been reset to the original value has no effect on the listing conditions and therefore should be removed at this point.

Using the change documents, the layout module versions affected are identified and updated to a global table. This table is updated in every Include. Therefore all the layout module versions that have been changed and all the assortments affected are recorded in the Includes. If a layout module version has already been taken into consideration by an earlier change it is not included in the table a second time. The assortments affected are an intersection of the selection and the current assignment of layouts to assortments. The function tells you whether it is a deletion, change or new creation.

The changes to the layout module versions are collected and then the layout version and all the assortments affected are handed over to the listing function in the Layout Workbench. The listing function in the Layout Workbench processes comparisons and variant handling. To do this, the relevant Layout Workbench function module is called from the Main Program.

The status report of this function is then issued as a log.