CFD_REGISTRY_CHECK - Custom Fields: Messages for Registry Check
The following messages are stored in message class CFD_REGISTRY_CHECK: Custom Fields: Messages for Registry Check.
It is part of development package S_CFD_REGISTRY_CHECK in software component BC-SRV-APS-EXT-FLD. This development package consists of objects that can be grouped under "Custom Fields: Application Registry Checks".
It is part of development package S_CFD_REGISTRY_CHECK in software component BC-SRV-APS-EXT-FLD. This development package consists of objects that can be grouped under "Custom Fields: Application Registry Checks".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Extensibility Registry: Consistency Checks |
| 001 | Reserve at least &1 bytes for the customer (&2% of &3 = &4 bytes) |
| 002 | Reserve at least &1 fields for the customer (&2% of &3 = &4 fields) |
| 003 | The maximum number of bytes is restricted to &1 |
| 004 | The maximum number of fields is restricted to &1 |
| 005 | Enter Source and Target Business Context for the Data Transfer |
| 006 | Internal error occurred |
| 007 | Width of table &1 is &2 bytes; quota is &3; Sum must be <= &4 bytes |
| 008 | Width of table &1 is &2 fields; quota is &3; Sum must be <= &4 fields |
| 009 | Entity &1 must be bound to a DDIC structure |
| 010 | Enter the DDIC Include which will carry persistent Custom Fields |
| 011 | Enter the DDIC Include which will carry transient Custom Fields |
| 012 | Enter the Extension Include View which you associate in your CDS View |
| 013 | Enter the Suffix which shall be used for the generated Custom Field names |
| 014 | Enter the Business Context which represents the extensible entity |
| 015 | DDIC Include &1 does not exist; check the name |
| 016 | CDS View &1 does not exist; check the name |
| 017 | VDM Core View &1 should have Annotation @VDM.viewType: #BASIC |
| 018 | VDM Core View &1 must have Annotation @EndUserText.label |
| 019 | Exactly one dummy field must exist in DDIC Include &1 |
| 020 | Dummy field name must differ in Persistence and Transient Fields Include |
| 021 | Business Context &1 has same Persistence Include but different Suffix &2 |
| 022 | Deviating quota information found for include &1 business context &2 |
| 023 | Extension Include View &1 must select from exactly one data source |
| 024 | DDIC Include &1 was not found in table &2 of Extension Include View &3 |
| 025 | Data Source &1 of Extension Include View &2 is not an existing DB Table |
| 026 | Enter the Name of your extensible CDS View |
| 027 | Register at least one Usage |
| 028 | Enter the Name of the Association Alias to the Extension Include View |
| 029 | Enter the Data Element whose labels are used to show a Role description |
| 030 | Business Context &1 has same Suffix but different Persistence Include &2 |
| 031 | Association Alias &1 must be unique within CDS View &2 |
| 032 | CDS View &1 should not be a Private View (Annotation @VDM.Private) |
| 033 | Business Context &1 does not exist; check the name |
| 034 | Data Element &1 does not exist; check the name |
| 035 | Enter the Name of your extensible OData Model |
| 036 | Enter the Name of your extensible OData Entity Type |
| 037 | Entity &1 must use same CDS View &2 for all Roles of Business Context &3 |
| 038 | Role Suffix &1 must differ for all Roles of Business Context &2 |
| 039 | Package &1: Labels of Element &2 will not be translated in all langauges |
| 040 | CDS View &1 has no association to View &2 |
| 041 | Association Alias &1 for View &2 does not exist in CDS View &3 |
| 042 | CDS View &1 not registered; check the name |
| 043 | Business Context data deviates from registered CDS View &1 |
| 044 | OData Model &1 does not exist; check the name |
| 045 | Entity Type &1 does not exist; check the name |
| 046 | Structure &1 of Entity &2 must contain Transient Fields Include &3 |
| 047 | Structure &1 of Entity &2 must contain Persistence Include &3 |
| 048 | Business Context &1 is not relevant for Structural Enhancement |
| 049 | Language Parameter &1 does not exist in CDS View &2; check the name |
| 050 | Same Dummy Field Name &1 in DDIC Include &2 of Business Context &3 found |
| 051 | Use VDM Basic View description or enter own Business Context description |
| 052 | Alias &1 not possible as Business Context &2 has no Draft Include View |
| 053 | Register at least one Relevance for your Business Context |
| 054 | Business Context not used for Structural Enhancement; clear Context Data |
| 055 | Include View &1 does not contain alias 'Persistence' |
| 056 | Use CDS View description or enter own description |
| 057 | Enter a description which will be shown in Key User Extension UI |
| 058 | Name clashes as ABAP view &1 and DDIC Include &2 are used in structure &3 |
| 059 | Entity Type &1 has SADL mapping to CDS View &2; Enter CDS View |
| 060 | Association &1 in CDS View &2 must have cardinality [0..1] or [1..1] |
| 061 | Package &1 of Business Context &2 not available for customers |
| 062 | Package &1 of CDS View registry &2 not available for customers |
| 063 | Model &1 is generated from CDS View; only CDS View needs to be registered |
| 064 | Entity Type &1 referenced in differently mapped Entity Sets |
| 065 | Analytical Query &1 must retrieve from underlying CDS View |
| 066 | Role Text Element &1 must differ for all Roles of Business Context &2 |
| 067 | Data Element &1 used to build label must not have a heading |
| 068 | Data Element &1 used to build label must not have a long text |
| 069 | Data Element &1 used to build label must not have a medium text |
| 070 | Data Element &1 used to build label must have a short text with length &2 |
| 071 | Incompatible change detected: Registry entry of &1 &2 &3 &4 was deleted |
| 072 | Incompatible change detected: '&1' changed from '&2' to '&3' |
| 073 | New Registry entry detected: '&1' |
| 074 | Comparison failed: '&1' |
| 075 | Same Role Suffix &1 with different Role Text &2 used in CDS registry &3 |
| 076 | Same Role Suffix &1 with different Role Text &2 used in OData registry &3 |
| 077 | For Roles you must use Business Context &1 more than once |
| 078 | For Roles you must use Entity &1 and Business Context &2 more than once |
| 079 | Package &1 of Data Element &2 not available for customers |
| 080 | Package &1 of CDS View &2 not available for customers |
| 081 | Package &1 of DDIC Structure &2 not available for customers |
| 082 | Package &1 of OData Model &2 not available for customers |
| 083 | Model must have one usage ("UI and Report" or "Form Template" or "API") |
| 084 | Registered Business Context &1 used in registry for CDS View &2 |
| 085 | Registered Business Context &1 used in registry for OData Model &2 |
| 086 | Registered Business Context &1 used in registry for BAdI &2 |
| 087 | Registered CDS View &1 used in registry for OData Model &2 |
| 088 | Derive description from Business Context or enter own description |
| 089 | Same Data Transfer &1 found in scenario step &2 and &3 |
| 090 | Registered Business Context &1 used in registry for Data Transfer &2 |
| 091 | Registered Data Transfer &1 used in registry for Business Scenario &2 |
| 092 | Package &1 of Data Transfer registry &2 not available for customers |
| 093 | Enter a Data Transfer |
| 094 | Data Transfer &1 not registered; check the name |
| 095 | Data Transfer &1 with source &2 and target &3 is not reachable |
| 096 | View Include &1 must select without filter (WHERE, GROUP_BY and HAVING) |
| 097 | Key field &1 of table &2 is not in projection list of Include View &3 |
| 098 | Analytical View &1 must use Annotation @ObjectModel |
| 099 | Dummy field name must be same in Persistence and Change Indicator Include |
| 100 | DDIC Include &1 cannot be reused for different extensibility purpose |
| 101 | Same DDIC Include &1 used in Business Context &2 |
| 102 | No Roles allowed for Business Contexts of Union |
| 103 | View Include &1 must differ for active and draft entity of Bus.Ctxt &2 |
| 104 | CDS View &1 must not use UNION operator |
| 105 | Transient Fields Include &1 was found in persistent table &2 |
| 106 | Chosen Source of Custom Field Data does not allow Ext. Include View info |
| 107 | Chosen Source of Custom Field Data does not allow underlying View info |
| 108 | Enter the Name of the underlying View |
| 109 | Alias &1 for underlying View &2 does not exist in CDS View &3 |
| 110 | SADL based consumption view &1 must retrieve from underlying CDS View |
| 111 | Query flag is not set, but CDS View &1 is an Analytical Query |
| 112 | Registered View &1 used in registry as underlying View for CDS View &2 |
| 113 | Delete all custom fields (e.g. &1) before executing incompatible changes |
| 114 | All Roles of Business Context &1 must use same underlying View |
| 115 | Group By flag must be set for CDS View with aggregation via Group By |
| 116 | No Roles allowed for CDS View which retrieves from underlying View |
| 117 | IsActiveEntity field is missing in projection list of CDS View &1 |
| 118 | Datasource Alias &1 for union case was not found in CDS View &2 |
| 119 | Condition Alias differs for active and draft entity of Bus.Ctxt &1 |
| 120 | On clause of Association &1 in CDS View &2 contains cast statement |
| 121 | On clause of Association &1 in CDS View &2 contains not only elements |
| 122 | On clause of Association &1 in CDS View &2 has not only 'equal' operator |
| 123 | On clause of Association &1 in CDS View &2 has unsupported statement |
| 124 | OData Entity &1 is not mapped to entered CDS View &2, but to CDS View &3 |
| 125 | Unknown View Type &1; Define Source of Extension Field Data |
| 126 | Chosen Source of Custom Field Data does not allow condition fields |
| 127 | Chosen Source of Custom Field Data does not allow Union Suffix |
| 128 | Enter Datasource Alias of Condition Field |
| 129 | Enter Name of Condition Field |
| 130 | Enter Condition Value |
| 131 | Name of Condition Field for Draft Union must always be: IsActiveEntity |
| 132 | Name clashes as union suffix &1 of underlying View &2 and &3 is same |
| 133 | Name clashes as Business Context &1 of underlying View &2 and &3 is same |
| 134 | For character like fields value &1 must written with apostroph (e.g. 'X') |
| 135 | For integer fields value &1 must written without apostroph (e.g. 12) |
| 136 | Context must contain at least one Union case |
| 137 | Draft Union for Business Context &1 must consist of two entries |
| 138 | Condition Value must be `'X'` for active and `''` for draft entity |
| 139 | Condition fields are required when Union Suffix is entered |
| 140 | Union Suffix is required when condition fields are entered |
| 141 | Union with Suffix &1 must at least consist of two entries |
| 142 | Condition field &1 is missing in projection list of CDS View &2 |
| 143 | Condition Alias &1 differs from Alias &2 of same Union Suffix &3 |
| 144 | Condition Field &1 differs from Field &2 of same Union Suffix &3 |
| 145 | Condition Value &1 must be unique within same Union Suffix &2 |
| 146 | Unsupported DDIC Type &1 of Condition Field &2 |
| 147 | Same Union Suffix &1 is used as Field Suffix in Business Context &2 |
| 148 | Same Union Suffix &1 used in CDS registry &2 |
| 149 | Same Suffix &1 is used as Union Suffix in CDS registry &2 |
| 150 | For Union case you must enter Union Suffix and Union Fields Include |
| 151 | Union Fields Include &1 identical to Include used in Business Context &2 |
| 152 | Dummy field &1 of Union Include &2 and Include &3 of Bus.Ctxt &4 is same |
| 153 | For invisible Usage no additional other Usage is possible |
| 154 | Redirect View flag is set, but CDS View &1 is not a Redirect View |
| 155 | Suffix &1 not valid; it must consist of exactly 3 alphanumeric characters |
| 156 | Group By flag must not be set for CDS View without Group By |
| 157 | Chosen View Type not allowed for CDS View with aggregation via Group By |
| 158 | Missing viewEnhancementCategory annotation [#PROJECTION_LIST, #GROUP_BY] |
| 159 | CDS View is used as Redirect View and must be set to invisible |
| 160 | Deviating text &1 for Entity &2 must be same for all Roles of Context &3 |
| 161 | Entity &1 and &2 have same deviating text &3 for Context &4 |
| 162 | Maintain deviating texts either for no or all Entities of Context &1 |
| 163 | For deviating texts Context &1 must be used for more than one Entity |
| 164 | Query flag is set, but CDS View &1 is not an Analytical Query |
| 165 | Reuse Extension Include View &1 for Business Context &2 and DB table &3 |
| 166 | CDS View &1 does not select from underlying View &2 |
| 167 | Incl. &1 reused for different implemented Entity &2 (&3) |
| 168 | Implementation Type &1 of Entity &2 differs from current implementation |
| 169 | Role Fields Include &1 identical to Include used in Business Context &2 |
| 170 | Dummy field &1 of Role Include &2 and Include &3 of Bus.Ctxt &4 is same |
| 171 | Enter the Role Fields Include which will carry transient Role text fields |
| 172 | Entity &1 must use same Role Include &2 for all Roles of Bus.Ctxt &3 |
| 173 | Union Include &1 missing in RDS Entity &2 datatype; Regenerate in SEGW |
| 174 | CDS View is not set to invisible but is RDS exposed in Model &1 |
| 175 | CDS View is RDS exposed in Model &1 which is not yet registered |
| 176 | CDS View is RDS exposed in Model &1 but not registered there |
| 177 | Redirect View flag is not set, but CDS View &1 is a Redirect View |
| 178 | Underlying View &1 used in Redirect View &2 and must be set to invisible |
| 179 | Assigned DDIC object &1 of Redirect View &2 is not an existing DB table |
| 180 | Include &1 is in DB table &2 but Context &3 not used in Redirect View &4 |
| 181 | Include &1 is in DB table &2 whose Redirect View &3 is not registered |
| 182 | Context &1 used in Redirect View &2, but DB table &3 has not Include &4 |
| 183 | Default Aggregation flag must be set according to current used annotation |
| 184 | Default Aggregation flag must not be set as not indicated by annotation |
| 185 | Performance: Condition Field &1 is not a constant but read from &2 |
| 186 | Analytical Query can only contain entries with same underlying CDS View |
| 187 | Transient Flds Incl. &1 not in RDS Entity &2 datatype; Regenerate in SEGW |
| 188 | Role Fields Include &1 not in RDS Entity &2 datatype; Regenerate in SEGW |
| 189 | Structure &1 of Entity &2 must contain Role Fields Include &3 |
| 190 | Structure &1 of Entity &2 must contain Union Fields Include &3 |
| 191 | Coding Block can only be enhanced for Customers; Clear other Percentages |
| 192 | Coding Block can not be mixed with other Context for same Union Suffix &1 |
| 193 | Enhancement category of DDIC Structure &1 must be at least: &2 |
| 194 | Performance: Please use client handling annotation @ClientHandling.type |
| 195 | Incompatible change detected: Insert of new branch for Union Suffix &1 |
| 196 | DDIC Object &1 is inconsistent and could not be read |
| 197 | Found &1 union branches in CDS view &2 but &3 branches were expected. |
| 198 | The order of union branches do not match. |
| 199 | Missing union all operator in union branch of subview &1. |
| 200 | Missing group by clause in union branch of subview &1. |
| 201 | Missing union branch &1 but found unkown branch &2. |
| 202 | Union all operator must not be set in union branch of subview &1. |
| 203 | Group by clause must not be set in union branch of subview &1. |
| 204 | Extension field data must be retrieved directly from underlying view. |
| 205 | Subview &1 must have a direct union suffix. |
| 206 | Alias &1 is used in more than one underlying view. |
| 207 | Getting OData Exposures for CDS View &1 failed (likely syntax error) |
| 208 | OData Model &1 could not be read (likely syntax error) |
| 209 | Former draft 1.0 extension association &1 not identical to active one &2 |
| 210 | Former draft 1.0 condition field alias &1 was not found in CDS View &2 |
| 211 | Target &1 of former draft 1.0 condition field alias &2 is not a CDS View |
| 212 | Consumption View &1 is used for OData exposure. Usage in RDS not allowed. |
| 213 | Transactional processing delegated. View must select from underlying view |
| 214 | Union Suffix &1 must be used exacly once in branch &2. Found &3 usages. |
| 215 | Group By flag is different in entry &1 and &2 of branch &3. |
| 216 | Union All flag is different in entry &1 and &2 of branch &3. |
| 217 | Underlying view is different in entry &1 and &2 of branch &3. |
| 218 | Position of direct union suffix &1 is different in branch &2 and &3. |
| 219 | Missing branch position &1 of branch &2 with direct union suffix &3. |
| 220 | Description fields not supported for CDS view &1 (due to group by clause) |
| 221 | Usage of DDIC suffix &1 in structure &2 for Include &3 cause DDIC errors |
| 222 | Define if your Registration supports Custom Fields and/or DSExtensions |
| 223 | Please do not forget to release &1 for 'C0' before delivery to customer. |
| 224 | Used Business Context &1 is not 'C0' released |
| 225 | Used Business Context &1 is not available in Cloud |
| 226 | Used Business Context &1 is not available in OnPremise |
| 227 | Please do not forget to release all entries before delivery to customer. |
| 228 | Entries can only be released, if main object is 'C0' released. |
| 229 | Used (underlying) CDS View &1 is not 'C0' released |
| 230 | Used (underlying) CDS View &1 is not available in Cloud |
| 231 | Used (underlying) CDS View &1 is not available in OnPremise |
| 232 | Used (underlying) CDS View entry &1 is not 'C0' released |
| 233 | Redirect CDS View entry &1 is not 'C0' released |
| 234 | Redirect CDS View &1 is not available in Cloud |
| 235 | Redirect CDS View &1 is not available in OnPremise |
| 236 | Union Suffix &1 of Redirect View &2 does not match persist. suffix |
| 237 | Direct Union Suffix &1 of Redirect View &2 does not match persist. suffix |
| 238 | Redirect View &1 must not use roles. |
| 239 | View &1 is below Redirect View &2 and must not use roles. |
| 240 | Used Data Transfer &1 is not 'C0' released |
| 241 | Used Data Transfer &1 is not available in Cloud |
| 242 | Used Data Transfer &1 is not available in OnPremise |
| 243 | The sum of all quota percentages must be 100 |
| 244 | Main object can only be released, if at least one entry is 'C0' released. |
| 245 | Register at least one Source of Field Data for Data Source Extensions |
| 246 | Alias and/or Name of Underlying View must be given |
| 247 | Source for Data Source Extensions not an Underlying View; clear data |
| 248 | SADL: Enter DDIC structure which will carry Data Source Extension Fields |
| 249 | Entity &1 with manual implementation type not supported |
| 250 | Enter the CDS View which is mapped to Entity &1 |
| 251 | Structure &1 of Entity &2 is not an existing DDIC structure |
| 252 | Used CDS View &1 does not support Data Source Extensions |
| 253 | Not all Branches for Position &1 are 'C0' released. |
| 254 | CDS View &1 must be 'C1' released for Key User Extensibility |
| 255 | Entity &1: SADL mapped view &2 is neither 'C1' released nor registered |
| 256 | Registered Business Context &1 used in registry for SAP GUI Context &2 |
| 257 | Delete all DSExtensions (e.g. &1) before executing incompatible changes |
| 258 | RDS: DDIC structure for Data Source Extensions unnecessary; clear field. |
| 259 | Entered DDIC structure &1 not unique; used also in Model &2 for Entity &3 |
| 260 | FLX class &1 is outdated; Regenerate via report CFD_CREATE_FLX_CLASS |
| 261 | No FLX class could be found in your OData class hierarchy for &1 |
| 262 | New Redirect Views currently not registerable; contact Extensibility team |
| 263 | DB table &1 of Incl. &2 has Redirect View &3; contact Extensibility team |
| 264 | Enter associated Business Object Type and Business Object Node Type |
| 266 | Transactional processing enabled. View must select from Ext. Include View |
| 267 | For Redirect View support of Data Source Extensions is not possible |
| 268 | For Analytical Query assocations as DSExtension source not allowed |
| 269 | Entered DDIC structure &1 must include structure &2 of Entity &3 |
| 270 | For Draft 2.0 Views support of Data Source Extensions is not possible |
| 271 | Business Object Type &1 does not exist; check the name |
| 272 | Business Object Node Type &1 does not exist for Business Object Type &2 |
| 273 | Business Object Type &1 and Node Type &2 can only be entered once |
| 274 | Migrated Draft 2.0 View &1 must keep association to Draft Include View &2 |
| 275 | Chosen View Type does not support to add fields automatically |
| 276 | Functionality "Add Field automatically" is not allowed for Roles |
| 277 | Functionality "Add Field automatically" is not allowed for Unions |
| 278 | Functionality "Add Field automatically" is not allowed for Redirect Views |
| 279 | View &1 used in Redirect View &2; "Add Field automatically" not allowed |
| 280 | For API Views ('C2' released) support of Data Source Ext. not allowed |
| 281 | Transactional processing enabled. Support of Data Source Ext. not allowed |
| 282 | Function Module &1 does not exist; check the name |
| 283 | Package &1 of Function Group &2 not available for customers |
| 284 | Enter the Name of the extensible Parameter |
| 285 | Enter the BAPI Parameter which represents the extension container |
| 286 | Enter the BAPI Structure which contains the Persistence Include |
| 287 | &1 Parameter &2 does not exist; check the name |
| 288 | Function Module &1 is registered as BAPI, but is not remote enabled |
| 289 | Function Module Parameter &1 and Context &2 not unique; Enter only once |
| 290 | Type of Parameter &1 does not contain Include &2 of Business Context &3 |
| 291 | Extension Structure &1 has no component with name KEY |
| 292 | Extension Structure &1 has no component with name DATA |
| 293 | Extension Structure &1 has no component with name DATAX |
| 294 | Include &1 of Context &2 not available in component DATA of structure &3 |
| 295 | Include &1 of Context &2 not available in component DATAX of structure &3 |
| 296 | Typing of BAPI Parameter &1 must be LIKE BAPIPAREX or TYPE BAPIPAREXTAB |
| 297 | Type &1 of Parameter &2 does not exist as structure or table type in DDIC |
| 298 | Suffix &1 must not start with Y or Z as this is reserved for partners |
| 299 | Entered structure &1 does not exist in DDIC |
| 300 | Enhancement category of Parameter type &1 must be at least: &2 |
| 301 | Enter the Type of the extensible Parameter &1 |
| 302 | For API Usage no additional other Usage is possible |
| 303 | Service Interface &1 does not exist |
| 304 | Package &1 of Service Interface &2 not available for customers |
| 305 | Enter the name of your extensible Service Interface |
| 306 | Enter the name of your Service Interface Operation |
| 307 | Enter the parameter type (input/output) of your operation |
| 308 | Enter the name of the Proxy Data Type |
| 309 | Operation &1 of Service Interface &2 does not exist |
| 310 | Operation &1 of Service Interface &2 has no Request |
| 311 | Operation &1 of Service Interface &2 has no Response |
| 312 | Proxy Data Type &1 does not exist |
| 313 | Data Type &1 is not contained in Response Message |
| 314 | Data Type &1 is not contained in Request Message |
| 315 | CDS View has annotation OData.Publish and is RDS exposed in &1 |
| 316 | Business Context not available in Cloud; clear Quota Data |
| 317 | IDoc Type &1 does not exist; check the name |
| 318 | Enter the IDoc Structure which contains the Persistence Include |
| 319 | Package &1 of IDoc Type &2 not available for customers |
| 320 | Function Module &1 must be set to invisible as not registered as BAPI |
| 321 | Business Context &1 not unique; Enter only once |
| 322 | Extension Structure Name &1 must not be greater than 27 characters |
| 323 | Entry with Context &1 for Operation &2 (&3) already exists |
| 324 | GTADIR access failed |
| 325 | GTADIR based persistence suffix uniqueness check could not be done |
| 326 | Extension Include View &1 must not be 'C1' released |
| 327 | Package &1 of Search Help &2 not available for customers |
| 328 | Enter CDS Value Help View and/or Leading View |
| 329 | Key fields of entered CDS View &1 not found |
| 330 | Association Target Name &1 must not be greater than 27 characters |
| 331 | DDIC search help &1 does not exist; check the name |
| 332 | Text Data Element &1 is only necessary for a field from a structured key |
| 333 | Component Identifier &1 only necessary for a field from a structured key |
| 334 | Enter Text Data Element for field &1 from a structured key |
| 335 | Enter Component Identifier for field &1 from a structured key |
| 336 | Enter typing Domain for field &1 of CDS View &2 |
| 337 | Package &1 of Domain &2 not available for customers |
| 338 | GUI Search Help &1 has no input parameter &2 |
| 339 | GUI Search Help &1 has no exporting parameter &2 |
| 340 | GUI Search Help parameter &1 not compatible to CDS View field &2 |
| 341 | Field &1 does not exist in CDS View &2 |
| 342 | Domain &1 does not exist; check the name |
| 343 | Same Component Identifier '&1' found for key field &2 and &3 |
| 344 | CDS View &1 must have Annotation @Search.searchable |
| 345 | Package &1: Description of &2 &3 will not be translated in all languages |
| 346 | BDEF &1: Mapping for &2 to Partner &3 has no CORRESPONDING addition |
| 347 | Semantic Object '&1' is not used as element annotation in any CDS view |
| 348 | Enter Semantic Object for Action '&1' |
| 349 | Same Component Text Data Element &1 found for key field &2 and &3 |
| 350 | ABAP dictionary data type &1 is not supported for CDS View field &2 |
| 351 | CDS View &1 is no RAP BO view (i.e. used in BDEF) |
| 352 | CDS View &1 is not registered for Business Context &2 |
| 353 | Enter an GUI Search Help exporting parameter for field &1 |
| 354 | T100 message &1 (&2) does not exist |
| 355 | Business Context NOTIFICATION_HEADER must not be used in a union |
| 356 | Business Context NOTIFICATION_HEADER must not be used in a scenario |
| 357 | T100 message &1 (&2) must not contain any placeholder |
| 358 | Package &1: T100 message &2 (&3) will not be translated in all languages |
| 359 | 'Associations of current view' set but no association set to available |
| 360 | The registered association &1 is not locally usable anymore |
| 361 | Draft table &1 must contain Include &2 of Business Context &3 |
| 362 | Chosen View Type not allowed for API Views ('C2' released) |
| 363 | CDS View &1 must not contain parameters |
| 364 | Reuse of data type &1 not allowed due to different 'C0' release state |
| 365 | Reuse of data type &1 not allowed due to different availability |
| 366 | Reuse of data Type &1 not consistent |
| 367 | Field &1: Define the UI.HIDDEN annotation directly in the help view |
| 368 | Reuse of data Type &1 not allowed |
| 369 | Registrations of reused operation message type &1 is different! |
| 370 | Domain &1 not compatible to CDS View field &2 |
| 371 | Association target &1 does not exists. |
| 372 | Availability of Data Transfer &1 and CDS View &2 is mutually exclusive |
| 373 | Value Help View &1 and Leading View &2 must have same number of keys |
| 374 | CDS Value Help View field &1 not compatible to Leading View field &2 |
| 375 | Foreign Key Association &1 in CDS View &2 has not only 'equal' operator |
| 376 | Foreign Key Association &1 in CDS View &2 contains not only elements |
| 377 | Foreign Key Association &1 in CDS View &2 contains 'OR' condition |
| 378 | Enter Value Help View Field which is mapped to Leading View Field &1 |
| 379 | Entered Value Help View Field &1 not unique; can be mapped only once |
| 380 | Foreign Key View &1 must have annotation '@ObjectModel.representativeKey' |
| 381 | CDS Value Help View and Leading View must not be identical |
| 382 | Cyclic Dependency detected where DSExtension may cause activation errors |
| 383 | &1&2&3&4 |
| 384 | Assocation &1 points to Target CDS View &2 but is registered with &3 |
| 385 | Target CDS View for Association &1 not given |
| 386 | Invalid foreign key association &1 for field &2 in view &3. |
| 387 | Invalid text association &1 for field &2 in view &3. |
| 388 | Invalid text tlement &1 for field &2 in view &3. |
| 389 | Foreign key target of field &1 must point to dimension view or null. |
| 390 | For OData Model &1 no Service could not be determined |
| 391 | CDS View &1 is 'deprecated' and must no longer be used |
| 392 | Association &1 is 'deprecated' and must no longer be used |
| 393 | Fields from not 'C1' released View &1 are not selectable for DSExtensions |
| 394 | &1 is an 'append' structure; Only 'normal' structures are allowed |
| 395 | To avoid clashes of custom fields, enter an Alias for Underlying View &1 |
| 396 | Registration name &1 is invalid (e.g. contains unallowed characters) |
| 397 | CDS View &1 has Source Type '&2' which is not supported by Extensibility |
| 398 | View &1 is client independent; could lead to syntax errors when extended |
| 399 | Registration of BAdI Defintion &1 is not 'C0' released |
| 400 | Enter mapped IRF Data Subject ID Field for View Field &1 |
| 401 | IRF Data Subject ID Field &1 entered without IRF Data Subject ID Type |
| 402 | IRF Data Subject ID Type &1 does not exist; check the name |
| 403 | IRF Data Subject ID Field &1 does not exist; check the name |
| 404 | Used IRF Data Subject ID Type &1 is not available in Cloud |
| 405 | Used IRF Data Subject ID Type &1 is not available in OnPremise |
| 406 | IRF Data Subject ID Field &1 not compatible to CDS View field &2 |
| 407 | IRF Data Subject ID Field &1 not unique; Enter only once |
| 408 | Dummy field name &1 must have length 30 to avoid usage of DDIC suffixes |
| 409 | IRF Data Mapping class entered without IRF Data Subject ID Type |
| 410 | Data Mapping Class &1 can't be instantiated publicly |
| 411 | Data Mapping Class &1 for Information Retrieval Framework does not exist |
| 412 | Data Mapping Class &1 must implement Interface 'IF_CFD_IRF_MAPPING' |
| 413 | DPP relevant Association Target is currently usable only within CBOs |
| 414 | Data Mapping Class &1 is not instantiatable (likely syntax error) |
| 415 | Data Mapping Class &1 is not instantiatable (CONSTRUCTOR with parameter) |
| 416 | Custom Field clash for association &1; enter Alias for Underlying View &2 |
| 417 | Dummy field name must be same in Transient Fields and Field Control Incl. |
| 418 | Field Control Include &1 was found in persistent table &2 |
| 419 | Choose either 'Denormalized' or 'Not Denormalized' for Text Handling |
| 420 | Bus.Ctxt &1 requires Field Control Incl. as View &2 has Denorm. Texts |
| 421 | Field Control Incl. &1 not in RDS Entity &2; Regenerate Model &3 in SEGW |
| 422 | Text Handling 'Denormalized' not supported for Views with Union |
| 423 | Registration of BAdI Defintion &1 is not available in Cloud |
| 424 | Leading View Field &1 misses Text Path '&2'; Go to registry in edit mode |
| 425 | Text Path '&1' of Value Help Field &2 differs from current path '&3' |
| 426 | Value Help Field &1 misses Text Path '&2'; Go to registry in edit mode |
| 427 | CDS View &1 used in Service Definition &2; Please classify text handling |
| 428 | Use 'Denormalized' Texts for Non-Projection View with Service Definition |
| 429 | Use 'Denormalized' Texts for Non-Projection View with 'OData.Publish' |
| 430 | 'Denormalized' Texts not allowed as &1 is used as underlying View in &2 |
| 431 | Data Source Extensions not allowed for Non-Projection View with BDEF &1 |
| 432 | 'Denormalized' Texts not allowed for Non-Projection View with BDEF &1 |
| 433 | Usage of Characteristics without Structural Enhancement not possible |
| 434 | Context used for Characteristics; enter valid Characteristics Persistence |
| 435 | Context not used for Characteristics; clear Characteristics Persistence |
| 437 | No support for 'C1' released Projection View when used in Service Binding |
| 438 | Projection View is 'C2' released which is not supported by Extensibility |
| 439 | No 'Denormalized' Texts: No UI Texts for CDS View with UI Service Binding |
| 440 | Text Path '&1' of Leading View Field &2 differs from current path '&3' |
| 441 | Text Field of Path '&1' for Value Help Field &2 is not character like |
| 442 | Text Field of Path '&1' for Leading View Field &2 is not character like |
| 443 | Chosen Source of Custom Field Data does not allow Characteristics info |
| 444 | Context &1: Enter CDS View to access generic Characteristics Persistence |
| 445 | Context &1: Enter CDS Alias to access generic Characteristics Persistence |
| 446 | Clear irrelevant Chacteristic Generic Persistence info for Context &1 |
| 447 | Chosen View Type does not allow Characteristics relevant Context &1 |
| 448 | Text Path '&1' not unique; used also for View Field Name &2 |
| 449 | Mandatory field &1 missing in characteristic persistence view view &2. |
| 450 | Mandatory Parameter P_KeyDate missing in original persistence view &1. |
| 451 | Text Handling 'Denormalized' not supported for Analytical Query |
| 452 | 'Denormalized' only allowed for Projection, API or VDM Consumption Views |
| 453 | Union suffix &1: CDS View &2 has different Text Handling than CDS View &3 |
| 454 | View Include &1 must select without filter (GROUPBY and HAVING). |
| 455 | View Include &1 must have parameter P_KeyDate. |
| 456 | Release of Registrations of CDS Projection Views is not allowed. |
| 457 | View &1 set to invisible but is 'C1' released; can be used in other apps |
| 458 | View &1: Parameter P_KeyDate must have data type DATS |
| 459 | View &1 Field &2 must have type &3. |
| 460 | Generic persistence view &1 must have only parameter P_KeyDate |
| 461 | Registered association &1 is not unique; used in data source &2 and &3 |
| 462 | Not draft enabled CDS view &1 is associated from draft view &2. |
| 463 | Chosen Source of Custom Field Data not allowed for Projection Views |
| 464 | BAdI for Hidden only allowed for CDS Views with UI Service Binding |
| 465 | Enter typing Domain for Text Field in path &1 of CDS View &2 |
| 466 | Text Domain &1 given without Text Field Path; clear Text Domain |
| 467 | Text Domain &1 for Field &2 not type compatible to Text Field in Path &3 |
| 468 | Assocation &1 has Data Source Alias '&2' but is registered with '&3' |
| 469 | Characteristic relevant CDS context must be marked as "Add Automatically" |
| 470 | Characteristic relevant CDS view must be marked as "Is Invisible". |
| 471 | Characteristic relevant CDS context and normal context must not be mixed. |
| 472 | View must be marked as Invisible because a context is always enabled. |
| 473 | Context &1 is always enabled, thus must be marked as add automatically. |
| 474 | Context &1 is always enabled. Union of different Bus. Ctxt not allowed. |
| 475 | Direct union and always enabled contexts are not allowed in combination. |
| 476 | Union context &1 is marked as always enabled but context &2 not. |
| 477 | Union context &1 has a different business context than context &2. |
| 478 | Business context &1 is always enabled but union context &2 not. |
| 479 | View needs to be invisble, because it`s (transitively) used by view &1. |
| 480 | View &1 must be annotated with @Analytics.dataCategory: #DIMENSION |
| 481 | Transactional proc. delegated: Underlying projection list not supported |
| 482 | Transactional proc. delegated: Usage of local associations not supported |
| 483 | Business context &1 is always enabled but CDS context &2 not. |
| 484 | Temporarily Extension Include View &1 can't be reused in Union Branch &2 |
| 485 | Registration of BAdI Defintion &1 does not exist; check the name |
| 486 | BAdI for Hidden not allowed if view is used in OData model (&1). |
| 487 | BAdI for Hidden not allowed if roles are used. |
| 488 | BAdI for Hidden not allowed for direct union. |
| 489 | Entity import parameter structure &1 does not exist. |
| 490 | Field &1 of BAdI Parameter is not in the view &2. |
| 491 | Enter Entity import parameter structure for BAdI Definition &1 |
| 492 | Enter BAdI Definition for Entity import parameter structure &1 |
| 493 | V2-View &1 need to register existing Alias &2 for underlying View &3 |
| 494 | View type &1 of &2 not supported for related RAP BO view in data transfer |
| 495 | View &1 cannot be used; all suffixes for business context &2 must equal |
| 496 | V2-View &1 need to register a Datasource Alias for Association &2 |
| 497 | Registration of BAdI Defintion &1 is not available in OnPremise |
| 498 | BAdI Definition &1 not registered for Scenario &2 |
| 499 | BAdI Registry &1 is missing Business Context &2 from CDS View &3 |
| 500 | Entity import parameter structure &1 must be 'C1' released |
| 501 | BAdI Definition &1 must have one filter |
| 502 | BAdI Definition &1 must have filter &2 of type '&3' |
| 503 | BAdI Interface &1 must have instance method &2 |
| 504 | Parameter &1 of BAdI Interface &2 must be '&3' |
| 505 | Parameter &1 of BAdI Interface &2 must have type &3 |
| 506 | BAdI Interface method &1 has not allowed parameter &2 |
| 507 | BAdI Interface method &1 must have parameters &2 and &3 |
| 508 | BAdI for Hidden not allowed for a Redirect View |
| 509 | BAdI for Hidden not allowed for an Analytical Query |
| 510 | Incl. &1 of Context &2 not allowed in BAdI structure &3 due to name clash |
| 511 | DataCategory 'Cube' is not set, but CDS View &1 is a Cube View |
| 512 | DataCategory 'Cube' is set, but CDS View &1 is not a Cube View |
| 513 | CDS View &1 is missing Business Context &2 from BAdI Registry &3 |
| 514 | Field &1 in CDS View and BAdI Parameter &2 is not type compatible |
| 515 | Enter BAdI Definition for Additional Data Class &1 |
| 516 | Enter Additional Data Class for BAdI parameter &1 |
| 517 | Additional Data Class &1 does not exist. |
| 518 | Field &1 of parameter IT_ENTITY_DATA is not type compatible with view &3 |
| 519 | Field &1 of parameter IT_ENTITY_DATA does not exist in View &3 |
| 520 | Line type of parameter RT_ADDITIONAL_DATA different from BADI parameter. |
| 521 | BADI &1 has no additional data parameter, so you cannot assign class &2 |
| 522 | BAdI additional data class &1 must have a static public method &2 |
| 523 | BAdI additional data class &1 method &2 must have required parameters |
| 524 | Registration Type 'Projection List' not supported for Projection Views |
| 525 | BAdI additional data class &1 method &2 exception &3 has wrong type. |
| 526 | Parameter &1 of BAdI interface &2 must be optional. |
| 527 | Data Source Ext. Usage must be invisible as View used as RDS in OData &1 |
| 528 | Data Source Ext. Usage is invisible, but View not used in OData Services |
| 529 | 'C1' View &1 registration for invisible Data Source Ext. Usage useless |
| 530 | BAdI import parameter structure &1 of View &2 not allowed to be reused |
| 531 | Usage of Business Context &1 relevant for Characteristics is not allowed |
| 532 | Characteristics Business Context can not be used for Logic Enhancements |
| 533 | On clause of Extension Association &1 lead to Syntax Error during usage |
| 534 | Read only is not allowed if view is used in OData model (&1). |
| 535 | 'Read only' only allowed for CDS Views with UI Service Binding |
| 536 | View &1 must have a core behavior definition to support mandatory. |
| 537 | View &1 must have a projection behavior definition to support read only. |
| 538 | Always enabled for Projection Views not allowed to avoid field collision |
| 539 | Chosen Source of Custom Field Data not allowed for V2-View &1 |
| 540 | Core BDEF for support of determinations and validations must be &1. |
| 541 | Projection BDEF for mandatory/ read only must be &1. |
| 542 | Identical include &1 within Persistence Incl. &2 lead to field collision |
| 543 | Identical include &1 of Persistence Incl. &2 found also for Bus.Ctxt &3 |
| 544 | View &1 not extensible as viewEnhancementCategory annotation set to #NONE |
| 545 | Invisible View &1 can not use BAdI for dynamically hiding custom fields |
| 546 | Invisible View &1 cannot enable "Read Only" for Key Users. |
| 547 | Core View &1 can not enable "Mandatory" for invisible Projection View &2 |
| 548 | BAdI for Hidden not for Custom Query (@ObjectModel.query.implementedBy) |
| 549 | For mandatory the underlying view &1 must support determinations and val. |
| 550 | Entity &1 must have an alias in the behavior definition &2. |
| 551 | Mandatory and read only requires a behavior definition. |
| 552 | BDEF &1 is not valid for entity &2. |
| 553 | Alias &1 is not valid for entity &2. |
| 554 | 'Mandatory' or 'Read only' is not possible for Views based on Unions |
| 555 | BDEF &1 must be extensible with validations on save to use 'Mandatory' |
| 556 | 'Mandatory'/'Read only': Entity &1 of BDEF &2 must be extensible |
| 557 | BDEF &1 must be extensible to use 'Read only' |
| 558 | Mandatory is not allowed if view is used in OData model &1. |
| 559 | Mandatory not allowed. Projection view &1 has ui and a2x service binding. |
| 560 | Conversion Exit &1 of CDS View field &2 not allowed in S/4 HANA |
| 561 | Entity &1: Draft mode must not change if mandatory is supported. |
| 562 | DSExtension exists with unallowed ConversionExit; No Serv.Binding allowed |
| 563 | Select * in View &1 leads to unallowed ConvExit; No Serv.Binding allowed |
| 564 | View &1 has the enterprise search annotation. Basic search not supported. |
| 565 | For Non-Projection View with BDEF &1 'Denormalized' texts not possible |
| 566 | Draft BDEF &1 for entity &2 must have 'extensible' PREPARE action |