CM_EHFND_REQ - Messages for Compliance Requirement
The following messages are stored in message class CM_EHFND_REQ: Messages for Compliance Requirement.
It is part of development package EHFND_BO_COMPLIANCE_REQ in software component EHS-SUS-CI. This development package consists of objects that can be grouped under "Business Objects for Compliance Requirements".
It is part of development package EHFND_BO_COMPLIANCE_REQ in software component EHS-SUS-CI. This development package consists of objects that can be grouped under "Business Objects for Compliance Requirements".
Message Nr ▲ | Message Text |
|---|---|
| 001 | "&1" is not a region of &2. Please enter a valid region. |
| 002 | &1: &2 |
| 003 | &1 with title "&2" already exists. |
| 004 | Paragraph "&1" already exists at this structure level. |
| 005 | Please move the paragraph under a new parent paragraph. |
| 006 | Cannot move the paragraph, as &1 is higher than &2 in the structure. |
| 007 | Cannot move the paragraph under the same parent paragraph. |
| 008 | &1 (&2) |
| 009 | &1 &2 &3 |
| 010 | BAdI for environmental limit checks is not implemented or activated. |
| 011 | &1 must be greater than &2. |
| 012 | Field "&1" contains an incorrect value. |
| 013 | &1, &2 |
| 014 | (&1) &2 |
| 015 | Cannot set status to Historical. The requirement is used in a scenario. |
| 016 | Cannot set status to Historical. The revision is not in the past. |
| 017 | Causes exceedance when the value is greater than &1. |
| 018 | Causes warning when the value is greater than &1 and less or equal to &2. |
| 019 | Causes warning when the value is greater than &1. |
| 020 | Causes exceedance when the value is less than &1. |
| 021 | Causes warning when the value is less than &1. |
| 022 | To provide a compliance requirement, use the input help. |
| 023 | Causes warning when the value is greater or equal to &1 and less than &2. |
| 024 | Chemical property "&1" does not exist. |
| 025 | Unit "&1" is not valid for chemical property "&2". |
| 026 | Cannot move existing paragraphs. You can move those in a new revision. |
| 027 | Unit "&1" with dimension "&2" is not applicable to subject dimension "&3" |
| 028 | Cannot use symbol combination "|~|" in compliance requirement title "&1" |
| 029 | "&1" = "&2" |
| 030 | &1, &2 |
| 031 | &1 &2, &3 |
| 032 | Equation "&1" already exists in this paragraph |
| 033 | Input variable "&1" is specified multiple times |
| 034 | Output variable "&1" is specified multiple times |
| 035 | Chemical property is valid only for subject of type substance/mixture |
| 036 | New valid input variables were added to the "Input Variables" table |
| 037 | All variables have already been added to the "Input Variables" table |
| 038 | "&1"; "&2" |
| 039 | Variable "&1" is specified multiple times |
| 040 | Cannot proceed; paragraph "&1" is incomplete |
| 041 | Expression for output variable "&1" of equation "&2" is not entered |
| 042 | Equation "&1" has no final result |
| 043 | Input variables "&1" with data source type "&2" cannot be aggregated |
| 044 | Data period "&1" is not valid for data source type "&2" |
| 045 | Variable "&1" must be aggregated first in output "&2" |
| 046 | Result expression of output variable "&1" has not been entered |
| 047 | Results of type "Final" must have the same data periods, or must be blank |
| 048 | Result "&1" used in expression of "&2" has invalid usage period |
| 049 | Too many listed substance matches (&1); choose additional search criteria |
| 050 | &1 with ID "&2" already exists. Please use a unique ID. |
| 051 | Number range object EHFNDREQID is not specified correctly. |
| 052 | Pattern "&1" is unknown. Please select a valid pattern. |
| 053 | End of transition period date must be after the effective date. |
| 054 | A new version of compliance requirement "&1" cannot be created. |
| 055 | Effective date of version "&1" must be later than previous version. |
| 056 | Business process "&1" is already assigned. |
| 057 | Version name "&1" already exists. Please use a unique version name. |
| 058 | Application "&1" is already assigned. |
| 059 | Exemption "&1" is already assigned. |
| 060 | Unit "&1" is not valid. Please select a valid unit. |
| 061 | The "Unit" field is empty. Use the value help to select a valid unit. |
| 062 | Component type "&1" is already assigned. |
| 063 | Enter a positive threshold. |
| 064 | Activity "&1" is already assigned. |
| 065 | Cannot set status to Historical. Compliance requirement has not expired. |
| 066 | Listed substance "&1" is already assigned to the list. |
| 067 | Cannot release. Please select at least one processing level. |
| 068 | Cannot release. Processing level assignment for pattern "&1" is invalid. |
| 069 | Cannot delete the compliance requirement. See additional details. |
| 070 | Cannot delete the compliance requirement because it is already released. |
| 071 | Log on in language EN to specify compliance requirements. |
| 072 | For environmental limit "&1", please provide the requested values. |
| 073 | Please assign at least one substance list. |
| 074 | Please assign at least one listed substance to substance list "&1". |
| 075 | List type "&1" of substance list "&2" is not allowed. |
| 076 | Compliance requirement version successfully assigned to delivery "&1". |
| 077 | Compliance requirement version is not assigned to delivery "&1". |
| 078 | Listed substance "&1" does not exist. |
| 079 | Listed substance "&1" added to the list. |
| 080 | Selected process integration levels are not supported by pattern "&1". |
| 081 | Cannot create own version of compliance requirement with pattern "&1". |
| 082 | Use a group of substances instead of substance "&1". |
| 083 | Specified subject is not valid for data source type "Chemical Data" |
| 084 | No version of compliance requirement "&1" can be created. |
| 085 | A new version of compliance requirement "&1" cannot be created. |
| 086 | No version of SAP-delivered compliance requirement "&1" can be created. |
| 087 | You cannot save compliance requirements with more than one action. |
| 088 | Paragraph with ID "&1" already exists for this requirement. |
| 089 | Cannot set status to "Historical". The requirement is in use. |
| 090 | Default compliance requirement pattern "&1" cannot be changed. |
| 091 | Pattern ID "&1" is not in the allowed namespace. |
| 092 | No permits found with permit lifecycle 'Expired' or 'For Renewal' |
| 093 | Recipient does not exist for selected permits |
| 094 | Action: Set to 'Expired' and 'For Renewal' completed. |
| 095 | Activation status could not be changed due to a system error. |
| 096 | &1 of &2 compliance requirements activated. |
| 097 | &1 of &2 compliance requirements deactivated. |
| 098 | No business user assigned to system user &1. |
| 099 | Permit Lifecycle "&1" will be set to "&2" |
| 100 | ------- Start of messages for program R_EHFND_REQ_MIGRATION ---------- |
| 101 | -------- End of messages for program R_EHFND_REQ_MIGRATION ----------- |
| 102 | Client &1: List "&2" with DB_KEY &3 - UUID/language combi. not unique |
| 103 | Client &1: List "&2" with PARENT_KEY &3 has no root or structure node |
| 104 | Client &1: List "&2" with PARENT_KEY &3 has multiple structure nodes |
| 105 | Client &1: List "&2" with PARENT_KEY &3 has no valid root record |
| 106 | Client &1: List "&2" with DB_KEY &3 - UPDATE statement failed |
| 107 | Client &1: Error (&2) occurred while committing data into the database |
| 108 | Client &1: Routine &2 finished in &3 ms |
| 109 | Client &1: Finished in &2 ms |
| 110 | Program R_EHFND_REQ_MIGRATION finished in &1 ms |
| 111 | Client &1: Regulatory list type "&2" has no chemical property code |
| 112 | Client &1: Chemical property code "&2" has no regulatory list type |
| 113 | Client &1: Migration started |
| 114 | Client &1: Requirement "&2" - UUID/language combination not unique |
| 115 | Client &1: Requirement "&2" - UPDATE statement failed |
| 116 | Can't change Permit Lifecycle to Expired before the expiration date |
| 117 | Client &1: Requirement "&2" - error during insert |
| 118 | Client &1: Requirement name "&2" - INSERT statement failed |
| 119 | Client &1: Official name "&2" - INSERT statement failed |
| 120 | Client &1: Issuing organization "&2" - INSERT statement failed |
| 121 | Client &1: Country/region "&2" - INSERT statement failed. |
| 122 | Client &1: Regulatory list "&2" - INSERT statement failed |
| 123 | Client &1: Regulatory list name "&2" - INSERT statement failed |
| 124 | Client &1: OEL values "&2" - INSERT statement failed |
| 125 | Client &1: Regulatory list revision "&2" - UPDATE statement failed |
| 126 | Client &1: Listed substance with key "&2" cannot be converted |
| 128 | Client &1: Number range interval for EHFNDREQID - UPDATE failed |
| 129 | Client &1: Number range interval for EHFNDREQID - INSERT failed |
| 130 | Sorry, cannot delete the equation; it is used in the listed calculations |
| 131 | You can safely delete the equation. Do you want to proceed? |
| 132 | Equation deleted successfully |
| 133 | Sorry, cannot move a subordinate paragraph above the top-level paragraph |
| 134 | Sorry, you cannot move the top-level paragraph |
| 135 | Cannot delete env. limit; it is used in the following scenario activities |
| 136 | Environmental limit can be safely deleted. Do you want to proceed? |
| 137 | Check entered URL manually and see long text. |
| 138 | Check URL manually. URL returned HTTP status code &1 and may not exist. |
| 139 | Add a protocol, such as "http://", to the entered URL. |
| 140 | URL cannot be checked. Contact the system administrator. |
| 141 | Compliance requirement cannot be released; check URL availability. |
| 142 | Check URL manually. A live check can't be run due to missing certificates |
| 143 | Data period "&1" of result "&2" differs from period "&3" of result "&4" |
| 144 | To resolve the URL issues, see the long text. |
| 145 | Calculation result "&1" produced the following error: &2&3&4 |
| 146 | Equation "&1": &2&3&4 |
| 147 | OEL with duplicate key found: &1;&2;&3;&4 |
| 148 | Paragraph "&1": &2&3&4 |
| 149 | Check the URL. The website was moved. |
| 150 | The character "@" is not allowed within URLs. |
| 151 | The key word "JavaScript" is not allowed within URLs. |
| 152 | URL format or syntax does not match the RFC 2396 standard. |
| 153 | Composition type "&1" does not exist. |
| 154 | Cannot save the status. |
| 155 | Please delete the duplicate entries for the languages. |
| 156 | Please delete the duplicate entries for the modes of transport. |
| 157 | Please delete the duplicate entries for the enclosure variants. |
| 158 | URL does not pass security policy. |
| 159 | Please correct the mode of transport "&1". |
| 160 | Please correct the enclosure variant "&1". |
| 161 | Check URL, you can release only with valid URL. |
| 162 | Unit "&1" is not valid for chemical/physical property "&2". |
| 163 | Client &1: Chemical property &2 - INSERT failed |
| 164 | Client &1: Chemical property &2 - no description for language &3 |
| 165 | Client &1: Chemical property &2 text &3 - INSERT failed |
| 166 | Client &1: Chemical property &2 unit &3 - INSERT failed |
| 167 | Client &1: Chemical property &2 language &3 - text &4 already exists |
| 168 | Client &1: DB table &2 - UPDATE failed |
| 169 | Client &1: Error (&2) occurred while modifying reglulatory list data |
| 170 | Client &1: Chemical property &2 has no property key |
| 171 | Client &1: DB table &2 - INSERT failed |
| 172 | Client &1: DB table &2 - missing root node for value &3 |
| 173 | Client &1: DB table &2 - missing text node |
| 174 | Regulatory list data deleted successfully |
| 175 | Cannot delete. Regulatory list data is used in the following activities: |
| 176 | Regulatory list data can be safely deleted. Do you want to proceed? |
| 177 | Cannot release object. Select at least one country/region. |
| 178 | Client &1: DB table &2 - INSERT failed |
| 179 | Cannot release object. Enter country/region &2 without region. |
| 180 | Cannot release object. Select at least one language. |
| 181 | Cannot release object. Ctry/reg &2 is already assigned to regulation &3. |
| 182 | The code of the qualifying words must be unique. |
| 183 | The code for qualifying word &1 is empty. |
| 184 | No translation in English available for &1. |
| 185 | No translation in &1 available for &2. |
| 186 | Translation in &1 is not required for &2. |
| 187 | The ID of the segregation group must be unique. |
| 188 | Enter Description Template |
| 189 | The Description Template cannot be deleted because it is in use. |
| 190 | Cannot delete compliance requirement. Regulatory list data is used in it. |
| 191 | Paragraph data deleted successfully. |
| 192 | The sequence of the selection rules must be unique. |
| 193 | Please enter valid characters for Compliance Requirements |
| 194 | Invalid Status "&2" for Permit Lifecycle "&1", select another status. |
| 196 | Choose a date before the Expiration Date &1 |
| 300 | Compliance requirement cannot be activated because it is already used. |
| 301 | Compliance requirement &1 can't be deactivated via mass deactivation. |
| 302 | Changes cannot be confirmed. Compliance requirement is already used. |
| 303 | Compliance requirement is being activated in the background. |
| 304 | Compliance requirement &1 is deactivated. |
| 305 | Compliance Requirement was created with key &1 |
| 306 | Enter mandatory action parameters |
| 307 | Valid "from" date must be later than, or equal to &1 |
| 308 | &1 new compliance requirements were created |
| 309 | 1 new compliance requirement was created |
| 310 | Compliance requirement "&1" cannot be activated due to a technical error. |
| 311 | Cannot compare compliance requirement version with itself. |
| 312 | This compliance requirement does not have a previous active version. |
| 313 | There is no comparator for CRVs with this pattern. |
| 314 | Specify a country/region to narrow down search results. |
| 315 | You cannot create tasks in requirements with historical revisions only. |
| 316 | There are more compliance requirement changes than can be displayed. |
| 317 | Retention period not met for &1 |
| 318 | Incomplete task definitions exist for &1 |
| 319 | Incomplete task instances exist for &1 |
| 320 | Planned task instances exist for &1 |
| 321 | No task instances exist for &1 |
| 322 | Setting archiving status failed for &1 |
| 323 | Compliance requirement update is confirmed. |
| 324 | Cannot delete compliance requirement. Some tasks aren't 'Canceled'. |
| 325 | Cannot delete SAP-delivered compliance requirements. |
| 326 | Compliance requirement deleted successfully. |
| 327 | Cannot delete paragraph. Some tasks aren't 'Canceled'. |
| 328 | Cannot delete paragraph. Regulatory list data is still used. |
| 329 | Enter information for one of the following required fields: &1 |
| 330 | Entered issuing authority is not a valid business partner |
| 331 | Issuing organization is updated |
| 332 | Update translations for issuing organization |
| 333 | Cannot release object; assign english as required language for documents |
| 334 | No data to download |
| 335 | Error in uploading data |
| 336 | Excel uploaded; save is required |
| 337 | No file to upload |
| 338 | Error in generating Excel |
| 339 | Excel empty; no data to upload |
| 340 | Compliance requirement &1 can't be deactivated because it is still used. |
| 341 | Enter a Valid Number |
| 350 | Cannot add list. Regulatory list &1 is already assigned. |
| 351 | Enter a valid list ID number |
| 352 | Compliance requirement "&1" has already been activated |
| 353 | Select at least one business process scenario. |
| 355 | Waste code with the same key already exists |
| 356 | Open Compliance Requirement: &1 exists |
| 357 | Compliance Requirement &1 cannot be Archived, incorrect component |
| 358 | Compliance Requirement &1 to be Archived |
| 359 | Previous compliance requirement is deactivated. |
| 360 | Only one validity area for domain "waste" permits allowed |
| 361 | You can't save a compliance requirement with duplicate actions |
| 362 | Cannot edit permit. Add country/region in the location's address first |
| 363 | There�s no region entered for this location |
| 364 | The country/region of the location and permit do not match |
| 365 | Invalid Location. Add country/region in the location's address first |
| 366 | You can't copy an existing hazardous label. Please choose another label. |
| 367 | Deletion with "Permit Lifecycle: &1" is not allowed |
| 368 | Choose a date after the Effective Date &1 |
| 369 | Compliance requirement "&1" can't be deactivated due to technical errors |
| 370 | |
| 371 | Compliance requirement "&1" is the last active Version of its Compl. Req. |
| 372 | Regulatory Level Unit cannot be empty if value is filled |
| 373 | Only one upper limit is allowed for Waste Permit |
| 374 | Risk level with name "&1" already exists for language &2. |
| 375 | Risk level name for language &1 already exists. |
| 384 | Permit with number "&1" already exists. Please use a unique number |