SWF_FLEX_DEF -
The following messages are stored in message class SWF_FLEX_DEF: .
It is part of development package SWF_FLEX_DEF in software component BC-BMT-WFM. This development package consists of objects that can be grouped under "Workflow: Flexible Workflow Definition".
It is part of development package SWF_FLEX_DEF in software component BC-BMT-WFM. This development package consists of objects that can be grouped under "Workflow: Flexible Workflow Definition".
Message Nr ▲ | Message Text |
---|---|
000 | GET_STREAM on entity '&1' is not supported |
001 | Filter on column &1 is not supported |
002 | UPDATE_STREAM on entity '&1' is not supported |
003 | Workflow definition is invalid and cannot be parsed |
004 | Scenario ID cannot be changed |
005 | Process is active. Action is not allowed |
006 | Process definition XML document does not fulfill the specification |
007 | Activation not allowed. Process in status '&1' |
008 | Scenario version cannot be changed |
009 | Class &1 is not existing |
010 | Workflow definition not found for scenario |
011 | Workflow does not exist |
012 | Authorization check for scenario activation causes exception |
013 | Scenario activation is currently locked |
014 | Enqueues for scenario activation cannot be written |
015 | Enqueues for scenario activation cannot be released |
016 | Class &1 does not inherit from class &2 |
017 | Scenario needs to be registered before it can be de-/activated |
018 | Missing authorization to de-/activate scenarios |
019 | Workflow definition is invalid. Artifact '&1' contains no version prefix. |
020 | Workflow ID cannot be changed |
021 | Deactivation not allowed. Process in status '&1' |
022 | Validity date(s) in the past can not be changed anymore |
023 | Validity range not valid |
024 | Subject is not valid |
025 | Scenario '&1' is not activated |
026 | Scenario version does not exist |
027 | Workflow is read only. |
028 | Not authorized for operation '&3' using the scenario '&1' (&2) |
029 | Duplicate process definitions in sequence of scenario |
030 | Filter on column &1 with operator &2 is not supported |
031 | Negative filter on column &1 is not supported |
032 | Deletion not allowed. Process in status '&1' |
033 | Parameter '&1' was assigned twice to condition '&2' |
034 | Parameter '&1' is missing in condition '&2' |
035 | Parameter '&1' for condition '&2' not defined in scenario |
036 | Condition '&1' not defined |
037 | Condition '&1' can not be used as start condition |
038 | Step '&1' is not defined in scenario |
039 | Parsing XML resource failed |
040 | XSD datatype &1 is not supported |
041 | Converting value '&1' for XSD datatype &2 failed |
042 | Agent rule '&1' for step '&2' is not defined in scenario |
043 | User '&1' for step '&2' does not exist |
044 | Principal type '&1' is not supported |
045 | Exception during process verification has occurred |
046 | A maximum of one activity allowed in predelivered content |
047 | Start conditions are not allowed in predelivered content |
048 | Conditions are not allowed in predelivered content |
049 | Expect opening tag '&1' in path '&2', but found '&3' |
050 | Expect closing tag '&1' in path '&2', but found '&3' |
051 | Validity range not valid |
052 | Validity is not supported in predelivered content |
053 | Deletion of predelivered content is not supported |
054 | Scenario &1 of predelivered content doesn't fit to &2 |
055 | Create object for class '&1' failed |
056 | Another predelivered workflow is already active |
057 | Scenario version &1 of predelivered content doesn't fit to &2 |
058 | Expected attribute '&1' in path '&2' not found |
059 | Error occurred while parsing the workflow resource |
060 | Duplicate action defined for outcome '&1' |
061 | Action defined for unknown outcome '&1' |
062 | Step '&1' in activity defined for outcome &2 is unknown |
063 | Step '&1' cannot be used as activity for outcome '&2' |
064 | Step '&1' can be used as activity for outcome only |
065 | Action '&1' used for outcome '&2' is not supported |
066 | Initialization Shared Object failed |
067 | Missing process definitions in sequence of scenario |
068 | Reference Time '&1' is not defined in scenario |
069 | Define unique name |
070 | Agent Rule '&1' not defined |
071 | Condition uses local container element &. Can't be used for start. |
072 | Define detailed data for item '&1' or delete it |
073 | Deadline Action '&1' is not defined in scenario |
074 | Offset '&1' is invalid. |
075 | Responsibility Management (TEAM) not configured |
076 | Team category '&' does not exist |
077 | Team category '&' is not valid |
078 | Property '&1' is not defined in scenario |
079 | Name '&' should consist of characters, digits and '_' |
080 | Class &1 is obsolete: Please use class inherits from &2 |
081 | SOT for leading object '&1' (&2.&3) is not defined |
082 | Leading object type not defined |
083 | Leading object has to be an importing parameter |
084 | Activate Scenario before generate BRF+ application |
085 | CDS View of leading object for BRF+ generation not defined |
086 | Invalid CDS View &1 for BRF+ generation |
087 | Generate BRF+ application. Please wait... |
088 | BRF+ application generated |
089 | Generate CDS view. Please wait... |
090 | Draft process definition exists already (scenario:&1;object:&2) |
091 | Active process definition not found (scenario:&1;object:&2) |
092 | Cannot get workitem ID! Check number range object SWW_WIID |
093 | Active process definition exists already (scenario:&1;object:&2) |
094 | Adhoc process has been started (scenario:&1;object:&2) |
095 | Draft process definition not found (scenario:&1;object:&2) |
096 | Missing details to create default process definition |
097 | Draft process definition exists with other origin (scenario:&1;object:&2) |
098 | Bad application object ID. Activation failed (scenario:&1;object:&2) |
099 | Team function '&1' for step '&2' is not defined in scenario |
100 | Agent rule type '&1' is not supported |
101 | Local principal group '&1' for step '&2' is not defined in workflow |
102 | Error retrieving the team attributes (scenario:&1;object:&2) |
103 | Error resolving team function &3 (scenario:&1;object:&2) |
104 | Enter a valid template type |
105 | Enter a valid stage for template of type "Process Layer" |
106 | Enter a stage |
107 | Enter a stage name |
108 | Stage &1 already exists within scenario &2. Enter a different stage |
109 | Scenario '&1' is not of type "Process Layer" |
110 | Validation type is not known |
111 | Team '&1' for step '&2' is not defined in scenario |
112 | Cannot delete draft template |
113 | Outcome ID '&' should consist of characters, digits and '_' |
114 | Create at least one outcome |
115 | Value '&1' not valid for parameter '&2' |
116 | Enter a value for property '&1' |
117 | Value '&1' not valid for property '&2' |
118 | Mandatory property '&2' is missing at activity '&1' |
119 | Scenario ID is mandatory parameter |
120 | Method is not supported for workflow instances |
121 | Do not change super class. Please create own class which inherits from &1 |
122 | Operation is not supported. |
123 | Activity exposed only for exception handling is missing predefined agents |
124 | The factory calendar is not supported for this scenario |
125 | Factory calendar is only supported for days |
126 | No authority for Scenario Id &1 |
127 | At least one action result should remain |
128 | Step type '&1' not allowed in main flow |
129 | Step type '&1' not allowed in review flow |
130 | CDS view is not up to date. Re-generation cancelled by user. |
131 | Template ID '&' has no corresponding CDS view and can't be used |
132 | CDS view '&' has no key field for work item ID and can't be used |
133 | CDS view '&' can't be analyzed. (Type not found) |
134 | Provide an email template. |
139 | Enter a short text for name '&'. Short text is needed for the app. |
140 | Scenario &1 was successfully activated and registered |
150 | Leading object of scenario &1, version &2 cannot be determined |
160 | No responsible assignment defined for step &1 |
170 | Workflow instance with id &1 is not of type reviewable |
171 | No review workflow found for workflow instance with id &1 |
172 | No workflow stream found for review workflow instance with id &1 |
173 | Workflow instance with id &1 can not be loaded |
174 | Block can not be inside a run-with-previous block |
175 | Extension step can not be inside a run-with-previous block |
176 | No run-with-previous feature allowed for scenario &1 and version &2 |
200 | Invalid service path '&1' |
210 | Upgrade of a non-draft process definition not supported |
211 | Upgrade of process definition failed |
212 | Deprecated format version '&1' |
220 | Agent rule '&1' for notification is not defined in scenario |
221 | Team function '&1' for notification is not defined in scenario |
222 | Local principal group '&1' for notification is not defined in workflow |
223 | Team '&1' for notification is not defined in scenario |
224 | Notification outcome id '&1' not defined in scenario |
225 | Notification eMail template id '&1' not valid for workflow |
226 | Notification trigger '&1' not valid |
227 | Required outcome id for notification sent at end is empty |
228 | User '&1' for notifications is invalid. |
230 | Workflow outcome id '&1' has no nature. |
233 | Agent rule '&1' for deadlines is not defined in scenario |
234 | Team function '&1' for deadlines is not defined in scenario |
235 | Local principal group '&1' for deadlines is not defined in workflow |
236 | Team '&1' for deadlines is not defined in scenario |
237 | Required recipient for deadline action email is not provided |
238 | Required email template for deadline action email is not provided |
239 | User '&1' for deadlines is invalid. |
250 | Predelivered content must be of format version &1 |
260 | Extension step '&1' for SAP WF Service must have a workflow definition |
261 | No workflow definition expected for step '&1' |
262 | Extension workflow definition id '&1' is not valid |
270 | Adaptation Transport Organizer notification is currently disabled. |
271 | Adaptation Transport Organizer not configured. |
272 | Scenario '&1' was already exported: Content cannot be changed. |
273 | Scenario '&1' was already imported: Content cannot be changed. |
274 | &1 Workflow Scenario(s) successfully added to transport &2. |
280 | Unlocking scenario failed. Adaption Transport Organizer is not configured |
281 | Unlocking scenario failed. |
300 | Can not determine changes without original stream (scenario:&1;object:&2) |