SCBO_CONSISTENCY_CHK - Consistency check messages for Custom Business Objects
The following messages are stored in message class SCBO_CONSISTENCY_CHK: Consistency check messages for Custom Business Objects.
It is part of development package S_CBO_MESSAGES in software component BC-SRV-APS-EXT-BO. This development package consists of objects that can be grouped under "Custom Business Objects: Messages".
It is part of development package S_CBO_MESSAGES in software component BC-SRV-APS-EXT-BO. This development package consists of objects that can be grouped under "Custom Business Objects: Messages".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Internal error. Please report an incident. |
| 001 | Node &1 contains at least one field without a field ID. |
| 002 | Field ID &1 of node &2 contains invalid characters. |
| 003 | Field ID &1 of node &2 is reserved. |
| 004 | A node ID is required. |
| 005 | Node ID &1 contains more than &2 characters. |
| 006 | Node ID &1 contains invalid characters. |
| 007 | Business object requires a name. |
| 008 | Field &1 of node &2 requires a field type. |
| 009 | Field ID &1 of node &2 contains more than &3 characters. |
| 010 | Field &1 of node &2 has an invalid type. |
| 011 | A value for the length of field &1 of node &2 is required. |
| 012 | The scale must not exceed the length of field &1 of node &2. |
| 013 | The length of field &1 of node &2 must not exceed &3 characters. |
| 014 | Field ID &1 of node &2 must start with a letter. |
| 015 | Exactly one root node is needed. |
| 016 | Parent node &1 of node &2 does not exist. |
| 017 | System is not configured to create business objects. |
| 018 | Business object ID is invalid. |
| 019 | Field ID &1 of node &2 contains lowercase letters. |
| 020 | Node ID &1 clashes with node ID &2. |
| 021 | Business object ID &1 must start with prefix &2. |
| 022 | The generation of a UI requires the generation of a service. |
| 023 | Node &1 requires at least one user-defined field. |
| 024 | The scale of field &1 of node &2 must not exceed value &3. |
| 025 | Generated IDs of fields &1 and &2 in node &3 clash. |
| 026 | Node ID &1 must start with a letter. |
| 027 | Field ID &1 of node &2 clashes with field &3. |
| 028 | The length of field &1 of node &2 must not exceed &3 digits. |
| 029 | The name of the root node differs from the business object name. |
| 030 | Node ID &1 clashes with field ID &2 of node &3. |
| 031 | Node ID &1 is an internally reserved value. |
| 032 | The key indicator cannot be set for the type of field &1 of node &2. |
| 033 | No key defined for node &1. The key cannot be added after transportation. |
| 034 | No key defined for node &1. |
| 035 | Key fields are allowed on root nodes only. |
| 036 | A value for the code list of field &1 of node &2 is required. |
| 037 | Custom code list &1 of field &2 of node &3 does not exist. |
| 038 | Custom code list &1 of field &2 of node &3 is not published. |
| 039 | The service and UI generation indicators must be specified identically. |
| 040 | The UI generation is not allowed. |
| 041 | Enter a valid business object for the association of field &1 of node &2. |
| 042 | Associated business object &1 of field &2 of node &3 does not exist. |
| 043 | Associated business object &1 of field &2 of node &3 is not published. |
| 044 | Object &1 can't be associated, it requires at least one root key field. |
| 045 | Field &1 of node &2 must not start with the prefix TO_ |
| 046 | Element &1 of node &2 must not associate own business object. |
| 047 | Action ID &1 of node &2 clashes with action ID &3. |
| 048 | Node &1 contains at least one action without an action ID. |
| 049 | Action ID &1 of node &2 contains invalid characters. |
| 050 | Action ID &1 of node &2 must start with a letter. |
| 051 | Field ID is missing on node &1. |
| 052 | Action ID is missing on node &1. |
| 053 | Business object requires a name in plural. |
| 054 | Name in plural "&1" is also used by other business object. |
| 055 | Multiple hierarchy feature is switched on, UI generation is not allowed. |
| 056 | Change of generated field &1 not allowed. |
| 057 | Field &1 marked as generated. This is not allowed. |
| 058 | Multiple hierarchy feature is switched off. |
| 059 | Business Object is outdated, please close and re-open the copy dialog. |
| 060 | Only published Business Objects can be copied. |
| 062 | Association field &1 of node &2 can have up to 24 characters. |
| 063 | Republish the business object to view the translations in the UI |
| 064 | Data Extraction Delta Update requires System Administrative Data. |
| 065 | &1&2&3 (Caused by business object &4) |
| 066 | Enabling Data access management requires generation of service. |
| 067 | Enabling Data access management requires generation of UI. |
| 068 | Enabling Data access management requires generation of change documents. |
| 069 | Associated business objects cannot have associations as key. |
| 070 | Data access management is not allowed. |
| 071 | Enabling Data access management requires System administrative data. |
| 072 | Association Target &1 requires Data Access Management. |
| 073 | The value help view must be based on the association view. |
| 074 | The value help view must include all keys of the association target. |
| 075 | The value help view &1 does not exist. |
| 076 | Please republish all associated objects. |
| 077 | Consistency Check returned issues for business object &1: |
| 078 | Translations of association target &1 changed. Please republish. |
| 079 | The value help view &1 contains errors. Please fix it and publish again. |
| 080 | Only one element can be used as page title. |
| 081 | Element &1 cannot be used as page title due to its type. |
| 082 | Scenario &1 does not exist. |
| 083 | The value help view must not contain parameters. |
| 084 | Data Extraction requires that feature is enabled in system. |