Kontakt

Ansicht
Dokumentation

RSLVCSTART - liveCache: Start liveCache in the Background

RSLVCSTART - liveCache: Start liveCache in the Background

BAL Application Log Documentation   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

This program is used to start a liveCache in an SCM system.

Integration

Prerequisites

  • The integration data for the liveCache must be correctly stored (transaction DB59 or LC10 -> Integration). You also need to be able to run DBMServer commands for the liveCache using the DBMRFC connection.
  • The executing user must have authorization to start a liveCache. This is contained in the roles SAP_BC_LVC_OPERATOR, SAP_BC_LVC_ADMINISTRATOR, and SAP_BC_LVC_SUPERUSER.
  • The SAP user stored in the User Profile Container of the DBMServer must match the entry for the standard liveCache user in the integration data.

Features

Selection

PCONNAME: Name of the database connection

Standard Variants

Output

Activities

Special Features:

  • The individual actions of the program and its result are stored in a table as an extended log. You can display this in transaction LC10 under "Properties" and "Operating".
  • The program initially attempts to set a lock (LC_ADMIN_<IV_CON_NAME>). If someone else already holds this lock, the program termiantes with an error message. The lock is released again when the program ends (with or without an error message).

Process Steps:

The program

  • Executes any preprocessing reports stored in the integration data, if the liveCache is not already ONLINE.
  • Informs all work processes that they need to use the secondary connection to check the validity of the next SQL statement before running it (if the liveCache is not already ONLINE).
  • Starts the liveCache by executing the script lcinit or lcinit.bat (Microsoft Windows), if the liveCache is not alredy ONLINE.
  • Checks the log file lcinit.log for error messages, if the liveCache was just started with the script.
  • Executes any postprocessing reports stored in the integration data.

Special Features of the Preprocessing and Postprocessing Reports

  • You can specify up to ten reports as preprocessing or postprocessing reports for an action.
  • The reports of a report chain of this type (such as a preprocesing report for starting) must all be different. Different chains (such as preprocessing reports and postprocessing reports for starting) can, however, contain the same reports.
  • The reports are processing by the program in an additional task
  • If you desire asynchronous processing, you can execute the reports asynchronously or schedule them as a background job.
  • If an error occurs or a termination of the program is desired, the reports can signal this by exporting a text to the main memory:
EXPORT report_return_text = <TEXT>
TO MEMORY ID 'LC_REPORT_RETURN_TEXT'
  • <TEXT>: up to 255 characters in length

  • <TEXT> that starts with "STOP ": Preprocessing or postprocessing report is signalling that further processing of the start, stop, or initialization process by the program should be terminated - for example, because the report is starting the liveCache itself. The program ends itself (without an error message).

  • <TEXT> that does not start with "STOP ": Preprocessing or postprocessing report is returning an error. For a more detailed erorr message, see the <TEXT>. The program terminates with an error message.

  • <TEXT>: You can view this in the detailed log in transaction LC10 (under "Properties# and "Operating#)

Example






ROGBILLS - Synchronize billing plans   General Data in Customer Master  
This documentation is copyright by SAP AG.

Length: 4520 Date: 20240520 Time: 124912     sap01-206 ( 57 ms )