Settings for Execution of Cycles 

Use

Select Settings to make technical settings.

Prerequisites

You have created an allocation cycle and are on the FI-SL: Execute <Allocation Type> : Initial Screen. To be able to carry out the appropriate settings, you have to have entered (or selected) the ledger, the parameters, and the flow control.

Features

Display variant

You use this indicator to control how the results list is compiled. The following information is stored in a display variant:

Database selection

You use this indicator to control how database access is to occur, in other words, how the data is selected from the database during allocation execution. The selected setting is only valid for the current cycle execution. However, you can save it as a variant. To save your settings permanently, choose . The following database selection methods are available:

Selection by cycle

For each dimension used in the cycle, the system determines the smallest and greatest value for this dimension in the entire cycle and uses this value interval as the basis for the database selection.

Advantage: Database is accessed exactly once.

Disadvantage: There is the risk that too many objects are selected. You have to eliminate the excess afterwards. The number of segments should not exceed 50.

Selection by segment

For each dimension used in the segment, the system determines the smallest and greatest value for this dimension in the entire segment and uses this value interval as the basis for the database selection.

Advantage: Performance is good, as database selection with number of segments is virtually linear and no longer exponential.

Disadvantage: Occasionally, the hit list is rather high.

Save extract

You can use this indicator to specify that reports are saved in extracts. The results lists are stored on the database after cycle execution (background processing/online). Enter a name for the extract. The system will propose this name again if you wish to view the results lists via Goto ® Extract management.

Flow trace on

You can use this indicator to define how data is selected from the database during the allocation execution. During execution of a cycle, the system logs all data relevant to error processing. You should activate this indicator if a cycle terminates with an error message or supplies erroneous results. It easier to identify errors when you are able to refer to runtime log data. You can call up this data in the system via the "Technical statistics" function. If you use background processing to process your cycle, the system generates a separate spool request that you are able to print out.

Runtime analysis on

You use this indicator to specify that runtimes of the various sections (database selection, iteration, and so on) are saved. If errors occurred during processing, you can display the runtime analysis for cycles and steps. You can then display this information on the Execution Screen via Goto ® Runtime analysis. To save your settings permanently, choose .

Technical settings

You can specify the way that the system reacts when errors occur.

Exit program

The subsequent cycles displayed on the initial screen of the allocation are not processed, the program terminates.

You should set this indicator if the cycles build on each other and subsequent errors are to be expected.

Change to simulation mode

The subsequent cycles displayed on the allocation initial screen are processed. ("Change to simulation mode").

You should set this indicator if cycles do not build upon each other and you wish to output all possible error sources in a program run for the defined allocation.