CM_CBESCOM -
The following messages are stored in message class CM_CBESCOM: .
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 |
|---|---|
| 000 | Exception &1 in implementation of BAdI BADI_EHSS_ADDITIONAL_DOCUMENT |
| 001 | ESComXML file does not exist |
| 002 | ESComXML file name &1 is invalid |
| 003 | ESComXML file name does not exist |
| 004 | ESComXML file is empty |
| 005 | Document key does not exist |
| 006 | ESComXML file does not exist |
| 007 | Different value assignment types for outputting exposure scenarios |
| 008 | Determination of composition refers to value assignment type '&1' (&2) |
| 009 | Errors occurred when saving ESComXML file &1 |
| 010 | ESComXML file was generated and saved for specification &1 |
| 011 | Specification &3: No comparison operator intended for characteristic &1 |
| 012 | File is not a valid ESComXML file |
| 013 | ESComXML file could not be decompressed |
| 014 | Error reading the report header |
| 015 | BAdI method 'IS_GEN_RELEVANT' and data determination not compatible |
| 016 | Document could not be created in document management system |
| 017 | Errors occured when reading report shipping order &1 |
| 018 | Errors occurred when creating report shipping order for ESComXML file |
| 019 | Document &1 in document management system is already used |
| 020 | Deletion of attachment in document &1 is not possible |
| 021 | Output format does not exist for communication &2 &3 |
| 022 | Only the first report shipping order was considered |
| 023 | ESComXML file was generated and saved (document &1) |
| 024 | Communication was changed to &1 &2 |
| 025 | ESComXML file could not be displayed |
| 026 | Report shipping order is created with ESComXML file |
| 027 | Document &1 does not exist |
| 028 | System checking if report shipping order &1 contains exposure scenarios |
| 029 | Report shipping order &1 created with ESComXML file |
| 030 | ESComXML file cannot be displayed |
| 031 | Exposure scenario for substance &1 is assigned to the product |
| 032 | No shipping of ESComXML file for shipping order &1 |
| 033 | Error determining corresponding characteristic for ESComXML attribute &1 |
| 034 | Characteristic &1 contains errors or does not exist |
| 035 | Value assignment type &1 contains errors or does not exist |
| 036 | Exposure scenarios could not be determined |
| 037 | XSL transformation failed |
| 038 | Error when reading substance data relevant for exposure scenario |
| 039 | Value assignment type &1 is not assigned to value assignment category C |
| 040 | No contributing scenario environment in exposure scenario |
| 041 | Error when reading usage for report generation variant &1 |
| 042 | Start of phrase validation of exposure scenario data for ESComXML |
| 043 | End of validation of exposure scenario data for ESComXML |
| 044 | Specification &1: Exactly one value expected in characteristic &4 |
| 045 | Identify phrases as substances or mixture |
| 046 | More than 1 val. assignment instance for val. assignment cat. &3 Spec. &1 |
| 047 | Characteristic &4 is not phrase-enabled |
| 048 | Specification &1: No ESCom phrase in characteristic &2 |
| 049 | Characteristic &1 (&2) is not assigned to an attribute |
| 050 | Version number of ESCom phrase library does not exist |
| 051 | Material name for material &1 could not be determined |
| 052 | ESComXML file is not shipped |
| 053 | Specification &3: No interval intended in characteristic &1 for ESComXML |
| 054 | Data for ESComXML attribute '&1' could not be determined |
| 055 | Specification &4: Data for ESComXML could not be determined |
| 056 | Specification &1: Exactly one identifier expected |
| 057 | Product and article category missing in contributing scenario 'Consumer' |
| 058 | Specification &1: Contributing scenario &1 classified several times |
| 059 | Specification &3: ESComXML section <&1> must be filled |
| 060 | Errors occurred when determining cardinality for ESComXML sections |
| 061 | Specification &1: No unit of measurement provided for component &4 |
| 062 | Contributing scenario &1 is not assigned correctly or is incomplete |
| 063 | More than one instance for composition '&2' of specification &1 |
| 064 | No contributing scenario Worker and Consumer in exposure scenario |
| 065 | -> Specification &1: Information for characteristic &3; see long text |
| 066 | No component in composition &1 |
| 067 | Environment parameter &1 could not be read |
| 068 | Environment parameter 'REPORT_DMS_SUPPORT' contains invalid data |
| 069 | Process could not be determined |
| 070 | Specification &3: Identifier with category &1 (type &2) does not exist |
| 071 | -> Information for invalid phrase &1; see long text |
| 072 | Internal system error when calling method &1 of class &2 |
| 073 | Internal system error when calling function module &1 |
| 074 | ESComXML file name &1 is invalid |
| 075 | -> Information on section &2 concerned in ESComXML; see long text |
| 076 | Specification &1: ESComXML attribute &4 expects exactly one value |
| 077 | An unexpected process context occurred |
| 078 | ESComXML file name does not exist |
| 079 | ESComXML file is empty |
| 080 | Document key for ESComXML file does not exist |
| 081 | Specification &1: Error while generating additional document |
| 082 | Specification &3: Error while sending additional document |
| 083 | Error in additional document for specification &1 variant &2 language &3 |
| 084 | Field '&1' is not maintained |
| 085 | Report shipping order &1 is not intended for shipping with ESComXML file |
| 086 | Value assignment type for compositions not maintained |
| 087 | Substance name of specification &1 could not be determined |
| 088 | Data cannot be read; rating is not maintained |
| 089 | Shipping is not possible; communication group is not maintained |
| 090 | Phrase prefix does not exist |
| 091 | Communication type of recipient is not valid for shipping reason &3 |
| 092 | E-mail attachment for ESComXML file could not be created |
| 093 | Check &1 is not defined in Customizing |
| 094 | E-mail address not assigned to sales organization &1 |
| 095 | DUNS code not assigned to sales organization &1 |
| 096 | ESComXML file does not exist |
| 097 | Communication type of recipient is not valid |
| 098 | Output device could not be determined |
| 099 | Message type for messaged scenario assignment does not exist |
| 100 | E-mail address could not be uniquely determined |
| 101 | E-mail address does not exist for sales organization &1 |
| 102 | Name of initator cannot be determined |
| 103 | Name of initiator could not be determined |
| 104 | EC number could not be determined for specification &1 |
| 105 | Specification is not classified as a substance or mixture |
| 106 | ESComXML file is not shipped |
| 107 | Error when reading the characteristic "ESComXML File Not Required" |
| 108 | Rating for reading ESComXML data is not unique |
| 109 | Phrase &1 references several ESCom phrases |
| 110 | Additional document is not displayed |
| 111 | Field &1 is not maintained in Customizing |
| 112 | Value &2 is not maintained in field '&1' |
| 113 | Value &2 for value &3 is not assigned in field &1 |
| 114 | No values exist |
| 115 | Specification &1: No ESCom phrase in mandatoy characteristic &2 |
| 116 | Phrase in characteristic &2 is ESCom placeholder phrase |
| 117 | Exposure scenario contains contributing scenario "Worker" and "Consumer" |
| 118 | UUID must have exactly 32 or 36 characters (current length &1 characters) |
| 119 | UUID has not been entered in the correct format |
| 120 | UUID should not be changed; do you really want to change the UUID? |
| 121 | Determination of dimension for unit of measure &1 failed |
| 122 | Format for date timestamp is not correct: D:yyyy-mm-dd T:hh:mm:ss |
| 123 | Date timestamp should not be changed; do you want to continue? |
| 124 | Various header data entered in exposure scenario |
| 125 | Specification type &1 should not be used for exposure scenarios |
| 126 | Specification &1: No header data exists in exposure scenario |
| 127 | Identifier contains an invalid date |
| 128 | Conversion of unit of measure &1 to unit of measure &2 failed |
| 129 | Determination of units of measure for dimension &1 failed |
| 130 | No ESCom phrase exists for unit of measurement &1 |
| 131 | Unit of measure reference does not exist in mapper attribute |
| 132 | Value assgmt type RMM: Environment contains effectiveness without measure |
| 133 | Identifier for UUID already exists |
| 134 | Error during automatic generation of the UUID |
| 135 | Date timestamp for exposure scenario already exists |
| 136 | Error during automatic generation of the date timestamp |
| 137 | UUID cannot be displayed in the correct format |
| 138 | Date timestamp cannot be displayed in the correct format |
| 139 | UUID &1 is used in multiple exposure scenarios for product |
| 140 | Contrbuting scenario exists more than once in exposure scenario |
| 141 | UUID &4 for contributing scenario used multiple times |
| 142 | Specification &4: Contributing scenarios are not maintained completely |
| 143 | Specification &4: No contributing scenario worker |
| 144 | Specification &4: No contributing scenario consumer |
| 145 | UUID &2 for contributing scenario also assigned to an exposure scenario |
| 146 | Specification &1: Warning while generating the additional document |
| 147 | Specification &1: Information for generating the additional document |
| 148 | ESComXML file not generated and saved for specification &1 |
| 149 | Specification &1: Warnings in additional document; variant &2, lang. &3 |
| 150 | Specification &1: Information in additional document; variant &2, lang &3 |
| 151 | No ESCom phrase exists for unit of measurement &1 |
| 152 | -> Information on affected characteristic &1; see long text |
| 153 | Value assignment type &1 (&2) is not assigned to an attribute |
| 154 | DUNS code of initiator could not be uniquely determined |
| 155 | Value &1 does not exist as a value for &2 |
| 156 | Values that are too large have resulted from unit of measure conversion |