USMD2 - Stammdaten: UI Modellierung
The following messages are stored in message class USMD2: Stammdaten: UI Modellierung.
It is part of development package USMD2_MAIN in software component CA-MDG-AF. This development package consists of objects that can be grouped under "Main objects of generic MDG UIs".
It is part of development package USMD2_MAIN in software component CA-MDG-AF. This development package consists of objects that can be grouped under "Main objects of generic MDG UIs".
Message Nr ▲ | Message Text |
|---|---|
| 001 | Select UI element type 'View' for UI element &1 (entity type &2) |
| 002 | Entity type &2, UI element &1: Higher-level UI element &3 does not exist |
| 003 | Assign a higher-level elem. with table el.type to UI el. &1 (ent.type &2) |
| 004 | UI elem. &1 (ent.type &2) is a view; a higher UI elem. cannot be assigned |
| 005 | UI elem. &1, entity type &2: Specify a different higher-level UI element |
| 006 | You cannot assign a Web Dynpro component to UI element &1 (ent.type &2) |
| 007 | Entity type &2 cannot be changed via change request |
| 008 | UI elem.&1, ent.tp.&2: No attributes can be assigned with UI elem.type &3 |
| 009 | Specify an attribute for UI element &1 with entity type &2 |
| 010 | Entity type &2, UI element &1: Preceding UI element &3 does not exist |
| 011 | Create a UI elem. with UI elem. &1 (ent.type &2) as higher-level UI elem. |
| 012 | Entity type &2, UI elem. &1: Interface view with name &3 does not exist |
| 013 | UI element &3, entity type &2: Select a UI element type for table rows |
| 014 | Use only alphanumeric characters for name &1 |
| 015 | Assign a Web Dynpro component to UI element &1 (entity type &2) |
| 016 | UI elem. &1, ent.type &2: Enter a Web Dynpro component and interface view |
| 017 | Specify the preceding UI element for UI element &1 (entity type &2) |
| 018 | UI element &1, ent.type &2: Process subdialog "Hierarchy Relationships" |
| 019 | UI el. &1, ent.type &2: Setting in "Hierarchy Relationships" is invalid |
| 020 | Enter a UI element |
| 021 | Enter the data model for UI model &1 and save your entry |
| 022 | Entity type &2 does not exist in associated data model &1 |
| 023 | Attribute &3 cannot be used for UI element &1 (entity type &2) |
| 024 | Ent.type &2, UI element &1: Attribute &3 has invalid values for checkbox |
| 025 | Entity type &2, UI element &1: Check the attribute &3 |
| 026 | Entity type &2, UI element &1: Web Dynpro component &3 cannot be used |
| 027 | Specified attribute cannot be used for UI element &1 (entity type &2) |
| 028 | Specify the edition type for change request type &1 |
| 029 | Create a UI elem. with UI elem. &1 (ent.type &2) as higher-level UI elem. |
| 030 | Entity type &2, UI element &1: Select an attribute with data type CHAR(1) |
| 031 | Entity type &2, UI element &1: Select an attribute with data type STRING |
| 032 | UI element &1: Entity type &2 does not permit hierarchy relationships |
| 033 | Entity type &2, UI element &1: Deselect the checkbox Hier.Vers.Enterable |
| 034 | Change request type &1: Add entity type &3 to edition type &2 first |
| 035 | Assign at least one entity type to change request type &1 |
| 036 | Save user &1 first |
| 037 | Save role &1 first |
| 038 | Higher-level UI element for &1 and &3 with ent.type &2 must be the same |
| 039 | Ent.type &2, UI elem.&1: UI element and preceding UI element are the same |
| 040 | UI element &1: UI element type "attachments" not possible for ent.type &2 |
| 041 | Change of edition type not possible; chg. request type &1 already in use |
| 042 | Change request type &1 already used in change request &2 |
| 043 | Deletion not possible; change request type &1 already in use |
| 044 | Error in BAdI USMD_UI_EVENT: &1&2&3&4 |
| 045 | Attribute &3 cannot be used for UI element &1 (entity type &2) |
| 046 | Specified attribute cannot be used for UI element &1 (entity type &2) |
| 047 | Inconsistencies between UI element &2 and UI element &1 |
| 048 | Entity type &2, UI element &1: Inconsistent table definition |
| 049 | Entity type &2, UI element &1: Table column with key field is missing |
| 050 | Specify the change request type |
| 051 | Entity type &2, UI element &1: Checkbox 'Hier.Vers.Enterable' deselected |
| 052 | Entity type &2, UI element &1: Preceding UI element is invalid |
| 053 | Ent. type &2, UI element &1: UI elem. type and Sets setting do not agree |
| 054 | Entity type &2, UI element &1: Enter a valid higher-level UI element |
| 055 | UI element &1: UI element type 'Sets' not possible for entity type &2 |
| 056 | Supplement the type of change request &1 with the entity type &2 |
| 057 | Specified attribute cannot be used for UI element &1 (entity type &2) |
| 058 | Select the entity type |
| 059 | Select the UI element type |
| 060 | Ent.type &2, UI el. &1: UI element and higher-lvl UI element are the same |
| 061 | Ent.type &2, UI el. &1: Specify a higher-lvl UI element with el.type View |
| 062 | EntType &2, UI el. &1: Higher-lvl UI elem. requires encasing UI elem.type |
| 063 | Entity type &2, UI element &1: Web Dynpro component &4 already used |
| 064 | Entity type &2: UI element type of UI element &1 cannot be used |
| 065 | Change request type &3: Entity type &2 not contained in data model &1 |
| 066 | Error in BAdI USMD_UI_EVENT2: &1&2&3&4 |
| 067 | Error in BAdI USMD_PRINT_FORM: &1&2&3&4 |
| 068 | Change request type &1: Specify either a scenario or a UI configuration |
| 069 | Chg.request type &3: UI configuration &1 does not exist for data model &2 |
| 070 | Chg.request type &1: 'Scenario', 'UI Config', 'Optional' are initialized |
| 071 | Change request type &1: Assigned workflow &2 does not exist |
| 072 | Change request type &1: No workflow assigned |
| 073 | Error in BAdI USMD_ISR_FORM: &1&2&3&4 |
| 074 | Change request type &3: Scenario &1 not possible for entity &2 |
| 075 | Change request types for edition type &2 cannot be processed |
| 076 | Standard form USMD_EDITION_CREQUEST will not be saved |
| 077 | There are more than &1 values; narrow down the selection |
| 078 | Change request type &1: Specify either an edition type or a data model |
| 079 | Change req. type &1: Data model &3 not suitable for business activity &2 |
| 080 | UI configuration &1 cannot be used |
| 081 | Error in BAdI USMD_CREQUEST: &1&2&3&4 |
| 082 | Error in BAdI USMD_SEARCH: &1&2&3&4 |
| 083 | Change request type &1: Specify a main entity type |
| 084 | Change request type &1: Main entity type &2 does not exist |
| 085 | Change request type &1: Entity type &2 is dependent on an edition |
| 086 | Data model cannot be changed; change request type &1 already in use |
| 087 | Access class &1 does not implement the interface "IF_USMD_SEARCH_DATA" |
| 088 | Access class &1 does not exist |
| 089 | Change request type &1: Business activity &2 does not exist |
| 090 | Change request type &1: 'Optional' is set for entity type &2 |
| 091 | Specify a business activity |
| 092 | Change request type &1: Specify only one business activity |
| 093 | Restrict the selection |
| 094 | Invalid date range |
| 095 | Edition &1 marked for release |
| 096 | Edition &1 is now in process |
| 097 | Edition &1 cannot be used |
| 098 | Changing of master data is no longer possible in edition &1 |
| 099 | Error in BAdI USMD_UI_SERVICES: &1&2&3&4 |
| 100 | No open or completed change requests found for the selected objects |
| 101 | Specify a standard data model |
| 102 | Data model &1 either does not exist or has an inconsistent definition |
| 103 | UI model &1 does not exist or cannot be used with data model &2 |
| 104 | No valid standard data model defined for your user master record |
| 105 | Change request &1 created |
| 106 | Enter a value for field &1 |
| 107 | Edition &1 already exists and cannot be changed |
| 108 | Edition &1 saved |
| 109 | Edition &1 deleted |
| 110 | Value &1 of field &2 already exists |
| 111 | Deletion not possible; edition &1 already in use |
| 112 | Draft for change request &1 has been deleted |
| 113 | Draft for Change Request &1 has been saved |
| 114 | Select a change request first |
| 115 | The edition you entered cannot be used for this type of change request |
| 116 | You have not yet uploaded a file |
| 117 | Specify a link |
| 118 | No objects specified for entity type &1 |
| 119 | No authorization for &1 of UI model &2 |
| 120 | Edition &1 cannot be used with data model &3 |
| 121 | Select the objects to be deleted first |
| 122 | A maximum of 999 rows can be inserted at one time |
| 123 | Entity type &2 cannot be processed in edition &1 |
| 124 | Mass change executed |
| 125 | Enter an explanation for your changes |
| 126 | You can only go to the next step |
| 127 | Entity &2 of type &1 already exists in change request &3 |
| 128 | Specify at least one attribute to be changed |
| 129 | Selection for mass change does not contain any values |
| 130 | Select one object to continue |
| 131 | You have approved change request &1 |
| 132 | Mass change not executed; assign a change request first |
| 133 | You are currently not the processor of change request &1 |
| 134 | Entity &2 of type &1 already exists in change request &3 |
| 135 | Changes were saved for change request &1 |
| 136 | Changes not saved; assign a change request first |
| 137 | No change request is assigned to you |
| 138 | Unable to switch to display mode |
| 139 | There are no changes to be saved |
| 140 | You have canceled the mass change |
| 141 | Edition &1 cannot be used; it is already released |
| 142 | Changing of master data is no longer possible in edition &1 |
| 143 | Entity &2 of entity type &1 has been deleted |
| 144 | Data not deleted; assign a change request first |
| 145 | The status of change request &3 does not allow for object changes |
| 146 | Edition &1 is already released |
| 147 | Specify the objects to be changed; required in change request type &1 |
| 148 | Edition &1 cannot be released yet; change requests open |
| 149 | No errors found |
| 150 | Edition &1 released |
| 151 | Select exactly one row |
| 152 | You have rejected change request &1 |
| 153 | You have agreed to the changes in change request &1 |
| 154 | You have rejected the changes in change request &1 |
| 155 | Enter values either for all higher-level fields or for none of them |
| 156 | Edition &1 cannot be released; no change requests assigned |
| 157 | Select a row to be deleted first |
| 158 | You have canceled the processing of change request &1 |
| 159 | You have finalized the processing of change request &1 |
| 160 | Object list of change request &1 cannot be processed |
| 161 | Object list for entity type &1: Row &2 has no value for &3 |
| 162 | Entities in draft of change request &1 cannot be loaded |
| 163 | Object list already contains entity &2 of type &1 |
| 164 | No data selected; change your selection criteria |
| 165 | Change request &1 is completed and can no longer be modified |
| 166 | Specify the entity type of the higher-level node or the predecessor node |
| 167 | Edition &1 is invalid as of &2 |
| 168 | Validity of existing edition restricted: Edition &1 now invalid as of &2 |
| 169 | Change request &1 is not assigned to you |
| 170 | The status of change request &1 does not allow for object changes |
| 171 | Change request &3 is not assigned to you |
| 172 | Cannot process the hierarchy relationship |
| 173 | Edition &1 cannot be valid as of &2; it is invalid as of &3 |
| 174 | Edition &1 cannot be created; same validity period as edition &2 |
| 175 | Attachment &1 can be processed only by user &2 |
| 176 | No change request specified for processing |
| 177 | You have forwarded change request &1 for revision |
| 178 | You have forwarded change request &1 |
| 179 | Entity &2 of entity type &1 already changed; must stay in change request |
| 180 | Enter a reason for your action on this change request |
| 181 | First select a row |
| 182 | Cannot delete entity &2 of entity type &1 |
| 183 | Hierarchy names can not be removed; choose Delete |
| 184 | Only the entities of entity type &1 are passed to the mass change |
| 185 | No valid UI model is defined in your user master record |
| 186 | No hierarchy version specified; cannot process the hierarchy relationship |
| 187 | The hierarchy entry cannot be moved up or down |
| 188 | The hierarchy entry cannot be ranked lower |
| 189 | The hierarchy entry cannot be ranked higher |
| 190 | Hierarchy names cannot be moved in the hierarchy |
| 191 | You have not cut or copied a hierarchy entry |
| 192 | The set that is shown contains data for multiple entity types |
| 193 | Entity &2 of type &1 is not yet assigned to a change request |
| 194 | UI model &1 does not exist |
| 195 | Unable to check the data; create and/or assign a change request first |
| 196 | Entity type &1 has different values in the selected rows |
| 197 | Select a node to be expanded |
| 198 | Select one or more search results in the hit list |
| 199 | UI element &1 already exists; select a different ID |
| 200 | Action not possible; different change requests for source and target |
| 201 | Specify a data model for UI model &1 |
| 202 | User &2 is locking UI model &1 |
| 203 | Action not possible; lower-level nodes in different change requests |
| 204 | Ambiguous change request for entity &2 of entity type &1 |
| 205 | Object list for entity type &1, row &2: Your change has been undone |
| 206 | The hierarchy entry cannot be inserted at the top level |
| 207 | Cannot delete entity &2 (entity type &1); entity is a hierarchy node |
| 208 | Cannot delete entity &2 (entity type &1); contained in another hierarchy |
| 209 | UI model &1 deleted |
| 210 | Validation for change request &1 started asynchronously |
| 211 | Cannot delete entity &2 (entity type &1); still contained in hierarchy |
| 212 | Cannot process the hierarchy relationship |
| 213 | Validation for edition &1 started asynchronously |
| 214 | Change request &1 can no longer be edited |
| 215 | Mass change of entity type &1 not possible; &1 has no attributes |
| 216 | Enter a single value for field &1 |
| 217 | Save change request &3 first |
| 218 | Entity &1 of entity type &2 does not exist in change request &3 |
| 219 | Select at least one entity of entity type &1 |
| 220 | Preview not possible: no Web user interface defined for entity type &1 |
| 221 | Sets contain entity type &1, which no longer exists |
| 222 | Action not possible; displaying updated data |
| 223 | Edition &1 of edition type &2 is already being processed |
| 224 | Drafts of change requests cannot be processed with this application |
| 225 | Preview not possible; no visible view exists for entity type &1 |
| 226 | The status of change request &3 does not allow for object changes |
| 227 | Change request &3 is not assigned to you |
| 228 | Only these protocols are permitted: http://, https://, ftp:// and file:// |
| 229 | Print preview not possible: BAdI USMD_UI_EVENT not implemented |
| 230 | Values of hierarchy name (&2) and higher-level node (&1) are inconsistent |
| 231 | Mass change cannot be performed for these objects |
| 232 | UI configuration &1 does not exist or is not possible for data model &2 |
| 233 | Edition &1 does not exist or is not possible for data model &2 |
| 234 | Entity type &1 does not exist or is not possible for data model &2 |
| 235 | Chg. request type &1 does not exist or is not possible for data model &2 |
| 236 | For field &1, choose the display type 'Text Representation' or 'Link' |
| 237 | Your user master record does not contain a valid UI configuration |
| 238 | Entity type &2 connot be processed in UI configuration &1 |
| 239 | Print preview not possible; Customizing settings missing for form &1 |
| 240 | Print preview not possible; error while creating Adobe PDF form |
| 241 | Data model &1: Role-dependent personalization data is being used |
| 242 | Specify a different hierarchy version |
| 243 | Change request &1 is not intended for processing single objects |
| 244 | Specify a value for the entity type or the edition |
| 245 | No hits found |
| 246 | Drag and drop to this position not possible; Use cut and paste |
| 247 | Specify the full template |
| 248 | Entity &2 cannot be processed in edition &3 |
| 249 | No value specified in row &1 for &2 |
| 250 | Specified selections are not suitable for edition &2 |
| 251 | UI configuration USMD_ENTITY_VALUE2 cannot be used |
| 252 | Entity type &2: Lead column &1 does not exist |
| 253 | In row &1, the To value &3 is less than the From value &2 |
| 254 | Ranges cannot be deleted; choose 'Remove' |
| 255 | To value &2 of range is less than From value &1 |
| 256 | Enter a From value and/or To value for the range |
| 257 | Ranges must be end nodes in the hierarchy |
| 258 | Cannot delete entity &2 (entity type &1); still contained in hierarchy |
| 259 | Entity type &1 cannot be used |
| 260 | Data model &1: 'Attachments' not possible for entity type &2 |
| 261 | Data model &1: 'Sets' not possible for entity type &2 |
| 262 | Data model &1: 'Hierarchy Relationship' not possible for entity type &2 |
| 263 | Data model &1: 'Text Translation' not possible for entity type &2 |
| 264 | Specify a data model for UI configuration &1 |
| 265 | Configuration USMD_ENTITY_VALUE2 cannot be processed |
| 266 | UIBB with configuration &3 cannot be used in UI configuration &4 |
| 267 | UIBB &1 cannot be used within entity type &3 |
| 268 | Identical list component for dependent entity type &1 used more than once |
| 269 | List component with config. &3 cannot be used in UI configuration &4 |
| 270 | UI configuration of Web Dynpro component configuration &1 is unknown |
| 271 | The log is displayed in a new window |
| 272 | You cannot use this application with SAP enhancement package 5 |
| 273 | Period &1 is invalid; valid period values are &2 to &3 |
| 274 | Key fields of entity type &1 have not yet been specified |
| 275 | Displaying updated data |
| 276 | UI configuration &1 has an error and needs to be adjusted |
| 277 | Validation not yet executed |
| 278 | Implementation of BAdI USMD_UI_EVENT2 has an error |
| 279 | No change request is assigned to you for processing entity type &1 |
| 280 | Change request type &1 cannot be used to process entity type &2 |
| 281 | Enter a description for the change request |
| 282 | Cannot determine a UI configuration |
| 283 | Search parameters for &1 (data model &2) saved under &4 for &3 |
| 284 | Search parameters &4 for &1 (data model &2) deleted for &3 |
| 285 | UIBB &1 cannot be used for the contained entity type &2 |
| 286 | No key mapping exists for entity &2 of entity type &1 |
| 287 | Entries &1 and &2 from &3 cannot be selected simultaneously |
| 288 | Do not enter a value for field &1; key is assigned internally |
| 289 | Also specify an edition for &2 for the selection "&1" |
| 290 | Entities of type &1 cannot be deleted; choose 'Remove' |
| 291 | No replication log exists for entity &2 of the type &1 |
| 292 | No replication log exists for change request &1 |
| 293 | BAdI implementation USMD_SEARCH hides all result columns |
| 294 | You have started the activation for change request &1 |
| 295 | No duplicates exist for entity &2 of entity type &1 |
| 296 | Do not enter a temporary key in field &1 |
| 297 | Hierarchy relationship cannot be displayed |
| 298 | You have no authorization for displaying all entities of entity type &1 |
| 299 | Implementation of BAdI USMD_UI_EVENT2 has an error |
| 300 | Entity type &1: You specified rows with identical keys |
| 301 | Maximum number of results must be at least 1 |
| 302 | Due date lies in the past |
| 303 | Changes are distributed across several change requests |
| 304 | Entity type &2 cannot be processed with change request &3 |
| 305 | There is no data to be checked |
| 306 | Entity &2 of type &1 already exists in change request &3 |
| 307 | Select a row first (lead selection) |
| 308 | Hierarchy names can be inserted only at the top level |
| 309 | Data has been reread and the display refreshed |
| 310 | Validation of change request produced errors |
| 311 | Validation of change request produced no errors |
| 312 | No objects of type &1 exist |
| 313 | Specify values either for all fields of entity type &1 or for no field |
| 314 | You cannot use this application with enhancement package 5 |
| 315 | Enter the data and time together |
| 316 | Search results limited to most recent &1 change documents |
| 317 | Language &1 already exists |
| 318 | Unable to instantiate the key mapping API |
| 319 | Specify search attributes for updating search patterns |
| 320 | Only the first 500 of &1 messages are displayed |
| 321 | Change request &1 has been resubmitted |
| 322 | Cannot determine a UI configuration |
| 323 | Cannot determine a UI configuration |
| 324 | Type of change request must be filled |
| 325 | Type &1 of change request &2 does not exist in the system |
| 326 | Cannot determine a UI configuration |
| 327 | Change request &1 resubmitted after rejection/revision |
| 328 | Change request &1 finalized; refresh the list |
| 329 | Entries for 'Fuzzy Search' are contradictory; loss of information |
| 330 | Entries for 'Search Active Data Only' contradictory; loss of information |
| 331 | You have no authorization for mass changes |
| 332 | More data records that match your selection criteria are available |
| 333 | Combination of OTC &1 and action &2 is not unique |
| 334 | Select an edition for the edition-dependent type &1 |
| 335 | Action &1 is invalid |
| 336 | UI application &1 is invalid |
| 337 | UI configuration &1 is invalid |
| 338 | No structure for field properties defined for entity &1 |
| 339 | Cannot determine attributes according to configuration settings |
| 340 | No change request type exists for business activity &1 |
| 341 | Change request data could not be checked |
| 342 | Data could not be checked for technical reasons |
| 343 | Processing of parallel change requests is not supported in this UI |
| 344 | Create a note and specify a reason for withdrawing the change request |
| 345 | Changing the parallel flag can cause conflicts for change request type &1 |
| 346 | CR type &1 is assigned to an edition type and cannot be used for PCR |
| 347 | Object &1 is currently in a parallel change request,and cannot be deleted |
| 348 | Search for edition-dependent data not possible; use different search |
| 349 | Change of data model may lead to corrupt change request data |
| 350 | Changes of edition type may lead to corrupt change request data |
| 351 | Workflow changes only affect new change requests |
| 352 | Deletion of entity type &1 may cause unexpected behaviour |
| 353 | Entity type list contains empty line; delete empty line |
| 354 | Create a change request first |
| 355 | Select exactly one change request for this action |
| 356 | Change request type &1: Specify either an edition type or set PCR flag |
| 357 | Enhancing scope for change request type &1 may lead to corrupt data |
| 358 | Reducing scope for change request type &2 may lead to corrupt data |
| 359 | Parallel processing not enabled for CR type &1; navigation not possible |
| 360 | Business process does not exist |
| 361 | CR type &3 scope: entity type &1 is not dependent of entity type &2 |
| 362 | Changes will be saved in change request &1 |
| 363 | Collective processing enabled for change request type &1 |
| 364 | CR type &1: enter at least one entity type which is in scope |
| 365 | &1 &2 already assigned to parallel change request &3 |
| 366 | &1 &2 already assigned to change request &3 with edition &4 |
| 367 | Cannot delete changed data from parallel change request |
| 368 | Select edition 1 (&3: &1) to be older than edition 2 (&3: &2) |
| 369 | Enter a value for field 'Country/Region' and choose ENTER |
| 370 | Printing not possible; no print form defined in Customizing |
| 371 | Search for Entities cannot be used, as new edition concept is activated |
| 372 | UI configuration &1 cannot be used |
| 373 | Replication timing inconsistent with edition; choose the other option |
| 374 | Deletion cannot be undone |
| 375 | Edition &1 does not exist |
| 376 | Changes were saved in corresponding change requests |
| 377 | Changed edition &1 cannot be saved; same validity period as edition &2 |
| 378 | |
| 379 | In the Notes tab page, explain your action &1 |
| 380 | In the Notes tab page, explain why you disagree with the change request |
| 381 | In the Notes tab page, explain why the change request requires revision |
| 382 | Action not possible; nodes locked in different change requests |
| 383 | Action not possible, target must be different with selected nodes |
| 384 | Select a row with pending change request |
| 385 | Unsaved changes exist. Display might be incomplete |
| 386 | Target must not be in sub tree of the selected nodes |
| 387 | Source UI: Application &1, Configuration &2 |
| 388 | Target UI: Application &1, Configuration &2 |
| 389 | Change request type &1: UI application &2 is invalid |
| 390 | Change request type &1: UI configuration &2 is invalid |
| 391 | Change request step-dependent navigation |
| 392 | Change request type-dependent navigation |
| 393 | Object type code/action-dependent navigation |
| 394 | Fix navigation target: USMD_CREQUEST_PROCESS |
| 395 | Parameter: &1 Value: &2 |
| 396 | Class: cl_usmd_navigation_assist Method: get_application_data |
| 397 | Change request step-dependent navigation was skipped |
| 398 | No navigation target UI identified |
| 399 | Fix navigation target: &1 |
| 400 | Check completed |
| 401 | Attachment search cannot include archived change requests |