Settlement Run 

The settlement units that are observed in a settlement run are identified when a settlement document is created from the definition of the selection variant.  In this way, the selection variants groups the settlement units that are to be settled together. The sub-settlement units are always settled together with their higher-level settlement units and any other sub-settlement units. New settlement units are automatically observed in subsequent settlement runs, provided they meet the selection criteria of the variant.

In the settlement workbench, a run can be created for a settlement document and then scheduled. Depending on the modifications you made to the procedure (workflow, job), the settlement run is automatically started. The details of a settlement run depend on the settlement procedure you choose. However some of the processing steps are common to all settlement runs. These are:

·        Generate instance of settlement run and set status (status: started)

·        Execute settlement steps (based on procedure): for example select points of delivery relevant to settlement, determine load shape of interval customers, and so on

·        Set final status (status: completed OK or terminated)

In addition to the processing status, the system stores information in the settlement document on the results profiles that were updated and sent.

During a settlement run, the following restrictions apply:

·        Within the settlement period, no historical changes can be made to the selected settlement units (for example the allocation of sub-settlement units to the higher-level settlement unit must be valid over the entire settlement period).

·        Active settlement only occurs when the settlement periods contain no gaps and do not overlap (for example if an active settlement is performed for January 2000 then the next active settlement can only be performed for February 2000).

·        Each settlement step can only be executed once per settlement run. The settlement steps can only be executed more than once (meaning once for each settlement unit- including parallel runs) if the settlement processes once settlement unit only.

·        Parallel settlement runs are only possible if is different settlement units are to be taken into account.

·        If a settlement run is terminated due to errors, or is manually stopped, the settlement steps can be recalculated in the next settlement run. However this recalculation only includes settlement steps that were not completed or with results that were not constantly saved. To have the system recalculate all the settlement steps, you must create a follow-up document. If you do this, the current settlement documents is excluded from further settlement runs.

A technical log and an application log is recorded for each settlement run. Depending on the settings in the settlement procedure the technical log is either a workflow or job log. The content and scope of the application log is primarily determined by the settings in the settlement steps. This means, each settlement determines which messages appear in the log. You can influence the number of messages in the log. To do this, suppress the display of detailed messages when you start the settlement step. If the Detail_Log is set to the initial value, the majority of technical messages are hidden.

In addition to the messages in the application log, all the critical errors that caused the termination of the settlement step are recorded in the error log. If the cause of the error is resolved, these error messages are automatically confirmed during the next settlement run (re-calculation by error).