Kontakt

Ansicht
Dokumentation

CRM_WEBREQ_INDEX_BUILD - Build Index for Web Requests After Upgrade to SAP CRM 5.0

CRM_WEBREQ_INDEX_BUILD - Build Index for Web Requests After Upgrade to SAP CRM 5.0

Fill RESBD Structure from EBP Component Structure   ABAP Short Reference  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

Program for creating the Web request index after the upgrade from CRM 4.0 to CRM 5.0

Integration

Prerequisites

This program must be scheduled after the upgrade to CRM Release 5.0 if you 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 it without 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 is started, this means the data is not written to the database, In this case, 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). This file must be accessible from the current application server and there must be write authorization at the operational system level. The user starting the program must have the relevant authorization for the authorization 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 avoid unnecessary system load, it is not advisable to reject a Commit Work after each document is converted. 100 is therefore used as the default value and this means that a commit occurs after 100 rejected index records at the end of the processing.

Standard Variants

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 log file.

Activities

Example






General Data in Customer Master   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

Length: 2488 Date: 20240520 Time: 054437     sap01-206 ( 47 ms )