DAAG_DESIGNTIME - Message Class for Data Aging Design Time
The following messages are stored in message class DAAG_DESIGNTIME: Message Class for Data Aging Design Time.
It is part of development package S_DAAG_DESIGNTIME in software component BC-CCM-DAG. This development package consists of objects that can be grouped under "Design Runtime of a Data Aging Object".
It is part of development package S_DAAG_DESIGNTIME in software component BC-CCM-DAG. This development package consists of objects that can be grouped under "Design Runtime of a Data Aging Object".
Message Nr ▲ | Message Text |
|---|---|
| 000 | *** Back-end messages: 001 - 299 *** |
| 001 | Data Management object &1 does not exist |
| 002 | Data Management object &1 already exists |
| 003 | User &2 is already editing Data Management object &1 |
| 004 | Error while locking Data Management object &1 |
| 005 | Data Management object &1 is not locked |
| 006 | Data Management object &1 is active |
| 007 | Data Management object &1 does not contain any tables |
| 008 | No authorization to activate object &1 |
| 009 | No authorization to execute object &1 |
| 010 | Data Management object &1 is not active |
| 011 | Enhancement &1 already exists |
| 012 | No authorization to deactivate Data Management object &1 |
| 013 | Enhancement &1 does not contain any tables |
| 014 | Data Management object &1 has enhancements and cannot be deleted |
| 015 | Table &1 occurs multiple times |
| 016 | Switch &1 is not switched on |
| 017 | Switch &1 is off; data management object &2 deactivated |
| 018 | Data management object &1 is active; you cannot change enhancement &2 |
| 019 | Data management object &1 is active; unable to create enhancements |
| 020 | Data management object &1 is active; unable to delete enhancement &2 |
| 021 | Enhancement name is mandatory |
| 022 | Name of extended object is mandatory |
| 023 | Description of application is mandatory |
| 024 | Tables and keys cannot be initial |
| 025 | Reuse object &1 is not consistent |
| 026 | Deletion not possible; &1 is used in another data management object |
| 027 | No enhancement object assigned to object to be extended |
| 028 | SQL error: &1 |
| 029 | Data management object &1 is active, cannot save reuse object |
| 030 | Allowed days for undo run cannot be more than 180 |
| 031 | Cannot save, aging object does not implement parallellization interface |
| 032 | DAgO &1 cannot be created while upgrade is running |
| 033 | Operation cannot be performed while upgrade is running |
| 034 | Runtime class creation failed; Package not specified |
| 035 | The auto activation of data aging object &1 during run is not enabled |
| 036 | The data in the partitioning object is less than the threshold value |
| 037 | The selected data aging object does not exist |
| 038 | You cannot set aging rules for the selected data aging object |
| 039 | The transaction code does not exist |
| 040 | No rules have been created yet for the aging object |
| 041 | The data aging object does not use aging rules in its definition |
| 042 | Aging rule design time objects consistency check failed |
| 043 | Invalid aging rule function: &1 |
| 044 | No result data object assigned to function: &1 |
| 045 | No data source object assigned to function: &1 |
| 046 | No function assigned to the data aging object. Cannot define rules |
| 047 | No instance of the application found. Cannot define rules |
| 048 | No aging rules have been defined for aging object &1 |
| 049 | No data for defining rules. |
| 050 | Rule creation failed due to internal error |
| 051 | Error in consistency checks of residence rule design time objects |
| 052 | Since NSE is active for the involved tables, data aging is not possible |
| 090 | No authorization to Create object &1 |
| 091 | No authorization to modify object &1 |
| 300 | *** UI messages: 301ff *** |
| 301 | Data Management object &1 was saved |
| 302 | Data Management object &1 was activated |
| 303 | Data Management object &1 was deactivated |
| 304 | Data Management object &1 is consistent |
| 305 | Data Management object &1 was deleted |
| 306 | Select a Data Management object |
| 307 | Data Management object cannot enhance itself |
| 308 | Data Management object &1 is not consistent |
| 309 | Data Management object &1 will not be enhanced |
| 310 | Table &1 is not used in other Data Management object |
| 311 | Finish editing Data Management object &1 |
| 312 | Enhancement &1 was saved |
| 313 | Enhancement &1 is consistent |
| 314 | Enhancement &1 is not consistent |
| 315 | No further enhancement spots were entered for object &1 |
| 316 | Enhancement spot &1 does not exist |
| 317 | Enhancement &1 was deleted |
| 318 | Select an enhancement |
| 319 | Data Management object &1 already has enhancements |
| 320 | Problems in the transport interface; action canceled |
| 321 | Number of key fields for table &1 set to maximum possible number |
| 322 | BAdI &1 is defined in enhancement spot &2 |
| 323 | No BAdI definition entered for Data Management object &1 |
| 324 | Unable to activate Data Management object &1 |
| 325 | Data was saved |
| 326 | Object type needs to be set for data aging |
| 327 | Invalid object type |
| 328 | Deletion not possible, DAgO &1 contains reuse objects |
| 329 | Transaction does not exist |
| 330 | &v Table not Associated with any Data Management object |
| 331 | Multiple entries of the same table cannot exist |
| 332 | Time reference table &1 doesn't exist |
| 333 | Time reference field &1 is not part of table &2 |
| 334 | Table &1 is not defined in the Table information section |
| 335 | Table &1 doesn't exist |
| 336 | No key relationship exists between tables &1 and &2 |
| 337 | Rule field &1 is not part of table &2 |
| 338 | No rule fields have been defined for object &1 |
| 339 | Table relationship between &1 and &2 occurs multiple times |
| 340 | Rule field &1 occurs multiple times |
| 341 | Time reference field &1 of table &2 is not a date field |
| 342 | No table relationships defined. Maintain a destruction runtime class |
| 343 | Table &1 cannot be used as it is not listed under participating tables |
| 344 | Select a date field in the Field Name column |
| 346 | Enter values in Rule Fields tab and Reference Fields tab |
| 347 | Duplicate values cannot be entered |
| 348 | Select a condition field in the Field column |
| 349 | Rule Field and Reference Field tab can have only one participating table |
| 350 | Table Name field cannot be empty |