CM_CBESCOM_INB -
The following messages are stored in message class CM_CBESCOM_INB: .
It is part of development package CBESCOM in software component EHS-SAF-ESM. This development package consists of objects that can be grouped under "EHS: Integration of Exposure Scenario Communication".
It is part of development package CBESCOM in software component EHS-SAF-ESM. This development package consists of objects that can be grouped under "EHS: Integration of Exposure Scenario Communication".
Message Nr ▲ | Message Text |
|---|---|
| 001 | ESComXML check; version '&1' invalid |
| 002 | Internal error while instantiating data import for version &1 |
| 003 | ESComXML file is empty; import request will not be created |
| 004 | File format '&1' is not supported |
| 005 | Selected file is not a valid ESComXML file |
| 006 | ESComXML file name '&1' is invalid |
| 007 | Error while uploading the ESComXML file |
| 008 | Document &1 (document type &2) created for ESComXML file |
| 009 | Internal error: ALV display cannot be initialized |
| 010 | Internal error in ALV display; class &1, method &2, exception &3 |
| 011 | Processing status was changed from '&2' to '&1' |
| 012 | Request &2: ESComXML file was uploaded; see log |
| 013 | Import request was not created |
| 014 | Substance &1 does not exist |
| 015 | Supplier material &1 does not exist |
| 016 | Log '&1' for ESComXML file '&2' cannot be displayed |
| 017 | &1 import requests were found |
| 018 | An import request was found |
| 019 | Import request &1 was already deleted |
| 020 | Check for request &1 started; update the worklist |
| 021 | Import request &2 locked by user &1; action not possible |
| 022 | Import request changed |
| 023 | Import requests changed |
| 024 | Import request could not be changed; try again |
| 025 | Import request could not be changed; try again |
| 026 | Error while determining the data in the ESComXML file |
| 027 | Processor could not be changed |
| 028 | &1 import requests deleted |
| 029 | Import request &1 cannot be deleted |
| 030 | Import request &2 cannot be deleted; check the status |
| 031 | Import request cannot be processed; check the status |
| 032 | Select one row only |
| 033 | Select a row |
| 034 | ESComXML file cannot be checked; check the status |
| 035 | Processor was changed to user '&1' |
| 036 | Select a valid ESComXML file |
| 037 | Extended ESComXML check was not started in the background |
| 038 | ESComXML file was checked; see check log |
| 039 | Enter the first name and last name of the processor |
| 040 | Internal error while instantiating staging area handler for version &1 |
| 041 | Internal error while preparing import for file &1 |
| 042 | Internal error: next free record number could not be determined |
| 043 | Component with record number &1 does not exist |
| 044 | Entry with record number &1 does not exist in the worklist |
| 045 | Internal error during processing of standard functions |
| 046 | Component details could not be saved |
| 047 | Substance &1 (spec. type &2) was assigned |
| 048 | Material '&1' was assigned |
| 049 | Material &2 is not assigned to substance &1 |
| 050 | Messages could not be added to the log |
| 051 | Mandatory informtion in attribute '&2' in section '&3' does not exist |
| 052 | Component entry with record number &1 does not exist |
| 053 | Exposure scenario details could not be generated |
| 054 | Usage descriptors could not be generated |
| 055 | Exposure scenario header data with record number &1 does not exist |
| 056 | Import request cannot be reset; check the status |
| 057 | Import request cannot be rejected; see the status |
| 058 | Generation language '&1' is not supported |
| 059 | Exposure scenarios cannot be selected; check the status |
| 060 | Environment contributing scenario cannot be uniquely assigned |
| 061 | Processing log for import request '&2' cannot be displayed |
| 062 | UUID '&1' of exposure scenario is not valid |
| 063 | Invalid number (&1) of supplier sections |
| 064 | Invalid number (&1) of supplier sections |
| 065 | UUID '&1' of the contributing scenario is not valid |
| 066 | Mandatory section '&1' does not exist in parent section '&2' |
| 067 | Exposure scenario &1 was checked successfully |
| 068 | Contributing scenario &1 was checked successfully |
| 069 | Expo. scenario does not contain contributing scenario worker or consumer |
| 070 | Exposure scenario contains contributing scenario worker or consumer |
| 071 | ESCom type of ESComXML file is invalid |
| 072 | REACH registration number '&1' is not valid |
| 073 | Supplier &1 was assigned |
| 074 | &1 non-ESCom phrases exist in exposure scenario |
| 075 | You are not authorized to display log '&1' |
| 076 | You are not authorized to display the processing log |
| 077 | Raw material &1 with record number &2 does not exist |
| 078 | Supplier material &1 (spec. type &2) was assigned |
| 079 | Component &1 was assigned to substance &2 (spec. type &3) |
| 080 | One import request was deleted |
| 081 | Exposure scenarios do not exist |
| 082 | ESComXML file &1 was checked |
| 083 | ESComXML version: &1 |
| 084 | Version of ESCom phrase library: &1 |
| 085 | Generation date: &1 |
| 086 | Generation language: &1 (&2) |
| 087 | ESCom type: &1 (&2) |
| 088 | &1 ESCom phrases and &2 non-ESCom phrases exist |
| 089 | Details for contributing scenarios could not be generated |
| 090 | REACH registration number does not exist |
| 091 | Error while initializing BAdI BADI_EHSS_ESC_INB_PROCESSING |
| 092 | No active implementation of BAdI BADI_EHSS_ESC_INB_PROCESSING |
| 093 | ESComXML files of type SUB (substance) are not supported |
| 094 | Substance was not assigned |
| 095 | Material was not assigned |
| 096 | Supplier was not assigned |
| 097 | Supplier material was not assigned |
| 098 | Component was not assigned |
| 099 | &1 exposure scenarios exist |
| 100 | An exposure scenario exists |
| 101 | Newer ESComXML file exists for supplier material '&1' |
| 102 | Data for supplier material '&1' is currently being imported |
| 103 | Supplier & has not been created |
| 104 | Supplier material &1 does not exist |
| 105 | Generation language: not specified |
| 106 | Date: &1 ; Time: &2 |
| 107 | Error while reading substance data |
| 108 | Check executed in the background |
| 109 | Check executed immediately |
| 110 | Supplier: &1 |
| 111 | Product name: &1 |
| 112 | Version of eSDS: &1 |
| 113 | Substance name: &1 |
| 114 | CAS number: &1 |
| 115 | EC number: &1 |
| 116 | REACH registration number: &1 |
| 117 | UUID: &1 |
| 118 | Version date: &1 |
| 119 | Maximum number of non-ESCom phrases exceeded |
| 120 | Mandatory information in attribute '&3' in section '&4' does not exist |
| 121 | Non-ESCom phrase &3 exists: attribute '&1', section '&2' |
| 122 | Non-ESCom phrase &4 exists: attr. '&1', compl. attr. '&2', section '&3' |
| 123 | Specification type &2 for the selected component is not supported |
| 124 | Specified material is not known |
| 125 | Usage profile &1 is invalid |
| 126 | Rejected import request cannot be reset |
| 127 | Supplier material &1 is assigned to another substance |
| 128 | Supplier material &3 is not assigned to substance &1 |
| 129 | Material &1 does not exist as an identifier |
| 130 | Material not selected for supplier material &1 |
| 131 | Supplier &1 does not exist as an identifier |
| 132 | Identifier not selected for supplier material &1 |
| 133 | Selection for exposure scenarios has been reset |
| 134 | Specification type &2 of selected substance is not supported |
| 135 | Assigned components are not unique |
| 136 | Import for import request &1 started (date: &2 ; time: &3) |
| 137 | Import could not be started; check the status |
| 138 | Import terminated (date: &1 ; time: &2) |
| 139 | Import was executed (date: &1 ; time: &2) |
| 140 | Error while importing the data; see additional messages |
| 141 | Exposure scenario header data cannot be uniquely assigned |
| 142 | Usage profile &1 is not valid |
| 143 | The substance you entered does not exist |
| 144 | Enter a supplier material |
| 145 | Error while calling the data import for import request &1 |
| 146 | Exposure scenario header data &1 will be created |
| 147 | Exposure scenario header data exists in system; &1 will be assigned |
| 148 | Contributing scenario &1 has incorrect specification type &2 |
| 149 | Component &1 substance assignment was deleted |
| 150 | Select at least one exposure scenario |
| 151 | Import request cannot be rejected; see the status |
| 152 | Background job &1 was scheduled: date &2; time &3 |
| 153 | Import request cannot be rescheduled; check the status |
| 154 | Background job &1 was started |
| 155 | Import request cannot be rescheduled; check the status |
| 156 | Placeholder phrase &1 does not exist in active library |
| 157 | Internal error while reading phrases |
| 158 | Placeholder phrase &1 does not exist in phrase set &2 |
| 159 | ESComXML file does not exist in document &1 |
| 160 | Specification &1 is locked by another user |
| 161 | Supplier material &1 is assigned |
| 162 | Val. assign. type '&1': Placeholder phrase exists in the ESComXML file |
| 163 | Checking import request &1... |
| 164 | Val. assign. type '&2': Phrase &1 does not exist |
| 165 | Val. assign. type '&3': Phrase &1 is not assigned to phrase set &2 |
| 166 | Val. assign. type '&2': Phrase &1 is not assigned as a phrase reference |
| 167 | Val. assign. type '&2': Phrase &1 is assigned to multiple active phrases |
| 168 | Val. assgnt type '&1': Unable to determine unit of measure for phrase &2 |
| 169 | New UUID: &1 |
| 170 | Import request &1 could not be updated; check messages |
| 171 | Value assignment type '&1': Value &2 is invalid |
| 172 | Data cannot be imported; no authorization for &1 |
| 173 | Environment contributing scenario &1 will be created |
| 174 | Environment contributing scenario exists in system; &1 will be assigned |
| 175 | Worker contributing scenario &1 will be created |
| 176 | Worker contributing scenario exists in system; &1 will be assigned |
| 177 | Consumer contributing scenario &1 will be created |
| 178 | Consumer contributing scenario exists in system; &1 will be assigned |
| 179 | Exposure scenario header data &1 has incorrect specification type &2 |
| 180 | Worker contributing scenario cannot be assigned uniquely |
| 181 | Consumer contributing scenario cannot be assigned uniquely |
| 182 | Component &1 is assigned |
| 183 | No component is assigned |
| 184 | Import requests could not be deleted; check messages |
| 185 | No maintenance log exists |
| 186 | Val. assign. type '&1', instance '&2': Placeholder phrases will be copied |
| 187 | Val. assignment type '&1': Only first scenario &2 instance is considered |
| 188 | Val. assignment type '&1': No value assignment instances in scenario &2 |
| 189 | Import terminated |
| 190 | Data change not possible; value assignment type is referenced |
| 191 | Data change is not possible; status does not permit change |
| 192 | Data change is possible; status warns when change is made |
| 193 | ------------------------------------------------------------------------ |
| 194 | Single-value characteristic exists for multi-value attribute |
| 195 | Value assignment type '&1': comparison operator &2 is not valid |
| 196 | Error when reading job data |
| 197 | Error while reading the data for import request &1 in work table TCGC0 |
| 198 | Error in Customizing for ESComXML import |
| 199 | Error during archiving of data record with record number '&1' |
| 200 | &1 exposure scenarios will be taken into account during import |
| 201 | 1 exposure scenario will be taken into account during import |
| 202 | Non-ESCom phrase &3 exists: attribute '&1', section '&2' |
| 203 | Non-ESCom phrase &3 exists: attribute '&1', section '&2' |
| 204 | Non-ESCom phrase &4 exists: attr. '&1', compl. attr. '&2', section '&3' |
| 205 | Non-ESCom phrase &4 exists: attr. '&1', compl. attr. '&2', section '&3' |