SAP ABAP Message Class GRFN_CLM (GRFN_CLM)
Basic Data
Hierarchy
☛
GRCFND_A (Software Component) GRC Foundation ABAP
⤷
GRC (Application Component) Governance, Risk and Compliance
⤷
GRFN_CLM (Package) Shared infrastructure for CLM integration
⤷
⤷
Attributes
| Message class | GRFN_CLM | |
| Short Description | ||
| Changed On | 20141106 | |
| Last Changed At | 194948 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 | Content importing/exporting started at &1 | The short text describes the object sufficiently | ||
| 2 | Content importing/exporting ended at &1 | The short text describes the object sufficiently | ||
| 3 | Simulation mode entered | The short text describes the object sufficiently | ||
| 4 | &1 objects have been processed | The short text describes the object sufficiently | ||
| 5 | Error found when processing object &1(&2) | The short text describes the object sufficiently | ||
| 6 | System starts to export entity &1 | The short text describes the object sufficiently | ||
| 7 | Entity &1 is exported successfully | The short text describes the object sufficiently | ||
| 8 | Object &1(&2) is exported successfully | The short text describes the object sufficiently | ||
| 9 | Valid-to date of object &1(&2) is &3 and cannot be extended | The short text describes the object sufficiently | ||
| 10 | Object &1(&2) has been created or updated | The short text describes the object sufficiently | ||
| 11 | Object ID is empty | The short text describes the object sufficiently | ||
| 12 | Entity &1 is not correct or supported | The short text describes the object sufficiently | ||
| 13 | Valid from date of object &1(&2) is not correct | The short text describes the object sufficiently | ||
| 14 | Valid to date of object &1(&2) is not correct | The short text describes the object sufficiently | ||
| 15 | Valid from date &3 of object &1(&2) is later than its valid to date &4 | The short text describes the object sufficiently | ||
| 16 | No overlap time between object &1(&2) and &3(&4) | The short text describes the object sufficiently | ||
| 17 | Object &1(&2) cannot be changed because there are some case objects | The short text describes the object sufficiently | ||
| 18 | Attr value of &2 in &1 is not compatible with system configuration | The short text describes the object sufficiently | ||
| 19 | Object &1 does not exist; maintain object &2 again | The short text describes the object sufficiently | ||
| 20 | Orgunit &1 cannot be assigned to regulation and corporate simultaneously | The short text describes the object sufficiently | ||
| 21 | &1's parent &2 does not exsit | The short text describes the object sufficiently | ||
| 22 | System does not contain any OLSP | The short text describes the object sufficiently | ||
| 23 | OLSP &1 is not included in the system list | The short text describes the object sufficiently | ||
| 24 | Validity of object &1(&2) is outside of its parent &3(&4) | The short text describes the object sufficiently | ||
| 25 | Object &1(&2) does not exist or is in error state | The short text describes the object sufficiently | ||
| 26 | Field &1 value of &2(&3) is not compatible with the defined value set | The short text describes the object sufficiently | ||
| 27 | Maintain the parent of &1(&2) in the XML file | The short text describes the object sufficiently | ||
| 28 | Risk source of object &1 is empty for risk &2 | The short text describes the object sufficiently | ||
| 29 | Relation between &1(&2) and &3(&4) does not exist in the system and XML | The short text describes the object sufficiently | ||
| 30 | Risk assertion &1 is not coming from account group &2(&3) | The short text describes the object sufficiently | ||
| 31 | Maintain the balance of account &1(&2) in version &3 only | The short text describes the object sufficiently | ||
| 32 | The relation between &1(&2) and &3(&4) is already existed | The short text describes the object sufficiently | ||
| 33 | Failed to find HR key of object &3(&4) for infotype &1 and subtype &2 | The short text describes the object sufficiently | ||
| 34 | Object &1(&2) is marked for update but does not exist in the system | The short text describes the object sufficiently | ||
| 35 | Object &1(&2) is marked for creation but it already exists in the system | The short text describes the object sufficiently | ||
| 36 | Field &1 is ignored as it is configured as hidden for regulation &2 | The short text describes the object sufficiently | ||
| 37 | Currency &1 is not valid | The short text describes the object sufficiently | ||
| 38 | Country &1 is not valid | The short text describes the object sufficiently | ||
| 39 | Region &1 is not valid | The short text describes the object sufficiently | ||
| 40 | Value &3 in field &2 of table &1 is not valid | The short text describes the object sufficiently | ||
| 41 | Country &1 doesn't have a region &2 | The short text describes the object sufficiently | ||
| 42 | Mandatory field &1 of object &2(&3) is an initial value | The short text describes the object sufficiently | ||
| 43 | Account-from is greater than Account-to of object &1(&2) | The short text describes the object sufficiently | ||
| 44 | Object &1(&2) has multiple risk source at the same time for risk &3(&4) | The short text describes the object sufficiently | ||
| 45 | Risk source of object &1 should be the parent object &2 for risk &3 | The short text describes the object sufficiently | ||
| 46 | Risk &1(&2) of object &3(&4) is not assigned to the risk source | The short text describes the object sufficiently | ||
| 47 | Maintain balance of &1(&2) in timeframe &3 and currency &4 only | The short text describes the object sufficiently | ||
| 48 | Scoping materiality analysis frequency not maintained in IMG node | The short text describes the object sufficiently | ||
| 49 | No significant threshold data maintained in the system | The short text describes the object sufficiently | ||
| 50 | Metadata loaded successfully for entity &1 | The short text describes the object sufficiently | ||
| 51 | Failed to load infotype data of object &1(&2) | The short text describes the object sufficiently | ||
| 52 | Object &1(&2) is skipped because it does not belong to entity &3 | The short text describes the object sufficiently | ||
| 53 | Failed to load regulation specific attributes of object &1(&2) | The short text describes the object sufficiently | ||
| 54 | Failed to load parent of object &1(&2) | The short text describes the object sufficiently | ||
| 55 | Failed to load risk assertion data of account group &1(&2) | The short text describes the object sufficiently | ||
| 56 | Failed to load balance data of account group &1(&2) | The short text describes the object sufficiently | ||
| 57 | Program exit because the subtype of regulation &1 is not maintained | The short text describes the object sufficiently | ||
| 58 | Program exit because regulation configuration is not provided | The short text describes the object sufficiently | ||
| 59 | Program exit because regulation configuration &1 exists with ID &2 | The short text describes the object sufficiently | ||
| 60 | Failed to load relation data of object &1(&2) | The short text describes the object sufficiently | ||
| 61 | No significant threshold data for timeframe &1 and year &2 in the system | The short text describes the object sufficiently | ||
| 62 | &1(&2) is not a significant account and cannot be assigned to &3(&4) | The short text describes the object sufficiently | ||
| 63 | Editting is not allowed because control rule assignments exist | The short text describes the object sufficiently | ||
| 64 | The regulation ID &1 of object &2(&3) must be from its parent | The short text describes the object sufficiently | ||
| 65 | Object &1(&2)'s parent &3(&4) is in error state | The short text describes the object sufficiently | ||
| 66 | Risk &1(&2) of object &3(&4) is not assigned to its parent | The short text describes the object sufficiently | ||
| 67 | The asserstion of &1 is not coming from account group &2(&3) | The short text describes the object sufficiently | ||
| 68 | The account group &1(&2) of control &3(&4) is not from parent subprocess | The short text describes the object sufficiently | ||
| 69 | Importing is triggered from &1 | The short text describes the object sufficiently | ||
| 70 | Exit on error is on | The short text describes the object sufficiently | ||
| 71 | Exit on error is off | The short text describes the object sufficiently | ||
| 72 | The current importing is an initial upload | The short text describes the object sufficiently | ||
| 73 | The indirect risk model(AS5) is used | The short text describes the object sufficiently | ||
| 74 | The direct risk model(SAS31) is used | The short text describes the object sufficiently | ||
| 75 | Start date is &1 and end date is &2 | The short text describes the object sufficiently | ||
| 76 | The parent &1 of regulation requirement &2 is not assigned to &3(&4) | The short text describes the object sufficiently | ||
| 77 | Key date is &1 | The short text describes the object sufficiently | ||
| 78 | The exported data is empty. | The short text describes the object sufficiently | ||
| 79 | Please select at least one entity | The short text describes the object sufficiently | ||
| 80 | Export: Object ID &1 mapping GUID &2 | The short text describes the object sufficiently | ||
| 81 | At least select one entry to process | The short text describes the object sufficiently | ||
| 82 | Data Sources have been exported successfully | The short text describes the object sufficiently | ||
| 83 | Parse BRF Plus Error: &1 | The short text describes the object sufficiently | ||
| 84 | Please select the correct file to upload | The short text describes the object sufficiently | ||
| 85 | Only file with extension name “ZIP” can be uploaded | The short text describes the object sufficiently | ||
| 86 | Error occurred when override event in GAF | The short text describes the object sufficiently | ||
| 87 | "Status" is mandatory | The short text describes the object sufficiently | ||
| 88 | Business Rules have been exported successfully | The short text describes the object sufficiently | ||
| 89 | &1 Business Rules have been processed, &2 of them have error | The short text describes the object sufficiently | ||
| 90 | &1 Data Sources have been processed, &2 of them have error | The short text describes the object sufficiently | ||
| 91 | Import: Object ID &1 mapping GUID &2 | The short text describes the object sufficiently | ||
| 92 | Content of the uploaded file is incorrect | The short text describes the object sufficiently | ||
| 93 | Entities with invalid connector status will not be imported into system | The short text describes the object sufficiently | ||
| 94 | Error occurred when validating the connector of Data source “&1”: &2 | The short text describes the object sufficiently | ||
| 95 | The rules you imported will be saved as content templates | The short text describes the object sufficiently | ||
| 96 | “Main Connector” is mandatory | The short text describes the object sufficiently | ||
| 97 | The status of main connector should be validated | The short text describes the object sufficiently | ||
| 98 | &1 is duplicated | The short text describes the object sufficiently | ||
| 99 | &1 does not exist | The short text describes the object sufficiently | ||
| 100 | Data upload complete; continue to import data to system | The short text describes the object sufficiently | ||
| 101 | Data upload has failed; check the application log | The short text describes the object sufficiently | ||
| 102 | Data upload has started; wait till process has completed | The short text describes the object sufficiently | ||
| 103 | Data has been transformed to XML and saved in file &1&2&3&4 | The short text describes the object sufficiently | ||
| 104 | &1 is used in sheet &2; but it does not exist | The short text describes the object sufficiently | ||
| 105 | &1 regulation specific value is maintained; but object does not exist | The short text describes the object sufficiently | ||
| 106 | Data has been saved to dataset &1 | The short text describes the object sufficiently | ||
| 107 | No XML data supplied | The short text describes the object sufficiently | ||
| 108 | &1 is used before being created | The short text describes the object sufficiently | ||
| 109 | &1 is found in system, ID &2 | The short text describes the object sufficiently | ||
| 110 | There are multiple objects in system named &1, a new ID(&2) is generated | The short text describes the object sufficiently | ||
| 111 | ID(&2) is generated for &1 | The short text describes the object sufficiently | ||
| 112 | Some of the selected languages aren't supported in GRC | The short text describes the object sufficiently | ||
| 113 | regulation does not exist. | The short text describes the object sufficiently | ||
| 114 | regulation '&1' does not exist. | The short text describes the object sufficiently | ||
| 115 | Subprocess &1 without controls can not be set to local changes NO. | The short text describes the object sufficiently | ||
| 116 | Subprocess &2 has been assigned to Orgunit &1 | The short text describes the object sufficiently | ||
| 117 | In Orgunit &1, subprocess &2 is duplicated | The short text describes the object sufficiently | ||
| 118 | &1 with initial ID found - cannot be handled by CLM | The short text describes the object sufficiently | ||
| 119 | Unknow BRF Plus ID &2 on Rule &1 | The short text describes the object sufficiently | ||
| 120 | BRF+ application GRFN_AM_RUNTIME configuration error, check note 1588564 | The short text describes the object sufficiently | ||
| 121 | BRF Plus &2 on Rule &1 has been exported | The short text describes the object sufficiently | ||
| 122 | BRF Plus has been imported | The short text describes the object sufficiently | ||
| 123 | BRF Plus &1 fail to import | The short text describes the object sufficiently |
History
| Last changed on/by | 20141106 | SAP | |
| SAP Release Created in | 600 |