REBDAO - Nachrichen des architektonischen Objekts
The following messages are stored in message class REBDAO: Nachrichen des architektonischen Objekts.
It is part of development package RE_BD_AO in software component RE-FX-BD. This development package consists of objects that can be grouped under "RE: Arch. Object (Master Data of Architectural Object)".
It is part of development package RE_BD_AO in software component RE-FX-BD. This development package consists of objects that can be grouped under "RE: Arch. Object (Master Data of Architectural Object)".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Object assignment cannot be changed for released object |
| 001 | An object of this category &1 exists already in the structure tree |
| 002 | Invalid assignment |
| 003 | Function &1 is not available |
| 004 | Specify architectural object type |
| 005 | Enter the number of the architectural object |
| 006 | Function &1 is not permitted for architectural object type &2 |
| 007 | Arch. object number &1 not in permitted range from &2 to &3 |
| 008 | Common usage &1 does not exist |
| 009 | No number was entered (despite external number assignment) |
| 010 | Architectural object with ID &1 already exists in the system |
| 011 | &1 must not be changed |
| 012 | Beginning of construction must be before date of completion |
| 013 | Date of application must be before date of building permit |
| 014 | Planning inquiry date must be before the application for building permit |
| 015 | Planning inquiry must be before construction start date |
| 016 | Planning inquiry must be before date of building permit |
| 017 | Planning inquiry must be before date of completion |
| 018 | Date when ready for occupation must be after completion date |
| 019 | Date when ready for occupation must be after construction start date |
| 020 | Enter the date for the start of funding |
| 021 | Funding start date must be before funding end date |
| 022 | Enter a date for the end of funding |
| 023 | Final inspection has to be after the completion date |
| 024 | Final inspection may not occur before construction start |
| 025 | Prior notice can only be given after the planning inquiry |
| 026 | The last renovation must be after the ready for occupation date |
| 027 | The last renovation must be after the date of completion |
| 028 | The last renovation must be after the construction start date |
| 029 | Measurement structure &1 does not exist |
| 030 | Building type &1 does not exist |
| 031 | The valid-from date must be before the valid-to date |
| 032 | There are still subordinate architectural objects (number: &1) |
| 033 | Subordinate architectural objects exist without deletion flag (no.: &1) |
| 034 | Architectural object of type &1 and number &2 does not exist |
| 035 | Architectural object type &1 does not exist |
| 036 | Hierarchy entered is not unique |
| 037 | Entry does not exist |
| 038 | Enter the ID of the architectural object |
| 039 | From-entry is greater than to-entry |
| 040 | Key &1 &2 (AOTYPE, AONR) is not in table &3 |
| 041 | More than 1 entry for key &1 &2 (AOTYPE, AONR) in table &3 |
| 042 | Arch. object &1 &2 (AOTYPE, AONR) does not have any hierarchy nodes |
| 043 | Object &1 &2 (AOTYPE, AONR) was not found |
| 044 | Enter an object type and object number |
| 045 | The hierarchy is not complete |
| 046 | Enter the next higher-level hierarchy node |
| 047 | Number assignment was not defined on the top level of the hierarchy |
| 048 | There is already another object type (&1) on the same level |
| 049 | Number assignment is not completely defined for the arch. hierarchy |
| 050 | Internal error: no top object entered for the list |
| 051 | Object still has errors, release is not possible |
| 052 | Arch. object type &1 (&2) is already on the top level |
| 053 | You cannot assign an architectural object type to itself |
| 054 | Number assignment is not defined for object &1 |
| 055 | Changing the ID of the architectural object is not allowed |
| 056 | Number assignment is not defined for arch. object type &1 |
| 057 | Arch. object with ID &1 does not exist |
| 058 | Number assignment is not possible for object type &1 |
| 059 | There is no higher-level node |
| 060 | Arch. object with ID &1 already exists in the hierarchy |
| 061 | Arch. object with ID &1 already exists in superordinate object |
| 062 | Arch. object &2 already exists in number range for &1 |
| 063 | Arch. object &1 already exists in the system |
| 064 | Number assignment is defined incorrectly |
| 065 | The ID &1 contains invalid symbols |
| 066 | No architectural object types are defined |
| 067 | No object type hierarchy is defined |
| 068 | Architectural object ID cannot be generated |
| 069 | Separator &1 contains invalid characters |
| 070 | Object ID code (&1) is longer than allowed in Customizing (&2) |
| 071 | Related reservation object is locked - only possible to display |
| 072 | In create mode the reservation object does not yet exist |
| 073 | Not possible to delete related reservation object &1 |
| 074 | Reservation object must be adjusted |
| 075 | Subord. arch. objects without a deletion ind. still exist (number: &1) |
| 080 | Reservations exist in period &1; change not possible |
| 081 | Occupancies exist in period &1; change not possible |
| 082 | Function &1 is not possible |
| 083 | Function not possible from &1 |
| 084 | Function &1 valid from &2 does not exist |
| 085 | Validity of function &1 is outside object validity &2 |
| 086 | You cannot delete reservation object &1; deletion is not permitted |
| 087 | Arch. obj. &1: reservation objects cannot be updated |
| 088 | 'Function' required field is not always filled |
| 090 | Reservations outside period &1 exist. Change not possible. |
| 091 | Reservations outside period &1 exist. Change not possible. |
| 092 | Arch. obj. &1: reservation objects cannot be updated |
| 093 | Reservation object &1 cannot be deleted |