Ansicht
Dokumentation

RMCVNEUL - Statistical Setup from Old Documents: Deliveries

General Material Data   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Description

Program RMCVNEUL is used to set up sales information structures. It reads delivery notes 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; 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 it up.

Program RMCVNEUL processes both archived delivery notes and those that are still resident in the system.

General Function Description

The program reads the documents indicated on the selection screen and initiates statistics updating. The difference between this and the creation of a delivery note online is that the statistical data is saved under version "000" (field VRSIO) when it is updated in the information structures online, and under the version that you define on the selection screen when the information structures are being set up. Version "000" is the version from which the Sales Information System draws its data. This means that your previous data is still available to you after you have run program RMCVNEUL. The old data is not replaced by the new data until later. This is described in the documentation on the setting up of 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 delivery note. This has the advantage that any subsequent change to the delivery note 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 delivery notes
  To prevent delivery notes from being changed during setting up of the information structures, you select "Block all delivery notes?". For test 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 the documents processed during setup. If so, 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 (for example, the customer in the delivery note 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) are identifed quickly.

• Note
  If you want to examine the data obtained by the setting up of an 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 record 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 generated by 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 to this effect 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 (document flow) from a cluster table into a transparent table.

Output

Example

Fill RESBD Structure from EBP Component Structure   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

Length: 4847 Date: 20240520 Time: 084945     sap01-206 ( 131 ms )