OST_BSDM - Web Service BOL Service Data Management
The following messages are stored in message class OST_BSDM: Web Service BOL Service Data Management.
It is part of development package WS_BOL_MD in software component CA-WUI-WST. This development package consists of objects that can be grouped under "Web Service Tool: Meta Data Storage".
It is part of development package WS_BOL_MD in software component CA-WUI-WST. This development package consists of objects that can be grouped under "Web Service Tool: Meta Data Storage".
Message Nr ▲ | Message Text |
---|---|
000 | Indirect recursion exists between &1 and &2 |
001 | Relationship &1 between &2 and &3 is missing; it has a 1:n cardinality |
002 | Result list object &1 is missing for selected query object &2 |
003 | Invalid descriptive names for BOL objects &1 |
004 | Root object is missing |
005 | Invalid root object: &1 |
006 | Error while deleting persisted information; service &1, component &2 |
007 | Invalid service design name: &1 |
008 | Invalid component name: &1 |
009 | Invalid root logical key: &1 |
010 | Root logical key &1 does not contain a value |
011 | Object ID not found |
012 | Descriptive relationship names are not well defined for object &1 |
013 | Invalid descriptive object names for BOL component: &1 |
014 | Descriptive object names are not well defined for object &1 |
015 | Invalid mapping SAP to ISO for &1 |
016 | &1 is not a root object or an access object |
017 | Invalid user selection for service &1, component &2 |
018 | Invalid time zone for &1 |
019 | BOL query object not found for design query object &1 |
020 | BOL query object &1 is not well defined |
021 | BOL query result object not found for BOL query object &1 |
022 | BOL query result object &1 is not well defined |
023 | BOL query object &1 not found |
024 | Invalid data format for &1 |
025 | An object has not been selected; select at least one object |
026 | Not possible to get data for service object &1 |
027 | Data type not supported; element &1 must be either a structure or table |
028 | Data type &1 does not have a corresponding design name |
029 | Mandatory field &1 must not be blank |
030 | Create not allowed for object &1 |
031 | Delete and change are not allowed for object &1 |
032 | No attributes were selected for object '&1' (&2) |
033 | Field &1 was assigned the default value &2 |
034 | Query result object &1 cannot be added to result |
035 | Object & is not designed to be used in a create service |
036 | Object & is not designed to be used in a change service |
037 | Object & is not designed to be used in a read service |
038 | Object & is not designed to be used in a query service |
039 | Root logical key of structure &1 does not contain a value |
040 | Data of input field &1-&2 will be lost (value: &3) |
041 | Design object name must not be initial (&1) |
042 | Parent design object for BOL object &1 could not be determined |
043 | Design object for BOL object &1 (parent: &2) could not be determined |
044 | Design object attribute could not be determined (&1 &2 &3) |
045 | Object key must be filled |
046 | Invalid result object for service &1, component &2, result object &3 |
047 | Parent design object for design object &1 could not be determined |
048 | Duplicate entries in table &1 |
049 | Object &1: logical key structure is missing |
050 | Design object &1 will be deleted from model |
051 | No attributes exist for design object &1 (BOL object: &2) |
052 | Key for object name &1, relationship name &2 must be filled |
053 | Result object "&1" is not supported (query "&2") |
054 | Select at least one operation |
055 | Runtime information reset; will be built up again with first call |
056 | Design object for BOL object &1-&2 could not be determined |
057 | Action code of &1 could not be interpreted |
058 | BOL model could not be read; service &1, component &2 |
059 | BOL relation &1 does not exist in BOL model for component &2 |
060 | Error in import conversion |
061 | No key field for relation &1 found; creation of object &2 requested |
062 | No query results |
063 | Key structure not defined for &1 |
064 | ID of object &1 could not be determined |
065 | For Object &1 &2 isn't a valid keystructure. |
066 | Component name for object &1 couldn't read |
067 | No access to GENIL model |
068 | Requested field &1 in object &2 is inactive. |
069 | Relation &1 is inactive for this operation |
070 | Requested relation &1 is inactive |
071 | Inactive Query &1 can't be used in a service |
072 | Inactive Query result &1 can't be used in a service |
073 | Inactive result object &1 of query object &2 can't be used in a service |
074 | Inactive field &1 of design object &2 can't be used in a service |
075 | Inactive relation &1 (design object &2) can't be used in a service |
076 | Select a query object to support query operation for service object |
077 | Resultobject &1 is not used in service object |
078 | Inactive Design object &1 can't be used in a service |
079 | &1 can't be used in a create service |
080 | Targetstructure &1 for object &2 is missing - readed information lost |