AXT_MODEL -
The following messages are stored in message class AXT_MODEL: .
It is part of development package AXT_MODEL in software component CA-GTF-EEW. This development package consists of objects that can be grouped under "Application Extensibility Tool: Model".
It is part of development package AXT_MODEL in software component CA-GTF-EEW. This development package consists of objects that can be grouped under "Application Extensibility Tool: Model".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Enhancement &1 is not locked |
| 001 | Assign enhancement &1 to a package |
| 002 | You need to lock enhancement &1 in a transport request |
| 003 | Version &2 of enhancement &1 does not exist |
| 004 | Enhancement &1 does not exist |
| 005 | System settings for logical system &1 could not be read |
| 006 | Logical system could not be determined |
| 007 | Enhancement &1 is inconsistent |
| 008 | Error during setup of catalog for enhancement &1 |
| 009 | &1&2&3&4 |
| 010 | Part &3 for object &2 is not enabled for enhancement &1 |
| 011 | Enhancement type &1 does not support objects and parts |
| 012 | Part &2 for object &1 does not exist |
| 013 | Part &2 for object &1 is for a different enhancement place |
| 014 | Enhancements for part &2 of object &1 are no longer allowed |
| 015 | Enhancement of type &1 for part &3 of object &2 is not possible |
| 016 | Reuse of enhancement &1 failed |
| 017 | Enhancement type &1 is not reusable |
| 018 | Define the system settings in transaction AXTSYS |
| 019 | Reused enhancement &1 is not active |
| 020 | Enhancement &1 could not be locked |
| 021 | Reused enhancement &1 is not active |
| 022 | You cannot delete enhancement &1 since it is still in use |
| 023 | Enhancement catalog &1 contains no active elements |
| 024 | Enhancement catalog &1 contains no elements to generate |
| 025 | New task is added to request &1 of user &2 |
| 026 | New task was added to request &1 of user &2 |
| 027 | Enhancement &1 has original system &2; make changes in original system |
| 028 | Enter a valid value instead of &1 |
| 029 | Error during generation of enhancements; generate only one enhancement |
| 030 | Field enhancement for place &1 is not possible due to database limit |
| 031 | Enhancement place definition &1 is inconsistent |
| 032 | Unknown registry context &1 |
| 033 | Context &1 is already registered |
| 034 | Default registry context is not set up |
| 035 | Enter a valid code for a dropdown list item instead of &1 |
| 036 | You cannot change the dropdown list for a reuse enhancement |
| 037 | Changing the field type leads to data loss |
| 038 | Field ID has to start with namespace &1 |
| 039 | Field ID &1 is already in use |
| 040 | Field &2: data type &1 is invalid |
| 041 | Changing the field ID leads to data loss |
| 042 | Enter a field ID |
| 043 | You cannot combine a dropdown list and a check table |
| 044 | You cannot specify an external dropdown list and also enter items |
| 045 | Dropdown list &1 does not exist |
| 046 | You cannot combine a check table and a search help |
| 047 | You cannot combine a dropdown list and a search help |
| 048 | Table &1 already contains field &2; check if this causes duplicates |
| 049 | Search help &1 is incompatible |
| 050 | Dropdown list &1 is incompatible |
| 051 | Enter a data type that matches the one of the search help |
| 052 | Field &3: Enter a maximum length of &1 for data type &2 |
| 053 | Field &3: Enter maximum number of decimal places &1 for data type &2 |
| 054 | Field &2: Search help is not allowed for data type &1 |
| 055 | Field &2: Dropdown list is not allowed for data type &1 |
| 056 | Field &2: Check table is not allowed for data type &1 |
| 057 | Dropdown lists and check tables only support &1 characters |
| 058 | Field ID &1 is already used by enhancement &2 |
| 059 | Enter a data type that matches the one of the check table key |
| 060 | Generation preparation of enhancement &1 failed; check enhancement log |
| 061 | Generation failed |
| 062 | Duplicate entry for reference name &1 with GUID_REF &2 |
| 063 | Reference name &1 with GUID_REF &2 not found |
| 064 | Error in registry |
| 065 | Inconsistent data; generation leads to data loss |
| 066 | Namespace of the enhancement (&1) does not allow package &2 |
| 067 | Error while calling generation BAdI for enhancement &1 |
| 068 | Invalid generation object type &1 |
| 069 | Another mass activation or upgrade is already running |
| 070 | Invalid generation parameter &2 for object type &1 |
| 071 | Invalid enhancement handler parameter &1 |
| 072 | Enhancement &1 can only be changed after the generation is finished |
| 073 | Search &1 belongs to application group &2, not &3 |
| 074 | Enter a field label for language &1 |
| 075 | Enhancement &1 caused an error during mass activation |
| 076 | Unknown error during generation |
| 077 | Error during mass activation; the corresponding enhancement is unknown |
| 078 | Enter a field label |
| 079 | Field &3: length &1 must be higher than number of decimal places &2 |
| 080 | Data type of key &1 does not allow lower case |
| 081 | Data type of key of &1 allows lower case |
| 082 | Data type of key of &1 has length &2 |
| 083 | Data type of key of &1 has &2 decimal places |
| 084 | Data type of &1 (&2) does not match |
| 085 | Enhancement category for customer include &1 cannot be determined |
| 086 | Dropdown list item with code '&1' is specified twice |
| 087 | Enter an alphanumeric field ID without a digit at the beginning |
| 088 | Enter a transportable package for enhancements for SAP Mobile |
| 089 | Invalid characters have been removed from dropdown list code &1 |
| 090 | Error in registry for BO &1 part &2 |
| 091 | Dropdown list item &1 does not have a description |
| 092 | &1 required &2 |
| 093 | Enter a data type |
| 094 | Field &1: Enter a length greater than 0 |
| 095 | Field &1: Specify a data type |
| 096 | Registry context class &1 does not exist |
| 097 | Enhancement for reuse is not active; generate it first |
| 098 | Enhancement for reuse is outdated; regenerate it first |
| 099 | Field ID is too long; use a field ID with a maximum of 16 characters |
| 100 | You need authorization to edit enhancements |
| 101 | Client settings prevent repository and cross-client customizing changes |
| 102 | Enhancement &1 is not active and cannot be transported |
| 103 | Enhancement &1 is marked as outdated and cannot be transported |
| 104 | Pre-export check for enhancement &1 has started |
| 105 | Enhancement &1 requires local regeneration |
| 106 | You cannot regenerate enhancement &1 in its original system |
| 107 | You are not authorized to create/change enhancements |
| 108 | Authorization check for object &1 &2 &3 &4 failed |
| 109 | This field enhancement uses customer includes |
| 110 | Data element &1 does not exist |
| 111 | Data type &1 is not supported |
| 112 | Field &1: Enter a different reference field ID than for the field ID |
| 113 | You cannot change the reporting type to &1 |
| 114 | Field &2: Field with data type &1 cannot be used as logical key |
| 115 | Logical key of an active enhancement cannot be changed |
| 116 | Changing the database table name would cause data loss |
| 117 | UI component &1 does not exist |
| 118 | UI component &1 cannot be used for this enhancement |
| 119 | All key fields have to be at the beginning of the table |
| 120 | Field of the enhancement is still used by Web service &1 |
| 121 | Catalog consolidation failed |
| 122 | Enter a UI window name |
| 123 | Enter a valid UI component that has been generated with AXTSYS |
| 124 | Substitution &1 is invalid |
| 125 | Manual field definition is invalid |
| 126 | Field name &1 is reserved |
| 127 | 'Enhanceable' checkbox can no longer be disabled |
| 128 | Internal error; element has no GUID |
| 129 | Package can no longer be changed |
| 130 | Pick list codes can only have 10 characters; field &1 has a length of &2 |
| 131 | You do not have certain authorizations; apply SAP Note 1251796 |
| 132 | You cannot regenerate Customizing for enhancement &1 in a foreign system |
| 133 | Customizing for enhancement &1 has to be transported manually |
| 134 | No system settings are made in AXTSYS; prefix is defaulted |
| 135 | Field &1: Field length (&2) is not fully used by picklist codes (&3) |
| 136 | Embeddable view is already embedded in &1 &2 |
| 137 | Enhancement could not be created |
| 138 | Attribute tag &1 is not accessible from this BO part (BOL object = &2) |
| 139 | View &1 is read-only |
| 140 | genIL component set &1 has errors and cannot be used |
| 141 | Object with the alias &1 already exists |
| 142 | Field with ID &1 is a key field in several tables |
| 143 | Enhancement &1 is obsolete; you can only delete it |
| 144 | Model definition of query &1 does not specify a result object |
| 145 | Specify a target ID |
| 146 | Generate a UI component for table enhancement from AXTSYS first |
| 147 | DTEL &1 and key field of check table &2 have different domains('&3'/'&4') |
| 148 | Field &1 is set as navigation link but the field is disabled |
| 149 | Object already contains a table with ID &1 |
| 150 | Table already contains a field with ID &1 |
| 151 | Context substitution &1 is unknown |
| 152 | Specify at least one field for table &1 |
| 153 | Use namespace (&1) for table name &2 |
| 154 | Table or structure &1 already exists |
| 155 | View or window with name &2 already exists for the component &1 |
| 156 | Enter a UI component |
| 157 | Window name &1 is invalid |
| 158 | Create a target UI component in AXTSYS before creating table enhancements |
| 159 | Select the first table field as logical key |
| 160 | Checkbox &1 has also been selected for logical key field &2 |
| 161 | Enhancing the search result list is only possible for 1:1 enhancements |
| 162 | Window name must not be longer than 60 characters |
| 163 | Window name &1 cannot be used because there are naming conflicts |
| 164 | Window name &1 for component &2 is already used by enhancement &3 |
| 165 | Application name &1 is already used by enhancement &2 |
| 166 | Target ID &1 is already defined for component &2 window &3 |
| 167 | Enter an application name |
| 168 | Name has to start with "&1" namespace |
| 169 | Application name &1 cannot be used |
| 170 | UI object &1 already exists |
| 171 | UI component &1 already exists |
| 172 | Extensible BO &1 already exists |
| 173 | Enter a description |
| 174 | Enter a description for language &1 |
| 175 | Target ID &1 is already defined for enhancement &2 |
| 176 | Could not set up elements for UI application |
| 177 | Application already contains a table with ID &1 |
| 178 | Target ID &1 is used several times |
| 179 | Enter a transport request |
| 180 | Table &1 does not exist |
| 181 | Enter an object name |
| 182 | Object name has to use namespace &1 |
| 183 | Object name &1 already exists |
| 184 | Specify a logical key for the header table |
| 185 | Key fields cannot be disabled |
| 186 | Application does not have a header table |
| 187 | Table &1 is not supported; select another database table |
| 188 | You cannot delete the header table of a rapid application |
| 189 | Table ID &1 is already used by enhancement &2 |
| 190 | Table uses namespace &1 but enhancement has namespace &2 |
| 191 | Table &1 is not a database table or database view |
| 192 | Enhancement &1 is still embedded in &2 &3 |
| 193 | Underscore is not permitted at 2nd or 3rd position |
| 194 | Authorization group &1 for S_TABU_DIS does not exist |
| 195 | BOL model for the Web service is empty |
| 196 | Target ID &1 cannot be used twice; choose a different target ID |
| 197 | Select a navigation link field for the header table |
| 198 | Logical link &1 cannot be used twice; choose a different logical link ID |
| 199 | Logical link &1 is already defined in the navigation bar customizing |
| 200 | Logical link ID &1 is already defined for enhancement &2 |
| 201 | Field &1 cannot be transient and a logical key |
| 202 | Existing table &1 cannot be a child of the new table &2 |
| 203 | Parent key &1 can only be mapped once in table &2 |
| 204 | Field &1 in table &2 is not compatible with parent key &3 |
| 205 | Parent key field &1 is not mapped to a field in child table &2 |
| 206 | 1:1 child table cannot have unmapped key fields (for example, &1) |
| 207 | Table ID &1 is used several times |
| 208 | Enter a component name |
| 209 | UI component &1 cannot be used |
| 210 | genIL component set &1 does not exist |
| 211 | genIL object type &1 is not supported |
| 212 | This element cannot be deleted |
| 213 | Search for table &1 has no parameters |
| 214 | 1:N table (&1) requires an unmapped key field |
| 215 | Enhancement &1 is not locked in a transport request; no need to deploy it |
| 216 | Enhancement &1 is inactive; finish generation before releasing it |
| 217 | Element &1 &2 of enhancement &3 is not locked in a transport |
| 218 | This rapid application uses an outdated UI generator |
| 219 | For the table, specify at least one field that is not calculated |
| 220 | Component &1 cannot be used for multiple subelements |
| 221 | You cannot add a DDIC table as a child of a new table |
| 222 | Header table already exists |
| 223 | You cannot use tables of this rapid application as check tables |
| 224 | The table is still used in the UI model. Remove the UI element first |
| 225 | Object &1 is used several times within one UI element unit |
| 226 | Only tables with a cardinality of 1:N can be table extensible |
| 227 | Maximum DB size exceeded; remove fields or reduce their length |
| 230 | Check table &2 is not supported for field &1 |
| 231 | Search help &2 is not supported for field &1 |
| 232 | FPM configuration ID &1 already exists |
| 233 | FPM configuration ID &1 is already used by enhancement &2 |
| 234 | FPM configuration ID &1 is already used by this enhancement |
| 235 | Enter an FPM configuration ID for the table below BOL object &1 |
| 236 | FPM configuration ID &1 is not allowed to contain special characters |
| 237 | FPM config ID &1 must have the same namespace (&2) as the enhancement |
| 238 | Clearing shared genIL model and AET handler cache |
| 240 | UI Component &1 does not support nested tables |
| 250 | genIL model for extensible object &1 could not be loaded |
| 251 | No rule builder defined for the rule type &1 |
| 252 | No rule builder defined for the rule ID &1 |
| 253 | No rule mapper defined for the rule ID &1 and object name &2 |
| 254 | No rule handler defined for the rule type &1 and object type &2 |
| 255 | No rule application defined |
| 256 | Rule parameter mapping for &1 already exists |
| 257 | No result object defined for the formula &1 |
| 258 | Rule handler only supports BOL entities |
| 259 | Calculation for field "&1" failed |
| 260 | No mapping defined for &1 |
| 261 | Specify a BOL object |
| 262 | &1 is not a valid parameter for a formula |
| 263 | Variable BPath return structures are not supported; adjust &1 |
| 264 | Only data elements as BPath return types are supported; adjust &1 |
| 265 | Parent relation in your BPath statement is ambiguous; adjust &1 |
| 266 | Formula is invalid |
| 267 | Parameter &1 needs a reference field path, otherwise you cannot use it |
| 268 | Invalid BOL relation within your formula; adjust &1 |
| 269 | Timepoint fields are not supported; use another parameter as &1 |
| 270 | BRFplus application &1 is not locked |
| 271 | BRFplus function &1 is not locked |
| 272 | Cannot use &1; it is not possible to trace an association backwards |
| 273 | Your global attribute tag is converted to the BPath statement &1&2&3&4 |
| 274 | Cannot use &1; &2 is not in the path and has ambiguous parent relations |
| 275 | Several BOL objects enhanced; you can assign formula to each BOL object |
| 276 | Remaining table space is not enough to support field enhancements |
| 277 | Reserved field quota has been exceeded |
| 278 | The table still has a child table in enhancement &1 |