W8 - Workflow: Ausdr�cke, Datenfluss
The following messages are stored in message class W8: Workflow: Ausdr�cke, Datenfluss.
It is part of development package SWA in software component BC-BMT-WFM. This development package consists of objects that can be grouped under "Business Workflow: Expressions, binding".
It is part of development package SWA in software component BC-BMT-WFM. This development package consists of objects that can be grouped under "Business Workflow: Expressions, binding".
Message Nr ▲ | Message Text |
---|---|
001 | & is not a valid & & input value |
002 | Error '&1' during deletion. Try again later |
003 | Declare constants for object references using input help |
004 | Value & does not correspond to the data type & of element & |
005 | Parameter error calling function & |
006 | Parameter error while calling function & (in function &) |
020 | The interface of function module '&1' does not correspond to conventions |
021 | Function modules correspond to workflow conventions |
051 | &1 errors occurred in binding assignment to &2 |
052 | &1 errors occurred in binding assignment to &3 |
053 | &1 errors occurred in the condition evaluation of &2 |
060 | Table action "Append" is only possible for single-level expressions |
063 | Reference '&1'('&2') has changed - binding adapted for '&3' |
064 | Conversion error while evaluating expression |
065 | Conversion error while evaluating condition & = & & & |
066 | Value for expression &1 cut |
067 | Text is too long |
068 | Data was saved |
069 | Input not supported for structured elements with data type '&1' |
070 | Reference structure & for expression & is not a valid structure |
071 | Element & has no structure reference, therefore no access to fld & in & |
072 | No access to field & in element & (expression & ) possible w/o structure |
073 | Element & from expression & is incompatible with structure & |
074 | Element & cannot be read with structure & |
075 | Source and target structures have different numbers of fields (&, &) |
076 | Saving element & contradicts structure & |
077 | Access to field & is not possible for multiline element & |
078 | Access to attribute & is not possible for multiline element & |
079 | Structure & has no field with name & |
080 | Structures & and & are not compatible |
081 | Element & does not refer to a structure |
082 | Element value with reference structure & becomes CHAR string of length & |
083 | CHAR string of length & becomes value with reference structure & |
084 | Access with line index () is not possible for element & (one line) |
085 | Access with line index () is not possible for expression part & |
086 | Object type & overwritten by object type & in target element |
087 | Source element & does not exist; target element & will be deleted |
088 | Source & corresponds to object type & and not & |
089 | Time specifications require the formatting defined in user defaults |
090 | Date specifications require the formatting defined in user defaults |
091 | Time specifications are expected in the internal format HHMMSS |
092 | Date specifications are expected in the internal format YYYYMMDD |
093 | Expression '&1' has an invalid length |
094 | Binding for element '&3' adapted to new data type or length |
095 | Element & may not be changed |
096 | Syntax '()' only allows read access to element & |
097 | Element & does not have a line with index & |
098 | Syntax '()' is only possible for elements of the container |
099 | Values in binding have maximum length & |
100 | No container definition available |
101 | Binding for container types & <- & is not defined |
102 | Parameter error calling editor for binding & <- & |
103 | Fast entry cannot be used for entry of individual elements |
104 | Binding definition inconsistent with (called) container definition & |
105 | Container element & is not loop element & |
106 | Constants cannot begin with '%' or '&' |
107 | No binding defined for mandatory import parameter & |
108 | Source & corresponds to object type & and not & |
109 | Reference types '&1' and '&2' are not compatible (expression '&3') |
110 | Syntax error in expression &1 |
111 | Parameter error calling editor for expression & |
112 | Specify a reference for expression & |
113 | Result (length &) is too short for source (length &) |
114 | The source field of a date cannot have the length & |
115 | The source field of a time cannot have the length & |
116 | The data type & cannot be converted to data type & |
117 | No definition exists in container &2 for element '&1' |
118 | Binding definition is consistent |
119 | ***** Binding definition: Direction "&", element & ***** |
120 | Messages were created when checking the expression -> see log |
121 | Variable does not have a & end character |
122 | Index element & does not have a & end character |
123 | '&1' is not an attribute of '&2' - use the F4 input help |
124 | Conversion of data type & to data type & is not supported |
125 | Object type & does not exist |
126 | Element & is not the specified table element & |
127 | & binding for element & has a critical error |
128 | Binding definition contains errors -> see Check |
129 | Table action not possible on element & |
130 | Table action "Append" not possible when reading an element |
131 | Multiline element & cannot be assigned to a single-line element |
132 | Expression & is an object and not a DDIC reference |
133 | Element & has been defined as single-line but can now become multiline |
134 | Assignment of variable object type & to object type & may contain errors |
135 | Input value & is not allowed |
136 | Expression type & is not supported |
137 | Constants cannot be declared here |
138 | Import elements cannot be processed since no source container defined |
139 | Element & not in source container |
140 | The respective element in & has no value |
141 | No element & in target container |
142 | Expression & refers to container elements that do not incorporate export |
143 | Attribute & cannot be overwritten |
144 | No container defined for & |
145 | Object type & overwrites initial object type of target element |
146 | & is not a valid entry |
147 | Container definition passed is empty |
148 | Declare either a system status or a user status |
149 | Function only allowed for data type CHAR (not for data type &) |
150 | Invalid data type for passing expression & |
151 | Expression type & has no processing for expression & |
152 | Expression & only allows single-line values |
153 | Object type & does not have any key fields |
154 | Element & from expression & is not in container |
155 | Object & could not be instantiated |
156 | Cursor does not show binding direction |
157 | Element & could not be recognized as an object reference |
158 | Value for container element & is initial, no attributes can be determined |
159 | Element & will not be overwritten |
160 | Lines that cannot be processed in the binding definition will be deleted |
161 | A constant cannot be assigned to a table element |
162 | Element & does not have a reference type (see container definition) |
163 | Object types & and & are not compatible |
164 | A table element cannot be assigned a system field |
165 | No appropriate elements for reference of & in container & |
166 | This function is not possible for element & |
167 | Select a container element |
168 | Error converting entry for field &-& |
169 | Error during input for element & |
170 | Error during type conversion |
171 | Date or time & does not exist |
172 | Conversion of format & is not currently supported |
173 | Reference field &-& for element & does not exist |
174 | Constants are restricted to only 80 characters |
175 | Expression & does not have a valid date format or time format |
176 | Value '&1' has an invalid length (&2) for the field '&3' |
177 | Enter the value for element & using the input help |
178 | Value of element & will be deleted from the container |
179 | Binding & & & will be deleted |
180 | This function is not available for binding direction ==> |
181 | Data type incompatible |
182 | References '&1' and '&2' are not compatible |
183 | Element & is assigned data for all source elements |
184 | Element & is the source for all target elements |
185 | Existence of object ( & & ) was not checked |
186 | Expression & is not a constant |
187 | Logical system & is not valid (current system: & ) |
188 | Element & is only intended for data export |
189 | The one line element & already contains the value & |
190 | Field or field value restrictions are only valid for "change" event & |
191 | Field or field value restrictions for "change" event only |
192 | Value & exists in client &, but check table & is client-specific |
193 | Value & is invalid in client &, but check table & is client-specific |
194 | Value & is allowed in language &, but check table & is language-specific |
195 | Value & is invalid in language &, but check table & is language-specific |
196 | Value & cannot be checked against table & |
197 | Reference field & - & for expression & does not exist |
198 | Value of type & is used for defining date (type &) |
199 | Expression '&' does not correspond to data type (&) of element & |
200 | Internal error in HTML generation: Line length exceeded (&) |
201 | Error in text replacement: '&1' is not in the container of WI &2 |
202 | Error in text replacement: Element '&1' does not exist in the container |
207 | No binding for required element &1&, use default value |
210 | Condensing of containers not supported for element &1 |
220 | Expression &1: Invalid syntax for access to structure field |
225 | Expression &1 does not type timestamp (TIMESTAMP, TIMESTAMPL). |
240 | Function module '&1' does not exist |
241 | Internal error accessing function module '&1' |
242 | Operation terminated |
243 | Binding module '&1' created in function group '&2' |
300 | *** Reserved for condition editor (300 - 399) |
301 | Function '&' not yet implemented |
302 | Internal program error: & & & & |
303 | The evaluation of the condition gives the result 'True' |
304 | The evaluation of the condition gives the result 'False' |
305 | Select a line area first |
306 | Only related lines can be selected as an area |
307 | Syntax check: The condition is correctly formulated |
308 | Row is incomplete |
309 | Add a relational operator (<, >, =, etc.) to line &1 |
310 | Operator '&' cannot be used in this position |
311 | Add a logical operator (AND, OR) to line &1 |
312 | Object type &1 does not have a method for checking existence |
313 | Existence check not successful for '&' |
314 | Perform the test first |
315 | Existing selection removed |
316 | No messages exist |
317 | Data converted |
318 | Select a suitable entry |
319 | Position the cursor on an expression |
320 | Position the cursor in column 'Expression 1' or 'Expression 2' |
321 | Choose a relational operator in the condition first |
322 | Choose a line in the condition by double-clicking |
323 | Simulated evaluation of the condition returns &1 error(s) |
324 | Maximum number of lines (&1) reached - operation aborted |
325 | Logical operator &1 (in line &2) is not permitted |
326 | No data stored currently |
327 | Define constants only on the right-hand side of the operator |
328 | Could not establish the type of expression '&' |
329 | Cursor automatically positioned on expression &1 |
330 | Expression not (yet) defined - no attributes available |
333 | &1 line(s) cut and moved to buffer |
334 | &1 line(s) copied to buffer |
335 | &1 line(s) inserted from buffer |
336 | Error accessing local file - operation aborted |
340 | Too many closing parentheses in line &1 |
341 | Opening parenthesis in line &1 not closed |
344 | Evaluation returns 'true'. &1 message(s) exist |
345 | Evaluation returns 'false'; &1 message(s) exist |
350 | Expression 1 ('&2') must be multiline for operator '&1' |
351 | Expression 2 ('&2') cannot be multiline for operator '&1' |
352 | Operator '&1' can only be applied to an object reference |
353 | Operator '&1' cannot be applied to a multiline element |
354 | Operator '&1' allows only one operand |
370 | The selected expression exceeds the maximum length allowed (&1) |
380 | Condition '&' saved and type linkage &.& <-> & created |
381 | Condition '&' saved and activated |
382 | Condition '&' deleted and type linkage updated |
383 | Condition '&1' saved (&2) |
384 | Condition '&1' deleted |
385 | Processing aborted - condition '&' not changed |
386 | No condition created |
387 | Condition '&1' not changed (&2) |
388 | Condition '&1' deleted with associated linkage '&2 <-> &3' |
389 | Attributes of condition '&1' changed |
396 | Mode switch not effective until next time condition editor called |
397 | Welcome to the condition editor (traditional mode) ... |
398 | Welcome to the condition editor ... |
399 | *** Reserved for workflow condition editor (300 - 399) |
401 | Invalid command '&1' received from HTML control |
402 | Invalid line index (&1) accessing internal table |
403 | Internal error: Invalid field lengths (SWBTYPECOU <-> SWBRULECOU) |
404 | Object type '&1' does not exist in Business Object Repository |
405 | Linkage for '&1-&2' <-> '&3' could not be created |
406 | Workflow & not found - enter a valid workflow ID |
408 | Attributes not changed |
409 | Personal settings saved |
410 | Internal error saving personal settings |
411 | HTML control: Error accessing resource '&1' |
412 | Change of name or currency of start condition not possible |
413 | Event linkage '&1'<->'&2.&3' deactivated |
414 | Event linkage '&1'<->'&2.&3' activated |
415 | Error accessing linkage '&1'<->'&2' |
416 | Start condition '&1' activated |
417 | Start condition '&1' deactivated |
418 | New default currency for start condition '&1': &2 |
419 | Default currency for start condition '&1' not changed |
420 | Name of start condition '&1' not changed |
421 | New name for start condition: '&1' |
422 | Object type '&1' defines no events. Use not possible. |
423 | Create a start condition; click the required event linkage |
424 | Choose a workflow task of type WS, WF, TS or T |
425 | Start condition being processed by user &1 - Only display possible |
426 | To process the start condition, choose change mode |
427 | Your selection was not changed |
428 | Start condition '&1' could not be activated |
430 | There are changes that have not been assigned to a transport request |
431 | There are no changes relevant for transport |
432 | Operation was canceled |
433 | &1 start condition(s) passed to transport request |
434 | No transport entries created |
435 | No exchange rate found for currency conversion '&1' -> '&2' |
436 | Error during currency conversion '&1' -> '&2' |
500 | *** Reserved for event manager (build time) *** |
501 | Incorrect parenthesis type used |
502 | Field restriction entered contains syntax errors |
503 | Field restriction entered does not contain entry '&1' at least |
504 | Field restriction entered correct and saved |
505 | Maximum field length exceeded |
506 | Entry '&1' not permitted syntactically |
515 | Conversion of field restriction not possible |
516 | Combined field restriction not correct syntactically |
518 | Old field restrictions successfully restored |
520 | Conversion only possible for field restrictions without entry KEY |
521 | Field restrictions and a combined field restriction exist |
522 | Combined field restriction could not be saved |
523 | A combined field restriction already exists |
525 | An old combined field restriction exists and is being loaded. |
526 | Field restrictions exist that have not yet been converted |
530 | Event container function module entry not saved |
531 | Event container function module entry saved |
532 | Combined field restriction could not be read |
533 | Save modified field restriction(s) |
600 | **** Reserved for SWA utility functions ****************************** |
601 | Field &1 can only take the first &2 characters of the result string |
602 | The maximum length supported for character strings here is &1 characters |
700 | Enter the business object type |
701 | Enter an event |
702 | Entry is inconsistent |
703 | Not more than 999 entries allowed for change document object |
704 | Change document object & does not exist |
705 | Enter a change document object |
706 | Key for change doc. object & and business object type & are incompatible |
707 | Internal error occurred during key check |
708 | No key information for change document object & |
709 | Internal error during event parameter check |
710 | Some parameters of event are not assigned values during creation |
711 | Internal error accessing database |
712 | No change document written for & when changed |
713 | No change document written for & when created |
714 | No change document written for & when deleted |
715 | Table & not used for change document object & |
716 | Enter a table for change document object & |
717 | Field & does not occur in table & |
718 | Creation/deletion of records in table & checked |
719 | Event & can only be a triggering event |
720 | Workflow requester flag only valid for create events |
721 | Status object and business object type keys incompatible |
722 | No key information exists for status object & |
723 | Field name 'KEY' can be used to check create/delete for table & |
724 | Only system status & or user status & possible |
725 | Event only triggered in case of change |
726 | Field & is not part of change document |
727 | Enter object type and event |
728 | Key already exists for change document object & |
729 | Business object type and change document object are incompatible |
730 | No transport request created |
800 | *** Reserved for trace manager *** |
801 | Workflow trace for work item &1 switched on (trace ID &2) |
802 | Workflow trace for work item &1 switched off |
803 | Job scheduling successful |
804 | Job & scheduled |
805 | A system error has occurred |
806 | Workflow trace & switched on for workflow |
807 | Workflow trace & switched off for workflow |
808 | Container debugging switched on |
809 | Container debugging switched off |
810 | Stored workflow trace cannot be deleted |
811 | &1 new entries |
812 | &1 from &2 entries will be displayed |
813 | &1 entries were found |
814 | Job & could not be scheduled |
899 | & & & & |
998 | No authorization to change an existing start condition |
999 | No authorization to create a new start condition |