SOS_MAPPING - Object Services: Nachrichten Persistenzabbildung
The following messages are stored in message class SOS_MAPPING: Object Services: Nachrichten Persistenzabbildung.
It is part of development package SOS_MAPPING in software component BC-ABA-LA-OBS. This development package consists of objects that can be grouped under "Object Services Relational Mapping".
It is part of development package SOS_MAPPING in software component BC-ABA-LA-OBS. This development package consists of objects that can be grouped under "Object Services Relational Mapping".
Message Nr ▲ | Message Text |
|---|---|
| 000 | & |
| 001 | &1&2&3&4 |
| 100 | Access to attribute failed - development object does not exist |
| 101 | Access to attribute failed - database error |
| 102 | Access to attribute failed - unexpected error |
| 103 | Mapping access failed - development object does not exist |
| 104 | Mapping access failed - unexpected error |
| 105 | No errors were found |
| 106 | Metadata operation failed - &1 |
| 107 | Table access failed - unexpected error |
| 108 | Access to class agent failed |
| 110 | Lock operation failed |
| 111 | You cannot make changes in display mode |
| 112 | Display mode |
| 113 | Change mode |
| 114 | Attribute is protected and cannot be changed |
| 115 | There is no inactive version of the mapping |
| 116 | No active version of the mapping exists |
| 120 | Attempt to load failed |
| 121 | Attempt to save failed |
| 122 | Check unsuccessful |
| 123 | Changes not allowed |
| 124 | Unable to find table or structure & |
| 125 | &: There is already a component with the same name |
| 126 | & is a reserved name |
| 127 | You can only use & to specify the GUID field |
| 128 | Key characteristic has been set automatically to READ ONLY |
| 129 | Persistence representation layer generated |
| 130 | Data was saved |
| 131 | & is not a table: The database access layer has been implemented manually |
| 132 | Cannot be assigned, due to a type conflict: Cannot change & |
| 133 | &: Persistence mapping was successful; attribute cannot be changed |
| 134 | & has already been assigned |
| 135 | The attribute name has not been defined |
| 136 | Redefinition of persistence mapping: first remove existing assignment |
| 137 | Type & is not compatible with existing field assignment |
| 138 | Field assignment invalid for reference: Fields are from different tables |
| 139 | This persistence mapping allows only one field assignment |
| 140 | The name & that you reserved is already assigned to a standard attribute |
| 141 | The name of the attribute &1 must start with the namespace &2 |
| 142 | OS_GUID is used as the attribute name |
| 143 | You cannot define a mapping for abstract classes |
| 144 | OS_TYPE is used as the attribute name |
| 145 | The persistence mapping has already been defined in a superclass |
| 146 | & is only valid when defining the TYPE field |
| 147 | You must specify a type for a value attribute |
| 148 | The TYPE field can only exist in the root class |
| 149 | A transient attribute, &, already exists in the superclass |
| 150 | You cannot edit this attribute |
| 151 | Attributes of abstract persistent classes cannot be edited |
| 152 | The attribute is specified in the defined superclass as read-only |
| 153 | The attribute is a reference in the defined superclass |
| 154 | The attribute is not a reference in the defined superclass |
| 155 | The mapping type is not valid in the redefinition of the mapping |
| 156 | Visibility and modifiability adapted to match the defined superclass |
| 157 | Type & is not compatible with type & in the defined superclass |
| 158 | Attributes with direct type specified are not valid in persistent classes |
| 159 | & is not a valid attribute name |
| 161 | The multiple access indicator has been set automatically |
| 200 | Error in mass operation: &1 of &2 operations failed |
| 201 | Could not change component &1 (class &2) |
| 202 | Could not delete component &1 (class &2) |
| 203 | Could not change inheritance for the class &1 (class &2) |
| 204 | Could not change redefinition of &1 (class &2) |
| 205 | Could not delete redefinition of &1 (class &2) |
| 206 | Could not change interface relationship &1 (class &2) |
| 207 | Could not change parameter &1 of &2 (class &3) |
| 208 | Could not delete parameter &1 of &2 (class &3) |
| 209 | Could not change exception &1 of &2 (class &3) |
| 210 | Could not delete exception &1 of &2 (class &3) |
| 211 | Include generation failed for &1 (class &2) |
| 212 | Forward declaration &1 failed (class &2) |
| 213 | Cannot delete interface relationship &1 (class &2) |
| 214 | Length of type &1 is greater than 9999 characters (class &2) |
| 300 | Error when generating class agent |
| 800 | Mapping header is empty |
| 801 | No attributes exist in mapping |
| 802 | Field & in mapping header is inconsistent |
| 803 | Wrong version in header of mapping |
| 804 | OWNACCESS contains wrong value in mapping header |
| 805 | Field & of mapping is inconsistent (header <-> attribute) |
| 806 | Second field found for identifier GUID in mapping |
| 807 | Unable to find key information in mapping |
| 808 | Object & is not active in ABAP Dictionary |
| 809 | ABAP Dictionary object & is not a table, structure, or view |
| 810 | ABAP Dictionary object & is a structure - OWNACCESS must be active |
| 811 | Database operations with view & are not allowed |
| 812 | Field & does not exist in ABAP Dictionary object & |
| 813 | Field & is not a key field of ABAP Dictionary object & |
| 814 | GUID field & is not a key field of ABAP Dictionary object & |
| 815 | Attribute name & for identifier GUID is incorrect |
| 816 | GUID field & has an incorrect type in dictionary object & |
| 817 | Attribute name & is reserved for identified GUID |
| 818 | Attribute & has the wrong reference type |
| 819 | Attribute &: Inverse attribute not allowed |
| 820 | Attribute &: FIELDTYPE is incorrect for reference attribute |
| 821 | Attribute &: Wrong data type for dictionary field |
| 822 | Attribute &: Reference type is wrong |
| 823 | Attribute &: Data type for ABAP Dictionary field & is empty |
| 824 | Persistent attribute & does not exist in mapping |
| 825 | Number of persistent attributes <> number of attributes in mapping |
| 826 | Attribute &: Wrong typing category in Class Builder |
| 827 | Attribute &: Typing category & wrong for FIELDTYPE & |
| 828 | Attribute &: Type & is not active in ABAP Dictionary |
| 829 | Attribute &: Type of field & is unequal |
| 830 | Unexpected error occurred in & |
| 831 | Unable to find mapping for class & |
| 832 | Unable to find mapping attributes for class & |
| 833 | Mapping name not specified |
| 834 | Mapping for class & already exists |
| 835 | Wrong parameter & in & |
| 836 | Unable to find mapping header for class & |
| 837 | Attribute &: You cannot map using the client field |
| 838 | Value attribute &: You cannot map using the key field |
| 839 | Attribute &: Complex attribute must be a value attribute |
| 840 | Reference attribute &: Class identifier missing |
| 841 | Class &: Could not find version & |
| 842 | Could not find mapping for class & in version & |
| 843 | Mapping is defined in another class |
| 844 | There is no mapping defined for the key field &1 in the table &2. |
| 845 | The business key and GUID must be defined in all tables |
| 846 | There is no mapping defined in the table &2 for the key field &1 |
| 847 | The GUID field & is a key field in the dictionary object & |
| 848 | The class & does not exist in the inheritance hierarchy |
| 849 | The manual generator setting has been chosen in the superclass & |
| 850 | The TYPE field exists more than once |
| 851 | The TYPE field can only exist in the root class |
| 852 | A dictionary object was used in the superclass and subclass |
| 853 | There is no mapping defined for one or more fields |
| 854 | QUERYACCESS and MULTIACCESS in the mapping header have invalid values |