CM_EHFND_API_TDEF -
The following messages are stored in message class CM_EHFND_API_TDEF: .
It is part of development package EHFND_API_TASK_DEFINITION in software component EHS-SUS-FND. This development package consists of objects that can be grouped under "API Package for Business Object Task Definition".
It is part of development package EHFND_API_TASK_DEFINITION in software component EHS-SUS-FND. This development package consists of objects that can be grouped under "API Package for Business Object Task Definition".
Message Nr ▲ | Message Text |
|---|---|
| 001 | Task Definition &1 have been already imported. |
| 002 | Task Definition &1 isn't unique, can't be imported. It appears &2 times. |
| 003 | Start of Processing of Task Definition &1. |
| 004 | Task Definition can't be imported if migration source field is empty. |
| 005 | Node &1 should have no more than 1 instance, but it has &2. |
| 007 | Only one host migration source can be filled at one time. |
| 008 | Task Definition &1 wasn't migrated due to errors. |
| 009 | Attribute "&1" has invalid timestamp. |
| 010 | Location with ID "&1" is not found. |
| 011 | Compliance requirement "&1" is not found. |
| 012 | Mandatory field "&1" is not filled. |
| 013 | Owner User (Business partner) "&1" is not found. |
| 014 | Assignee (Business partner) "&1" is not found. |
| 015 | Approver (Business partner)"&1" is not found. |
| 016 | Semantic object "&1" is not configured for task creation. |
| 017 | Task type (workflow event) "&1" is not found. |
| 018 | Task priority "&1" is not found. |
| 019 | Task status "&1" is not found. |
| 020 | Recurrence type "&1" is not found. |
| 021 | Change management request type "&1" is not found. |
| 022 | Notification type "&1" is not found. |
| 024 | For recurrence type "&1" the following fields should be specified: &2&3&4 |
| 025 | For recurrence type "&1" and offset "&2" field "&3" must be specified. |
| 027 | Task Definition &1 was sucessfully migrated. |
| 028 | Task Definition &1 was sucessfully migrated in Test Mode. |
| 030 | Approver can only be specified for task workflow event "&1". |
| 031 | Approver must be specified for task workflow event "&1". |
| 032 | Task with class &1 and event &2 is not configured. |
| 033 | Paragraph ID is empty. Must be filled to create reference. |
| 034 | Paragraph ID "&1" is not found for Compliance Requirement "&2". |
| 035 | Planned instance: mandatory field "&1" is not filled. |
| 036 | Follow up: mandatory field "&1" is not filled. |
| 037 | Due date "&1" can't be before start date "&2". |
| 038 | Paragraph "&1" of Host Object "&2" cannot be referenced. |
| 039 | Start and Due dates of instance must be within definiton time frame &1. |
| 040 | Database error. Data has not been updated (entity: &1). |
| 041 | Follow up category "&1" is not found in the system. |
| 042 | Incident ID must be filled for follow up activity. |
| 043 | Incident ID "&1" is not found in the system. |
| 044 | Migration of tasks for object "&1" is not supported currently. |
| 045 | Migration of task type "&1" is not supported yet. |
| 046 | Attribute "&1" is disabled for object "&2" and task type "&3". |
| 048 | Recurrence end date cannot be in the past if status is not "Closed". |
| 049 | Compliance scenario "&1" is not found. |
| 050 | References cannot be done for Host Object of type "&1". |
| 051 | Offset value "&1" is not found in the system. |
| 052 | Month value "&1" is not found in the system. |
| 053 | Due In Unit value "&1" is not found in the system. |
| 054 | Date "&1" is not valid for attribute "&2". |
| 055 | No one or more than one host migration source is provided. |
| 056 | Specified recurrence day "&1" is invalid. |