Time Concept 

Use

The tasks and the objects belonging to an internal control (such as processes, controls, and their assessments) are time-dependent. This means that the settings for a control may be different at different times. You can keep track of these differences (and when the changes were made, and so forth) in the system, since each status is stored with different time information.

Features

When a task is executed in MIC, the following time views (which are independent of each other) are displayed in parallel:

·        Timeframe

Each object or task, such as an assessment, is valid for a specific date interval, such as a quarter.

·        Date

Each task or every change that is made to an object is performed on a specific date. The last change made within a timeframe is logged.

If you need a more detailed log of the changes, you can activate it using the system parameter rec/client. The relevant tables are selected for a change log. For more information, see under Record Table Changes in Customizing for MIC.

Note that the date does not have to fall within the timeframe. For example, you can perform an assessment for Q1 2004 on May 27, 2004.

Some tasks have to be performed on a regular basis, in particular the tests and assessments. When scheduling the tasks, you specify how frequently (such as annually or quarterly) these tasks should be performed. You can specify which frequencies are available under Edit Attribute Values in Customizing. In Customizing under Edit Frequency Timeframes, you can specify which timeframes can be selected for a frequency.

The timeframe for which the execution of a task is valid depends on how you access the task:

·        If the task has been scheduled, you therefore access it from the task list, and the timeframe specified during scheduling applies.

·        If you access the task from the navigation area, the timeframe that you specified in the personalization settings applies.