REBDOA - Nachrichten f�r Objektbeziehungen
The following messages are stored in message class REBDOA: Nachrichten f�r Objektbeziehungen.
It is part of development package RE_BD_OA in software component RE-FX-BD. This development package consists of objects that can be grouped under "RE: Object Assignment".
It is part of development package RE_BD_OA in software component RE-FX-BD. This development package consists of objects that can be grouped under "RE: Object Assignment".
Message Nr ▲ | Message Text |
|---|---|
| 001 | Relationship &1: object &2 is not assigned to object &3 on &4 |
| 002 | &1: assignment already exists |
| 003 | &1 is already assigned to &3 in period &2 |
| 004 | Object type &1 not allowed to be assigned using assignment type &2 |
| 005 | Objects of type &1 not allowed to be assigned to &2 |
| 006 | Object of type &2 cannot be assigned to object &1 |
| 007 | Informational assignment is not allowed for object &1 (&2) |
| 008 | Only informational assignment is allowed for object &1 (&2) |
| 009 | Object &1 (&2) cannot be used for distribution |
| 010 | Internal error: no interface is entered for assignment type &1 |
| 011 | Assignment to &1 not adopted: &2 |
| 012 | &1 is not allowed since the activity "Assign" is not allowed |
| 013 | &1 (or superordinate object) already exists in &2 (&3) |
| 014 | &1 - assignment &2: the object validity is only in area &3 |
| 015 | Internal error: number for &1 is temporary at save; object type &2 |
| 016 | Object &1 &2 is still used in condition &3 |
| 017 | Internal error: an object was not entered for assignment |
| 018 | &1 cannot be assigned to itself |
| 019 | &1 is assigned more than once with overlapping dates to &2 |
| 020 | &1 is assigned to different objects in period &2 (input tax distribution) |
| 021 | Indicator for relevance to option rate already set for &1 in object &2 |
| 022 | Unit of measurement not entered for object &1 (&2) |
| 023 | &1 (&2) measurement amount of object (&3) less than assignment (&4) |
| 024 | There are no allowed object types for the assignment |
| 025 | Order &1 does not exist |
| 026 | Number &1 for object group assigned more than once ('&2' and '&3') |
| 027 | &1/&2: you did not enter an object for assignment |
| 028 | Not possible to assign object &1 |
| 029 | &1 is already assigned to &2 (&3 to &4) |
| 030 | Assigning subobjects is not allowed for object type &1 |
| 031 | &1 is already assigned to &2 (&3 to &4) |
| 032 | &1 (&2) definition of the possession dates is not consistent |
| 033 | &1 (&2) the possession dates extend beyond the validity of the object |
| 034 | Operation is not allowed, change only in COA company code |
| 035 | &1 - Assignment &2: Validity of cost center lies only in area &3 |
| 036 | &1 - Assignment &2: The org. unit validity is only in area &3 |
| 037 | &1 - assignment &2: the object validity is only in area &3 |
| 038 | Number &1 for contract object is assigned more than once ('&2' and '&3') |
| 039 | &1 - assignment &2: the object validity is only in area &3 |
| 040 | Asset &2 already exists for contract object &1 |
| 041 | Contract object type &1 is obsolete |
| 042 | Contract object type &1 does not exist. |
| 043 | The object type &1 cannot be used for object groups |
| 100 | Internal error: assigned to object group but not to object itself |
| 101 | Int.error: assigned to object group and multiple assign. to object itself |
| 102 | Internal error: object group belonging to it is not assigned |
| 103 | Internal error: the same object group is assigned more than once |
| 104 | Internal error: object is assigned more than once at same time |