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
⤷ 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 | 001 | Content importing/exporting started at &1 | The short text describes the object sufficiently | |
2 | 002 | Content importing/exporting ended at &1 | The short text describes the object sufficiently | |
3 | 003 | Simulation mode entered | The short text describes the object sufficiently | |
4 | 004 | &1 objects have been processed | The short text describes the object sufficiently | |
5 | 005 | Error found when processing object &1(&2) | The short text describes the object sufficiently | |
6 | 006 | System starts to export entity &1 | The short text describes the object sufficiently | |
7 | 007 | Entity &1 is exported successfully | The short text describes the object sufficiently | |
8 | 008 | Object &1(&2) is exported successfully | The short text describes the object sufficiently | |
9 | 009 | Valid-to date of object &1(&2) is &3 and cannot be extended | The short text describes the object sufficiently | |
10 | 010 | Object &1(&2) has been created or updated | The short text describes the object sufficiently | |
11 | 011 | Object ID is empty | The short text describes the object sufficiently | |
12 | 012 | Entity &1 is not correct or supported | The short text describes the object sufficiently | |
13 | 013 | Valid from date of object &1(&2) is not correct | The short text describes the object sufficiently | |
14 | 014 | Valid to date of object &1(&2) is not correct | The short text describes the object sufficiently | |
15 | 015 | Valid from date &3 of object &1(&2) is later than its valid to date &4 | The short text describes the object sufficiently | |
16 | 016 | No overlap time between object &1(&2) and &3(&4) | The short text describes the object sufficiently | |
17 | 017 | Object &1(&2) cannot be changed because there are some case objects | The short text describes the object sufficiently | |
18 | 018 | Attr value of &2 in &1 is not compatible with system configuration | The short text describes the object sufficiently | |
19 | 019 | Object &1 does not exist; maintain object &2 again | The short text describes the object sufficiently | |
20 | 020 | Orgunit &1 cannot be assigned to regulation and corporate simultaneously | The short text describes the object sufficiently | |
21 | 021 | &1's parent &2 does not exsit | The short text describes the object sufficiently | |
22 | 022 | System does not contain any OLSP | The short text describes the object sufficiently | |
23 | 023 | OLSP &1 is not included in the system list | The short text describes the object sufficiently | |
24 | 024 | Validity of object &1(&2) is outside of its parent &3(&4) | The short text describes the object sufficiently | |
25 | 025 | Object &1(&2) does not exist or is in error state | The short text describes the object sufficiently | |
26 | 026 | Field &1 value of &2(&3) is not compatible with the defined value set | The short text describes the object sufficiently | |
27 | 027 | Maintain the parent of &1(&2) in the XML file | The short text describes the object sufficiently | |
28 | 028 | Risk source of object &1 is empty for risk &2 | The short text describes the object sufficiently | |
29 | 029 | Relation between &1(&2) and &3(&4) does not exist in the system and XML | The short text describes the object sufficiently | |
30 | 030 | Risk assertion &1 is not coming from account group &2(&3) | The short text describes the object sufficiently | |
31 | 031 | Maintain the balance of account &1(&2) in version &3 only | The short text describes the object sufficiently | |
32 | 032 | The relation between &1(&2) and &3(&4) is already existed | The short text describes the object sufficiently | |
33 | 033 | Failed to find HR key of object &3(&4) for infotype &1 and subtype &2 | The short text describes the object sufficiently | |
34 | 034 | Object &1(&2) is marked for update but does not exist in the system | The short text describes the object sufficiently | |
35 | 035 | Object &1(&2) is marked for creation but it already exists in the system | The short text describes the object sufficiently | |
36 | 036 | Field &1 is ignored as it is configured as hidden for regulation &2 | The short text describes the object sufficiently | |
37 | 037 | Currency &1 is not valid | The short text describes the object sufficiently | |
38 | 038 | Country &1 is not valid | The short text describes the object sufficiently | |
39 | 039 | Region &1 is not valid | The short text describes the object sufficiently | |
40 | 040 | Value &3 in field &2 of table &1 is not valid | The short text describes the object sufficiently | |
41 | 041 | Country &1 doesn't have a region &2 | The short text describes the object sufficiently | |
42 | 042 | Mandatory field &1 of object &2(&3) is an initial value | The short text describes the object sufficiently | |
43 | 043 | Account-from is greater than Account-to of object &1(&2) | The short text describes the object sufficiently | |
44 | 044 | Object &1(&2) has multiple risk source at the same time for risk &3(&4) | The short text describes the object sufficiently | |
45 | 045 | Risk source of object &1 should be the parent object &2 for risk &3 | The short text describes the object sufficiently | |
46 | 046 | Risk &1(&2) of object &3(&4) is not assigned to the risk source | The short text describes the object sufficiently | |
47 | 047 | Maintain balance of &1(&2) in timeframe &3 and currency &4 only | The short text describes the object sufficiently | |
48 | 048 | Scoping materiality analysis frequency not maintained in IMG node | The short text describes the object sufficiently | |
49 | 049 | No significant threshold data maintained in the system | The short text describes the object sufficiently | |
50 | 050 | Metadata loaded successfully for entity &1 | The short text describes the object sufficiently | |
51 | 051 | Failed to load infotype data of object &1(&2) | The short text describes the object sufficiently | |
52 | 052 | Object &1(&2) is skipped because it does not belong to entity &3 | The short text describes the object sufficiently | |
53 | 053 | Failed to load regulation specific attributes of object &1(&2) | The short text describes the object sufficiently | |
54 | 054 | Failed to load parent of object &1(&2) | The short text describes the object sufficiently | |
55 | 055 | Failed to load risk assertion data of account group &1(&2) | The short text describes the object sufficiently | |
56 | 056 | Failed to load balance data of account group &1(&2) | The short text describes the object sufficiently | |
57 | 057 | Program exit because the subtype of regulation &1 is not maintained | The short text describes the object sufficiently | |
58 | 058 | Program exit because regulation configuration is not provided | The short text describes the object sufficiently | |
59 | 059 | Program exit because regulation configuration &1 exists with ID &2 | The short text describes the object sufficiently | |
60 | 060 | Failed to load relation data of object &1(&2) | The short text describes the object sufficiently | |
61 | 061 | No significant threshold data for timeframe &1 and year &2 in the system | The short text describes the object sufficiently | |
62 | 062 | &1(&2) is not a significant account and cannot be assigned to &3(&4) | The short text describes the object sufficiently | |
63 | 063 | Editting is not allowed because control rule assignments exist | The short text describes the object sufficiently | |
64 | 064 | The regulation ID &1 of object &2(&3) must be from its parent | The short text describes the object sufficiently | |
65 | 065 | Object &1(&2)'s parent &3(&4) is in error state | The short text describes the object sufficiently | |
66 | 066 | Risk &1(&2) of object &3(&4) is not assigned to its parent | The short text describes the object sufficiently | |
67 | 067 | The asserstion of &1 is not coming from account group &2(&3) | The short text describes the object sufficiently | |
68 | 068 | The account group &1(&2) of control &3(&4) is not from parent subprocess | The short text describes the object sufficiently | |
69 | 069 | Importing is triggered from &1 | The short text describes the object sufficiently | |
70 | 070 | Exit on error is on | The short text describes the object sufficiently | |
71 | 071 | Exit on error is off | The short text describes the object sufficiently | |
72 | 072 | The current importing is an initial upload | The short text describes the object sufficiently | |
73 | 073 | The indirect risk model(AS5) is used | The short text describes the object sufficiently | |
74 | 074 | The direct risk model(SAS31) is used | The short text describes the object sufficiently | |
75 | 075 | Start date is &1 and end date is &2 | The short text describes the object sufficiently | |
76 | 076 | The parent &1 of regulation requirement &2 is not assigned to &3(&4) | The short text describes the object sufficiently | |
77 | 077 | Key date is &1 | The short text describes the object sufficiently | |
78 | 078 | The exported data is empty. | The short text describes the object sufficiently | |
79 | 079 | Please select at least one entity | The short text describes the object sufficiently | |
80 | 080 | Export: Object ID &1 mapping GUID &2 | The short text describes the object sufficiently | |
81 | 081 | At least select one entry to process | The short text describes the object sufficiently | |
82 | 082 | Data Sources have been exported successfully | The short text describes the object sufficiently | |
83 | 083 | Parse BRF Plus Error: &1 | The short text describes the object sufficiently | |
84 | 084 | Please select the correct file to upload | The short text describes the object sufficiently | |
85 | 085 | Only file with extension name “ZIP” can be uploaded | The short text describes the object sufficiently | |
86 | 086 | Error occurred when override event in GAF | The short text describes the object sufficiently | |
87 | 087 | "Status" is mandatory | The short text describes the object sufficiently | |
88 | 088 | Business Rules have been exported successfully | The short text describes the object sufficiently | |
89 | 089 | &1 Business Rules have been processed, &2 of them have error | The short text describes the object sufficiently | |
90 | 090 | &1 Data Sources have been processed, &2 of them have error | The short text describes the object sufficiently | |
91 | 091 | Import: Object ID &1 mapping GUID &2 | The short text describes the object sufficiently | |
92 | 092 | Content of the uploaded file is incorrect | The short text describes the object sufficiently | |
93 | 093 | Entities with invalid connector status will not be imported into system | The short text describes the object sufficiently | |
94 | 094 | Error occurred when validating the connector of Data source “&1”: &2 | The short text describes the object sufficiently | |
95 | 095 | The rules you imported will be saved as content templates | The short text describes the object sufficiently | |
96 | 096 | “Main Connector” is mandatory | The short text describes the object sufficiently | |
97 | 097 | The status of main connector should be validated | The short text describes the object sufficiently | |
98 | 100 | &1 is duplicated | The short text describes the object sufficiently | |
99 | 101 | &1 does not exist | The short text describes the object sufficiently | |
100 | 102 | Data upload complete; continue to import data to system | The short text describes the object sufficiently | |
101 | 103 | Data upload has failed; check the application log | The short text describes the object sufficiently | |
102 | 104 | Data upload has started; wait till process has completed | The short text describes the object sufficiently | |
103 | 105 | Data has been transformed to XML and saved in file &1&2&3&4 | The short text describes the object sufficiently | |
104 | 106 | &1 is used in sheet &2; but it does not exist | The short text describes the object sufficiently | |
105 | 107 | &1 regulation specific value is maintained; but object does not exist | The short text describes the object sufficiently | |
106 | 108 | Data has been saved to dataset &1 | The short text describes the object sufficiently | |
107 | 109 | No XML data supplied | The short text describes the object sufficiently | |
108 | 110 | &1 is used before being created | The short text describes the object sufficiently | |
109 | 111 | &1 is found in system, ID &2 | The short text describes the object sufficiently | |
110 | 112 | There are multiple objects in system named &1, a new ID(&2) is generated | The short text describes the object sufficiently | |
111 | 113 | ID(&2) is generated for &1 | The short text describes the object sufficiently | |
112 | 114 | Some of the selected languages aren't supported in GRC | The short text describes the object sufficiently | |
113 | 115 | regulation does not exist. | The short text describes the object sufficiently | |
114 | 116 | regulation '&1' does not exist. | The short text describes the object sufficiently | |
115 | 117 | Subprocess &1 without controls can not be set to local changes NO. | The short text describes the object sufficiently | |
116 | 130 | Subprocess &2 has been assigned to Orgunit &1 | The short text describes the object sufficiently | |
117 | 131 | In Orgunit &1, subprocess &2 is duplicated | The short text describes the object sufficiently | |
118 | 200 | &1 with initial ID found - cannot be handled by CLM | The short text describes the object sufficiently | |
119 | 300 | Unknow BRF Plus ID &2 on Rule &1 | The short text describes the object sufficiently | |
120 | 301 | BRF+ application GRFN_AM_RUNTIME configuration error, check note 1588564 | The short text describes the object sufficiently | |
121 | 302 | BRF Plus &2 on Rule &1 has been exported | The short text describes the object sufficiently | |
122 | 303 | BRF Plus has been imported | The short text describes the object sufficiently | |
123 | 304 | 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 |