/BOBF/CONF -
The following messages are stored in message class /BOBF/CONF: .
It is part of development package /BOBF/CONFIGURATION in software component BC-ESI-BOF. This development package consists of objects that can be grouped under "Business Object Processing Configuration".
It is part of development package /BOBF/CONFIGURATION in software component BC-ESI-BOF. This development package consists of objects that can be grouped under "Business Object Processing Configuration".
Message Nr ▲ | Message Text |
---|---|
000 | Configuration error has occurred |
001 | Configuration has been saved |
002 | Error occurred while reading the configuration data |
003 | Configuration errors were not found |
004 | No access to business object &1 proxy data |
005 | Interface &1 was generated successfully |
006 | Interface &1 could not be generated |
007 | Internal error in configuration management |
008 | Could not find the requested element |
009 | The configuration was not changed |
010 | An error occurred while saving the configuration |
011 | Unknown business object |
012 | Business object &1 not active |
013 | Structure &1 has been created |
014 | Structure &1 has been activated |
015 | Structure &1 could not be activated |
016 | Structure &1 already exists |
017 | A recursion (cycle) exists in scoring determination dependencies of BO &1 |
018 | Structure &1 could not be created |
019 | Business object name &1 already exists |
020 | Configuration for business object &1 was activated |
021 | Active version does not exist for business object &1 |
022 | Inactive version does not exist for business object &1 |
023 | Structure/database table &1 was deleted |
024 | Structure/database table &1 could not be deleted |
025 | Business Object &1 was not generated and cannot be deleted |
026 | Name proposal is not possible |
027 | Association is not maintained for node &1 as &2 node for &3 &4 |
028 | Association does not exist from node &1 to node &2 |
029 | Method &1 of class &2 for &3 &4 was implemented incorrectly |
030 | Enter namespace and/or prefix for proper name proposals |
031 | ABAP OO class &1 does not implement the required interface &2 |
032 | ABAP OO class &1 does not exist in DDIC |
033 | Business object &1 was not found |
034 | Business object &1 could not be loaded |
035 | Business object name and business object model name are required |
036 | Access denied |
037 | A BOPF Business Object &1 already exists, but was not generated |
038 | &1 name already exists |
039 | &1 name contains characters that are not allowed |
040 | Version of business object &1 has been created |
041 | Choose exactly one version |
042 | Choose two versions for a comparison |
043 | No class name for access class maintained |
044 | Access Class &1 successfully generated |
045 | Node &1 is set lockable but not loadable |
046 | No interface name for constants interface maintained |
047 | Node category name &1 already exists |
048 | Query name/Query proxy name &1 already exists |
049 | Proxy business object is not original in this system (origin system &1) |
050 | Functionality is currently under construction |
051 | Business object &1 is a dependent object |
052 | Meta data error reported by Enterprise Service Framework |
053 | Business Object &1 already exists |
054 | Database table &1 already exists |
055 | Database table &1 has been created |
056 | Database table &1 could not be created |
057 | Database table &1 has been activated |
058 | Database table &1 could not be activated |
059 | Table type &1 already exists |
060 | Table type &1 has been created |
061 | Table type &1 could not be created |
062 | Table type &1 has been activated |
063 | Table type &1 could not be activated |
064 | Attribute mapping configuration is inconsistent |
065 | Attribute property configuration is inconsistent |
066 | Lost elements that are obsolete exist in the configuration |
067 | Run Check && Correct |
068 | Framework elements are missing, inconsistent or superfluous |
069 | Import of proxy &1 in BO &2 is prohibited because &2 is not a proxy BO |
070 | Class &1 of &2 &3 does not exist in the repository |
071 | Class &1 of &2 &3 does not implement the required interface &4 |
072 | Method &1 of class &2 has not been implemented (&3 &4) |
073 | Method &1 of class &2 has not been activated (&3 &4) |
074 | &1 cannot be called because it is not enabled for any node category |
075 | &1 is never executed because requesting nodes are not defined |
076 | Class /BOPF/CL_LIB_H_PLACEBO does not provide any functionality |
077 | Model elements are missing, inconsistent or superfluous |
078 | Test data container &1 does not exist |
079 | Test data container variant &1 does not exist |
080 | &1 is not maintained |
081 | Mapper class for &1 is not maintained |
082 | Target package name and/or correction number was not provided |
083 | Attribute Mapper Class failed to generate |
084 | Model inconsistent, cardinality &1 of association &2 unknown |
085 | Generic unit test currently only supported for proxy business objects |
086 | Business Object &1 is already assigned to the proxy business object &2 |
087 | LCP wrapper class &1 for BO node &2 has successfully generated |
088 | No BO Node with maintained class name for LCP wrapper class exists |
089 | Association Class for association &1 on node &2 is missing |
090 | Class/interface &1 of &2 &3 has syntax errors |
091 | &1 is not active or inconsistent |
092 | Class &1 of &2 &3 is not instanciable (instanciation not public) |
093 | Business object &1 is not a proxy business object |
094 | Runtime object of business object &1 has been invalidated |
095 | Business object &1 has been activated |
096 | Default queries have been generated |
097 | Element not visible in tree -> Settings... |
098 | Business object &1 has been renamed |
099 | Enter the new name for business object &1 |
100 | Attribute & is not an BOPF Element |
101 | &1 &2 |
102 | Attribute & does not exist |
103 | Database table &1 is not client-dependent |
104 | Primary key of database table &1 is configured incorrectly |
105 | Index on parent attribute &1 for database &2 is missing or incorrect |
106 | Primary key of database table &1 does contain superfluous elements |
107 | Index on alternative key &1 for database &2 is missing or incorrect |
108 | Obsolete way of structuring primary keys for database &1 detected |
109 | Business object &1 is not a projection of template BO &2 |
110 | Transient node &1 contains non-transient subnode &2 |
111 | Constants interface &1 has syntax errors (-> check element names) |
112 | Access class &1 has syntax errors (-> check alias names) |
113 | Proxy BO was imported incompletely; check model and re-import |
114 | BOPF BO version is out-of-date, please re-import proxy business object |
115 | Obsolete conversion rule &1 used in mapping for &2 &3 |
116 | Conversion rule &1 used in mapping for &2 &3 does not exist |
117 | Wrong datatype assigned to conversion rule &1 for field &2 in &3 &4 |
118 | Attribute &1 of database table &2 needs to be part of primary key |
119 | Attribute &1 of alt. key &2 for node &3 is not part of node structure |
120 | Alias &1 for &2 &3 already exists |
121 | Internal attribute for conversion rule &1 may not be assigned (&2 &3) |
122 | Class name for generated field mapping not maintained |
123 | Class &1 not generated (generated field mapping); check the class name |
124 | Business object has been adjusted; see list of changes |
125 | Business object is consistent |
126 | Association &1 from node &2 to &3 has wrong cardinality - 1:1, 1:c only |
127 | An interface method does not exist for message data type &1 |
128 | Different mapper classes for nodes with same proxy node name &1 found |
129 | Direct composition for nodes with same proxy node name &1 is mandatory |
130 | 'Key is equal to parent key' flag is mandatory for node &1 |
131 | Persistency mapping field &1 of node &2 does not exist on database &3 |
132 | Data type RAW16 mandatory for persistency mapping field &1 of node &2 |
133 | DB_GROUP &1 of node &2 persistency mapping does not exist on database |
134 | Superfluous attribute &1 found for database &2 of node &3 |
135 | Node &1 within DO will not be configured as 'Can be locked separately' |
136 | Node category contains status schema but status class is missing |
137 | Status schema &1 of node category &2 does not exist |
138 | Constants interface missing in association attribute binding: &1 |
139 | ValueFrom &1 not found in interface &2 for assoc.binding: &3 |
140 | ValueFrom &1 not found in proxy paramstruc. &2 for assoc.binding:&3 |
141 | ValueFrom &1 not found in data of source node &2 for assoc.bind.:&3 |
142 | Attribute &1 not found in datastructure of node &2 for assoc.binding: &3 |
143 | Error in test data container tool |
144 | Variants already existing and not overwritten |
145 | One attribute &1 needs to be marked as not redundant in &2 mapping: &3 |
146 | Redundant flag(s) missing for redundant attribute &1 in &2 mapping: &3 |
147 | Performance leak: Maintain static properties for node category &1 in ESR |
148 | Action &1 for adoption of foreign numbers already exists |
149 | Action &1 for adoption of foreign numbers created |
150 | Interface &1 does not include the tag interface /BOPF/IF_LIB_CONSTANTS |
151 | Class &1 does not implement tag interface &2 |
152 | Table type &1 was deleted |
153 | Table type &1 could not be deleted |
154 | Data element &1 was deleted |
155 | Data element &1 could not be deleted |
156 | Constants interface &1 of &2 of &3 does not exist |
157 | Field &1 of alternative key &2 node &3 is not mapped to any proxy field |
158 | Library class &1 is obsolete |
159 | Class &1 inherits from obsolete library class &2 |
160 | &1 must include &2 |
161 | &1 must be of line type &2 |
162 | &1 is missing |
163 | &1 does not exist |
164 | &1 does not exist in an active version |
165 | &1 must be of type &2 |
166 | &1 must be enhancable (&2) |
167 | &1 must be enhancable ("character-type" or "character-type or numeric") |
168 | Error in LCP facade |
169 | Structure &1 could not be created (attribute information missing) |
170 | Test Data Container variant is not maintained |
171 | Status schema is not maintained in node category &1 |
172 | Datatype used for group &1 of database &2 not found in node datatype &3 |
173 | Proxy attribute &1&4 of &2 &3 is not mapped or not set to final disable |
174 | Access class is out of date: Regeneration necessary |
175 | Check determination dependency (&1 likely to be successor of &2) |
176 | No status class maintained - status node is disabled during runtime |
177 | Root node key &1 does not exist |
178 | BO Container generation cancelled |
179 | Generated Mapper Class is out of date: Regeneration necessary |
180 | Transient nodes must not be set as separately loadable |
181 | Transient nodes must not be set as separately lockable |
182 | Conversion rule &1 is mandatory for mapping of attribute &2 in &3 &4 |
183 | Conversion rule &1 is superfluous for mapping of attribute &2 in &3 &4 |
184 | Superfluos conv. rule &1 is assigned; proxy attr. has no directive '&2' |
185 | Error during cleanup of duplicate entities |
186 | Due to model refactoring a model cleanup has to be performed |
187 | Internal alternative key &1 of node &2 shall not contain attribute &3 |
188 | Cleanup after refactoring executed successfully |
189 | Extensibility: Node &1 uses unknown BOPF buffer &2 |
190 | Extensibility: Node &1 is not extensible, but extension include is given |
191 | Extensibility: Node &1 is extensible, but no ext. include is registered |
192 | Extensibility: Node &1 is extensible, but no extension include is given |
193 | Extensibility: Ext. include &1 differs from &2 in extension registration |
194 | Extensibility: Extension include &1 has wrong enhancement category |
195 | Extensibility: Datatype &1 does not contain extension include &2 |
196 | Extensibility: Databasetable &1 does not contain extension include &2 |
197 | Extensibility: Node &1 does not exist in proxy model |
198 | Extensibility: Check whether node &1 is extensible failed |
199 | Class &1 must only be used in &2 actions |
200 | Class &1 must only be used in &2 |
201 | Class &1 must only be used in &2 validations |
202 | Action &1 for handling of business object events already exists |
203 | Combined table type of node &1 does not have secondary key &2 for &3 &4 |
204 | Second. key &1 of comb. tab. type of node &2 does not start with field &3 |
205 | A secondary key should be specified for &1 &2 |
206 | Second. key &1 of comb. tab. type of &2 does not start with a field of &3 |
207 | Field &1 of value set is not part of structure of &2 |
208 | Attribute &1 for value set &1 in &2 &3 missing |
209 | Functionality currently not available |
210 | Datatype of alt.key &1 should be structured; generated field mapping used |
211 | &1 name may not be initial |
212 | Maintained status associations of node &1 do not match |
213 | No status associations maintained for node &1. Run check && correct |
214 | No status associations maintained for node &1 |
215 | Mapping of attr. &1 of &2 &3 superfluous; Proxy attr. is final disabled |
216 | Performance warning: Generated field mapping is not being used |
217 | Lock behavior '&1' must not be used for proxy Business Objects |
218 | Mandatory attribute &1 of consistency group &2 is missing |
219 | Could not retrieve access trace |
220 | &1 is not a consist. status variable and used in &2 &3. Please check type |
221 | Immediate consistency check not possible for status var. with 3 states |
222 | Dependent dets. before retrieve &1 and &2 do not have common trigger node |
223 | Dependent determinations &1 and &2 are not enabled for a common exec time |
224 | Categories of dependent validations &1 and &2 differ. Check dependency |
225 | Dependent act. validations &1 and &2 have no common action. Please check |
226 | Group node must not be hierarchically lower than assigned validations |
227 | Proxy attr. &1&2 of &3 &4 mapped as redundant but not set final read-only |
228 | Group node must not be hierarchically lower than assigned DO nodes |
229 | Association is used in model - implementation or assoc binding necessary |
230 | Association set as "modeled" but not set as foreign key |
231 | Trigger nodes of det. &1 exec. 'Before Retrieve' need to be transient |
232 | Dependent dets. after loading &1 and &2 not trig. for same loading group |
233 | &1 must be '&2' |
234 | &1 must be '&2' or inherit from it |
235 | Model information is corrupt. Please contact support |
236 | Import of delta data failed |
237 | NodeID construction rule not maintained. Run check && correct |
238 | Wrong NodeID construction rule not maintained. Run check && correct |
239 | Obsolet entries in DB-Table SCOL_NODE_ID_CON found |
240 | DO connection not standard - DO relic determination not added |
241 | DO library class &1 recommended for implementation of DO association &2 |
242 | Constant &1 not found in interface &2 for attribute mapping of node &3 |
243 | Node &1 is not configured as trigger node of determination &2 |
244 | Attr. &1 of &2 &3 mapped using a constant but not set final read-only |
245 | Action &1 for handling of business object events created |
246 | Det. at time "after loading" has no (or only modelled) write node |
247 | Attribute info. missing for write node of det. at time "after loading" |
248 | Data type of attr. &1 in mapping of &2 &3 is not compatible to proxy type |
249 | Length of attr. &1 in mapping of &2 &3 not equal to length of proxy attr. |
250 | Performance leak: Status Nodes still used in model |
251 | Missing create, update or delete trigger for node &1 of determination &2 |
252 | Data element &1 used for &2 alt.key &3 deviates from node attr. |
253 | Data type/length mismatch between &1 alt.key &2 and node attr. |
254 | Include &1 in structure &2 must have group name '&3' |
255 | Dtel of ValueFrom &1 deviates from attr. &2 of node &3 assoc.bind. &4 |
256 | Type/length mismatch between ValueFrom &1 and attr. &2 of node &3 for &4 |
257 | Link to DO is stored at DO; Source attribute &1 is superfluous |
258 | Attribute Mapper Class &1 was generated successfully |
259 | Data element &1 of altkey &2 needs to be of type &3 |
260 | Database index &1 already exists |
261 | Database index &1 has been created |
262 | Database index &1 could not be created |
263 | Database index &1 has been activated |
264 | Database index &1 could not be activated |
265 | Database table &1 does not exist |
266 | Mandatory data type &1 and table type &2 missing for alt.key. &3 |
267 | Table type &1 of alt.key. &2 needs to be a standard table |
268 | Transaction mode '&1' shall be used for proxy Business Objects |
269 | Change mode '&1' shall be used for det. &2 (exec. time '&3') |
270 | Determination cat. '&1' shall be used for det. &2 (exec. time '&3') |
271 | Action &1 uses change mode '&2' and has no (or only modeled) write nodes |
272 | Write node attr. &1 of determination &2 is not transient |
273 | Only assoc. binding category '&1' is allowed for composition bindings |
274 | Node &1 has a property det. or status but property change trigger missing |
275 | Missing trigger (Create/Update/Delete) for property change trigger &1 |
276 | Subtree properties are enabled but buffer dispatcher &1 is not maintained |
277 | Buffer dispatcher &1 is in use but node &2 has no buffer class maintained |
278 | Conversion rule &1 is in use in mapping for attr. &2 of &3 &4 |
279 | Property buffer class &1 is suggested for property node &2 |
280 | Class names were proposed. Check proposals and execute generation again |
281 | Business object &1 is set to final |
282 | Class &1 must be regenerated due to model changes |
283 | Wrong change mode used for library class (see library settings) |
284 | Subclass of class &1 recommended for implementation of DO association &2 |
285 | Nothing to be generated |
286 | Namespace or prefix not maintained |
287 | Lock/Unlock action shall use common class (suggestion: &1) |
288 | Node &1 needs to be configured as lockable separately |
289 | Message registry not available |
290 | All messages are already registered |
291 | Messages have been registered |
292 | No messages for registration found |
293 | Usage of message &1 &2 could not be registered (message not registered) |
294 | Registration of messages failed |
295 | Library class &1 is in status released but offers no documentation |
296 | Locking class mismatch: &1 uses class &2, but action &3 uses class &4 |
297 | Value &1 is not in the value range of domain &2 |
298 | Table type &1 of alt.key. &2 shall not have unique primary/secondary keys |
299 | Missing mandatory attr. KEY in &1 key of table type &2 (node &3) |
300 | Superfluous attributes in &1 key of table type &2 (node &3) |
301 | Table row used as key def. in &1 key of table type &2 (node &3) |
302 | Table type &1 of node &2 shall not use a unique &3 key |
303 | Class &1 needs to implement CREATE method, assoc. is create enabled |
304 | Msg. registry of lib. &1 inconsistent: &2 does not contain text attr. &3 |
305 | Determination cat. of det. &1 does not match edit mode |
306 | Index on reverse foreign key attr. &1 for database &2 missing/incorrect |
307 | Action property change trigger missing for SAM action &1 |
308 | Superfluous write node &1 for det. &2 (no cross lock group request nodes) |
309 | Write node(s) missing for det. &1; request nodes trigger cross lockgroups |
310 | Edit mode '&1' not allowed for persist. det. &2; cross-lock trigger exist |
311 | Library class '&1' shall be used as &2 on node &3 |
312 | Library validation &1 shall be configured as &2 with trigger &3 |
313 | ESI alt.key &1 shall not be configured as not-unique |
314 | Filtered assoc. &1 without implementation class or association binding |
315 | Request node &1~TO_ROOT is superfluous; &2~TO_PARENT is sufficient |
316 | Assoc. &1 configured as '&2' for attr. &3; use pattern: '&4' |
317 | Execution time of det. &1 shall be exclusively: '&2' |
318 | Business object &1 is abstract and cannot be instantiated |
319 | Code proposal not possible due to insufficient model information |
320 | Root node &1 needs to be lockable separately |
321 | Lock class &1 does not support lock-depth of node &2 |
322 | BOPF lock classes do not support lock-depth > 3 |
323 | Val. &1 configured for consist. group &2 but CHECK trigger missing |
324 | Trigger node &1 is in separat lockgroup; remove request node for det. &2 |
325 | No active version selected for generation of note |
326 | There is already a note for a higher support package level |
327 | Note &1 for support package level &2 already exists |
328 | Support package level needs to be in the range of SP &1 and SP &2 |
329 | There is already a note for version &1 |
330 | There is already a note for version in the selected version range |
331 | Invalid status of note implementation (should be "in process") |
332 | Note inconsistent. Please contact SAP Support. |
333 | Support package level or release of note do not match system status |
334 | No SAP Release found for business object &1 |
335 | No relevant changes found |
336 | Note existence could not be checked |
337 | Note &1 does not exist |
338 | No Software Component found for business object &1 |
339 | Business Object is still used by inheriting Business Object |
340 | After loading determination &1 uses a node with non-caching buffer |
341 | GenIL component &1 could not be registered |
342 | GenIL component &1 could not be deregistered |
343 | GenIL &1 name &2 already exists |
344 | &1 GenIL name must not be initial |
345 | GenIL component name is already in use |
346 | GenIL prefix is already in use |
347 | GenIL component name must not be initial |
348 | GenIL prefix must not be initial |
349 | Design Documents can only be generated in Unicode Systems |
350 | Query &1 not provided by GenIL due to missing query data type |
351 | GenIL component is not yet registered |
352 | Regeneration of BOPF Constant Interface &1 failed |
353 | Version not marked as extendible but inherited extendible nodes exist |
354 | Constant Interface defined in Association Binding does not exist (&1) |
355 | Constant of Interface defined in Association Binding doesn't exist (&1) |
356 | Association Binding of Association &1 incomplete |
357 | Authorization object &1 does not exit |
358 | Authorization field &1 of object &2 is already mapped |
359 | Authorization field &1 does not exist at object &2 |
360 | Authorization object &1 is not assigned to node |
361 | Authorization object &1 is already assigned to node |
362 | Authorization object &1 does not contain generic field &2 |
363 | Authorization relevance flag marked, but check class not specified |
364 | Authorization check class specified, but relevance flag not marked |
365 | Authorization check class &1 does not exist |
366 | Auth. class &1 does not inherit from /BOBF/CL_[FRW|LIB]_AUTHORITY_CHECK |
367 | Authorization field mapping: target attribute &1 does not exist |
368 | Auth. assignment/mapping exists, but relevance flag at node not marked |
369 | Auth. field mapping: target attribute &1 not charlike or length > 40 |
370 | Query has to be implemented, since authority checking is switched on |
371 | Const. interf. &1 has missing &2 attributes (&3 has no active version) |
372 | Business Object &1 selected for load invalidation |
373 | BO Load of &1 was invalidated with return code &2; terminate_changer='&3' |
374 | BO Load of &1 was freed with return code &2; terminate_changer='&3' |
375 | System Maintenance in parallel: Only display operations are possible |
376 | An inactive version of BO &1 exists; Activate in ADT before editing |
377 | BO &1 was not previously locked by current user; change not possible |
378 | Determination pattern not supported |
379 | Determination pattern &1: No trigger node |
380 | Determination pattern &1: Trigger node not transient |
381 | Determination pattern &1: Set trigger node for one of &2 |
382 | No evaluation timepoint |
383 | Determination pattern &1: Remove trigger node for any of &2 |
384 | Display mode only |
385 | Display mode only (Enhancement object) |
386 | No attributes: Missing combined structure |
387 | No attributes: Check combined structure |
388 | Data Type &1 already exists |
389 | Delete BO &1 via modify core service not possible; Use action ROOT-DELETE |
390 | Validation &1 marked as Check Before Save, but Check trigger missing |
391 | Transient structure &1 of node &2 uses element name &3 of persist. struc. |
392 | &1: no Trigger defined |
393 | Alternative Key Field &1 does not exist in Node Persistent Structure |
394 | Alternative Key &1 has no Field defined |
395 | Alternative Key &1 has no Data Type defined |
396 | Alternative Key &1 has no Data Table Type defined |
397 | &1 name has to begin with 'A-Z', '_' or '/' |
398 | DB index &1 is not used by an Alt. Key definition. Please check/delete. |
399 | Structure &1 has check issues in DDIC. Please check/correct. |
400 | Structured Alternative Key &1 must not be named with a field name |
401 | Structure &1 must not contain a client field (data type CLNT) |
402 | Structure &1 contains field name &2, which is reserved by BOPF |
403 | Structure &1 contains field name &2, which doesn't start with a letter |
404 | Missing create, update or delete trigger for node &1 of validation &2 |
405 | Data Type of Alternative Key &1 is not of type 'Data element' |
406 | Neither Association Binding nor Association Class defined |
407 | Adding BO to transport fails during Constant Interface generation |
408 | Structure &1 contains component &2 with type 'TYPE REF TO' |
409 | Structure &1 contains component &2 with type structure or table type |
410 | Interface &1 does not need to be generated. Configuration is not changed. |
411 | Alternative Key &1 contains the same fields as Alternative Key &2 |
412 | authority field mapping of node &1 uses non-existent association |
413 | Legacy DAC can't be applied for node &1: Alternative Key &2 is missing |
414 | Display mode only (Business Object is generated from CDS View) |
415 | Custom Action &1 has typed exporting parameter (not allowed for Draft) |
416 | Chosen determination pattern is invalid for Generated BOs |
417 | Invalid Lock Behavior |
418 | Be sure to end the session after SAVE or CLEANUP |
419 | Invalid Transaction Mode |
420 | This Lock Behavior only supports Transaction Mode "Endless Editing" |
421 | Lock Behavior "Update Lock" does not support "Endless Editing" |
422 | Dependent Object &1 is already associated with node &2 |
423 | Association for action &1 with read / write node does not exist |
424 | Please use the Eclipse-based BO editor (it will replace transaction BOBX) |
425 | &1 name has to end with 'A-Z' or '0-9' |
426 | Authority check class must inherit from &1 (&2) |
427 | DELETE action class must inherit from &1 (&2) |
428 | Implementation of LOCK action must inherit from &1 (&2) |
429 | Draft class must inherit from &1 (&2) |
430 | Exporting parameter of action &1 defined incompletely |
431 | BOBX is locked for your user. Please use BOPF in Eclipse instead |
432 | BO &1 already exists in another system (&2) |
433 | LOCK action class must be or must inherit from &1 (&2) |
434 | Missing trigger (Create/Update/Delete) for validation &1 of node &2 |
435 | Save rejected: cannot delete generated node! Node keys are inconsistent! |
436 | Save rejected: root node key is inconsistent! |
437 | BO '&1' doesn't use Smart Validations; migrate the BO using report &2 |
438 | Multiple status variables are assigned to attribute &1 on node &2 |
439 | Current association category only supports binding operator "EQ" (&1) |
440 | Exporting parameter structure &1 of action &2 is not a flat structure |
441 | Dependency between enhancement and core determination is not supported |
443 | A recursion (cycle) exists in scoring validation dependencies of BO &1 |
444 | Fatal configuration error: BO &1 root node missing |
445 | Data type &1 of alternative key &2 does not exist (BO &3, node &4) |
446 | Lock action &1 does not support key type of BO node &2-&3 |
447 | Action name &1 is reserved for draft support. Choose an other name |
448 | You are not authorized |
449 | Delete Trigger has no effect for node &1 of validation &2 |
450 | Altern. Key &1 contains same fields as DB_KEY (both w/ Uniqueness Check) |
451 | Don't define a Finalization Dependency to 'RAP' Business Object &1 |
452 | Abstract Entity &1 (Exporting Parameter) does not exist (Action &2) |
453 | Node component &1 used for Alternative key &2 (&3) has data type SSTRING |
456 | Library Class &1 is not released for RAP-enabled BOs |
457 | Super Library Class &1 (Inheritance) is not released for RAP-enabled BOs |
458 | Library Class &1 is marked 'obsolete' for RAP-enabled BOs |
459 | Super Lib. Class &1 (Inheritance) is marked 'obsolete' for RAP-enabl. BOs |
460 | Target BO is 'RAP-enabled', Source BO is not (or vice versa) (&1) |
461 | Constants Interface &1 was generated based on the active version of &2 |
462 | Business Object &1 may be outdated, Synchronization w/ BDEF/CDS required |
463 | 'Exporting Parameter BO' of action &1 is initial |
464 | 'Exporting Parameter Node' of action &1 is initial |
465 | 'Exporting Parameter BO' of action &1 does not exist (unknown BO key) |
466 | 'Exporting Parameter Node' of action &1 does not exist (unknown Node key) |
467 | Define Struct. + Tabletype parallel to Abstr. Entity &1 in AI (Action &2) |
468 | Abstract Entity &1 (Importing Parameter) does not exist (Action &2) |
469 | Define Struct. + Tabletype parallel to Abstr. Entity &1 in AI (Action &2) |
470 | Display mode only (RAP enabled BO) |
471 | Activate corresponding CDS View (this will trigger Check && Correct) |
472 | Change BO slightly and activate BO (this will trigger Check && Correct) |
473 | Code exit RESUME is not available in RAP: Adapt class &1 |
474 | Code exit CHECK_STATIC_AUTHORITY is not available in RAP: Adapt class &1 |
475 | Binding w/ 'Data Acc. relevant' supports op. EQ|NE|GT|GE|LT|LE only (&1) |
476 | Editing in BOBF will prevent editing in BOBX, ADT, BOB |
899 | &1&2&3&4 |