SAP ABAP Message Class GRFN_MIGRATION (Migration messages)
Basic Data
Hierarchy
☛
GRCFND_A (Software Component) GRC Foundation ABAP
⤷ GRC-RM (Application Component) GRC Risk Management
⤷ GRFN_MIGRATION (Package) All Reports for migration
⤷ GRC-RM (Application Component) GRC Risk Management
⤷ GRFN_MIGRATION (Package) All Reports for migration
Attributes
Message class | GRFN_MIGRATION | |
Short Description | Migration messages | |
Changed On | 20141106 | |
Last Changed At | 192242 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 001 | Migration report &1 started at &2 | The short text describes the object sufficiently | |
2 | 002 | Migration report &1 completed at &2 | The short text describes the object sufficiently | |
3 | 003 | Position the cursor on a line in the list | The short text describes the object sufficiently | |
4 | 004 | Select only one entry | The short text describes the object sufficiently | |
5 | 005 | Execute the prerequisite report before executing this report | The short text describes the object sufficiently | |
6 | 010 | &1 global compliance roles &2 migrated successfully | The short text describes the object sufficiently | |
7 | 011 | &1 regulation-specific roles (SOX) &2 migrated successfully | The short text describes the object sufficiently | |
8 | 012 | No customer-extended selection procedure found; migration not necessary | The short text describes the object sufficiently | |
9 | 013 | &1 global compliance roles &2 need to be migrated | The short text describes the object sufficiently | |
10 | 014 | &1 regulation-specific roles (SOX) &2 need to be migrated | The short text describes the object sufficiently | |
11 | 015 | Migration of &1 global compliance roles &2 failed | The short text describes the object sufficiently | |
12 | 016 | Migration of &1 regulation-specific roles (SOX) &2 failed | The short text describes the object sufficiently | |
13 | 017 | Simulation mode on; will not commit to DB | The short text describes the object sufficiently | |
14 | 018 | &1 customer-extended selection procedure &2 migrated successfully | The short text describes the object sufficiently | |
15 | 019 | Migration of &1 customer-extended selection procedure &2 failed | The short text describes the object sufficiently | |
16 | 020 | Document &1 (2.0) attached to activity &2 needs to be migrated | The short text describes the object sufficiently | |
17 | 021 | New document (3.0) &1 has been created on object &2 as replacement for &3 | The short text describes the object sufficiently | |
18 | 022 | Error in migration of document &1 (2.0) | The short text describes the object sufficiently | |
19 | 023 | Document &1 already migrated to document &2 | The short text describes the object sufficiently | |
20 | 024 | Document &1 (2.0) attached to risk &2 needs to be migrated | The short text describes the object sufficiently | |
21 | 025 | Document &1 (2.0) attached to incident &2 needs to be migrated | The short text describes the object sufficiently | |
22 | 026 | Document &1 (2.0) needs to be migrated | The short text describes the object sufficiently | |
23 | 027 | Migration of &1 customer-extended selection procedure text failed | The short text describes the object sufficiently | |
24 | 029 | Enter an RFC destination | The short text describes the object sufficiently | |
25 | 030 | &1 records have been updated to table &2 | The short text describes the object sufficiently | |
26 | 031 | &1 records of &2 converted successfully | The short text describes the object sufficiently | |
27 | 032 | &1 converted with errors | The short text describes the object sufficiently | |
28 | 033 | MIC migration for common configuration data successful | The short text describes the object sufficiently | |
29 | 034 | MIC migration for common configuration data failed | The short text describes the object sufficiently | |
30 | 035 | No CDF infotype found in T777D | The short text describes the object sufficiently | |
31 | 036 | MIC migration for configure data is successful | The short text describes the object sufficiently | |
32 | 037 | MIC migration for configure data failed | The short text describes the object sufficiently | |
33 | 038 | &1 records of &2 are downloaded at &3 | The short text describes the object sufficiently | |
34 | 039 | &1 records of &2 are converted successfully in simulation mode | The short text describes the object sufficiently | |
35 | 040 | BC Set for role relevance (BC_SET_ROLES) successfully activated | The short text describes the object sufficiently | |
36 | 041 | BC Set for role relevance (BC_SET_ROLES) could not be activated | The short text describes the object sufficiently | |
37 | 042 | For details see BC Set activation log: &1 | The short text describes the object sufficiently | |
38 | 043 | MIC migration for common configuration data successful in simulation mode | The short text describes the object sufficiently | |
39 | 045 | Risk catalog successfully generated | The short text describes the object sufficiently | |
40 | 046 | Risk catalog failed to generate | The short text describes the object sufficiently | |
41 | 047 | Risks are converted with failure | The short text describes the object sufficiently | |
42 | 048 | Regulation hierarchy failed to generate in simulation mode | The short text describes the object sufficiently | |
43 | 049 | Regulation &1 already exists; program will not create new one | The short text describes the object sufficiently | |
44 | 050 | Regulation name cannot be empty | The short text describes the object sufficiently | |
45 | 051 | Regulation group name cannot be empty | The short text describes the object sufficiently | |
46 | 052 | Choose regulation from dropdown list | The short text describes the object sufficiently | |
47 | 053 | Regulation hierarchy successfully generated with ID &1 | The short text describes the object sufficiently | |
48 | 054 | Regulation hierarchy failed to generate | The short text describes the object sufficiently | |
49 | 055 | Regulation &1 does not have regulation object | The short text describes the object sufficiently | |
50 | 056 | &1 records of task plan group successfully converted | The short text describes the object sufficiently | |
51 | 057 | &1 records of task plan successfully converted | The short text describes the object sufficiently | |
52 | 058 | &1 records in Case tables successfully converted | The short text describes the object sufficiently | |
53 | 059 | &1 records of Case table timeframe successfully converted | The short text describes the object sufficiently | |
54 | 060 | Remediation plan owner successfully assigned | The short text describes the object sufficiently | |
55 | 061 | Risk driver cannot be empty | The short text describes the object sufficiently | |
56 | 062 | Risk impact cannot be empty | The short text describes the object sufficiently | |
57 | 063 | User &1 is assigned to remediation plan &2 as owner | The short text describes the object sufficiently | |
58 | 064 | Cannot assign user &1 to remediation plan &2 as owner | The short text describes the object sufficiently | |
59 | 065 | Object table GRPCOBJTYPERESP is empty; no upgrade initiated | The short text describes the object sufficiently | |
60 | 066 | &1 records of object responsible person are converted successfully | The short text describes the object sufficiently | |
61 | 067 | &1 records of object responsible person are converted with failure | The short text describes the object sufficiently | |
62 | 068 | All records in case table successfully converted in simulation mode | The short text describes the object sufficiently | |
63 | 070 | Agenslot mapping table GRPCAGENTSLOTMAP is empty; no upgrade initiated | The short text describes the object sufficiently | |
64 | 071 | Cannot find related role of &1 in GRPCROLEMAP | The short text describes the object sufficiently | |
65 | 072 | Role-task table GRPCROLETASK is empty; no upgrade initiated | The short text describes the object sufficiently | |
66 | 073 | &1 records of agent slot are converted successfully | The short text describes the object sufficiently | |
67 | 074 | &1 records of agent slot are converted with failure | The short text describes the object sufficiently | |
68 | 075 | As entry &1 &2 &3 &4 exists, no data has been inserted | The short text describes the object sufficiently | |
69 | 076 | &1 records of org. unit attribute are converted successfully | The short text describes the object sufficiently | |
70 | 077 | &1 records are converted with failure | The short text describes the object sufficiently | |
71 | 080 | Role assignment table HRP5303 is empty; no upgrade initiated | The short text describes the object sufficiently | |
72 | 081 | &1 records of role assignment are converted successfully | The short text describes the object sufficiently | |
73 | 082 | &1 records of role assignment are converted with failure | The short text describes the object sufficiently | |
74 | 083 | PFCG role &1 conversion failed | The short text describes the object sufficiently | |
75 | 084 | & PFCG roles are failed during generation | The short text describes the object sufficiently | |
76 | 085 | &1 roles have been inserted into table GRPCROLEMAP | The short text describes the object sufficiently | |
77 | 086 | Role &1 has been converted to PFGC role | The short text describes the object sufficiently | |
78 | 087 | PFCG role &1 conversion failed, &2 | The short text describes the object sufficiently | |
79 | 088 | Old role &1 has already been converted to PFCG role | The short text describes the object sufficiently | |
80 | 089 | Check and fix the errors, then re-execute the program | The short text describes the object sufficiently | |
81 | 090 | There is no attribute value for frequency | The short text describes the object sufficiently | |
82 | 091 | There is no attribute value text for frequency | The short text describes the object sufficiently | |
83 | 092 | There is no attribute value for timeframe | The short text describes the object sufficiently | |
84 | 093 | There is no attribute value text for timeframe | The short text describes the object sufficiently | |
85 | 094 | Frequency and timeframe converted successfully | The short text describes the object sufficiently | |
86 | 095 | Frequency and timeframe converted with failure | The short text describes the object sufficiently | |
87 | 096 | No log found | The short text describes the object sufficiently | |
88 | 097 | Risk catalog successfully generated in simulation mode | The short text describes the object sufficiently | |
89 | 098 | Risk catalog generation failed in simulation mode | The short text describes the object sufficiently | |
90 | 099 | Migration error &1 | The short text describes the object sufficiently | |
91 | 100 | MIC master data has been downloaded successfully | The short text describes the object sufficiently | |
92 | 101 | MIC master data has been downloaded with errors | The short text describes the object sufficiently | |
93 | 102 | Infotype &1 is not in MIC system | The short text describes the object sufficiently | |
94 | 103 | Infotype &1 is not in PC system | The short text describes the object sufficiently | |
95 | 104 | Error occurred when creating risk category | The short text describes the object sufficiently | |
96 | 105 | Infotype table &1 is not in PC system | The short text describes the object sufficiently | |
97 | 106 | Data downloaded: &1 | The short text describes the object sufficiently | |
98 | 109 | Execution of migration program completed | The short text describes the object sufficiently | |
99 | 110 | Execution of upgrade program completed | The short text describes the object sufficiently | |
100 | 111 | Migration of &1 account group significance failed | The short text describes the object sufficiently | |
101 | 112 | &1 account group significance migrated successfully | The short text describes the object sufficiently | |
102 | 114 | Cannot upgrade remediation plan: &1 | The short text describes the object sufficiently | |
103 | 118 | &1 records of table &2 converted with failure | The short text describes the object sufficiently | |
104 | 120 | MIC document has been migrated | The short text describes the object sufficiently | |
105 | 121 | MIC document has been migrated with errors | The short text describes the object sufficiently | |
106 | 125 | Priorities of control objective category &1, &2 cannot be the same | The short text describes the object sufficiently | |
107 | 126 | Control objective category was converted successfully | The short text describes the object sufficiently | |
108 | 127 | Conversion of control objective category failed | The short text describes the object sufficiently | |
109 | 131 | No CO found for control &1 in &2 - &3 | The short text describes the object sufficiently | |
110 | 132 | No CO category chosen for control &1 in &2 - &3 | The short text describes the object sufficiently | |
111 | 133 | Insert group &1 for control &2 in &3 - &4 | The short text describes the object sufficiently | |
112 | 134 | Insert subgroup &1 for control &2 in &3 - &4 | The short text describes the object sufficiently | |
113 | 135 | &1 control group has been converted | The short text describes the object sufficiently | |
114 | 136 | &2 control subgroup has been converted | The short text describes the object sufficiently | |
115 | 138 | Simulation result: PFCG role &1 will be converted from old role &2 | The short text describes the object sufficiently | |
116 | 139 | Simulation result: &1 records can be updated to table &2 | The short text describes the object sufficiently | |
117 | 140 | Execution of upgrade program carried out in simulation mode | The short text describes the object sufficiently | |
118 | 141 | Execution of migration program carried out in simulation mode | The short text describes the object sufficiently | |
119 | 142 | Risks have been converted | The short text describes the object sufficiently | |
120 | 150 | Conversion of related links has failed | The short text describes the object sufficiently | |
121 | 151 | Scoping materiality analysis frequency not maintained in IMG node | Space: object requires documentation | |
122 | 155 | Selection procedure content for task plan &1 has been converted | The short text describes the object sufficiently | |
123 | 156 | Selection procedure ID &1 has been converted to &2 at task &3 | The short text describes the object sufficiently | |
124 | 160 | Conversion of attachments and links failed | The short text describes the object sufficiently | |
125 | 161 | Attachments and links have been converted | The short text describes the object sufficiently | |
126 | 170 | Document clean-up program has executed | The short text describes the object sufficiently | |
127 | 180 | Error when cancelling workflow instance &1 | The short text describes the object sufficiently | |
128 | 181 | Cancelled old workflow instance &1 | The short text describes the object sufficiently | |
129 | 182 | Error when triggering new workflow instance for the case &1 | The short text describes the object sufficiently | |
130 | 183 | Successfully triggered a new workflow for the case &1 | The short text describes the object sufficiently | |
131 | 184 | &1 instances of template &2 will be restarted | The short text describes the object sufficiently | |
132 | 186 | Error when receiving workflow instance &1 | The short text describes the object sufficiently | |
133 | 187 | &1 instances of template &2 have been restarted | The short text describes the object sufficiently | |
134 | 188 | &1 instances of template &2 should be restarted | The short text describes the object sufficiently | |
135 | 190 | Regulation &1 is not configured in backend | The short text describes the object sufficiently | |
136 | 191 | Risk driver &1 is not configured in backend | The short text describes the object sufficiently | |
137 | 192 | Risk impact &1 is not configured in backend | The short text describes the object sufficiently | |
138 | 200 | SQL error when query from table &1; program exit | The short text describes the object sufficiently | |
139 | 201 | No valid data found in table &1; program exit | The short text describes the object sufficiently | |
140 | 202 | SQL error updating table &1; program exit | The short text describes the object sufficiently | |
141 | 203 | Program exit at exception: &1 | The short text describes the object sufficiently | |
142 | 204 | Begin date is not valid; it must be before 1990.01.01 | The short text describes the object sufficiently | |
143 | 205 | No data found at table &1; no need to update | The short text describes the object sufficiently | |
144 | 206 | No processor at case &1; no need to set the remediation plan owner | The short text describes the object sufficiently | |
145 | 207 | No authorization template defined for role &1 | The short text describes the object sufficiently | |
146 | 208 | Regulations have been migrated | The short text describes the object sufficiently | |
147 | 209 | Migration of regulations has failed | The short text describes the object sufficiently | |
148 | 210 | &1 records are invalid data | The short text describes the object sufficiently | |
149 | 211 | Case '&1' migration error: &2 | The short text describes the object sufficiently | |
150 | 220 | &1 Audit Trail records will be converted | The short text describes the object sufficiently | |
151 | 221 | Merge into &1 actions with GRC2010 Audit Trail style | The short text describes the object sufficiently | |
152 | 222 | &1 actions have previously been converted | The short text describes the object sufficiently | |
153 | 223 | &1 actions are stored successfully | The short text describes the object sufficiently | |
154 | 224 | &1 actions failed to store because of DB error. | The short text describes the object sufficiently | |
155 | 225 | Error when storing the action &1 of the object &2 | The short text describes the object sufficiently | |
156 | 226 | Error when converting the detail: object &1 action &2 sequence &3 | The short text describes the object sufficiently | |
157 | 227 | &1 actions are partially stored | The short text describes the object sufficiently | |
158 | 228 | Simulation; so rollback occurs | The short text describes the object sufficiently | |
159 | 250 | Local process &1 of org. &2, ctrl proc. &3 to be merged to lcl process &4 | The short text describes the object sufficiently | |
160 | 251 | Role &1, user &2 will be assigned to local process &3 | The short text describes the object sufficiently | |
161 | 252 | Local Process &1 of org. unit &2 assigned from central proc &3 is removed | The short text describes the object sufficiently | |
162 | 253 | Document &1 with ID &2 has been linked to local process &3 | The short text describes the object sufficiently | |
163 | 254 | Local process &1 of org. unit &2 updated: valid from &3, valid to &4 | The short text describes the object sufficiently | |
164 | 255 | Local IELC group &1 org. &2, ctrl grp. &3 to be merged to lcl IELC grp &4 | The short text describes the object sufficiently | |
165 | 256 | Document &1 with ID &2 has been linked to local IELC group &3 | The short text describes the object sufficiently | |
166 | 257 | Local IELC group &1 of org. unit &2 updated: valid from &3; valid to &4 | The short text describes the object sufficiently | |
167 | 258 | Local IELC group &1 of org &2 assigned from ctrl IELC group &3 is removed | The short text describes the object sufficiently | |
168 | 259 | Data already exists in Table &1 | The short text describes the object sufficiently | |
169 | 260 | Data in backup Table &1 has been removed | The short text describes the object sufficiently | |
170 | 261 | Regulation - Organization relation creation failed | The short text describes the object sufficiently | |
171 | 262 | Program will create info type 5307 for organization &1 on regulation &2 | The short text describes the object sufficiently | |
172 | 263 | Program will create relation between organization &1 and regulation &2 | The short text describes the object sufficiently | |
173 | 264 | Fail to set regulation specific flag for organization &1 on regulation &2 | The short text describes the object sufficiently | |
174 | 280 | Add relation 975 in evaluation path PC_M3M1, see upgrade guide | Space: object requires documentation | |
175 | 281 | Remove relation 975 in evaluation path PC_M3M1, see upgrade guide | Space: object requires documentation | |
176 | 282 | Direct relation has been created before. Contact SAP support. | The short text describes the object sufficiently | |
177 | 283 | Relationship is not available for &1 . | The short text describes the object sufficiently | |
178 | 284 | Object ID &1 is inconsistent. | The short text describes the object sufficiently |
History
Last changed on/by | 20141106 | SAP | |
SAP Release Created in | 300 |