CM_EHFND_CRR - Messages for Compliance Requirement Result
The following messages are stored in message class CM_EHFND_CRR: Messages for Compliance Requirement Result.
It is part of development package EHFND_BO_CRR in software component EHS-SUS-FND. This development package consists of objects that can be grouped under "Business Object Compliance Requirement Result".
It is part of development package EHFND_BO_CRR in software component EHS-SUS-FND. This development package consists of objects that can be grouped under "Business Object Compliance Requirement Result".
Message Nr ▲ | Message Text |
|---|---|
| 001 | Compliance assessment "&1" released. |
| 002 | Compliance assessment "&1" cannot be released due to unsaved drafts. |
| 003 | Compliance assessment "&1" cannot be released due to unknown status. |
| 004 | Available since &1. |
| 005 | Compliance assessment "&1" cannot be released due to invalid status. |
| 006 | Processor has been assigned to the compliance assessment. |
| 007 | Compliance assessment is already assigned to &1. |
| 008 | &1 does not have the required authorization for the assessment. |
| 009 | Processor has been removed from the compliance assessment. |
| 010 | New version of compliance assessment "&1" cannot be created. Log &2 |
| 011 | Compliance assessment "&1" cannot be released due to a technical error. |
| 012 | New version of compliance assessment "&1" has been created. |
| 013 | Cannot save compliance assessment "&1" due to errors. Log &2 |
| 014 | Cannot initiate assessment. See the log for &1. |
| 015 | An error occurred during release of compliance assessment "&1". Log &2 |
| 016 | Exemption "&1" is already assigned. |
| 017 | Compliance statement "&1" is already assigned. |
| 018 | Compliance assessment is inconsistent: &1. |
| 019 | Compliance assessment is released. |
| 020 | New version of the compliance assessment has been created. |
| 021 | User does not exist. |
| 022 | Compliance assessment has been created. |
| 023 | Cannot create compliance assessment "&1" due to errors. Log &2. |
| 024 | Cannot delete compliance assessment "&1" due to errors. |
| 025 | New version of compliance assessment "&1" cannot be created. |
| 026 | Logical key of the compliance assessment is invalid. |
| 027 | Compliance assessment inconsistent because CRV &1 does not exist. |
| 028 | Can't copy attachments for compliance assessment "&1". |
| 029 | Compliance assessment is locked: &1. |
| 050 | --- Validation classes --- |
| 051 | Enter a text with a maximum of &1 characters and spaces. |
| 052 | Subsection item "&1" is already assigned. |
| 053 | Subsection item "&1" missing in the database. |
| 054 | Subsection item &1 could not be read. |
| 100 | Action is not allowed for this compliance assessment. |
| 200 | --- Data Access Class --- |
| 201 | An error occurred during the insertion of a record. SY-SUBRC = &1. |
| 202 | Cannot insert into database. Primary key already exists. |
| 203 | An error occurred during the update of a record. SY-SUBRC = &1. |
| 204 | An error occurred during the deletion of a record. SY-SUBRC = &1. |
| 205 | A technical error occurred during generation of technical key. |
| 206 | Compliance assessment "&1" was deleted. |
| 207 | Compliance assessment not found. |
| 210 | --- Subnode determination class -- |
| 211 | Error in the subsection determination of CRR BO &1. |
| 212 | Error in the subsection determination of CRR subsection &1. |
| 300 | --- Silent Data migration --- |
| 301 | CRRs have been migrated correctly. |
| 302 | Marked non-PMA calc. CRR &1 without related in-progress CRR for deletion. |
| 303 | Number of updated in-progress CRRs in solution area &1: &2. |
| 304 | Number of deleted CRRs in PMA and non-PMA: &1. |
| 305 | Calculated CRRs differ from in-progress CRRs and were kept. |
| 306 | In-progress CRR &1 could not be locked and will be migrated again. |
| 307 | CRR &1 proc. status &2 from pat. &3 is deleted as logical key is invalid. |
| 308 | From &1 CRRs to migrate, &2 have a valid and &3 an invalid logical key. |
| 309 | From &1 valid CRRs, &2 have a PMA and &3 have non-PMA solution area. |
| 310 | Subpackage processing started for &1 CRRS. Remaining CRRs: &2. |
| 312 | Read &1 related calc. PMA CRRs for &2 in-progress PMA CRRs from database. |
| 313 | Read &1 related in-prog. non-PMA CRRs for &2 calc. non-PMA CRR from DB. |
| 314 | SDM locked &1 in-progress CRRs and left &2 unlocked with unknown pattern. |
| 315 | Update of the CRRs failed with error code: &1. |
| 318 | CRR &1 with proc.. status &2 is kept as SDM did not migrate it correctly. |
| 319 | The deletion flag could not be updated to &1. |