Ansicht
Dokumentation

RMCVNEUA - Statistical Setup from Old Documents: Orders

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   PERFORM Short Reference  
This documentation is copyright by SAP AG.

Description

Program RMCVNEUA is used to set up the sales information structures. It reads sales orders and updates statistically relevant data as if it had just been created. The only difference is that the statistical data is not directly available in the Sales Information System (SIS); instead, data is transferred to SIS on request. This ensures that the quality of the statistical data does not suffer if an error occurs in setting up.

Program RMCVNEUA processes both archived orders and orders that are still resident in the system.

General Function Description

The program reads the documents indicated on the selection screen and initiates the statistics updating. The difference between this and the creation of an order online is that the statistical data is saved under version (field VRSIO) "000" when the information structures are updated online, and under the version that you define on the selection screen if you are setting them up. Version "000" is the version from which the Sales Information System draws its data. This means that your previous data will still be available after you have run program RMCVNEUA. The old data is not replaced by the new data until later. This step in the setting up process is described in the documentation on sales information structures. You can specify whether the program updates the documents it has processed in such a way that the currently determined update group is entered in the order. This has the advantage that any subsequent change to an order takes place according to the same rules as the setup process. Archived documents are not updated, since this would use up too many resources, and since archived documents are not normally changed anyway.

Special Functions

• Run time limitation
  The program allows you to specify when processing will end. For example, if it runs at the weekend you can decide to end processing on Monday morning when online operations resume. This is particularly important if all orders have been blocked (see below). You can also specify whether the program will terminate with an error message or whether the job will end normally. The former may be desirable if other actions are to follow on from successful completion of the program.
  The processing status is stored, independently of whether or not the program has terminated abnormally, under the name you enter in table 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 the documents processed during setup. This will be done in accordance with the settings made in the Sales and Distribution configuration menu.

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

• Note
  If you want to examine the data obtained by the setting up of an SAP standard information structure before you copy the data to your "actual version", you can use the standard analyses. Include the parameter "MCR" in your user master and enter, as its value, the version you want to look at. Now run the standard analysis that evaluates the information structure. The data you see is the data resulting from the setup process. Now delete the parameter "MCR" from your user master record.

If you set the "MCR" parameter in your user master record, the system issues a message accordingly when you run a standard analysis.

Requirements

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

Output

Example

ABAP Short Reference   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Length: 4843 Date: 20240520 Time: 054501     sap01-206 ( 124 ms )