SAP® Documentation

Single view

/SCMB/RSC_SIM - Simulate and Test Process Scheduling

BAL_S_LOG - Application Log: Log header data   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.
SAP E-Book

Title

Configurable Process Scheduling - Test and Analysis

Purpose

This program is suitable for the following applications:

  • To test the use of scheduling data (master data and Customizing)
    In parallel to master data and Customizing maintenance, you can test the effects of these changes on scheduling, without executing applications that use scheduling.
  • To analyze the scheduling of applications or application documents that have saved a scheduling log to the database.

Integration

Prerequisites

Features

Selection

Input is divided into several subscreens:

Defines one (or several) entry point date(s) that you can use to start the scheduling algorithm within a specified process definition. If you specify several entry point dates, then this system processes them sequentially according to priority. The system uses the master entry point date, which you entered in the master input template, last of all. As soon as a date calculation with an entry point date leads to a result that is consistent with the master entry point date, the system regards this as the overall result and calculates no further dates using the remaining entry point dates.

You can enter the following criteria as initial date:

  • An activity and date category
  • A date type
  • A derived date type

You can set date specifications. You can specify a global date limit, so that no date is permitted before this limit. You can override this limit by specifying single dates. Single date specifications can be either date-specific limits or explicit date specifications.

You can set push/pull optimization. In this kind of optimization, the system, starting from a certain push/pull date, once again propagates forwards(push) and backwards (pull) through the scheduling activity network at the end of date calculation. This leads to a renewed date calculation for the activities affected by this propagation.

You can specify a time unit assignment set - this overrides a set contained in the process definition. You can use this set to specify the time unit for date types. The time unit of a date influences the scheduling result, since the dates in the time zone of the related activity in this time zone are rounded.

You can enter a table of properties as specification data. Scheduling behavior is influenced by these externally-specified properties and the data defined in the scheduling schema.

If you would like to see the output of the scheduling log once you have finished executing the scheduling test, then you must activate data retention and the output of the log. If you would like to continually save to the database, then you must activate data backup.

You can also show the output of logs that already exist (without executing scheduling) by choosing Data from Database.

You can use these settings when carrying out a technical analysis (for example, a runtime analysis using the transaction SE30).

The number of scheduling requests determines how many (identical) requests the system uses to execute the scheduling function in the form of a collective call.

The number of repetitions determines how often the system calls the scheduling function consecutively. Note however, that the total number of scheduling requests to be executed is the product of 'Number of Scheduling Requests' and 'Number of Repetitions'.

Standard Variants

Output

A process scheduling log or a list of existing logs is displayed.

Activities

Example






ROGBILLS - Synchronize billing plans   ABAP Short Reference  
This documentation is copyright by SAP AG.

Length: 4071 Date: 20191212 Time: 015626     sap01-206 ( 35 ms )

Our Service

Looking for Support? Questions?

The

Consolut

Callback-Service

Leave us your contact details and we will call you back. Panels marked with * are mandatory.