SAP ABAP Message Class REBD (RE - Messages - Objects)
Basic Data
Hierarchy
☛
EA-FIN (Software Component) EA-FIN
⤷
RE-FX-BD (Application Component) Basic Data
⤷
RE_BD_OA (Package) RE: Object Assignment
⤷
⤷
Attributes
| Message class | REBD | |
| Short Description | RE - Messages - Objects | |
| Changed On | 20130531 | |
| Last Changed At | 105112 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 | Valid-from date of object is before valid-from date of group | Space: object requires documentation | ||
| 2 | Valid-to date of object is after valid-to date of group | Space: object requires documentation | ||
| 3 | The object group requires a name | Space: object requires documentation | ||
| 4 | You must specify the object | Space: object requires documentation | ||
| 5 | No items selected | Space: object requires documentation | ||
| 6 | The selection may only contain one or no object group | Space: object requires documentation | ||
| 7 | Object type &1 does not exist, or is not permitted | Space: object requires documentation | ||
| 8 | &1 &2 does not exist | Space: object requires documentation | ||
| 9 | To insert, select only one item or no item | Space: object requires documentation | ||
| 10 | &1 &2 was assigned to object group &3 | Space: object requires documentation | ||
| 11 | Error in Drag&Drop | Space: object requires documentation | ||
| 12 | Object group name &1 has already been assigned | Space: object requires documentation | ||
| 13 | Object &1 &2 has multiple assignments with time overlaps | Space: object requires documentation | ||
| 14 | Deletion not possible since &1 &2 is used in condition &3 | Space: object requires documentation | ||
| 15 | Enter object type | Space: object requires documentation | ||
| 16 | A new assignment line has been inserted | Space: object requires documentation | ||
| 17 | &1 assignment lines were deleted | Space: object requires documentation | ||
| 18 | No permitted object types are defined | Space: object requires documentation | ||
| 19 | No permitted object types defined | Space: object requires documentation | ||
| 20 | Assignment of object type &1 to an object group is not allowed | Space: object requires documentation | ||
| 21 | The first entry is already displayed | Space: object requires documentation | ||
| 22 | The last entry is already displayed | Space: object requires documentation | ||
| 23 | Object &1 does not exist | Space: object requires documentation | ||
| 24 | &1 &2 &3 &4 | Space: object requires documentation | ||
| 25 | &1 not possible since object is used in deleted condition(s) | Space: object requires documentation | ||
| 26 | Validity is not within the term of the object (&1 to &2) | Space: object requires documentation | ||
| 27 | &1 is already assigned to object &2 (&3 to &4) | |||
| 28 | Object &1 &2 is not allowed for this object | Space: object requires documentation | ||
| 29 | &1 is not allowed for this object | The short text describes the object sufficiently | ||
| 30 | The validity of the object is between &1 and &2 | Space: object requires documentation | ||
| 31 | &1 assignment lines were added | Space: object requires documentation | ||
| 32 | &1 or higher-level already exists in contract &2 (&3 to &4) | Space: object requires documentation | ||
| 33 | Object type unknown | Space: object requires documentation | ||
| 34 | Entry of assignment terminated | Space: object requires documentation | ||
| 35 | Contract is lease-out, objects copied only for informational purposes | Space: object requires documentation | ||
| 36 | Contract is lease-in, objects copied only for informational purposes | Space: object requires documentation | ||
| 37 | Contract does not contain any objects | Space: object requires documentation | ||
| 38 | The object is a contract object in real estate contracts (number: &1) | Space: object requires documentation | ||
| 39 | Validity of &1 is not limited to lease-in period | Space: object requires documentation | ||
| 40 | &1 is not valid for whole lease-in period | Space: object requires documentation | ||
| 41 | Object group number &1 does not exist | Space: object requires documentation | ||
| 42 | The object is still in contracts without a deletion flag (number: &1) | Space: object requires documentation | ||
| 43 | &1 not allowed because deletion indicator or flag is set | Space: object requires documentation | ||
| 44 | The selected object assignment no longer exists | Space: object requires documentation | ||
| 45 | Occupancy contract only allowed for common property | The short text describes the object sufficiently | ||
| 46 | Object &1 &2 is not allowed for an assessment contract | The short text describes the object sufficiently | ||
| 47 | Not possible to replace since &1 &2 is used in condition &3 | The short text describes the object sufficiently | ||
| 48 | Object is still used in offers without deletion flag (number: &1) | The short text describes the object sufficiently | ||
| 49 | There are active meters (number: &1) | The short text describes the object sufficiently | ||
| 50 | Validity of object &1 &2 is not within the assignment time period | Space: object requires documentation | ||
| 51 | Validity of object &1 &2 is not within productive holdings time period | Space: object requires documentation | ||
| 52 | More than &1 objects were assigned | Space: object requires documentation | ||
| 53 | Only field status purposes "1=Object originated in SAP system" allowed | The short text describes the object sufficiently | ||
| 54 | End date &1 of &2 &3 is before the end of assignment &4 | Space: object requires documentation | ||
| 55 | Object assignment of &2 to &1 is not supported | The short text describes the object sufficiently |
History
| Last changed on/by | 20130531 | SAP | |
| SAP Release Created in | 46C |