Ansicht
Dokumentation

QAM_IAM_VC_DATSC - Make Settings for Date Determination and Traffic Lights

General Data in Customer Master   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

In this Customizing activity, you make the following settings in a date schema:

• You store the rules according to which determination of dates for issues and assigned activities is to run. For example, you can specify that the expected start date of the activities for an issue is to be set to one day after the creation date of the issue. Date determination can be triggered by QIM users using a pushbutton when processing an issue. Any changes to dates are recorded as entries in a log.

• You store the rules according to which traffic lights are displayed to indicate the due dates of issues and activities in the issue hierarchy. For example, you can specify that as of three days before the expected end date of an activity until its expected end date a yellow traffic light is shown, and a red traffic light is shown as of the expected end date.

You can either assign a date schema directly to an issue type or have it determined by BRFplus rules. If a date schema is found by the BRFplus determination, this has precedence over the date schema entered for the issue type.

1. Create a date schema and make the necessary settings at the level of the date schema. Specify, for example, after how many days the logs are to be deleted.
2. To set up date determination at issue level, you make the following settings in the detail view for issue date determination:
1. First, select the timepoint code that is to be changed by date determination.
2. Specify which other timepoint code is to be referenced in the determination. Instead of a timepoint code, you can also specify the creation date of the issue as the reference.
3. Enter the offset between the resulting timepoint code and the referenced timepoint code or creation date. You can enter positive or negative values.
4. Select whether all date fields are to be filled by date determination, or if only initial values (that is, empty date fields) or values already determined by the system should be overwritten when a new determination is run.
3. To set up date determination at activity level, you make the respective settings in the detail view for activity date determination. Here, you can distinguish between different activity types and you can specify whether the settings are also to be taken into account for long-term activities. To map dependencies between activities and the parent issue, you can decide whether the referenced timepoint codes should refer to the activity itself or to the issue.
4. To define the traffic light settings at issue level, on the Issue Date Determination screen you select the timepoint code that is to be significant for the traffic light control, and under Traffic Light Settings you make settings in various rows to determine which traffic light icon is to be displayed when. Here, you can distinguish between issues that can still be processed and issues that are already completed. The sequence in which you store the rules for a timepoint code has no influence. The system produces the result with the highest weighting. For more information about the weighting stored in the system and for example, see the documentation for the fields Open Issue/Activity and Completed Issue/Activity.
5. To define the traffic light settings at activity level, on the Activity Date Determination screen you select the significant timepoint code and make the relevant settings under Traffic Light Settings.
6. In Customizing under Define Issue Types, assign a default date schema to the issue type and specify a BRFplus application or function for date schema determination if required.

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   CPI1466 during Backup  
This documentation is copyright by SAP AG.

Length: 4257 Date: 20240523 Time: 204538     sap01-206 ( 99 ms )