CM_EHENV_MDEF -
The following messages are stored in message class CM_EHENV_MDEF: .
It is part of development package EHENV_BO_MDEF_IMPL in software component EHS-SUS-EM. This development package consists of objects that can be grouped under "Implementation for Business Object Measurement Definition".
It is part of development package EHENV_BO_MDEF_IMPL in software component EHS-SUS-EM. This development package consists of objects that can be grouped under "Implementation for Business Object Measurement Definition".
Message Nr ▲ | Message Text |
|---|---|
| 001 | Cannot create data collection; an entry with the same details exists |
| 002 | There is no person responsible with role "&2" for location "&1" |
| 003 | &1 &2, &3 / ID: &4 |
| 004 | &1 &2, &3 |
| 006 | No value details; the corresponding data collection is not available |
| 007 | Option is temporarily not available |
| 008 | Cannot insert amount entries for &1; data collection is locked |
| 009 | Cannot insert overdue entries for &1; BOPF modification failed |
| 010 | Cannot delete overdue entries from &1; BOPF modification failed |
| 011 | Cannot read key &1 from the database table &2 |
| 012 | Records where &1 &2 &3 &4 |
| 013 | Cannot insert amount entries for &1; BOPF modification failed |
| 015 | Cannot proceed; subject is not specified |
| 026 | Inactive data collections contain collected values |
| 027 | Subject does not exist for the chosen data collection type |
| 030 | &1 at &2 |
| 031 | &1 records of &2 &3 |
| 040 | Value: &1, unit: &2 |
| 041 | Data collection definition key or ID is not provided |
| 042 | Query by data collection definition ID caused exception "&1" |
| 050 | Location: &1 |
| 051 | &1 missing records of &2 since &3 |
| 052 | Notification of overdue data collections was sent to &1 |
| 053 | Cannot notify the responsible &1 of existing overdue data collections |
| 054 | Notification of escalating overdue data collections was sent to &1 |
| 055 | Cannot notify &1 of escalating overdue data collections |
| 056 | Time zone of data collection &1 updated to &2 by the assigned location |
| 057 | Skipping data collection &1; time zone not set |
| 058 | &1 active data collections to be checked for overdue value collection |
| 059 | Check &1 is not supported; check failed |
| 060 | Period &1 is not supported |
| 061 | Due date was not determined for schedule &1 |
| 062 | Cannot send notification; a supervisor is not set for data collection &1 |
| 063 | Job execution user: &1 |
| 064 | Location type: &1 |
| 065 | Compliance scenario, to which data collection "&1" belongs, is not active |
| 066 | Job started: Options &1; Execution period &2h; Test mode &3; Ext. log &4 |
| 067 | Number of selected records: &1 |
| 068 | Scheduled data collection skipped (&1): root &2; schedule &3 |
| 069 | Already existing record (source_root_key_ref = &1), (valuetimestamp = &2) |
| 070 | Query for records caused exception "&1" |
| 071 | Manual collection of "Hourly" data is not allowed; select "Automatic" |
| 072 | To activate an automatic data collection, you must specify ext. source |
| 073 | Data collection definition with the same external source already exists |
| 074 | Cannot delete; the data collection records are referenced in a deviation |
| 075 | Data collection with the same name exists in this compliance scenario |
| 076 | Due date was not determined for data collection "&1" in scenario "&2" |
| 077 | Data classifier is used in location aggregation |