/IAM/OBJECT_QIM - QIM-specific messages
The following messages are stored in message class /IAM/OBJECT_QIM: QIM-specific messages.
It is part of development package /IAM/DDIC_QAM in software component CA-IAM-ENG. This development package consists of objects that can be grouped under "DDIC and surrounding functions (F4,View-Maint.,.) of QIM".
It is part of development package /IAM/DDIC_QAM in software component CA-IAM-ENG. This development package consists of objects that can be grouped under "DDIC and surrounding functions (F4,View-Maint.,.) of QIM".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Selection for field &1 is too unspecific (&2 hits) |
| 001 | Issue &2: Field "&1" is already set and should not be overwritten |
| 002 | Issue &2: Reference date for determination of "&1" not available |
| 003 | Issue &2: Determination of date for field "&1" is not possible |
| 004 | Issue &2: Field "&1" was changed from &3 to &4 |
| 005 | Issue &2: Initial field "&1" was set to &3 |
| 011 | Activity &2: Field "&1" is already set and should not be overwritten |
| 012 | Activity &2: Reference date for determination of "&1" not available |
| 013 | Activity &2: Determination of date for field "&1" is not possible |
| 014 | Activity &2: Field "&1" was changed from &3 to &4 |
| 015 | Activity &2: Initial field "&1" was set to &3 |
| 020 | No dates determined because date schema &2 was not changed for issue &1 |
| 021 | Dates determined using date schema &2 for issue &1 |
| 022 | Date determination using date schema &2 for issue &1 set no date |
| 023 | No date determination because no date schema was found for issue &1 |
| 024 | Date determination simulated using date schema &2 for issue &1 |
| 025 | Date schema &1 determined via BRF+ |
| 026 | Dates of step not updated because the issue was not locked |
| 027 | Dates of step not updated due to missing authorization |
| 040 | Issue &1: timepoint "&2" will be reached in &3 day(s) |
| 041 | Issue &1: timepoint "&2" is &3 day(s) overdue |
| 042 | Issue &1: timepoint "&2" will be reached in &3 hour(s) |
| 043 | Issue &1: timepoint "&2" is &3 hour(s) overdue |
| 044 | Issue &1: No value available for timepoint "&2" |
| 045 | Activity &1: timepoint "&2" will be reached in &3 day(s) |
| 046 | Activity &1: timepoint "&2" is &3 day(s) overdue |
| 047 | Activity &1: timepoint "&2" will be reached in &3 hour(s) |
| 048 | Activity &1: timepoint "&2" is &3 hour(s) overdue |
| 049 | Activity &1: No value available for timepoint "&2" |
| 050 | Step &1: timepoint "&2" will be reached in &3 day(s) |
| 051 | Step &1: timepoint "&2" is &3 day(s) overdue |
| 052 | Step &1: timepoint "&2" will be reached in &3 hour(s) |
| 053 | Step &1: timepoint "&2" is &3 hour(s) overdue |
| 054 | Step &1: No value available for timepoint "&2" |