SAP ABAP Message Class AXT_MODEL (AXT_MODEL)
Basic Data
Hierarchy
☛
WEBCUIF (Software Component) SAP Web UI Framework
⤷
CA-GTF-EEW (Application Component) Easy Enhancement Workbench
⤷
AXT_MODEL (Package) Application Extensibility Tool: Model
⤷
⤷
Attributes
| Message class | AXT_MODEL | |
| Short Description | ||
| Changed On | 20130531 | |
| Last Changed At | 122031 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 | Enhancement &1 is not locked | The short text describes the object sufficiently | ||
| 2 | Assign enhancement &1 to a package | The short text describes the object sufficiently | ||
| 3 | You need to lock enhancement &1 in a transport request | The short text describes the object sufficiently | ||
| 4 | Version &2 of enhancement &1 does not exist | The short text describes the object sufficiently | ||
| 5 | Enhancement &1 does not exist | The short text describes the object sufficiently | ||
| 6 | System settings for logical system &1 could not be read | |||
| 7 | Logical system could not be determined | The short text describes the object sufficiently | ||
| 8 | Enhancement &1 is inconsistent | The short text describes the object sufficiently | ||
| 9 | Error during setup of catalog for enhancement &1 | The short text describes the object sufficiently | ||
| 10 | &1&2&3&4 | The short text describes the object sufficiently | ||
| 11 | Part &3 for object &2 is not enabled for enhancement &1 | The short text describes the object sufficiently | ||
| 12 | Enhancement type &1 does not support objects and parts | The short text describes the object sufficiently | ||
| 13 | Part &2 for object &1 does not exist | The short text describes the object sufficiently | ||
| 14 | Part &2 for object &1 is for a different enhancement place | The short text describes the object sufficiently | ||
| 15 | Enhancements for part &2 of object &1 are no longer allowed | The short text describes the object sufficiently | ||
| 16 | Enhancement of type &1 for part &3 of object &2 is not possible | The short text describes the object sufficiently | ||
| 17 | Reuse of enhancement &1 failed | The short text describes the object sufficiently | ||
| 18 | Enhancement type &1 is not reusable | The short text describes the object sufficiently | ||
| 19 | Define the system settings in transaction AXTSYS | The short text describes the object sufficiently | ||
| 20 | Reused enhancement &1 is not active | The short text describes the object sufficiently | ||
| 21 | Enhancement &1 could not be locked | The short text describes the object sufficiently | ||
| 22 | Reused enhancement &1 is not active | The short text describes the object sufficiently | ||
| 23 | You cannot delete enhancement &1 since it is still in use | The short text describes the object sufficiently | ||
| 24 | Enhancement catalog &1 contains no active elements | The short text describes the object sufficiently | ||
| 25 | Enhancement catalog &1 contains no elements to generate | The short text describes the object sufficiently | ||
| 26 | New task is added to request &1 of user &2 | The short text describes the object sufficiently | ||
| 27 | New task was added to request &1 of user &2 | The short text describes the object sufficiently | ||
| 28 | Enhancement &1 has original system &2; make changes in original system | The short text describes the object sufficiently | ||
| 29 | Enter a valid value instead of &1 | The short text describes the object sufficiently | ||
| 30 | Error during generation of enhancements; generate only one enhancement | The short text describes the object sufficiently | ||
| 31 | Field enhancement for place &1 is not possible due to database limit | Space: object requires documentation | ||
| 32 | Enhancement place definition &1 is inconsistent | The short text describes the object sufficiently | ||
| 33 | Unknown registry context &1 | The short text describes the object sufficiently | ||
| 34 | Context &1 is already registered | The short text describes the object sufficiently | ||
| 35 | Default registry context is not set up | The short text describes the object sufficiently | ||
| 36 | Enter a valid code for a dropdown list item instead of &1 | The short text describes the object sufficiently | ||
| 37 | You cannot change the dropdown list for a reuse enhancement | Space: object requires documentation | ||
| 38 | Changing the field type leads to data loss | The short text describes the object sufficiently | ||
| 39 | Field ID has to start with namespace &1 | The short text describes the object sufficiently | ||
| 40 | Field ID &1 is already in use | The short text describes the object sufficiently | ||
| 41 | Field &2: data type &1 is invalid | The short text describes the object sufficiently | ||
| 42 | Changing the field ID leads to data loss | The short text describes the object sufficiently | ||
| 43 | Enter a field ID | The short text describes the object sufficiently | ||
| 44 | You cannot combine a dropdown list and a check table | The short text describes the object sufficiently | ||
| 45 | You cannot specify an external dropdown list and also enter items | The short text describes the object sufficiently | ||
| 46 | Dropdown list &1 does not exist | The short text describes the object sufficiently | ||
| 47 | You cannot combine a check table and a search help | The short text describes the object sufficiently | ||
| 48 | You cannot combine a dropdown list and a search help | The short text describes the object sufficiently | ||
| 49 | Table &1 already contains field &2; check if this causes duplicates | The short text describes the object sufficiently | ||
| 50 | Search help &1 is incompatible | |||
| 51 | Dropdown list &1 is incompatible | The short text describes the object sufficiently | ||
| 52 | Enter a data type that matches the one of the search help | The short text describes the object sufficiently | ||
| 53 | Field &3: Enter a maximum length of &1 for data type &2 | The short text describes the object sufficiently | ||
| 54 | Field &3: Enter maximum number of decimal places &1 for data type &2 | The short text describes the object sufficiently | ||
| 55 | Field &2: Search help is not allowed for data type &1 | The short text describes the object sufficiently | ||
| 56 | Field &2: Dropdown list is not allowed for data type &1 | The short text describes the object sufficiently | ||
| 57 | Field &2: Check table is not allowed for data type &1 | The short text describes the object sufficiently | ||
| 58 | Dropdown lists and check tables only support &1 characters | The short text describes the object sufficiently | ||
| 59 | Field ID &1 is already used by enhancement &2 | The short text describes the object sufficiently | ||
| 60 | Enter a data type that matches the one of the check table key | The short text describes the object sufficiently | ||
| 61 | Generation preparation of enhancement &1 failed; check enhancement log | Space: object requires documentation | ||
| 62 | Generation failed | The short text describes the object sufficiently | ||
| 63 | Duplicate entry for reference name &1 with GUID_REF &2 | The short text describes the object sufficiently | ||
| 64 | Reference name &1 with GUID_REF &2 not found | The short text describes the object sufficiently | ||
| 65 | Error in registry | The short text describes the object sufficiently | ||
| 66 | Inconsistent data; generation leads to data loss | The short text describes the object sufficiently | ||
| 67 | Namespace of the enhancement (&1) does not allow package &2 | The short text describes the object sufficiently | ||
| 68 | Error while calling generation BAdI for enhancement &1 | The short text describes the object sufficiently | ||
| 69 | Invalid generation object type &1 | The short text describes the object sufficiently | ||
| 70 | Another mass activation or upgrade is already running | The short text describes the object sufficiently | ||
| 71 | Invalid generation parameter &2 for object type &1 | The short text describes the object sufficiently | ||
| 72 | Invalid enhancement handler parameter &1 | The short text describes the object sufficiently | ||
| 73 | Enhancement &1 can only be changed after the generation is finished | Space: object requires documentation | ||
| 74 | Search &1 belongs to application group &2, not &3 | The short text describes the object sufficiently | ||
| 75 | Enter a field label for language &1 | The short text describes the object sufficiently | ||
| 76 | Enhancement &1 caused an error during mass activation | The short text describes the object sufficiently | ||
| 77 | Unknown error during generation | The short text describes the object sufficiently | ||
| 78 | Error during mass activation; the corresponding enhancement is unknown | The short text describes the object sufficiently | ||
| 79 | Enter a field label | The short text describes the object sufficiently | ||
| 80 | Field &3: length &1 must be higher than number of decimal places &2 | The short text describes the object sufficiently | ||
| 81 | Data type of key &1 does not allow lower case | The short text describes the object sufficiently | ||
| 82 | Data type of key of &1 allows lower case | The short text describes the object sufficiently | ||
| 83 | Data type of key of &1 has length &2 | The short text describes the object sufficiently | ||
| 84 | Data type of key of &1 has &2 decimal places | The short text describes the object sufficiently | ||
| 85 | Data type of &1 (&2) does not match | The short text describes the object sufficiently | ||
| 86 | Enhancement category for customer include &1 cannot be determined | The short text describes the object sufficiently | ||
| 87 | Dropdown list item with code '&1' is specified twice | Space: object requires documentation | ||
| 88 | Enter an alphanumeric field ID without a digit at the beginning | The short text describes the object sufficiently | ||
| 89 | Enter a transportable package for enhancements for SAP Mobile | The short text describes the object sufficiently | ||
| 90 | Invalid characters have been removed from dropdown list code &1 | The short text describes the object sufficiently | ||
| 91 | Error in registry for BO &1 part &2 | The short text describes the object sufficiently | ||
| 92 | Dropdown list item &1 does not have a description | The short text describes the object sufficiently | ||
| 93 | &1 required &2 | The short text describes the object sufficiently | ||
| 94 | Enter a data type | The short text describes the object sufficiently | ||
| 95 | Field &1: Enter a length greater than 0 | The short text describes the object sufficiently | ||
| 96 | Field &1: Specify a data type | The short text describes the object sufficiently | ||
| 97 | Registry context class &1 does not exist | The short text describes the object sufficiently | ||
| 98 | Enhancement for reuse is not active; generate it first | The short text describes the object sufficiently | ||
| 99 | Enhancement for reuse is outdated; regenerate it first | The short text describes the object sufficiently | ||
| 100 | Field ID is too long; use a field ID with a maximum of 16 characters | The short text describes the object sufficiently | ||
| 101 | You need authorization to edit enhancements | The short text describes the object sufficiently | ||
| 102 | Client settings prevent repository and cross-client customizing changes | Space: object requires documentation | ||
| 103 | Enhancement &1 is not active and cannot be transported | The short text describes the object sufficiently | ||
| 104 | Enhancement &1 is marked as outdated and cannot be transported | The short text describes the object sufficiently | ||
| 105 | Pre-export check for enhancement &1 has started | The short text describes the object sufficiently | ||
| 106 | Enhancement &1 requires local regeneration | The short text describes the object sufficiently | ||
| 107 | You cannot regenerate enhancement &1 in its original system | The short text describes the object sufficiently | ||
| 108 | You are not authorized to create/change enhancements | The short text describes the object sufficiently | ||
| 109 | Authorization check for object &1 &2 &3 &4 failed | The short text describes the object sufficiently | ||
| 110 | This field enhancement uses customer includes | The short text describes the object sufficiently | ||
| 111 | Data element &1 does not exist | The short text describes the object sufficiently | ||
| 112 | Data type &1 is not supported | The short text describes the object sufficiently | ||
| 113 | Field &1: Enter a different reference field ID than for the field ID | The short text describes the object sufficiently | ||
| 114 | You cannot change the reporting type to &1 | The short text describes the object sufficiently | ||
| 115 | Field &2: Field with data type &1 cannot be used as logical key | The short text describes the object sufficiently | ||
| 116 | Logical key of an active enhancement cannot be changed | The short text describes the object sufficiently | ||
| 117 | Changing the database table name would cause data loss | The short text describes the object sufficiently | ||
| 118 | UI component &1 does not exist | The short text describes the object sufficiently | ||
| 119 | UI component &1 cannot be used for this enhancement | The short text describes the object sufficiently | ||
| 120 | All key fields have to be at the beginning of the table | The short text describes the object sufficiently | ||
| 121 | Field of the enhancement is still used by Web service &1 | The short text describes the object sufficiently | ||
| 122 | Catalog consolidation failed | The short text describes the object sufficiently | ||
| 123 | Enter a UI window name | The short text describes the object sufficiently | ||
| 124 | Enter a valid UI component that has been generated with AXTSYS | The short text describes the object sufficiently | ||
| 125 | Substitution &1 is invalid | The short text describes the object sufficiently | ||
| 126 | Manual field definition is invalid | The short text describes the object sufficiently | ||
| 127 | Field name &1 is reserved | The short text describes the object sufficiently | ||
| 128 | 'Enhanceable' checkbox can no longer be disabled | The short text describes the object sufficiently | ||
| 129 | Internal error; element has no GUID | The short text describes the object sufficiently | ||
| 130 | Package can no longer be changed | The short text describes the object sufficiently | ||
| 131 | Pick list codes can only have 10 characters; field &1 has a length of &2 | The short text describes the object sufficiently | ||
| 132 | You do not have certain authorizations; apply SAP Note 1251796 | The short text describes the object sufficiently | ||
| 133 | You cannot regenerate Customizing for enhancement &1 in a foreign system | The short text describes the object sufficiently | ||
| 134 | Customizing for enhancement &1 has to be transported manually | Space: object requires documentation | ||
| 135 | No system settings are made in AXTSYS; prefix is defaulted | Space: object requires documentation | ||
| 136 | Field &1: Field length (&2) is not fully used by picklist codes (&3) | Space: object requires documentation | ||
| 137 | Embeddable view is already embedded in &1 &2 | The short text describes the object sufficiently | ||
| 138 | Enhancement could not be created | The short text describes the object sufficiently | ||
| 139 | Attribute tag &1 is not accessible from this BO part (BOL object = &2) | Space: object requires documentation | ||
| 140 | View &1 is read-only | The short text describes the object sufficiently | ||
| 141 | genIL component set &1 has errors and cannot be used | The short text describes the object sufficiently | ||
| 142 | Object with the alias &1 already exists | The short text describes the object sufficiently | ||
| 143 | Field with ID &1 is a key field in several tables | The short text describes the object sufficiently | ||
| 144 | Enhancement &1 is obsolete; you can only delete it | The short text describes the object sufficiently | ||
| 145 | Model definition of query &1 does not specify a result object | Space: object requires documentation | ||
| 146 | Specify a target ID | The short text describes the object sufficiently | ||
| 147 | Generate a UI component for table enhancement from AXTSYS first | Space: object requires documentation | ||
| 148 | DTEL &1 and key field of check table &2 have different domains('&3'/'&4') | The short text describes the object sufficiently | ||
| 149 | Field &1 is set as navigation link but the field is disabled | The short text describes the object sufficiently | ||
| 150 | Object already contains a table with ID &1 | The short text describes the object sufficiently | ||
| 151 | Table already contains a field with ID &1 | The short text describes the object sufficiently | ||
| 152 | Context substitution &1 is unknown | The short text describes the object sufficiently | ||
| 153 | Specify at least one field for table &1 | The short text describes the object sufficiently | ||
| 154 | Use namespace (&1) for table name &2 | The short text describes the object sufficiently | ||
| 155 | Table or structure &1 already exists | The short text describes the object sufficiently | ||
| 156 | View or window with name &2 already exists for the component &1 | The short text describes the object sufficiently | ||
| 157 | Enter a UI component | The short text describes the object sufficiently | ||
| 158 | Window name &1 is invalid | The short text describes the object sufficiently | ||
| 159 | Create a target UI component in AXTSYS before creating table enhancements | Space: object requires documentation | ||
| 160 | Select the first table field as logical key | The short text describes the object sufficiently | ||
| 161 | Checkbox &1 has also been selected for logical key field &2 | The short text describes the object sufficiently | ||
| 162 | Enhancing the search result list is only possible for 1:1 enhancements | The short text describes the object sufficiently | ||
| 163 | Window name must not be longer than 60 characters | The short text describes the object sufficiently | ||
| 164 | Window name &1 cannot be used because there are naming conflicts | Space: object requires documentation | ||
| 165 | Window name &1 for component &2 is already used by enhancement &3 | The short text describes the object sufficiently | ||
| 166 | Application name &1 is already used by enhancement &2 | The short text describes the object sufficiently | ||
| 167 | Target ID &1 is already defined for component &2 window &3 | The short text describes the object sufficiently | ||
| 168 | Enter an application name | The short text describes the object sufficiently | ||
| 169 | Name has to start with "&1" namespace | The short text describes the object sufficiently | ||
| 170 | Application name &1 cannot be used | The short text describes the object sufficiently | ||
| 171 | UI object &1 already exists | The short text describes the object sufficiently | ||
| 172 | UI component &1 already exists | The short text describes the object sufficiently | ||
| 173 | Extensible BO &1 already exists | The short text describes the object sufficiently | ||
| 174 | Enter a description | The short text describes the object sufficiently | ||
| 175 | Enter a description for language &1 | The short text describes the object sufficiently | ||
| 176 | Target ID &1 is already defined for enhancement &2 | The short text describes the object sufficiently | ||
| 177 | Could not set up elements for UI application | The short text describes the object sufficiently | ||
| 178 | Application already contains a table with ID &1 | The short text describes the object sufficiently | ||
| 179 | Target ID &1 is used several times | The short text describes the object sufficiently | ||
| 180 | Enter a transport request | The short text describes the object sufficiently | ||
| 181 | Table &1 does not exist | The short text describes the object sufficiently | ||
| 182 | Enter an object name | The short text describes the object sufficiently | ||
| 183 | Object name has to use namespace &1 | The short text describes the object sufficiently | ||
| 184 | Object name &1 already exists | The short text describes the object sufficiently | ||
| 185 | Specify a logical key for the header table | The short text describes the object sufficiently | ||
| 186 | Key fields cannot be disabled | The short text describes the object sufficiently | ||
| 187 | Application does not have a header table | The short text describes the object sufficiently | ||
| 188 | Table &1 is not supported; select another database table | Space: object requires documentation | ||
| 189 | You cannot delete the header table of a rapid application | The short text describes the object sufficiently | ||
| 190 | Table ID &1 is already used by enhancement &2 | The short text describes the object sufficiently | ||
| 191 | Table uses namespace &1 but enhancement has namespace &2 | Space: object requires documentation | ||
| 192 | Table &1 is not a database table or database view | The short text describes the object sufficiently | ||
| 193 | Enhancement &1 is still embedded in &2 &3 | The short text describes the object sufficiently | ||
| 194 | Underscore is not permitted at 2nd or 3rd position | The short text describes the object sufficiently | ||
| 195 | Authorization group &1 for S_TABU_DIS does not exist | The short text describes the object sufficiently | ||
| 196 | BOL model for the Web service is empty | The short text describes the object sufficiently | ||
| 197 | Target ID &1 cannot be used twice; choose a different target ID | The short text describes the object sufficiently | ||
| 198 | Select a navigation link field for the header table | The short text describes the object sufficiently | ||
| 199 | Logical link &1 cannot be used twice; choose a different logical link ID | The short text describes the object sufficiently | ||
| 200 | Logical link &1 is already defined in the navigation bar customizing | The short text describes the object sufficiently | ||
| 201 | Logical link ID &1 is already defined for enhancement &2 | The short text describes the object sufficiently | ||
| 202 | Field &1 cannot be transient and a logical key | The short text describes the object sufficiently | ||
| 203 | Existing table &1 cannot be a child of the new table &2 | The short text describes the object sufficiently | ||
| 204 | Parent key &1 can only be mapped once in table &2 | The short text describes the object sufficiently | ||
| 205 | Field &1 in table &2 is not compatible with parent key &3 | The short text describes the object sufficiently | ||
| 206 | Parent key field &1 is not mapped to a field in child table &2 | The short text describes the object sufficiently | ||
| 207 | 1:1 child table cannot have unmapped key fields (for example, &1) | The short text describes the object sufficiently | ||
| 208 | Table ID &1 is used several times | The short text describes the object sufficiently | ||
| 209 | Enter a component name | The short text describes the object sufficiently | ||
| 210 | UI component &1 cannot be used | The short text describes the object sufficiently | ||
| 211 | genIL component set &1 does not exist | The short text describes the object sufficiently | ||
| 212 | genIL object type &1 is not supported | The short text describes the object sufficiently | ||
| 213 | This element cannot be deleted | The short text describes the object sufficiently | ||
| 214 | Search for table &1 has no parameters | Space: object requires documentation | ||
| 215 | 1:N table (&1) requires an unmapped key field | The short text describes the object sufficiently | ||
| 216 | Enhancement &1 is not locked in a transport request; no need to deploy it | Space: object requires documentation | ||
| 217 | Enhancement &1 is inactive; finish generation before releasing it | Space: object requires documentation | ||
| 218 | Element &1 &2 of enhancement &3 is not locked in a transport | Space: object requires documentation | ||
| 219 | This rapid application uses an outdated UI generator | The short text describes the object sufficiently | ||
| 220 | For the table, specify at least one field that is not calculated | The short text describes the object sufficiently | ||
| 221 | Component &1 cannot be used for multiple subelements | The short text describes the object sufficiently | ||
| 222 | You cannot add a DDIC table as a child of a new table | The short text describes the object sufficiently | ||
| 223 | Header table already exists | The short text describes the object sufficiently | ||
| 224 | You cannot use tables of this rapid application as check tables | The short text describes the object sufficiently | ||
| 225 | The table is still used in the UI model. Remove the UI element first | The short text describes the object sufficiently | ||
| 226 | Object &1 is used several times within one UI element unit | The short text describes the object sufficiently | ||
| 227 | Only tables with a cardinality of 1:N can be table extensible | The short text describes the object sufficiently | ||
| 228 | Maximum DB size exceeded; remove fields or reduce their length | The short text describes the object sufficiently | ||
| 229 | Check table &2 is not supported for field &1 | The short text describes the object sufficiently | ||
| 230 | Search help &2 is not supported for field &1 | The short text describes the object sufficiently | ||
| 231 | FPM configuration ID &1 already exists | The short text describes the object sufficiently | ||
| 232 | FPM configuration ID &1 is already used by enhancement &2 | The short text describes the object sufficiently | ||
| 233 | FPM configuration ID &1 is already used by this enhancement | The short text describes the object sufficiently | ||
| 234 | Enter an FPM configuration ID for the table below BOL object &1 | The short text describes the object sufficiently | ||
| 235 | FPM configuration ID &1 is not allowed to contain special characters | The short text describes the object sufficiently | ||
| 236 | FPM config ID &1 must have the same namespace (&2) as the enhancement | The short text describes the object sufficiently | ||
| 237 | Clearing shared genIL model and AET handler cache | The short text describes the object sufficiently | ||
| 238 | UI Component &1 does not support nested tables | Space: object requires documentation | ||
| 239 | genIL model for extensible object &1 could not be loaded | The short text describes the object sufficiently | ||
| 240 | No rule builder defined for the rule type &1 | The short text describes the object sufficiently | ||
| 241 | No rule builder defined for the rule ID &1 | The short text describes the object sufficiently | ||
| 242 | No rule mapper defined for the rule ID &1 and object name &2 | The short text describes the object sufficiently | ||
| 243 | No rule handler defined for the rule type &1 and object type &2 | The short text describes the object sufficiently | ||
| 244 | No rule application defined | The short text describes the object sufficiently | ||
| 245 | Rule parameter mapping for &1 already exists | The short text describes the object sufficiently | ||
| 246 | No result object defined for the formula &1 | The short text describes the object sufficiently | ||
| 247 | Rule handler only supports BOL entities | The short text describes the object sufficiently | ||
| 248 | Calculation for field "&1" failed | The short text describes the object sufficiently | ||
| 249 | No mapping defined for &1 | The short text describes the object sufficiently | ||
| 250 | Specify a BOL object | The short text describes the object sufficiently | ||
| 251 | &1 is not a valid parameter for a formula | The short text describes the object sufficiently | ||
| 252 | Variable BPath return structures are not supported; adjust &1 | The short text describes the object sufficiently | ||
| 253 | Only data elements as BPath return types are supported; adjust &1 | The short text describes the object sufficiently | ||
| 254 | Parent relation in your BPath statement is ambiguous; adjust &1 | The short text describes the object sufficiently | ||
| 255 | Formula is invalid | Space: object requires documentation | ||
| 256 | Parameter &1 needs a reference field path, otherwise you cannot use it | The short text describes the object sufficiently | ||
| 257 | Invalid BOL relation within your formula; adjust &1 | Space: object requires documentation | ||
| 258 | Timepoint fields are not supported; use another parameter as &1 | The short text describes the object sufficiently | ||
| 259 | BRFplus application &1 is not locked | The short text describes the object sufficiently | ||
| 260 | BRFplus function &1 is not locked | The short text describes the object sufficiently | ||
| 261 | Cannot use &1; it is not possible to trace an association backwards | The short text describes the object sufficiently | ||
| 262 | Your global attribute tag is converted to the BPath statement &1&2&3&4 | The short text describes the object sufficiently | ||
| 263 | Cannot use &1; &2 is not in the path and has ambiguous parent relations | Space: object requires documentation | ||
| 264 | Several BOL objects enhanced; you can assign formula to each BOL object | Space: object requires documentation | ||
| 265 | Remaining table space is not enough to support field enhancements | Space: object requires documentation | ||
| 266 | Reserved field quota has been exceeded | Space: object requires documentation | ||
| 267 | The table still has a child table in enhancement &1 | The short text describes the object sufficiently |
History
| Last changed on/by | 20130531 | SAP | |
| SAP Release Created in | 700 |