Purpose
Program for creating the Web request index after the upgrade from CRM4.0 to CRM 5.0

Prerequisites
This program must be scheduled after the upgrade to CRM Release 5.0 ifyou work with Web service requests. Otherwise, the "request category"field cannot be searched for in transaction processing.

Features

• The program can also be started if there are no Web requests. If you are
not sure, no errors will occur if you start the program.

• The program can be restarted. If the program terminates or you are not
sure whether the metadata has already been converted, you can restart itwithout any problems.

• The program can be started for test purposes

Selection
Selection parameter : "Test run", "commit-counter" and "log file"
If you set the "test run" indicator (default value), only a test run isstarted, this means the data is not written to the database, In thiscase, it is only logged to the memory and cannot be accessed later.
If this indicator is not set, an actual run is started. In this case,logging takes place to one of the files you specified (log file). Thisfile must be accessible from the current application server and theremust be write authorization at the operational system level. The userstarting the program must have the relevant authorization for theauthorization object S_DATASET at the SAP level.
With actual runs, the system checks that the log file is accessible-
The commit counter manages the commits in the database. To avoidunnecessary system load, it is not advisable to reject a Commit Workafter each document is converted. 100 is therefore used as the defaultvalue and this means that a commit occurs after 100 rejected indexrecords at the end of the processing.

Output


• Test run: Log information is written to the memory and displayed there
after the run. It is deleted after the run.

• Actual run: Log information is written to the file specified and is
displayed there after the run. It is available after the run in the logfile.