Message Number list used by SAP ABAP Program OSMW_IMP_MAIN_VIEW (MappingWizard: Implementierung lokale Klasse MAIN_VIEW)
SAP ABAP Program
OSMW_IMP_MAIN_VIEW (MappingWizard: Implementierung lokale Klasse MAIN_VIEW) is using
| # | Object Type | Object Name | Object Description | Note |
|---|---|---|---|---|
| 1 | SOS_MAPPING - 148 | The TYPE field can only be available in the root class | ||
| 2 | SOS_MAPPING - 138 | Field assignment invalid for reference: Fields are from different tables | ||
| 3 | SOS_MAPPING - 139 | This persistence mapping allows only one field assignment | ||
| 4 | SOS_MAPPING - 140 | The name & that you reserved is already assigned to a standard attribute | ||
| 5 | SOS_MAPPING - 141 | The name of the attribute &1 must start with the namespace &2 | ||
| 6 | SOS_MAPPING - 142 | OS_GUID is used as the attribute name | ||
| 7 | SOS_MAPPING - 144 | OS_TYPE is used as the attribute name | ||
| 8 | SOS_MAPPING - 145 | The persistence mapping has already been defined in a superclass | ||
| 9 | SOS_MAPPING - 146 | & is only valid when defining the TYPE field | ||
| 10 | SOS_MAPPING - 147 | You must specify a type for a value attribute | ||
| 11 | SOS_MAPPING - 137 | Type & is not compatible with existing field assignment | ||
| 12 | SOS_MAPPING - 149 | A transient attribute, &, already exists in the superclass | ||
| 13 | SOS_MAPPING - 152 | The attribute is specified in the defined superclass as read-only | ||
| 14 | SOS_MAPPING - 153 | The attribute is a reference in the defined superclass | ||
| 15 | SOS_MAPPING - 154 | The attribute is not a reference in the defined superclass | ||
| 16 | SOS_MAPPING - 155 | The mapping type is not valid in the redefinition of the mapping | ||
| 17 | SOS_MAPPING - 156 | Visibility and modifiability adapted to match the defined superclass | ||
| 18 | SOS_MAPPING - 157 | Type & is not compatible with type & in the defined superclass | ||
| 19 | SOS_MAPPING - 159 | & is not a valid attribute name | ||
| 20 | SOS_MAPPING - 300 | Error when generating class agent | ||
| 21 | SOS_MAPPING - 123 | Changes not allowed | ||
| 22 | SOS_MAPPING - 104 | Mapping access failed - unexpected error | ||
| 23 | SOS_MAPPING - 105 | No errors were found | ||
| 24 | SOS_MAPPING - 111 | You cannot make changes in display mode | ||
| 25 | SOS_MAPPING - 112 | Display mode | ||
| 26 | SOS_MAPPING - 113 | Change mode | ||
| 27 | SOS_MAPPING - 115 | There is no inactive version of the mapping | ||
| 28 | SOS_MAPPING - 116 | No active version of the mapping exists | ||
| 29 | SOS_MAPPING - 120 | Attempt to load failed | ||
| 30 | SOS_MAPPING - 121 | Attempt to save failed | ||
| 31 | SOS_MAPPING - 001 | &1&2&3&4 | ||
| 32 | SOS_MAPPING - 125 | &: There is already a component with the same name | ||
| 33 | SOS_MAPPING - 127 | You can only use & to specify the GUID field | ||
| 34 | SOS_MAPPING - 128 | Key characteristic has been set automatically to READ ONLY | ||
| 35 | SOS_MAPPING - 130 | Data was saved | ||
| 36 | SOS_MAPPING - 132 | Cannot be assigned, due to a type conflict: Cannot change & | ||
| 37 | SOS_MAPPING - 133 | &: Persistence mapping was successful; attribute cannot be changed | ||
| 38 | SOS_MAPPING - 135 | The attribute name has not been defined | ||
| 39 | SOS_MAPPING - 136 | Redefinition of persistence mapping: first remove existing assignment |