/SMB/SBA1 - Message Class for BCset Direct Active
The following messages are stored in message class /SMB/SBA1: Message Class for BCset Direct Active.
It is part of development package /SMB/COMMON in software component SV-CLD-FRM-INF. This development package consists of objects that can be grouped under "Commonly used objects".
It is part of development package /SMB/COMMON in software component SV-CLD-FRM-INF. This development package consists of objects that can be grouped under "Commonly used objects".
Message Nr ▲ | Message Text |
|---|---|
| 000 | & & & & |
| 001 | BC-Set definition &1 does not exist. Define it in change activity dialog |
| 002 | Enter an existing BC-Set |
| 003 | The Test Data Container & does not exist |
| 004 | Open file error: &1 |
| 005 | Read file error: &1 |
| 006 | Invalid file type |
| 007 | Wrong data format (use UTF-16) |
| 008 | Separator is not allowed |
| 009 | Access denied: &1 |
| 010 | Disk full or write protected |
| 011 | Write file error: &1 |
| 012 | File not found |
| 013 | Select only one item to maintain |
| 014 | Select an item to maintain |
| 015 | You can only maintain the language-independent field |
| 016 | The Test Data Container is initial, please maintain values |
| 017 | Directory &1 does not exist |
| 018 | The selected cell &1 can't be linked |
| 019 | Duplicate alias name, choose another one |
| 020 | The maximal number of test data containers is reached |
| 021 | Wrong parameters |
| 022 | Test data container & does not exist |
| 023 | Central data reference format is not correct. & |
| 024 | Unknown parameters & |
| 025 | BC-Set has been activated |
| 026 | Enter an existing definition file |
| 027 | Select at least one language |
| 028 | Can not maintain mapped field |
| 029 | Test data container alias must not be blank |
| 030 | Wrong file path |
| 031 | The navigation to system log is terminated due to an unexpected error |
| 032 | Separator is not allowed |
| 033 | Installation data table is empty |
| 034 | File path is not set |
| 035 | Specify a target language |
| 036 | File format error |
| 037 | Can not map 'Multi-Language Text Exist' field |
| 038 | Variant name must not be empty |
| 039 | Variant name: &1 is duplicate |
| 040 | Target language & does not exist in language set (released languages) |
| 041 | Target language can not be found in installation data |
| 042 | The LOG tables are locked |
| 043 | Length of installation data field: &1 exceeded |
| 044 | Length of installation data file name: &1 exceeded |
| 045 | Select a cell, not a column |
| 046 | Set download/upload codepage to UTF-8 |
| 047 | Enter the file path |
| 048 | Enter the input file name |
| 049 | File & does not exist |
| 050 | Select at least one test data container for upload |
| 051 | The Assigned Type &1 exists in the TDC-alias &2, clear it first |
| 052 | Path '&1' does not exist |
| 053 | Cental data files have been uploaded |
| 054 | Installation data value has been entered |
| 055 | Allowed values have already been entered - clear them first |
| 056 | New type &1 will be created automatically as it doesn't exist so far |
| 057 | Type description must not be empty |
| 058 | Empty file content |
| 059 | Enter values in all fields |
| 060 | No personalizaiton activity defined in this solution |
| 061 | No file exists in this solution |
| 062 | Unknow error (contact the developer/create message) |
| 063 | Select one entry |
| 064 | No valid BC-Set found in Definition XML File |
| 065 | Information: The filename &1 is already used in another activity |
| 066 | Test Data Container "&1", Parameter "&2" is already assigned to type "&3" |
| 067 | Enter object name |
| 068 | Encoding of the file & is not unicode (UTF-16) |
| 069 | The two fixed columns shall be [VARIANT] and [DESCRIPTION] ( file & ) |
| 070 | No parameter in file & |
| 071 | No data in file & |
| 072 | There is an empty column (after parameter &). Parameter name is required |
| 073 | & BC-Set Definition has been imported sucessfully |
| 074 | RFC destination error |
| 075 | Parameter & in BC Set does not exist in installation data file & |
| 076 | The XML file format is not correct |
| 077 | Scope item & has no target language. Activate it from edit view |
| 078 | Object & is currently locked by user & |
| 079 | No definition selected |
| 080 | Field & has the same default value &, but different recnumber & , & |
| 081 | Field &, default value & in definition, does not match value in BC-Set & |
| 082 | Folder can only be added at root node (solution) or folder level |
| 083 | Error occurs when displaying object |
| 084 | Folder can't be deleted since it contains personalization activities |
| 085 | Building Block is not used in favorite solution |
| 086 | Variants can only be maintained in language English |
| 087 | To edit variants, maintain date format in user settings as 'DD.MM.YYYY' |
| 088 | To edit variants, maintain decim. not. in user settings as '1.234.567,89' |
| 100 | TDC file has been uploaded |
| 101 | Error occurs when getting solution definition data |
| 102 | Solution folder is not set |
| 103 | Solution folder does not exist |
| 104 | |
| 105 | |
| 106 | Test Data Container: & is not defined in corresponding ECATT/BCSET Object |
| 107 | File & is empty |
| 108 | Error occurs when inserting the installation data table |
| 109 | File: & not found |
| 110 | File not set |
| 111 | Value doesn't exist for file: &, variant ID: &, parameter: & |
| 112 | Pattern & error |
| 113 | Error occurs when updating the installation data table |
| 114 | Cannot upload file & |
| 115 | Type: & is not maintained in TYPE table |
| 116 | Value does not exist in file name: & variant ID: & type: & |
| 117 | There is no installation data for current solution. Upload data |
| 118 | Test Data Container: & has no external file (Check Object) |
| 119 | Parameter: & does not exist in file: & |
| 120 | Data conversion error for file & |
| 121 | Error occurs when restoring the solution |
| 122 | Error retrieving web data for file & |
| 123 | Pattern & 's parameter & error |
| 124 | Variant ID overflow |
| 125 | File: & Variant ID: & can't be deleted |
| 126 | Type: & does not exist in file: & |
| 127 | Parameter name or type should be imported |
| 128 | TDC object name or TDC file name should be imported |
| 129 | Select one entry |
| 130 | ECATT & does not exist |
| 131 | Filename must not be blank |
| 132 | Enter the ECATT name |
| 133 | Maintain referencing information or org. type |
| 134 | Allowed values maintaned. Clear them and enter forbidden values? |
| 135 | Forbidden values maintained. Clear them and enter allowed values? |
| 136 | &1 Data element type is not maintained |
| 137 | Maintain data element properly |
| 138 | There is no parameter in the ECATT & |
| 139 | Select a solution node |
| 140 | Select a scope item node |
| 141 | Select a solution or scope item node |
| 142 | There is no scope item in solution & |
| 143 | Definition file folder does not exist |
| 144 | External file folder does not exist |
| 145 | Folder is empty |
| 146 | Installation data have been downloaded |
| 147 | Installation data have been uploaded |
| 148 | Select a Building Block node |
| 149 | Enter a solution ID via user settings |
| 150 | Select an ECATT or a BC Set node |
| 151 | Select an ECATT test configuration with external data |
| 152 | Select a BC Set to be activated with external data |
| 153 | Enter a folder for definition file via user setting |
| 154 | TDC Parameter is initial |
| 155 | Parameter is assigned to &. In file the same parameter is assigned to & |
| 156 | Parameters in file &1 do not match the parameters in object &2.&3 |
| 157 | Parameter name & (column No. &) also exists in other colum in file & |
| 158 | Duplicate variant ID & exists in file & |
| 159 | Value has wrong data type. Variant ID:&, Parameter name:&, filename:& |
| 160 | Variant ID is blank. Line & in file & |
| 161 | There is no data for solution & in &. Please & |
| 162 | Value & can not follow the pattern. Alias:&, Parameter:& is correct |
| 163 | Data upload terminated due to errors |
| 164 | There is no Building Block under solution &. Please & |
| 165 | File & is not a correct text file with extension '.TXT' for activity & |
| 166 | TDC assignment & is not a correct pattern for object &'s parameter & |
| 167 | There is no external file to upload for solution & |
| 168 | TDC object does not exist for alias & |
| 169 | Central data reference & in file does not match BC set definition |
| 170 | File &1 variant &2: value "&3" not found in TDC &4 |
| 171 | Variant &'s value & is duplicate with other variant for parameter & in & |
| 172 | Definition for BC set &1 does not exist |
| 173 | Bitmap files required for the display of the enterprise strucure |
| 174 | File &1 variant &2: parameter "&3" uses a reference but no TDC is defined |
| 175 | File &1 variant &2: parameter "&3" reference cannot be resolved ("&4") |
| 176 | Variant ID &1 is already in use |
| 177 | Creating new variant in file &1 failed |
| 178 | Variant &1 does not exist |
| 179 | Reading variant &1 failed |
| 180 | Technical error occurred: &1 |
| 181 | The file key must be specified completely |
| 182 | Variant data contains errors |
| 183 | Technical error in change recording |
| 184 | Key &1 is already used in variant &2 |
| 185 | Key parameter &1 was supplied multiple times |
| 186 | TDC assignment &1 of object &2 is not correct or not a supported type |
| 187 | File &1 not found. File State will be generated with empty file hash. |
| 188 | Changing variant &1 in file &2 failed |
| 190 | Error cascading changes |
| 191 | No file has been supplied |
| 192 | Two equal global items cannot be under the same solution |
| 193 | You can continue as a local definition |
| 194 | No scope item is selected |
| 200 | & & does already exist |
| 201 | Business Object Error |
| 202 | There is no Key Attribute for & |
| 203 | You haven't maintain Assignemnt for &'s attribute & |
| 204 | No Parameter is maintained in file & for & |
| 205 | There is no key value in file & for & |
| 206 | You haven't maintained assignment file for Business Object & |
| 207 | No & exists with key & |
| 208 | The value that you input should be in & characters |
| 209 | There is no personalization activity definition for the solution & |
| 210 | No file is found with solution id & and personalization id & |
| 211 | No filename is entered for & |
| 212 | You haven't entered file name for attribute & of & |
| 213 | The parameter & can not be changed |
| 214 | There is no TDC for parameter & in file &, you can not maintain it in TDC |
| 215 | & with key & does not exist in file & |
| 216 | Please enter file name for assignment of & |
| 217 | & & cann't be assigned to & & |
| 218 | & & have duplicate records in installation data file - not allowed |
| 219 | Combine type & is not defined (type definition in BB Builder) |
| 220 | Field & can't be empty |
| 221 | The original Business Object can not be deleted |
| 222 | The Business Object can not be deleted due to the sub object & & |
| 223 | Can not assign original Business Object & |
| 224 | Assignment between & & and & & does already exist |
| 225 | Assignment failed! & & has been assigned to & |
| 226 | & & can not be assigned without assignment with & |
| 227 | & & can not be assigned to & & with different company code assignment |
| 228 | Deletion failed! & & belonged to & & |
| 229 | Unlink failed! Related & has been used |
| 230 | Installation data file does not exist |
| 231 | No variant id for key value & of & |
| 232 | No assignment relation exists between & and & |
| 233 | & & is not available |
| 234 | Can not assign the original & & |
| 235 | Can not referencing information, & & is original |
| 236 | Update failed! & & does already exist in file & |
| 237 | & & exists in address file, does not exist in installation data file & |
| 238 | Unlink failed! & has been linked to &, they have the same company code & |
| 239 | Variant ID is initial in file &1 for parameter &2 |
| 240 | BC-Set is not specified. |
| 241 | BC-Set does not exist in table BC-Set Def. Header ( /SMB/BC_DEF_INFO ). |
| 242 | Error when reading BCset Definition. |
| 300 | Method call error in control framework |
| 301 | Error occurs when creating framework objects |
| 302 | Current enterprise structure has been saved |
| 303 | Error occurs when calling Business Object |
| 304 | Select the target language generated from released language list |
| 305 | Drag and Drop Org Unit under Expert Mode (Caution) |
| 306 | Create instance error |
| 307 | &1 does not exist |
| 308 | The value has not been changed |
| 309 | Type: &1 can not be assigned to type: &2 |
| 310 | &1 does already exists |
| 311 | Error occurs when creating tree |
| 312 | Current Org Unit Type can not be assigned again |
| 313 | The assignment can not be deleted |
| 314 | The org. unit cannot be deleted |
| 315 | You can only delete the new created org. unit |
| 316 | You can only delete the new created assignment |
| 317 | You can only make assignment on the new created org. unit |
| 318 | No file found for this personalization activity |
| 319 | Enter a value for the mandantory field |
| 320 | Error occurs when loading data |
| 321 | Error occurs when creating ALV |
| 322 | Current selected org unit is invalid (instance can not be found) |
| 323 | Current selected org unit is invalid (instance is null) |
| 324 | Same PAID for this file defined, input new ID or choose other function |
| 325 | UPDATE /SMB/SBA1_PA_DEF Failed |
| 326 | No language-dependent description available |
| 327 | You can not assign the org. unit to the same predesessor twice |
| 328 | All personalization activities have been saved for current solution ID |
| 329 | Data element error |
| 330 | Installation data for current solution not uploaded or maintained |
| 331 | The org. type selected is not maintained in Business Object mapping |
| 332 | Enter the sales organization number |
| 333 | Sales organiztion does not exist |
| 334 | Current distribution channel hasn't been assigned to sales organization |
| 335 | Current division hasn't been assigned to sales organization |
| 336 | Enter the distribution channel number |
| 337 | Enter the division number |
| 338 | Test |
| 339 | No active language maintained for this solution |
| 340 | Solution &1 does not exist |
| 341 | Select at least one active language |
| 342 | The language key &1 cannot be found in solution data |
| 343 | Target language &1 can not be found in released languages |
| 344 | Instance from Business Object type &1 is initial |
| 345 | You can not assign &1 to &2 |
| 346 | Edit mode &1 is not supported |
| 347 | Set graphic profile |
| 348 | Set up graphic profile manually |
| 349 | Set up graphic layout manually |
| 350 | Graphic profile and layout have been updated |
| 351 | Select the target language |
| 352 | No file has been selected |
| 353 | In 'Expert' mode, everything can be changed |
| 354 | BMP files do not exist in &. Copy BMP files to &.& |
| 355 | File & for personalization does not exist in solution & |
| 356 | Personalization & definition have been created |
| 357 | No installation data for file, please maintain it before this action |
| 358 | Create a personalization activity |
| 359 | Enter a variant ID |
| 360 | Personalization activity description is required |
| 361 | Save current enterprise structure data |
| 362 | Upload installation data before you maintain variant IDs |
| 363 | No activity for personalization found. |
| 364 | Enter a Business Object type description |
| 365 | The Business Object type ' & ' input is illegal |
| 366 | The same entries exist, delete the entry and re-enter it |
| 367 | No translation workpackage found |
| 368 | Delete transl. workpackage (solution:& , target language: &, creator: &)? |
| 369 | Translation workpackage for Solution & has been created |
| 370 | Translation workpackage needs to be recreated for changes to take effect |
| 371 | Please maintain parameter root first |
| 372 | Creating translation activities for Building Block & |
| 373 | File & is locked by & |
| 374 | Parameter roots maintained succesfully |
| 375 | Enter valid characters only |
| 376 | Data have been saved |
| 377 | Saving not possible; Parameter is duplicate |
| 378 | Completed &; need confirmation &; no translation & |
| 379 | No translation workpackage found |
| 380 | Translation workpackage for solution & is updated |
| 381 | Value & not found in relevant central data (&) |
| 382 | value & already exist in central data (&, &) |
| 383 | BC-Set name does not exist or contains no data |
| 384 | ECATT configuration & does not exist |
| 385 | Selected field is not the field name of the table |
| 386 | Enter field name |
| 387 | Enter table name |
| 388 | Enter table and field names |
| 389 | Table does not exist |
| 390 | Error in PME, check input data |
| 391 | Error creating temp. objects for definition. Processing cancelled. |
| 392 | DATA.xml not found in ZIP file |
| 393 | Function not available |
| 394 | & definitions of & successfully imported |
| 395 | Zip File does not exist |
| 396 | Variant &1 already in PME or already selected, choose another line |
| 397 | Only deselect a line that you selected (&1) |
| 398 | File contains no variants |
| 399 | Error in GMD layer. |
| 400 | Error in PME. |
| 401 | Error in ecatt framework. |
| 402 | Error in type definition. |
| 403 | Empty filename |
| 404 | Could not access workarea of installation data files |
| 405 | XML generation error |
| 406 | GUI download failed |
| 407 | No data found for solution &1 |
| 408 | Error concerning used types |
| 409 | Error in GMD layer |
| 410 | IMG &1 failed to activate |
| 411 | Enter Variant ID |
| 413 | Duplicate Variant ID '&1' |
| 414 | A TDC was used in Task &1 &2 &3 that was not in the definition |
| 415 | Not contained in favorite Solution |
| 416 | Error when creating file object &1 |
| 417 | Database error when reading content |
| 418 | Solution ID has not been specified |
| 419 | Deleting a variant or changing variant keys is not permitted |
| 420 | File version &1 is not supported |
| 421 | No installation data found in global PME |
| 422 | Insert into &1 database failed. |
| 423 | No data found in PME table. |
| 424 | Inserting log information failed. |
| 500 | No buffering |
| 501 | Parameter &1 must not be set twice in variant &2 |