Description
Program RMCVNEUL is used to set up sales information structures. Itreads delivery notes and updates statistically relevant data as if ithad just been created. The only difference is that the statistical datais not directly available in the Sales Information System; instead,data is transferred to SIS on request. This ensures that the quality ofthe statistical data does not suffer if an error occurs in setting itup.
Program RMCVNEUL processes both archived delivery notes and those thatare still resident in the system.

General Function Description
The program reads the documents indicated on the selection screen andinitiates statistics updating. The difference between this and thecreation of a delivery note online is that the statistical data issaved under version "000" (field VRSIO) when it is updated in theinformation structures online, and under the version that you define onthe selection screen when the information structures are being set up.Version "000" is the version from which the Sales Information Systemdraws its data. This means that your previous data is still availableto you after you have run program RMCVNEUL. The old data is notreplaced by the new data until later. This is described in thedocumentation on the setting up of sales information structures. Youcan specify whether the program updates the documents it has processedin such a way that the currently determined update group is entered inthe delivery note. This has the advantage that any subsequent change tothe delivery note takes place according to the same rules as the setupprocess. Archived documents are not updated, since this would use uptoo many resources, and since archived documents are not normallychanged anyway.

Special Functions

• Run time limitation

The program allows you to specify when processing will end. Forexample, if it runs at the weekend you can decide to end processing onMonday morning when online operations resume. This is particularlyimportant if all orders have been blocked (see below). You can alsospecify whether the program will terminate with an error message orwhether the job will end normally. The former may be desirable if otheractions are to follow on from successful completion of the program.
The processing status is stored, independently of whether or not theprogram has terminated abnormally, under the name you enter intable TMCW1.

• Blocking all delivery notes

To prevent delivery notes from being changed during setting up of theinformation structures, you select "Block all delivery notes?". Fortest purposes, however, you may wish to leave this field unselected.

• Redetermination of the update group

You can specify whether the update group should be redetermined for thedocuments processed during setup. If so, this will be done inaccordance with the settings made in the Sales and Distributionconfiguration menu.

• Error handling

If the program finds a faulty document (for example, the customer inthe delivery note no longer exists), it writes the document and thecause of the error to the batch log and no updating takes place. Youcan define the number of erroneous documents the program is allowed tofind before it terminates. It is a good idea to start by running theprogram with a low number of tolerated, erroneous documents. In thisway, universal errors (such as a company code that no longer exists)are identifed quickly.

• Note

If you want to examine the data obtained by the setting up of aninformation structure before you copy the data to your "actualversion", you can use the standard analyses. Include the parameter"MCR" in your user master record and enter, as its value, the versionyou want to look at. Now run the standard analysis that evaluates theinformation structure. The data you see is the data generated by thesetup process. Now delete the parameter "MCR" from your user masterrecord.
If you set the "MCR" parameter in your user master record, the systemissues a message to this effect when you run a standard analysis.

• The program should be executed in batch mode only.


• It is essential that you follow the steps described in the
documentation on the setting up of sales information structures.
For Release 2.1 A, you need to convert table VBFA (document flow) froma cluster table into a transparent table.