SAP ABAP Message Class /BOBF/CONF (/BOBF/CONF)
Basic Data
Hierarchy
☛
SAP_BS_FND (Software Component) SAP Business Suite Foundation
⤷
AP-RC-BOF-CFN (Application Component) Business Object Processing Framework Configuration
⤷
/BOBF/CONFIGURATION (Package) Business Object Processing Configuration
SAP_BS_FND (Software Component) SAP Business Suite Foundation⤷
AP-RC-BOF-CFN (Application Component) Business Object Processing Framework Configuration⤷
/BOBF/CONFIGURATION (Package) Business Object Processing Configuration 
Attributes
| Message class |  |
/BOBF/CONF |
| Short Description |  |
|
| Changed On |  |
20140121 |
| Last Changed At |  |
111007 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 |  000 |
Configuration error has occurred | The short text describes the object sufficiently | |
| 2 | 001 |
Configuration has been saved | The short text describes the object sufficiently | |
| 3 | 002 |
Error occurred while reading the configuration data | The short text describes the object sufficiently | |
| 4 | 003 |
Configuration errors were not found | The short text describes the object sufficiently | |
| 5 | 004 |
No access to business object &1 proxy data | The short text describes the object sufficiently | |
| 6 | 005 |
Interface &1 was generated successfully | The short text describes the object sufficiently | |
| 7 | 006 |
Interface &1 could not be generated | The short text describes the object sufficiently | |
| 8 | 007 |
Internal error in configuration management | The short text describes the object sufficiently | |
| 9 | 008 |
Could not find the requested element | The short text describes the object sufficiently | |
| 10 | 009 |
The configuration was not changed | The short text describes the object sufficiently | |
| 11 | 010 |
An error occurred while saving the configuration | The short text describes the object sufficiently | |
| 12 | 011 |
Unknown business object | The short text describes the object sufficiently | |
| 13 | 012 |
Business object &1 not active | The short text describes the object sufficiently | |
| 14 | 013 |
Structure &1 has been created | The short text describes the object sufficiently | |
| 15 | 014 |
Structure &1 has been activated | The short text describes the object sufficiently | |
| 16 | 015 |
Structure &1 could not be activated | The short text describes the object sufficiently | |
| 17 | 016 |
Structure &1 already exists | The short text describes the object sufficiently | |
| 18 | 017 |
A recursion exists in the scoring dependencies | The short text describes the object sufficiently | |
| 19 | 018 |
Structure &1 could not be created | The short text describes the object sufficiently | |
| 20 | 019 |
Business object name &1 already exists | The short text describes the object sufficiently | |
| 21 | 020 |
Configuration for business object &1 was activated | The short text describes the object sufficiently | |
| 22 | 021 |
Active version does not exist for business object &1 | The short text describes the object sufficiently | |
| 23 | 022 |
Inactive version does not exist for business object &1 | The short text describes the object sufficiently | |
| 24 | 023 |
Structure/database table &1 was deleted | The short text describes the object sufficiently | |
| 25 | 024 |
Structure/database table &1 could not be deleted | The short text describes the object sufficiently | |
| 26 | 025 |
Business Object &1 was not generated and cannot be deleted | The short text describes the object sufficiently | |
| 27 | 026 |
Name proposal is not possible | The short text describes the object sufficiently | |
| 28 | 027 |
Association is not maintained for node &1 as &2 node for &3 &4 | The short text describes the object sufficiently | |
| 29 | 028 |
Association does not exist from node &1 to node &2 | The short text describes the object sufficiently | |
| 30 | 029 |
Method &1 of class &2 for &3 &4 was implemented incorrectly | The short text describes the object sufficiently | |
| 31 | 030 |
Enter namespace and/or prefix for proper name proposals | The short text describes the object sufficiently | |
| 32 | 031 |
ABAP OO class &1 does not implement the required interface &2 | The short text describes the object sufficiently | |
| 33 | 032 |
ABAP OO class &1 does not exist in DDIC | The short text describes the object sufficiently | |
| 34 | 033 |
Business object &1 was not found | The short text describes the object sufficiently | |
| 35 | 034 |
Business object &1 could not be loaded | The short text describes the object sufficiently | |
| 36 | 035 |
Business object name and business object model name are required | The short text describes the object sufficiently | |
| 37 | 036 |
Access denied | The short text describes the object sufficiently | |
| 38 | 037 |
A BOPF Business Object &1 already exists, but was not generated | The short text describes the object sufficiently | |
| 39 | 038 |
&1 name already exists | The short text describes the object sufficiently | |
| 40 | 039 |
&1 name contains characters that are not allowed | The short text describes the object sufficiently | |
| 41 | 040 |
Version of business object &1 has been created | The short text describes the object sufficiently | |
| 42 | 041 |
Choose exactly one version | The short text describes the object sufficiently | |
| 43 | 042 |
Choose two versions for a comparison | The short text describes the object sufficiently | |
| 44 | 043 |
No class name for access class maintained | The short text describes the object sufficiently | |
| 45 | 044 |
Access Class &1 successfully generated | The short text describes the object sufficiently | |
| 46 | 045 |
Node &1 is set lockable but not loadable | The short text describes the object sufficiently | |
| 47 | 046 |
No interface name for constants interface maintained | The short text describes the object sufficiently | |
| 48 | 047 |
Node category name &1 already exists | The short text describes the object sufficiently | |
| 49 | 048 |
Query name/Query proxy name &1 already exists | The short text describes the object sufficiently | |
| 50 | 049 |
Proxy business object is not original in this system (origin system &1) | The short text describes the object sufficiently | |
| 51 | 050 |
Functionality is currently under construction | The short text describes the object sufficiently | |
| 52 | 051 |
Business object &1 is a dependent object | The short text describes the object sufficiently | |
| 53 | 052 |
Meta data error reported by Enterprise Service Framework | The short text describes the object sufficiently | |
| 54 | 053 |
Business Object &1 already exists | The short text describes the object sufficiently | |
| 55 | 054 |
Database table &1 already exists | The short text describes the object sufficiently | |
| 56 | 055 |
Database table &1 has been created | The short text describes the object sufficiently | |
| 57 | 056 |
Database table &1 could not be created | The short text describes the object sufficiently | |
| 58 | 057 |
Database table &1 has been activated | The short text describes the object sufficiently | |
| 59 | 058 |
Database table &1 could not be activated | The short text describes the object sufficiently | |
| 60 | 059 |
Table type &1 already exists | The short text describes the object sufficiently | |
| 61 | 060 |
Table type &1 has been created | The short text describes the object sufficiently | |
| 62 | 061 |
Table type &1 could not be created | The short text describes the object sufficiently | |
| 63 | 062 |
Table type &1 has been activated | The short text describes the object sufficiently | |
| 64 | 063 |
Table type &1 could not be activated | The short text describes the object sufficiently | |
| 65 | 064 |
Attribute mapping configuration is inconsistent | The short text describes the object sufficiently | |
| 66 | 065 |
Attribute property configuration is inconsistent | The short text describes the object sufficiently | |
| 67 | 066 |
Lost elements that are obsolete exist in the configuration | The short text describes the object sufficiently | |
| 68 | 067 |
Run Check && Correct | Space: object requires documentation | |
| 69 | 068 |
Framework elements are missing, inconsistent or superfluous | The short text describes the object sufficiently | |
| 70 | 069 |
Import of proxy &1 in BO &2 is prohibited because &2 is not a proxy BO | The short text describes the object sufficiently | |
| 71 | 070 |
Class &1 of &2 &3 does not exist in the repository | The short text describes the object sufficiently | |
| 72 | 071 |
Class &1 of &2 &3 does not implement the required interface &4 | The short text describes the object sufficiently | |
| 73 | 072 |
Method &1 of class &2 has not been implemented (&3 &4) | The short text describes the object sufficiently | |
| 74 | 073 |
Method &1 of class &2 has not been activated (&3 &4) | The short text describes the object sufficiently | |
| 75 | 074 |
&1 cannot be called because it is not enabled for any node category | The short text describes the object sufficiently | |
| 76 | 075 |
&1 is never executed because requesting nodes are not defined | The short text describes the object sufficiently | |
| 77 | 076 |
Class /BOPF/CL_LIB_H_PLACEBO does not provide any functionality | The short text describes the object sufficiently | |
| 78 | 077 |
Model elements are missing, inconsistent or superfluous | The short text describes the object sufficiently | |
| 79 | 078 |
Test data container &1 does not exist | The short text describes the object sufficiently | |
| 80 | 079 |
Test data container variant &1 does not exist | The short text describes the object sufficiently | |
| 81 | 080 |
&1 is not maintained | The short text describes the object sufficiently | |
| 82 | 081 |
Mapper class for &1 is not maintained | The short text describes the object sufficiently | |
| 83 | 082 |
Target package name and/or correction number was not provided | The short text describes the object sufficiently | |
| 84 | 083 |
Attribute Mapper Class failed to generate | The short text describes the object sufficiently | |
| 85 | 084 |
Model inconsistent, cardinality &1 of association &2 unknown | The short text describes the object sufficiently | |
| 86 | 085 |
Generic unit test currently only supported for proxy business objects | The short text describes the object sufficiently | |
| 87 | 086 |
Business Object &1 is already assigned to the proxy business object &2 | The short text describes the object sufficiently | |
| 88 | 087 |
LCP wrapper class &1 for BO node &2 has successfully generated | The short text describes the object sufficiently | |
| 89 | 088 |
No BO Node with maintained class name for LCP wrapper class exists | The short text describes the object sufficiently | |
| 90 | 089 |
Association Class for association &1 on node &2 is missing | The short text describes the object sufficiently | |
| 91 | 090 |
Class/interface &1 of &2 &3 has syntax errors | The short text describes the object sufficiently | |
| 92 | 091 |
&1 is not active or inconsistent | The short text describes the object sufficiently | |
| 93 | 092 |
Class &1 of &2 &3 is not instanciable (instanciation not public) | The short text describes the object sufficiently | |
| 94 | 093 |
Business object &1 is not a proxy business object | The short text describes the object sufficiently | |
| 95 | 094 |
Runtime object of business object &1 has been invalidated | The short text describes the object sufficiently | |
| 96 | 095 |
Business object &1 has been activated | The short text describes the object sufficiently | |
| 97 | 096 |
Default queries have been generated | The short text describes the object sufficiently | |
| 98 | 097 |
Element not visible in tree -> Settings... | The short text describes the object sufficiently | |
| 99 | 098 |
Business object &1 has been renamed | The short text describes the object sufficiently | |
| 100 | 099 |
Enter the new name for business object &1 | The short text describes the object sufficiently | |
| 101 | 100 |
Attribute & is not an BOPF Element | The short text describes the object sufficiently | |
| 102 | 101 |
&1 &2 | The short text describes the object sufficiently | |
| 103 | 102 |
Attribute & does not exist | The short text describes the object sufficiently | |
| 104 | 103 |
Database table &1 is not client-dependent | The short text describes the object sufficiently | |
| 105 | 104 |
Primary key of database table &1 is configured incorrectly | The short text describes the object sufficiently | |
| 106 | 105 |
Index on parent attribute &1 for database &2 is missing or incorrect | The short text describes the object sufficiently | |
| 107 | 106 |
Primary key of database table &1 does contain superfluous elements | Space: object requires documentation | |
| 108 | 107 |
Index on alternative key &1 for database &2 is missing or incorrect | The short text describes the object sufficiently | |
| 109 | 108 |
Obsolete way of structuring primary keys for database &1 detected | The short text describes the object sufficiently | |
| 110 | 109 |
Business object &1 is not a projection of template BO &2 | The short text describes the object sufficiently | |
| 111 | 110 |
Transient node &1 contains non-transient subnode &2 | The short text describes the object sufficiently | |
| 112 | 111 |
Constants interface &1 has syntax errors (-> check element names) | The short text describes the object sufficiently | |
| 113 | 112 |
Access class &1 has syntax errors (-> check alias names) | The short text describes the object sufficiently | |
| 114 | 113 |
Proxy BO was imported incompletely; check model and re-import | The short text describes the object sufficiently | |
| 115 | 114 |
BOPF BO version is out-of-date, please re-import proxy business object | The short text describes the object sufficiently | |
| 116 | 115 |
Obsolete conversion rule &1 used in mapping for &2 &3 | The short text describes the object sufficiently | |
| 117 | 116 |
Conversion rule &1 used in mapping for &2 &3 does not exist | The short text describes the object sufficiently | |
| 118 | 117 |
Wrong datatype assigned to conversion rule &1 for field &2 in &3 &4 | The short text describes the object sufficiently | |
| 119 | 118 |
Attribute &1 of database table &2 needs to be part of primary key | The short text describes the object sufficiently | |
| 120 | 119 |
Attribute &1 of alt. key &2 for node &3 is not part of node structure | The short text describes the object sufficiently | |
| 121 | 120 |
Alias &1 for &2 &3 already exists | The short text describes the object sufficiently | |
| 122 | 121 |
Internal attribute for conversion rule &1 may not be assigned (&2 &3) | The short text describes the object sufficiently | |
| 123 | 122 |
Class name for generated field mapping not maintained | The short text describes the object sufficiently | |
| 124 | 123 |
Class &1 not generated (generated field mapping); check the class name | The short text describes the object sufficiently | |
| 125 | 124 |
Business object has been adjusted; see list of changes | The short text describes the object sufficiently | |
| 126 | 125 |
Business object is consistent | The short text describes the object sufficiently | |
| 127 | 126 |
Association &1 from node &2 to &3 has wrong cardinality - 1:1, 1:c only | The short text describes the object sufficiently | |
| 128 | 127 |
An interface method does not exist for message data type &1 | The short text describes the object sufficiently | |
| 129 | 128 |
Different mapper classes for nodes with same proxy node name &1 found | The short text describes the object sufficiently | |
| 130 | 129 |
Direct composition for nodes with same proxy node name &1 is mandatory | The short text describes the object sufficiently | |
| 131 | 130 |
'Key is equal to parent key' flag is mandatory for node &1 | The short text describes the object sufficiently | |
| 132 | 131 |
Persistency mapping field &1 of node &2 does not exist on database &3 | The short text describes the object sufficiently | |
| 133 | 132 |
Data type RAW16 mandatory for persistency mapping field &1 of node &2 | The short text describes the object sufficiently | |
| 134 | 133 |
DB_GROUP &1 of node &2 persistency mapping does not exist on database | The short text describes the object sufficiently | |
| 135 | 134 |
Superfluous attribute &1 found for database &2 of node &3 | Space: object requires documentation | |
| 136 | 135 |
Node &1 within DO will not be configured as 'Can be locked separately' | The short text describes the object sufficiently | |
| 137 | 136 |
Node category contains status schema but status class is missing | The short text describes the object sufficiently | |
| 138 | 137 |
Status schema &1 of node category &2 does not exist | The short text describes the object sufficiently | |
| 139 | 138 |
Constants interface missing in association attribute binding: &1 | The short text describes the object sufficiently | |
| 140 | 139 |
ValueFrom &1 not found in interface &2 for assoc.binding: &3 | The short text describes the object sufficiently | |
| 141 | 140 |
ValueFrom &1 not found in proxy paramstruc. &2 for assoc.binding:&3 | The short text describes the object sufficiently | |
| 142 | 141 |
ValueFrom &1 not found in data of source node &2 for assoc.bind.:&3 | The short text describes the object sufficiently | |
| 143 | 142 |
Attribute &1 not found in datastructure of node &2 for assoc.binding: &3 | The short text describes the object sufficiently | |
| 144 | 143 |
Error in test data container tool | The short text describes the object sufficiently | |
| 145 | 144 |
Variants already existing and not overwritten | The short text describes the object sufficiently | |
| 146 | 145 |
One attribute &1 needs to be marked as not redundant in &2 mapping: &3 | The short text describes the object sufficiently | |
| 147 | 146 |
Redundant flag(s) missing for redundant attribute &1 in &2 mapping: &3 | The short text describes the object sufficiently | |
| 148 | 147 |
Performance leak: Maintain static properties for node category &1 in ESR | Space: object requires documentation | |
| 149 | 148 |
Action &1 for adoption of foreign numbers already exists | The short text describes the object sufficiently | |
| 150 | 149 |
Action &1 for adoption of foreign numbers created | The short text describes the object sufficiently | |
| 151 | 150 |
Interface &1 does not include the tag interface /BOPF/IF_LIB_CONSTANTS | The short text describes the object sufficiently | |
| 152 | 151 |
Class &1 does not implement tag interface &2 | The short text describes the object sufficiently | |
| 153 | 152 |
Table type &1 was deleted | The short text describes the object sufficiently | |
| 154 | 153 |
Table type &1 could not be deleted | The short text describes the object sufficiently | |
| 155 | 154 |
Data element &1 was deleted | The short text describes the object sufficiently | |
| 156 | 155 |
Data element &1 could not be deleted | The short text describes the object sufficiently | |
| 157 | 156 |
Constants interface &1 of &2 of &3 does not exist | The short text describes the object sufficiently | |
| 158 | 157 |
Field &1 of alternative key &2 node &3 is not mapped to any proxy field | The short text describes the object sufficiently | |
| 159 | 158 |
Library class &1 is obsolete | The short text describes the object sufficiently | |
| 160 | 159 |
Class &1 inherits from obsolete library class &2 | The short text describes the object sufficiently | |
| 161 | 160 |
&1 must include &2 | The short text describes the object sufficiently | |
| 162 | 161 |
&1 must be of line type &2 | The short text describes the object sufficiently | |
| 163 | 162 |
&1 is missing | The short text describes the object sufficiently | |
| 164 | 163 |
&1 does not exist | The short text describes the object sufficiently | |
| 165 | 164 |
&1 does not exist in an active version | The short text describes the object sufficiently | |
| 166 | 165 |
&1 must be of type &2 | The short text describes the object sufficiently | |
| 167 | 166 |
&1 must be enhancable (&2) | The short text describes the object sufficiently | |
| 168 | 167 |
&1 must be enhancable ("character-type" or "character-type or numeric") | The short text describes the object sufficiently | |
| 169 | 168 |
Error in LCP facade | The short text describes the object sufficiently | |
| 170 | 169 |
Structure &1 could not be created (attribute information missing) | The short text describes the object sufficiently | |
| 171 | 170 |
Test Data Container variant is not maintained | The short text describes the object sufficiently | |
| 172 | 171 |
Status schema is not maintained in node category &1 | The short text describes the object sufficiently | |
| 173 | 172 |
Datatype used for group &1 of database &2 not found in node datatype &3 | The short text describes the object sufficiently | |
| 174 | 173 |
Proxy attribute &1&4 of &2 &3 is not mapped or not set to final disable | The short text describes the object sufficiently | |
| 175 | 174 |
Access class is out of date: Regeneration necessary | Space: object requires documentation | |
| 176 | 175 |
Check determination dependency (&1 likely to be successor of &2) | The short text describes the object sufficiently | |
| 177 | 176 |
No status class maintained - status node is disabled during runtime | The short text describes the object sufficiently | |
| 178 | 177 |
Root node key &1 does not exist | The short text describes the object sufficiently | |
| 179 | 178 |
BO Container generation cancelled | The short text describes the object sufficiently | |
| 180 | 179 |
Generated Mapper Class is out of date: Regeneration necessary | The short text describes the object sufficiently | |
| 181 | 180 |
Transient nodes must not be set as separately loadable | Space: object requires documentation | |
| 182 | 181 |
Transient nodes must not be set as separately lockable | Space: object requires documentation | |
| 183 | 182 |
Conversion rule &1 is mandatory for mapping of attribute &2 in &3 &4 | The short text describes the object sufficiently | |
| 184 | 183 |
Conversion rule &1 is superfluous for mapping of attribute &2 in &3 &4 | The short text describes the object sufficiently | |
| 185 | 184 |
Superfluos conv. rule &1 is assigned; proxy attr. has no directive '&2' | The short text describes the object sufficiently | |
| 186 | 185 |
Error during cleanup of duplicate entities | The short text describes the object sufficiently | |
| 187 | 186 |
Due to model refactoring a model cleanup has to be performed | The short text describes the object sufficiently | |
| 188 | 187 |
Internal alternative key &1 of node &2 shall not contain attribute &3 | The short text describes the object sufficiently | |
| 189 | 188 |
Cleanup after refactoring executed successfully | The short text describes the object sufficiently | |
| 190 | 189 |
Extensibility: Node &1 uses unknown BOPF buffer &2 | The short text describes the object sufficiently | |
| 191 | 190 |
Extensibility: Node &1 is not extensible, but extension include is given | The short text describes the object sufficiently | |
| 192 | 191 |
Extensibility: Node &1 is extensible, but no ext. include is registered | The short text describes the object sufficiently | |
| 193 | 192 |
Extensibility: Node &1 is extensible, but no extension include is given | The short text describes the object sufficiently | |
| 194 | 193 |
Extensibility: Ext. include &1 differs from &2 in extension registration | The short text describes the object sufficiently | |
| 195 | 194 |
Extensibility: Extension include &1 has wrong enhancement category | The short text describes the object sufficiently | |
| 196 | 195 |
Extensibility: Datatype &1 does not contain extension include &2 | The short text describes the object sufficiently | |
| 197 | 196 |
Extensibility: Databasetable &1 does not contain extension include &2 | The short text describes the object sufficiently | |
| 198 | 197 |
Extensibility: Node &1 does not exist in proxy model | The short text describes the object sufficiently | |
| 199 | 198 |
Extensibility: Check whether node &1 is extensible failed | The short text describes the object sufficiently | |
| 200 | 199 |
Class &1 must only be used in &2 actions | The short text describes the object sufficiently | |
| 201 | 200 |
Class &1 must only be used in &2 | The short text describes the object sufficiently | |
| 202 | 201 |
Class &1 must only be used in &2 validations | The short text describes the object sufficiently | |
| 203 | 202 |
Action &1 for handling of business object events already exists | The short text describes the object sufficiently | |
| 204 | 203 |
Combined table type of node &1 does not have secondary key &2 for &3 &4 | The short text describes the object sufficiently | |
| 205 | 204 |
Second. key &1 of comb. tab. type of node &2 does not start with field &3 | The short text describes the object sufficiently | |
| 206 | 205 |
A secondary key should be specified for &1 &2 | The short text describes the object sufficiently | |
| 207 | 206 |
Second. key &1 of comb. tab. type of &2 does not start with a field of &3 | The short text describes the object sufficiently | |
| 208 | 207 |
Field &1 of value set is not part of structure of &2 | The short text describes the object sufficiently | |
| 209 | 208 |
Attribute &1 for value set &1 in &2 &3 missing | The short text describes the object sufficiently | |
| 210 | 209 |
Functionality currently not available | The short text describes the object sufficiently | |
| 211 | 210 |
Datatype of alt.key &1 should be structured; generated field mapping used | The short text describes the object sufficiently | |
| 212 | 211 |
&1 name may not be initial | The short text describes the object sufficiently | |
| 213 | 212 |
Maintained status associations of node &1 do not match | The short text describes the object sufficiently | |
| 214 | 213 |
No status associations maintained for node &1. Run check && correct | The short text describes the object sufficiently | |
| 215 | 214 |
No status associations maintained for node &1 | The short text describes the object sufficiently | |
| 216 | 215 |
Mapping of attr. &1 of &2 &3 superfluous; Proxy attr. is final disabled | Space: object requires documentation | |
| 217 | 216 |
Performance warning: Generated field mapping is not being used | The short text describes the object sufficiently | |
| 218 | 217 |
Lock behavior '&1' must not be used for proxy Business Objects | The short text describes the object sufficiently | |
| 219 | 218 |
Mandatory attribute &1 of consistency group &2 is missing | The short text describes the object sufficiently | |
| 220 | 219 |
Could not retrieve access trace | The short text describes the object sufficiently | |
| 221 | 220 |
&1 is not a consist. status variable and used in &2 &3. Please check type | The short text describes the object sufficiently | |
| 222 | 221 |
Immediate consistency check not possible for status var. with 3 states | The short text describes the object sufficiently | |
| 223 | 222 |
Dependent dets. before retrieve &1 and &2 do not have common trigger node | The short text describes the object sufficiently | |
| 224 | 223 |
Dependent determinations &1 and &2 are not enabled for a common exec time | Space: object requires documentation | |
| 225 | 224 |
Categories of dependent validations &1 and &2 differ. Check dependency | The short text describes the object sufficiently | |
| 226 | 225 |
Dependent act. validations &1 and &2 have no common action. Please check | Space: object requires documentation | |
| 227 | 226 |
Group node must not be hierarchically lower than assigned validations | The short text describes the object sufficiently | |
| 228 | 227 |
Proxy attr. &1&2 of &3 &4 mapped as redundant but not set final read-only | Space: object requires documentation | |
| 229 | 228 |
Group node must not be hierarchically lower than assigned DO nodes | The short text describes the object sufficiently | |
| 230 | 229 |
Association is used in model - implementation or assoc binding necessary | Space: object requires documentation | |
| 231 | 230 |
Association set as "modeled" but not set as foreign key | The short text describes the object sufficiently | |
| 232 | 231 |
Trigger nodes of det. &1 exec. 'Before Retrieve' need to be transient | The short text describes the object sufficiently | |
| 233 | 232 |
Dependent dets. after loading &1 and &2 not trig. for same loading group | The short text describes the object sufficiently | |
| 234 | 233 |
&1 must be '&2' | The short text describes the object sufficiently | |
| 235 | 234 |
&1 must be '&2' or inherit from it | The short text describes the object sufficiently | |
| 236 | 235 |
Model information is corrupt. Please contact support | The short text describes the object sufficiently | |
| 237 | 236 |
Import of delta data failed | The short text describes the object sufficiently | |
| 238 | 237 |
NodeID construction rule not maintained. Run check && correct | The short text describes the object sufficiently | |
| 239 | 238 |
Wrong NodeID construction rule not maintained. Run check && correct | The short text describes the object sufficiently | |
| 240 | 239 |
Obsolet entries in DB-Table SCOL_NODE_ID_CON found | The short text describes the object sufficiently | |
| 241 | 240 |
DO connection not standard - DO relic determination not added | The short text describes the object sufficiently | |
| 242 | 241 |
DO library class &1 recommended for implementation of DO association &2 | The short text describes the object sufficiently | |
| 243 | 242 |
Constant &1 not found in interface &2 for attribute mapping of node &3 | The short text describes the object sufficiently | |
| 244 | 243 |
Node &1 is not configured as trigger node of determination &2 | The short text describes the object sufficiently | |
| 245 | 244 |
Attr. &1 of &2 &3 mapped using a constant but not set final read-only | The short text describes the object sufficiently | |
| 246 | 245 |
Action &1 for handling of business object events created | The short text describes the object sufficiently | |
| 247 | 246 |
Det. at time "after loading" has no (or only modelled) write node | Space: object requires documentation | |
| 248 | 247 |
Attribute info. missing for write node of det. at time "after loading" | Space: object requires documentation | |
| 249 | 248 |
Data type of attr. &1 in mapping of &2 &3 is not compatible to proxy type | The short text describes the object sufficiently | |
| 250 | 249 |
Length of attr. &1 in mapping of &2 &3 not equal to length of proxy attr. | The short text describes the object sufficiently | |
| 251 | 250 |
Performance leak: Status Nodes still used in model | The short text describes the object sufficiently | |
| 252 | 251 |
Missing create, update or delete trigger for node &1 of determination &2 | The short text describes the object sufficiently | |
| 253 | 252 |
Data element &1 used for &2 alt.key &3 deviates from node attr. | The short text describes the object sufficiently | |
| 254 | 253 |
Data type/length mismatch between &1 alt.key &2 and node attr. | The short text describes the object sufficiently | |
| 255 | 254 |
Include &1 in structure &2 must have group name '&3' | The short text describes the object sufficiently | |
| 256 | 255 |
Dtel of ValueFrom &1 deviates from attr. &2 of node &3 assoc.bind. &4 | Space: object requires documentation | |
| 257 | 256 |
Type/length mismatch between ValueFrom &1 and attr. &2 of node &3 for &4 | The short text describes the object sufficiently | |
| 258 | 257 |
Link to DO is stored at DO; Source attribute &1 is superfluous | The short text describes the object sufficiently | |
| 259 | 258 |
Attribute Mapper Class &1 was generated successfully | The short text describes the object sufficiently | |
| 260 | 259 |
Data element &1 of altkey &2 needs to be of type &3 | The short text describes the object sufficiently | |
| 261 | 260 |
Database index &1 already exists | The short text describes the object sufficiently | |
| 262 | 261 |
Database index &1 has been created | The short text describes the object sufficiently | |
| 263 | 262 |
Database index &1 could not be created | The short text describes the object sufficiently | |
| 264 | 263 |
Database index &1 has been activated | The short text describes the object sufficiently | |
| 265 | 264 |
Database index &1 could not be activated | The short text describes the object sufficiently | |
| 266 | 265 |
Database table &1 does not exist | The short text describes the object sufficiently | |
| 267 | 266 |
Mandatory data type &1 and table type &2 missing for alt.key. &3 | The short text describes the object sufficiently | |
| 268 | 267 |
Table type &1 of alt.key. &2 needs to be a standard table | The short text describes the object sufficiently | |
| 269 | 268 |
Transaction mode '&1' shall be used for proxy Business Objects | The short text describes the object sufficiently | |
| 270 | 269 |
Change mode '&1' shall be used for det. &2 (exec. time '&3') | The short text describes the object sufficiently | |
| 271 | 270 |
Determination cat. '&1' shall be used for det. &2 (exec. time '&3') | The short text describes the object sufficiently | |
| 272 | 271 |
Action &1 uses change mode '&2' and has no (or only modeled) write nodes | The short text describes the object sufficiently | |
| 273 | 272 |
Write node attr. &1 of determination &2 is not transient | The short text describes the object sufficiently | |
| 274 | 273 |
Only assoc. binding category '&1' is allowed for composition bindings | The short text describes the object sufficiently | |
| 275 | 274 |
Node &1 has a property det. or status but property change trigger missing | Space: object requires documentation | |
| 276 | 275 |
Missing trigger (Create/Update/Delete) for property change trigger &1 | The short text describes the object sufficiently | |
| 277 | 276 |
Subtree properties are enabled but buffer dispatcher &1 is not maintained | The short text describes the object sufficiently | |
| 278 | 277 |
Buffer dispatcher &1 is in use but node &2 has no buffer class maintained | The short text describes the object sufficiently | |
| 279 | 278 |
Conversion rule &1 is in use in mapping for attr. &2 of &3 &4 | The short text describes the object sufficiently | |
| 280 | 279 |
Property buffer class &1 is suggested for property node &2 | The short text describes the object sufficiently | |
| 281 | 280 |
Class names were proposed. Check proposals and execute generation again | The short text describes the object sufficiently | |
| 282 | 281 |
Business object &1 is set to final | The short text describes the object sufficiently | |
| 283 | 282 |
Class &1 must be regenerated due to model changes | The short text describes the object sufficiently | |
| 284 | 283 |
Wrong change mode used for library class (see library settings) | The short text describes the object sufficiently | |
| 285 | 284 |
Subclass of class &1 recommended for implementation of DO association &2 | The short text describes the object sufficiently | |
| 286 | 285 |
Nothing to be generated | The short text describes the object sufficiently | |
| 287 | 286 |
Namespace or prefix not maintained | The short text describes the object sufficiently | |
| 288 | 287 |
Lock/Unlock action shall use common class (suggestion: &1) | The short text describes the object sufficiently | |
| 289 | 288 |
Node &1 needs to be configured as lockable separately | The short text describes the object sufficiently | |
| 290 | 289 |
Message registry not available | The short text describes the object sufficiently | |
| 291 | 290 |
All messages are already registered | The short text describes the object sufficiently | |
| 292 | 291 |
Messages have been registered | The short text describes the object sufficiently | |
| 293 | 292 |
No messages for registration found | The short text describes the object sufficiently | |
| 294 | 293 |
Usage of message &1 &2 could not be registered (message not registered) | The short text describes the object sufficiently | |
| 295 | 294 |
Registration of messages failed | The short text describes the object sufficiently | |
| 296 | 295 |
Library class &1 is in status released but offers no documentation | The short text describes the object sufficiently | |
| 297 | 296 |
Locking class mismatch: &1 uses class &2, but action &3 uses class &4 | The short text describes the object sufficiently | |
| 298 | 297 |
Value &1 is not in the value range of domain &2 | The short text describes the object sufficiently | |
| 299 | 298 |
Table type &1 of alt.key. &2 shall not have unique primary/secondary keys | The short text describes the object sufficiently | |
| 300 | 299 |
Missing mandatory attr. KEY in &1 key of table type &2 (node &3) | The short text describes the object sufficiently | |
| 301 | 300 |
Superfluous attributes in &1 key of table type &2 (node &3) | The short text describes the object sufficiently | |
| 302 | 301 |
Table row used as key def. in &1 key of table type &2 (node &3) | The short text describes the object sufficiently | |
| 303 | 302 |
Table type &1 of node &2 shall not use a unique &3 key | The short text describes the object sufficiently | |
| 304 | 303 |
Class &1 needs to implement CREATE method, assoc. is create enabled | Space: object requires documentation | |
| 305 | 304 |
Msg. registry of lib. &1 inconsistent: &2 does not contain text attr. &3 | The short text describes the object sufficiently | |
| 306 | 305 |
Determination cat. of det. &1 does not match edit mode | The short text describes the object sufficiently | |
| 307 | 306 |
Index on reverse foreign key attr. &1 for database &2 missing/incorrect | Space: object requires documentation | |
| 308 | 307 |
Action property change trigger missing for SAM action &1 | Space: object requires documentation | |
| 309 | 308 |
Superfluous write node &1 for det. &2 (no cross lock group request nodes) | Space: object requires documentation | |
| 310 | 309 |
Write node(s) missing for det. &1; request nodes trigger cross lockgroups | The short text describes the object sufficiently | |
| 311 | 310 |
Edit mode '&1' not allowed for persist. det. &2; cross-lock trigger exist | The short text describes the object sufficiently | |
| 312 | 311 |
Library class '&1' shall be used as &2 on node &3 | The short text describes the object sufficiently | |
| 313 | 312 |
Library validation &1 shall be configured as &2 with trigger &3 | The short text describes the object sufficiently | |
| 314 | 313 |
ESI alt.key &1 shall not be configured as not-unique | The short text describes the object sufficiently | |
| 315 | 314 |
Filtered assoc. &1 without implementation class or association binding | The short text describes the object sufficiently | |
| 316 | 315 |
Request node &1~TO_ROOT is superfluous; &2~TO_PARENT is sufficient | The short text describes the object sufficiently | |
| 317 | 316 |
Assoc. &1 configured as '&2' for attr. &3; use pattern: '&4' | The short text describes the object sufficiently | |
| 318 | 317 |
Execution time of det. &1 shall be exclusively: '&2' | The short text describes the object sufficiently | |
| 319 | 318 |
Business object &1 is abstract and cannot be instantiated | The short text describes the object sufficiently | |
| 320 | 319 |
Code proposal not possible due to insufficient model information | Space: object requires documentation | |
| 321 | 320 |
Root node &1 needs to be lockable separately | The short text describes the object sufficiently | |
| 322 | 321 |
Lock class &1 does not support lock-depth of node &2 | The short text describes the object sufficiently | |
| 323 | 322 |
BOPF lock classes do not support lock-depth > 3 | The short text describes the object sufficiently | |
| 324 | 323 |
Val. &1 configured for consist. group &2 but CHECK trigger missing | The short text describes the object sufficiently | |
| 325 | 324 |
Trigger node &1 is in separat lockgroup; remove request node for det. &2 | The short text describes the object sufficiently | |
| 326 | 325 |
No active version selected for generation of note | The short text describes the object sufficiently | |
| 327 | 326 |
There is already a note for a higher support package level | The short text describes the object sufficiently | |
| 328 | 327 |
Note &1 for support package level &2 already exists | The short text describes the object sufficiently | |
| 329 | 328 |
Support package level needs to be in the range of SP &1 and SP &2 | The short text describes the object sufficiently | |
| 330 | 329 |
There is already a note for version &1 | The short text describes the object sufficiently | |
| 331 | 330 |
There is already a note for version in the selected version range | The short text describes the object sufficiently | |
| 332 | 331 |
Invalid status of note implementation (should be "in process") | The short text describes the object sufficiently | |
| 333 | 332 |
Note inconsistent. Please contact SAP Support. | The short text describes the object sufficiently | |
| 334 | 333 |
Support package level or release of note do not match system status | The short text describes the object sufficiently | |
| 335 | 334 |
No SAP Release found for business object &1 | The short text describes the object sufficiently | |
| 336 | 335 |
No relevant changes found | The short text describes the object sufficiently | |
| 337 | 336 |
Note existence could not be checked | The short text describes the object sufficiently | |
| 338 | 337 |
Note &1 does not exist | The short text describes the object sufficiently | |
| 339 | 338 |
No Software Component found for business object &1 | The short text describes the object sufficiently | |
| 340 | 339 |
Business Object is still used by inheriting Business Object | The short text describes the object sufficiently | |
| 341 | 340 |
After loading determination &1 uses a node with non-caching buffer | The short text describes the object sufficiently | |
| 342 | 341 |
GenIL component &1 could not be registered | The short text describes the object sufficiently | |
| 343 | 342 |
GenIL component &1 could not be deregistered | The short text describes the object sufficiently | |
| 344 | 343 |
GenIL &1 name &2 already exists | The short text describes the object sufficiently | |
| 345 | 344 |
&1 GenIL name must not be initial | The short text describes the object sufficiently | |
| 346 | 345 |
GenIL component name is already in use | The short text describes the object sufficiently | |
| 347 | 346 |
GenIL prefix is already in use | The short text describes the object sufficiently | |
| 348 | 347 |
GenIL component name must not be initial | The short text describes the object sufficiently | |
| 349 | 348 |
GenIL prefix must not be initial | The short text describes the object sufficiently | |
| 350 | 349 |
Design Documents can only be generated in Unicode Systems | The short text describes the object sufficiently | |
| 351 | 350 |
Query &1 not provided by GenIL due to missing query data type | The short text describes the object sufficiently | |
| 352 | 351 |
GenIL component is not yet registered | The short text describes the object sufficiently | |
| 353 | 352 |
Regeneration of BOPF Constant Interface &1 failed | The short text describes the object sufficiently | |
| 354 | 353 |
Version not marked as extendible but inherited extendible nodes exist | The short text describes the object sufficiently | |
| 355 | 354 |
Constant Interface defined in Association Binding does not exist (&1) | The short text describes the object sufficiently | |
| 356 | 355 |
Constant of Interface defined in Association Binding doesn't exist (&1) | The short text describes the object sufficiently | |
| 357 | 356 |
Association Binding of Association &1 incomplete | The short text describes the object sufficiently | |
| 358 | 357 |
Authorization object &1 does not exit | The short text describes the object sufficiently | |
| 359 | 358 |
Authorization field &1 of object &2 is already mapped | The short text describes the object sufficiently | |
| 360 | 359 |
Authorization field &1 does not exist at object &2 | The short text describes the object sufficiently | |
| 361 | 360 |
Authorization object &1 is not assigned to node | The short text describes the object sufficiently | |
| 362 | 361 |
Authorization object &1 is already assigned to node | The short text describes the object sufficiently | |
| 363 | 362 |
Authorization object &1 does not contain generic field &2 | The short text describes the object sufficiently | |
| 364 | 363 |
Authorization relevance flag marked, but check class not specified | The short text describes the object sufficiently | |
| 365 | 364 |
Authorization check class specified, but relevance flag not marked | The short text describes the object sufficiently | |
| 366 | 365 |
Authorization check class &1 does not exist | The short text describes the object sufficiently | |
| 367 | 366 |
Auth. class &1 does not inherit from /BOBF/CL_[FRW|LIB]_AUTHORITY_CHECK | The short text describes the object sufficiently | |
| 368 | 367 |
Authorization field mapping: target attribute &1 does not exist | The short text describes the object sufficiently | |
| 369 | 368 |
Auth. assignment/mapping exists, but relevance flag at node not marked | The short text describes the object sufficiently | |
| 370 | 369 |
Auth. field mapping: target attribute &1 not charlike or length > 40 | The short text describes the object sufficiently | |
| 371 | 370 |
Query has to be implemented, since authority checking is switched on | The short text describes the object sufficiently | |
| 372 | 371 |
Const. interf. &1 may have missing node attributes (&2: inactive version) | The short text describes the object sufficiently | |
| 373 | 372 |
Business Object &1 selected for load invalidation | The short text describes the object sufficiently | |
| 374 | 373 |
BO Load of &1 was invalidated with return code &2; terminate_changer='&3' | The short text describes the object sufficiently | |
| 375 | 374 |
BO Load of &1 was freed with return code &2; terminate_changer='&3' | The short text describes the object sufficiently | |
| 376 | 375 |
System Maintenance in parallel: Only display operations are possible | Space: object requires documentation | |
| 377 | 378 |
Determination pattern not supported | Space: object requires documentation | |
| 378 | 379 |
Determination pattern &1: No trigger node | Space: object requires documentation | |
| 379 | 380 |
Determination pattern &1: Trigger node not transient | Space: object requires documentation | |
| 380 | 381 |
Determination pattern &1: Set trigger node for one of &2 | Space: object requires documentation | |
| 381 | 382 |
No evaluation timepoint | Space: object requires documentation | |
| 382 | 383 |
Determination pattern &1: Remove trigger node for any of &2 | Space: object requires documentation | |
| 383 | 384 |
Display mode only | Space: object requires documentation | |
| 384 | 385 |
Display mode only (Enhancement object) | Space: object requires documentation | |
| 385 | 386 |
No attributes: Missing combined structure | The short text describes the object sufficiently | |
| 386 | 387 |
No attributes: Check combined structure | The short text describes the object sufficiently | |
| 387 | 899 |
&1&2&3&4 | The short text describes the object sufficiently |
History
| Last changed on/by | |
20140121 | SAP |
| SAP Release Created in | 702 |
