Description
Program RMCVNEUA is used to set up the sales information structures. Itreads sales orders and updates statistically relevant data as if it hadjust been created. The only difference is that the statistical data isnot directly available in the Sales Information System (SIS); 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 up.
Program RMCVNEUA processes both archived orders and orders that arestill resident in the system.

General Function Description
The program reads the documents indicated on the selection screen andinitiates the statistics updating. The difference between this and thecreation of an order online is that the statistical data is saved underversion (field VRSIO) "000" when the information structures are updatedonline, and under the version that you define on the selection screenif you are setting them up. Version "000" is the version from which theSales Information System draws its data. This means that your previousdata will still be available after you have run program RMCVNEUA. Theold data is not replaced by the new data until later. This step in thesetting up process is described in the documentation on salesinformation structures. You can specify whether the program updates thedocuments it has processed in such a way that the currently determinedupdate group is entered in the order. This has the advantage that anysubsequent change to an order takes place according to the same rulesas the setup process. Archived documents are not updated, since thiswould use up too many resources, and since archived documents are notnormally changed anyway.

• 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 orders

To prevent orders from being changed during setting up of the info
structures, you select the field "Block all orders?". For test purposes,however, you may wish to leave this field unselected.

• Redetermination of the update group

You can specify whether the update group will be redetermined for thedocuments processed during setup. This will be done in accordance withthe settings made in the Sales and Distribution configuration menu.

• Error handling

If the program finds a faulty document when setting up the informationstructures (for example, the customer in the order no longer exists),it writes the document and the cause of the error to the batch log andno updating takes place. You can define the number of erroneousdocuments the program is allowed to find before it terminates. It is agood idea to start by running the program with a low number oftolerated erroneous documents. In this way, universal errors (such as acompany code that no longer exists) can be quickly identified.

• Note

If you want to examine the data obtained by the setting up of an SAPstandard information structure before you copy the data to your "actualversion", you can use the standard analyses. Include the parameter"MCR" in your user master and enter, as its value, the version you wantto look at. Now run the standard analysis that evaluates theinformation structure. The data you see is the data resulting from 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 accordingly 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 (the document flow)from a cluster table into a transparent table.