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