Defining Dependencies

Use

Programs and transactions that have been included in the task list template using chronological process steps as part of an organizational structure frequently involve business-related or system-related dependencies that need to be portrayed for the process flow to be processed smoothly.

In the configuration of the Closing Cockpit (CLOCOC), you can display these predecessor relationships under Dependencies . When you enter a relationship between programs and transactions here, this relationship is checked during subsequent processing in the application (CLOCO), thereby ensuring the correct sequence is applied.

Prerequisites

You have already assigned the transactions and programs as tasks in the task list template (see Creating Tasks ).

Procedure

In the configuration transaction of the Closing Cockpit , access the Change <Template Name> screen.

  1. To be able to define dependencies, choose Dependencies .

  2. Select the task for which you want to define one or more (hierarchical) predecessor relationships.

    Note Note

    The combination of relationships is managed from the standpoint of the successor. In this way, an activity can have more than one predecessor.

    End of the note.

  3. If the selected task in the Dependencies detail screen appears, you can use drag and drop to assign to this activity any same-level or hierarchical predecessor from the task list template.

Result

By creating dependencies in the Closing Cockpit application, you have ensured that programs and transactions can only be scheduled or executed once the predecessor activities have been processed successfully (without errors).