/MOC/OBJECT - MoC redefined Messages of Message Class /IAM/OBJECT
The following messages are stored in message class /MOC/OBJECT: MoC redefined Messages of Message Class /IAM/OBJECT.
It is part of development package /MOC/DDIC in software component CA-IAM-MOC. This development package consists of objects that can be grouped under "Management of Change: DDIC and Customizing Objects".
It is part of development package /MOC/DDIC in software component CA-IAM-MOC. This development package consists of objects that can be grouped under "Management of Change: DDIC and Customizing Objects".
Message Nr ▲ | Message Text |
---|---|
000 | Internal error (class &1, method &2 ) |
001 | &1 |
002 | &1&2&3&4 |
100 | Change request type &1 has been set to 'Inactive' |
195 | Wildcards/ranges not supported for ID-mapping relevant objects |
196 | Internal error: missing object type for ID &1 in selection condition |
197 | Internal error: unexpected usage of ID mapping in BO &1 |
198 | BO &1, query &2: Attribute mapping has empty result |
199 | BO &1, query &2: Conversion failed for attribute &3 |
200 | BO &1: Internal error accessing query configuration |
201 | BO &1, query &2: Internal error determining selection mode |
202 | BO &1, query &2: Attribute &3 invalid |
203 | Nothing found |
204 | Selection restricted to &1 hits |
205 | BO &1, query &2: Internal error building WHERE clause |
206 | BO &1, query &2: Internal error executing dynamic selection |
207 | Only one responsible partner allowed |
208 | Responsible partner missing |
209 | Not more than one text of type &1 allowed |
210 | Number range interval missing in change request type &1 in application &2 |
211 | BO &1: Internal error accessing BO configuration |
212 | BO &1: Internal error, inconsistency for long texts between BO and DO |
213 | BO &1, node cat. det.:Application/ change request type missing |
214 | BO &1, node cat. det.:No node category for appl. &2, CR type &3 |
215 | BO &1, node category determination: No such node category: &2 |
216 | Change request cannot be closed because activity "&2" (&1) is still open |
217 | BO &1, action called with inconsistent action parameters |
218 | BO &1: Internal error accessing application configuration |
219 | Application &1 has no text schema; adding long texts not possible |
220 | &1: Invalid timestamp &2 |
221 | &1: Invalid time zone &2 |
222 | &1: Timestamp &2 not converted into local time |
223 | &1: Invalid date or time (&2/ &3) |
224 | &1: Local date/ time converted without time offset |
225 | Search request too complex; reduce number of given criteria |
226 | Text of unit &1 not found |
227 | BO &1:Internal error accessing BOL configuration |
228 | Object &1:Internal error accessing BOL object data: key structure &2 |
229 | BO &1:Internal error accessing reference object data via BOL |
230 | Failed to access reference object descriptions |
231 | Failed to access description of reference object &1 &2 in &3 |
232 | Error reading name for user &1 |
233 | No Reporter role is defined for change request type &1 |
234 | Business partner does not exist |
235 | Failed to check whether reference object exists |
236 | Reference object &1, ID &2 does not exist in system &3 |
237 | Reference object &1, ID &2, system &3, occurs more than once |
238 | Activity not created, no data |
239 | Activity not created, specify at least template or type |
240 | Activity template &1 is marked as inactive |
241 | Activity type &1 is marked as inactive |
242 | Text type for description is missing |
243 | No business partner &1 found |
244 | Reference object &1, ID &2, system &3 not verified (Customizing missing) |
245 | Change request cannot be deleted because activity &1 is still open |
246 | Activity cannot be deleted because activity '&1' has status '&2' |
247 | There must be at least one entry for the mandatory partner role &1 |
248 | Partner role &1 can only be entered once because it is defined as unique |
249 | Change request &1 cannot be deleted |
250 | Partner role &1 is used although it is defined as inactive in Customizing |
251 | BO &1, node cat. det.;application/ activity type missing |
252 | BO &1, node cat. det.;no node category for appl. &2, activity type &3 |
253 | Change request type &1 not valid for application &2 |
254 | Attachment not added;invalid URL |
255 | Attachment not added;change request category &1 has no document scheme |
256 | Attachment not added;document type &1 not allowed for &2 |
257 | Attachment not added;MIME type &1 not allowed for document type &2 |
258 | Attachment not added; document type &1 not valid |
259 | Attachment not added; document type &1 has no attachment type |
260 | Attachment not added; enter a document type |
261 | Attachment not added; invalid doc. schema &1 assigned to CR type &2 |
262 | MIME type &1 not allowed for document type &2 |
263 | Document type &1 not allowed for &2 |
264 | Document type &1 not valid or not assigned to document schema &2 |
265 | Partner cannot be deleted because partner role &1 is mandatory |
266 | Business partner is missing for mandatory partner role &1 |
267 | Missing subordinate CR type for CR category &1 (&3) in CR type &2 (&4) |
268 | Approval required for change request type &1 |
270 | &1: End date must not be earlier than start date |
271 | No authorization to process CR for: &3 (CR type &1, group &2) |
272 | No authorization for changed fields (CR type &1, auth. group &2) |
273 | Enter reference object ID for object type &1 |
274 | Enter reference object type for object &1 |
275 | Check Customizing for dependent object 'attachment folder', BO &1 |
277 | No authorization for description: &3 (CR type &1, text type &2) |
278 | Change request type &1 contains no valid partner role |
279 | Activity type &1 contains no valid partner role &2 |
281 | Error accessing form &1 for printing |
282 | Error creating PDF |
283 | No authorization for: &3 (object type &1, logical system &2) |
284 | No authorization for plant &1 (object type &2, logical system &3) |
285 | No authorization for: &3 (document type &1, change request type &2) |
286 | Status cannot be changed as data is inconsistent for change request &1 |
287 | Status cannot be changed as data is inconsistent for activity &1 |
288 | Invalid subtype &1 of object &2 |
289 | No authorization to change CR in status &3 (CR type &1, group &2) |
290 | Status of change request changed from &1 to &2 |
291 | Activity cannot be deleted because activity &1 is obligatory |
292 | Status of activity changed from &1 to &2 |
293 | No dependent object access for object type &1, change request type &2 |
294 | No authorization to change &3 (CR type &1, authorization group &2) |
295 | Unable to process follow-up action &1 of activity &2 |
296 | No authorization to change &3 (activity type &1, authorization group &2) |
297 | Business partner is missing for partner role &1 in change request &2 |
298 | Business partner &1 is already assigned to partner role &2 |
299 | You cannot move an activity down if it is already at the bottom |
300 | You cannot move an activity up if it is already at the top |
302 | Movement is not possible because activity &1 is locked by &2 |
303 | No authorization to change &4 (CR type &1, acty type &2, auth. group &3) |
304 | There are also related objects for which you have no authorization |
305 | Follow-up action &1 with mode &2 cannot be executed at exec. time &3 |
306 | &1 &2 is not completed yet |
307 | No authorization to change activity in status &3 (Act. type &1, group &2) |
310 | Change request cannot be deleted because there are still subordinate CRs |
311 | Change request cannot be deleted because there are still activities |
312 | Activity cannot be deleted because there are still subactivities |
313 | Action can not be executed for activity &1 |
314 | Activity &1 is in digital signature process, action can not be executed |
317 | No authorization for: &2 (object type &1) |
318 | Wrong subordinate CR type &1 (&3) for change request type &2 (&4) |
319 | Triggering follow-up action &1 not possible without saving activity &2 |
320 | Follow-up action &1 of activity &2: Mandatory obj. reference &3 missing |
321 | No authorization to access logical system &1 for object type &2 (&3) |
322 | Activity &1; status '&2' not possible, as current status is '&3' |
323 | Activity templ. &1 does not exist, but is assigned to change req. type &2 |
324 | Error in activity determination; activity template ID &1 does not exist |
325 | BO &1, query &2; invalid table name |
326 | BO &1, query &2; ID mapping has inconsistent result |
327 | Follow-up action &1 of activity &2; could not create object of type &3 |
328 | BO &1, query &2; invalid characters in result string |
329 | Partner determination; result with partner role &1 skipped |
330 | Partner determination successfully executed; &1 added/&2 changed |
333 | Activity determination successfully executed; &1 activities added |
334 | &2 changed to &1 |
335 | No authorization for change log &1 |
355 | Reference object type &1 not allowed for change request type &2 |
356 | Object type &1 not allowed as main ref. object for change request type &2 |
400 | Multiple business partners found for system user &1 |
401 | No business partner found for system user &1 |
500 | Number range interval for activity missing in change request type &1 |
501 | Enter an activity category |
502 | No node category found for activity category &1 |
503 | Positions with position origin &1 cannot be processed |
504 | Activity cannot be closed because subactivity &1 is still open |
505 | Error in partner determination: BRFplus application &1 not found |
506 | Error in partner determination: BRFplus function &1 not found |
507 | Processing is not possible because activity &1 is locked by &2 |
508 | Error in partner determination |
509 | You cannot change status of activity &1 |
510 | Activity determination: BRFplus function &1 for application &2 not found |
511 | Error in activity determination |
512 | Error in activity determination for activity template &1 |
514 | Business partner &1 has status '&2' |
515 | Activity &1 is not locked and cannot be changed |
516 | Positions for role &1 cannot be found to determine the business partners |
520 | Change of activity type not allowed; new type has a different category |
521 | Activity &2: Mandatory partner role &1 is missing |
522 | Activity &2: Partner role &1 occurs more than once although it is unique |
523 | Activity &2: Partner role &1 used but it is defined as inactive |
524 | Activity &2: Specify business partner for mandatory partner role &1 |
525 | Activity &2: Business partner &1 has status 'Not Released' |
526 | Activity &1: Business partner does not exist |
528 | Activity &1: Automatic status change to &2 not possible |
529 | Activity &1: Reference system is missing for reference object &2 |
530 | Activity &1: Reference system for reference objects is not unique |
531 | Activity &1: You must enter a business partner under 'People Involved' |
532 | Activity &2: Business partner is missing for partner role &1 |
533 | Activity &3: Business partner &1 is already assigned to partner role &2 |
555 | Attachment not added; activity category &1 has no document schema |
556 | Attachment not added; document type &1 not allowed for activity type &2 |
561 | Attachment not added; invalid doc. schema &1 assigned to activity type &2 |
571 | No authorization to process activity for: &3 (activity type &1, group &2) |
572 | No authorization for changed fields (activity type &1, auth. group &2) |
600 | Select exactly one activity |
601 | Activity type & is not valid |
602 | Activity template & is not valid |
603 | Due date cannot be calculated for activity &1 |
604 | Unit &1 not found |
605 | Conversion of unit &1 to unit &2 not possible |
606 | No default partner role for activity type &1; delete 'Responsible' entry |
620 | Status of activity &1 does not allow archiving |
621 | Activity node of activity &1 is incomplete and prevents archiving |
625 | Change request hierarchy of change request &1 does not allow archiving |
626 | Status of change request &1 does not allow archiving |
628 | Activities of change request &1 are not archived |