SWB_OBJECT_TYPES - WB: Object Types
The following messages are stored in message class SWB_OBJECT_TYPES: WB: Object Types.
It is part of development package SWB_OBJECT_TYPES in software component BC-DWB-UTL-BRR. This development package consists of objects that can be grouped under "Management of Object Types".
It is part of development package SWB_OBJECT_TYPES in software component BC-DWB-UTL-BRR. This development package consists of objects that can be grouped under "Management of Object Types".
Message Nr ▲ | Message Text |
|---|---|
| 002 | Object type & is not a logical transport object |
| 003 | & is active in Version Management; thus, usage area VERS is mandatory |
| 004 | Usage area &1 cannot be deleted for object type &2 |
| 005 | Object type &1 does not exist |
| 010 | Object type usage area & does not exist |
| 011 | Object type usage area & is obsolete and should not be selected |
| 013 | Usage area &1 is not valid for WB types |
| 014 | Usage area &1 is not valid for R3TR types |
| 022 | Usage area & does not exist |
| 025 | &1: Usage areas &2 and &3 cannot be matched up |
| 030 | Class & cannot be run |
| 031 | Class & does not implement interface & |
| 032 | Class & cannot be analyzed |
| 034 | A service class (IF_WB_ACCESS) must be specified for object type & & |
| 035 | Object Type & &, Usage Area &: Service class missing |
| 036 | Several subtypes are marked as Main Object Type: &1, &2 |
| 037 | The length of name &1 should not exceed 30 characters |
| 038 | No WB subtype is marked as main type |
| 040 | Maximum object name length &: value must be & according to R3TR def. |
| 041 | Maximum object name length for type &: value & is too small |
| 042 | Maximum object name length for type &: value & is too large |
| 044 | Name of default subtype (&1) and name of R3TR type (&2) are not the same |
| 045 | Names of default subtype are empty |
| 046 | Object type &1 does not conform to constraints on legacy type group |
| 047 | Object type &1 is in a classic type group; special considerations needed |
| 050 | Error while generating table entries for & in WB tables |
| 051 | WB table entries were successfully generated for object type & |
| 052 | Invalidation of shared memory area &1 has failed |
| 060 | Generic existence check for objects of type & is not possible |
| 062 | Error while instantiating class & for object type & |
| 063 | Error in object type API during handling of object type & |
| 070 | Error while generating a container ID for WB browser tool & |
| 071 | Browser tool class &1 is already used in another context (&2) |
| 072 | Usage area & will be declared in several subtypes |
| 073 | Usage area &2 was not specified for subtype &1 |
| 074 | Object type group &1 does not exist |
| 075 | Insufficient data regarding the URI of the REST resource |
| 076 | Class & does not exist |
| 077 | & is not a class |
| 078 | The category scheme must be longer than 8 characters |
| 079 | For the default subtype, the category term must not be empty |
| 080 | The WB subtype & is longer than 3 characters |
| 081 | The persistency class is missing |
| 082 | The category scheme is already used in object type group & |
| 083 | The resource category is invalid. Allowed values are 0, 1, and 2. |
| 085 | Object type &1: The URI is too short (&2) |
| 086 | Object type &1: The URI does not start with /sap/bc/ |
| 087 | Object type &1: The URI is already used by object type &2 |
| 088 | Object type &1: The URI contains invalid characters (&2) |
| 089 | Object type &1: The URI has too few segments |
| 090 | Tool class &1 is already used for a different object type (&2) |
| 095 | Object type &1: The URI path must not end with a '/' |
| 096 | Object type &1: The URI is too long; maximum length is 40 characters |
| 097 | Object type group &1 has a different category scheme |
| 101 | Display of historic version for objects of type &1 is not yet implemented |
| 110 | Object type & contains advanced data; use SAP GUI editor |
| 111 | No data are defined for usage area &1 |
| 112 | Visibility in object list: current setting does not match DOCUMENTATION |
| 113 | Object type &1 is not TLOGO, therefore VERS details must be empty |
| 114 | Object type &1 is TLOGO, therefore VERS details must not be empty |