LTR2_CM_CHECK_BO - LTR2 checks on Business Objects of Content Module
The following messages are stored in message class LTR2_CM_CHECK_BO: LTR2 checks on Business Objects of Content Module.
It is part of development package LTR2_CM in software component CA-LT. This development package consists of objects that can be grouped under "LTR2 Content Module".
It is part of development package LTR2_CM in software component CA-LT. This development package consists of objects that can be grouped under "LTR2 Content Module".
Message Nr ▲ | Message Text |
---|---|
000 | Check on Business Object Properties |
001 | Business object GUID '&3' is invalid; see long text |
002 | Data model &3 exists in the content module only |
003 | Namespace &3 conflicts with the content module namespace; see long text |
004 | Scope status conflicts; see long text |
005 | Duplicate alias &3 found in the content module |
006 | Check on consistency with Business Object Dictionary |
007 | Data model &3 missing from the content module; see long text |
008 | Data Model status consistent with that in Business Object Dictionary |
009 | Business object in the content module does not contain any data models |
010 | Business object not approved; see long text |
011 | Approval status: &3 |
012 | Invalid data found; see long text |
013 | Alias value is initial |
014 | Alias: &3 |
015 | Checks on Data Models |
016 | Data Model &3 |
017 | Check in Data Model properties |
018 | Namespace: &3 |
019 | Data model GUID '&3' is invalid; see long text |
020 | Data model tables inconsistent with those in business object dictionary |
021 | Data model &3 not consistent in the Content Module |
022 | Data model status consistent with that in business object dictionary |
023 | Table &3 not exist in business object dictionary |
024 | Table &3 missing from the conent module |
025 | Check on selection settings |
026 | &3&4 |
027 | Migration settings not allowed with transformation method '&3' |
028 | Technical selection: &3 |
029 | Preselection table: &3 |
030 | Check on dependency settings |
031 | Preselection Settings |
032 | Business objects with initial GUID found |
033 | Field &3 of table &4 is missing in the IOBJ |
034 | Filter also assigned to field &3 of table &4 |
036 | Technical selection value &3 is invalid |
037 | Preselection table &3 is invalid |
038 | 'No preselection table' option is not allowed for sub business objects |
039 | Table &3 with sequence number &4 |
040 | Invalid data will be removed and the changes will be saved. |
041 | Invalid business object will be removed and the changes will be saved. |
042 | Invalid data model will be removed and the changes will be saved. |
043 | Do you want to continue? |
044 | Invalid data removed |
045 | Table ID '&3' is missing in data model &4 |
046 | Invalid business object removed |
048 | Invalid data model removed |
050 | New business object alias will be generated. |
051 | The changes will be saved. |
052 | New business object alias is generated. |
053 | No business object found with alias &1; no data changed |
054 | No business object alias changed |
055 | Content module &1 is invalid; no data changed |
056 | Position ID &1 is invalid; no data changed |
057 | Data model &1 is invalid; no data changed |
058 | Business object data synchronized with business object dictionary |
059 | Content module &1 does not exist |
060 | Alias &1 is unique in the content module; no data changed |
061 | Need parent position for data model &1 |
062 | Data model is synchronized with business object dictionary |
064 | Preselection setting is set to default value |
065 | Preselection setting value will be set to default. |
066 | No preselection setting in the content module |
067 | Businisess object will be synchronized with business object dictionary. |
068 | Data model will be synchronized with business object dictionary. |
069 | The scope status of the business object will be updated. |
070 | The business object is set to in scope |
071 | Data models not consistent with those in business object dictionary |
072 | The business object is set to out of scope |
073 | Check on filter assignments |
074 | Filter not found with GUID '&3' |
075 | Fieldname '&3' of table '&4' is missing in the IOBJ |
076 | Fieldname '&3' of table '&4' is not character-like; see long text |
077 | Dependency also defined to the field '&3' of table '&4' |
078 | Only CM-Specific BO is allowed for filter assignment |