R11 - Business Partner und BDT
The following messages are stored in message class R11: Business Partner und BDT.
It is part of development package S_BUPA_GENERAL in software component BC-SRV-BP. This development package consists of objects that can be grouped under "SAP Business Partner: Basic Components".
It is part of development package S_BUPA_GENERAL in software component BC-SRV-BP. This development package consists of objects that can be grouped under "SAP Business Partner: Basic Components".
Message Nr ▲ | Message Text |
|---|---|
| 001 | * Organization: from 600: archiving |
| 002 | You are not authorized to display this data; see long text |
| 003 | Search results contain no blocked business partners. See long text. |
| 004 | Business function BUPA_ILM_BF is not activated; see long text |
| 005 | You are not authorized to block/unblock data; see long text |
| 006 | You cannot change business partner &1; see long text |
| 007 | All BP with the criteria you specified are already locked |
| 008 | There are no locked BP that meet the criteria specified |
| 009 | Bus. partner &1 linked with one-time customer &2 cannot be locked |
| 010 | Bus. partner &1 linked with one-time supplier &2 and cannot be locked |
| 011 | Gender &1 does not exist |
| 012 | No address-dependent attributes available for business partner &. |
| 013 | No address-dependent attribute with address no. &2 available for BP &1 |
| 046 | No partners found for stated selection |
| 047 | Do not enter parameters &1 and &2 at the same time |
| 050 | Deletion of partner not possible; memory is inconsistent |
| 090 | Details in &1 &2 &3 &4 not compatible |
| 098 | No appropriate external grouping exists for partner number &1 |
| 099 | Industry system &1 not reserved for data exchange |
| 100 | No display variant exists |
| 101 | For customers only |
| 102 | Maximum search time exceeded, hit list incomplete |
| 103 | Enter other search criteria |
| 104 | No higher-level table was defined for table & |
| 105 | Specify the root of the tree |
| 106 | Enter one root table only |
| 107 | A table cannot be its own higher-level table |
| 108 | Selection limited to & hits |
| 109 | No variants exist |
| 110 | Error in & & when calling & & |
| 111 | No search possible |
| 112 | You cannot change the business partner grouping |
| 113 | Address number & does not exist |
| 114 | External business partner number is blank |
| 115 | Internal standard grouping &1 must not be deleted |
| 116 | External standard grouping &1 must not be deleted |
| 117 | No internal standard grouping exists |
| 118 | No external standard grouping exists |
| 119 | Business partner GUID is blank |
| 120 | Business partner &1 does not have GUID &2 |
| 121 | Business partner &1 does not have external number &2 |
| 122 | Business partner with GUID &1 does not have external number &2 |
| 123 | Specify at least one number for the business partner |
| 124 | Business partner with GUID &1 does not exist |
| 125 | Business partner &1 has not been assigned to any role |
| 126 | BP category &1 does not fit the data in category &2 |
| 127 | Contact person relationship already exists between partners &1 and &2 |
| 128 | Contact person relationship does not exist between partners &1 and &2 |
| 129 | Specify at least one number for the address |
| 130 | An address with GUID &2 does not exist for business partner &1 |
| 131 | Address &2 for business partner &1 does not have GUID &3 |
| 132 | Address &2 for business partner &1 does not have external number &3 |
| 133 | The address with GUID &2 for business partner &1 does not have ext.no.&3 |
| 134 | No address with external number &2 exists for business partner &1 |
| 135 | Specify an address number or address GUID |
| 136 | Address already exists for contact person relationship between &1 and &2 |
| 137 | Country/region key &1 does not match ISO code &2. |
| 138 | Language key &1 does not match ISO code &2 |
| 139 | There is no address with internal number &2 for partner &1 |
| 140 | No address usage found for business partner &1 and address type &2 |
| 141 | No address usages found |
| 142 | Business partner &1: No address usage for address &2, address type &3 |
| 143 | No bank details found |
| 144 | No credit card details found |
| 145 | Specify at least one number for a set of bank details |
| 146 | No contact person relationship exists for partner &1 |
| 147 | Business partner &1 does not (yet) have a GUID |
| 148 | No business partner found |
| 149 | Enter valid selection parameters |
| 150 | Employee relationship does not exist between partners &1 and &2 |
| 151 | Employee relationship between partners &1 and &2 already exists |
| 152 | Partner &1's bank details with ID &2 do not have external ID &3 |
| 153 | No BP role exists for partner &1 |
| 154 | No category &1 relationship exists for partner &2 |
| 155 | Passed partner number &1 and found partner number &2 do not match |
| 156 | Passed partner GUID &1 and found partner GUID &2 do not match |
| 157 | Passed ext. BP no. &1 and found ext. BP no. &2 do not match |
| 158 | Business partner with GUID &1 does not exist |
| 159 | The passed partner numbers are inconsistent |
| 160 | No matching business partner found |
| 161 | Employee relationship between &1 and &2 does not exist |
| 162 | Contact person relationship between partners &1 and &2 already exists |
| 163 | Contact person relationship between partners &1 and &2 does not exist |
| 164 | Contact person relationship in the period from &1 to &2 is invalid |
| 165 | Relationship between partner &1 and &2 does not exist |
| 166 | Relationship Between Partner &1 and &2 Already Exists |
| 167 | Error-Tolerant Search for Business Partners is Not Possible |
| 168 | This folder is still being used in filter view &1 |
| 169 | No address exists for transaction &2 in business partner &1 |
| 170 | You Must Not Delete View Because It is Still Being Used In Transactions |
| 171 | No Industry Data Found |
| 172 | Specify an industry system |
| 173 | Specify an industry |
| 174 | No Industry Data Found for Business Partner &1 |
| 175 | For Partner &1, Industry &2 Already Created With Industry Key &3 |
| 176 | No ID Numbers Found |
| 177 | No ID Number Found For Business Partner &1 |
| 178 | ID number &2 with ID type &3 already created for partner &1 |
| 179 | Industry &1 Not Defined for Industry Key System &2 |
| 180 | No Business Partner Matching the Search Criteria Found |
| 181 | The Where-Used List Does Not Have Any Reference |
| 182 | Partner &1: Industry &2 does not exist for industry system &3 |
| 183 | Text for transaction &1 does not exist in language &2 |
| 184 | Business Partner May Not be Changed Because of Status & |
| 185 | Business partner &1 has status &2 |
| 186 | Number &1 already exists for ID type &2 |
| 187 | Industry &1 already exists for industry system &2 |
| 188 | Maximum of 5 industries permitted for ERP industry system |
| 189 | The standard industry is not unique for industry system &1 |
| 190 | Enter ID Type |
| 191 | Enter ID Number |
| 192 | Enter a Valid ID Type |
| 193 | Entries Included in Request &1 |
| 194 | Identification types do not exist |
| 195 | Identification type &1 is not defined for persons |
| 196 | Identificaton type &1 is not defined for organizations |
| 197 | Identification type &1 is not defined for groups |
| 198 | No Industries Exist |
| 199 | No Industries Exist for Industry System & |
| 200 | Validity End is Before Registration Date |
| 201 | Business partner & does not have any relationships |
| 202 | There is no address &3 for the relationship between partner &1 and &2 |
| 203 | Industry &1 Does Not Exist in Industry System &2 |
| 204 | There Must be At Least One Basic Node |
| 205 | Nothing May Refer to Itself |
| 206 | Parameter &1 has not been specified for name format check |
| 207 | Industry &1 may not be deleted because it is referred to |
| 208 | Industries &1 may not be deleted because they are referred to |
| 209 | Industry &1 for industry number system &2 already deleted |
| 210 | Shareholder relationship already exists between partners &1 and &2 |
| 211 | Shareholder relationship invalid in period from &1 to &2 |
| 212 | Shareholder relationship between partners &1 and &2 does not exist |
| 213 | Internet user for user &1 may not be intialized |
| 214 | Enter the Internet user |
| 215 | Number &1 already deleted for identification type &2 |
| 216 | Internet user &1 already assigned to user &2 |
| 217 | Internet user &1 already assigned to partner &2 |
| 218 | Password invalid |
| 219 | Password and repeat password must be identical |
| 220 | User group &1 does not exist |
| 221 | User role &1 already assigned |
| 222 | Roles of reference user &1 were added |
| 223 | User &1 of user &2 blocked |
| 224 | You are not authorized to maintain user data |
| 225 | Select one role only |
| 226 | You are not authorized to maintain user &1 |
| 227 | User &2 does not have authorization for assignment of user group &1 |
| 228 | Relationship in period from &1 to &2 not valid |
| 229 | No business partner exists for user &1 |
| 230 | No business partnerr exists for Internet user &1 |
| 231 | New planning date must be greater than current date |
| 232 | Old or new planning date invalid |
| 233 | New planning date must be different to the old planning date |
| 234 | There are conflicts with other plans for object &1 (&2) |
| 235 | No plans found for date &1 for object &2 (&3) |
| 236 | Postponement of planning for object &2 (&1) already marked |
| 237 | In the case of &1, no data for partner &2 found in memory |
| 238 | No BP relationship exists for differentiation type value &1 |
| 239 | Address type &1 may not be deleted |
| 240 | Address &1 already indicated as standard address |
| 241 | The move date occurs in the past |
| 242 | No move target address exists |
| 243 | Internal error when calling operation module &; a check table is missing |
| 244 | Error in validity periods of addresses |
| 245 | Error for validity periods of address usages |
| 246 | Conversion error; the date is invalid |
| 247 | No bank details exist for change |
| 248 | Change not possible; ID &1 would occur more than once in the change chain |
| 249 | Cannot move; address &1 would then occur more than once in the move chain |
| 250 | No address-independent communication data exists for business partner &1 |
| 251 | Communication data applied |
| 252 | Transfer of communication data not possible |
| 253 | Standard industry system was changed |
| 254 | The target ID does not exist in the bank details change |
| 255 | No usages correspond to the selection criteria |
| 256 | All applications selected are inactive |
| 257 | No APIs exist for the selected active applications |
| 258 | There is no active distribution application (table TB048) |
| 259 | Maintenance of time-dependent data not permitted,as schedules still exist |
| 260 | No partners found for this selection |
| 261 | Only &1 sections may be assigned! |
| 262 | Only &1 views may be assigned! |
| 263 | You may not enter any numbers in the dialog for ID type &1 |
| 264 | You may not delete any numbers in the dialog for ID type &1 |
| 265 | Validity period of the target bank details is not sufficient |
| 266 | Validity period not permitted; bank details are change target of ID &1 |
| 267 | Validity period of the target move address is not sufficient |
| 268 | Validity period not permitted; address is move target of other addresses |
| 269 | Selected address already assigned to address type &1 |
| 270 | Telephone number &1 &2 ambiguous; identified using CONSNUMBER |
| 271 | Telephone number &1 &2 already exists |
| 272 | Fax number &1 &2 ambiguous; identified using CONSNUMBER |
| 273 | Fax number &1 &2 already exists |
| 274 | Teletex number &1 &2 ambiguous; identified using CONSNUMBER |
| 275 | Teletex number &1 &2 already exists |
| 276 | Telex number &1 &2 ambiguous; identified using CONSNUMBER |
| 277 | Teletex number &1 &2 already exists |
| 278 | SMTP &1 &2 ambiguous; identified using CONSNUMBER |
| 279 | SMTP &1 already exists |
| 280 | Remote mail &1 &2 ambiguous; identified using CONSNUMBER |
| 281 | Remote mail address &1 &2 already exists |
| 282 | X.400 &1 &2 &3 ambiguous; identified using CONSNUMBER |
| 283 | X.400 &1 &2 &3 already exists |
| 284 | RFC &1 ambiguous; identified using CONSNUMBER |
| 285 | RFC &1 already exists |
| 286 | Printer &1 ambiguous; identified using CONSNUMBER |
| 287 | Printer &1 already exists |
| 288 | SSF address &1 ambiguous; identified using CONSNUMBER |
| 289 | SSF address &1 already exists |
| 290 | URI address &1 ambiguous; identified using CONSNUMBER |
| 291 | URI address &1 already exists |
| 292 | Pager address &1 &2 ambiguous; identified using CONSNUMBER |
| 293 | Pager address &1 &2 already exists |
| 294 | Gaps not permitted in the validity periods of the business partner data |
| 295 | No validity gaps allowed |
| 296 | Reference period insufficient |
| 297 | No overlapping of validities allowed |
| 300 | No update is defined for BP role &1 |
| 301 | Business partner &1 is a duplicate |
| 302 | Business partner &1 may not be deleted |
| 303 | Fatal error during attempted deletion of &1 |
| 304 | Transaction may be started only in development client |
| 305 | &1 &2 deleted |
| 306 | No dates that deviated from current date allowed |
| 330 | Identification type &1, identification number &2 do not exist in BP &3 |
| 331 | Identification type &1, idenfication number &2 already deleted. |
| 332 | Bank details &1 of business partner &2 already deleted. |
| 333 | Address &1 of business partner &2 already deleted |
| 334 | BP &1 does not exist in role &2 diff. type &3 diff. type value &4 |
| 335 | Errors occurred during call of function module &1 |
| 336 | This language may be maintained only for persons |
| 337 | Not possible to search with wildcards without specifying a country/region |
| 338 | There is no standard usage for address usage &1 |
| 339 | Cannot search for fax numbers without specifying a country/region. |
| 340 | Result of duplicate check incomplete |
| 341 | Select exactly one business partner |
| 342 | Select exactly one relationship |
| 343 | The &1 &2 &3 &4 is a duplicate |
| 345 | The function ( & ) is not supported in this case |
| 346 | Time dependency of table &1 cannot be deactivated |
| 347 | Settings for development &1 not maintained for object &2 |
| 348 | Activation settings not yet maintained |
| 349 | Data set &1 for BP &2 maintained time-dependently,despite inact.time dep. |
| 350 | Multiple validity periods can be selected for BP &1 |
| 351 | Data of BP &1 from table &2 does not match the table's time constraint |
| 352 | Valid-to and valid-from date necessary in order to change the validity |
| 353 | Initial creation of a BP with restricted validity not allowed |
| 354 | Creation of new validity period not possible |
| 355 | Choose a new validity period |
| 356 | Creation of a validity period possible only with error-free data |
| 357 | Deletion of currently displayed validity period not possible |
| 358 | Validity change for currently displayed period not allowed |
| 359 | Scheduling no longer possible using the field VALDT |
| 360 | No central data for partner &1 in the required database activity &2 |
| 361 | Address-dependent attribute for address &1 was already deleted. |
| 400 | *** BDT *** |
| 401 | Enter a value for field &1 |
| 402 | No values can be passed in field &1 |
| 403 | Application object &1: No BAPI field > dynpro field assignment exists |
| 404 | Generation of dynpro containers is locked by user &1 |
| 405 | No selection made |
| 406 | No change documents selected for your field selection |
| 407 | Use '+' for generic entries |
| 408 | Generic indicators for dynpro field and DB field only simultaneous |
| 409 | Generic indicators for DI field and DB field only simultaneous |
| 410 | No standard industry stated for standard industry number system &1 |
| 411 | Application Object &1: Application &2 not active. |
| 412 | DB field->dynpro field assignments missing for fields of field group &1 |
| 413 | Fields of field group &1 can be found on a different dynpro |
| 414 | Errors in DB field->dynpro field assignments for fields of field group &1 |
| 415 | Multi-assignment of field group &1 by DB field -> dynpro field assignment |
| 416 | No assignment exists for the passed screen sequence category &1 |
| 417 | Additional field groupings using criterion &1 exist |
| 418 | Field grouping for field group &1 for &2 is: &3. |
| 419 | No authorizatio for &1 of field group &2. |
| 420 | No screen number stated for view &1. |
| 421 | No program name stated for view &1. |
| 422 | No screen number and program name stated for view &1. |
| 423 | BDT object &1 in language &2 not available. |
| 424 | BDT object &1 not available. |
| 425 | Application object &1 in client &2 not available |
| 426 | Language key &1 not available in system |
| 427 | No application objects available for client &1 |
| 428 | Client &1 does not exist |
| 429 | No application object texts available for client &1 |
| 430 | Application object &1: Results table of screen sequences is empty |
| 431 | Application object &1: Results table of screens is empty |
| 432 | Application object &1: Results table of screen texts is empty |
| 433 | Application object &1: Results table of sections is empty |
| 434 | Application object &1: Results table of sections texts is empty. |
| 435 | Application object &1: Results table of views is empty |
| 436 | Application object &1: Results table of view texts is empty |
| 437 | Application object &1: Results table of additional checks is empty |
| 438 | Applic.obj.&1:Results table of screen sequence screen assignment is empty |
| 439 | Application object &1:Results table of screen section assignment is empty |
| 440 | Application object &1: Results table of screen sequences is empty. |
| 441 | Application object &1: Results table of screen sequence texts is empty |
| 442 | Applicatn object &1:Results table of screen sequence categories is empty. |
| 443 | Application object &1: Results table of screen sequence texts is empty |
| 444 | Appl.obj.&1:Results table of scrn sequ.categ. scrn sequ assgnmnt is empty |
| 445 | Applicat. object &1:Results table of field group field assgnment is empty |
| 446 | Applic. object &1: Results table of view field group assignment is empty |
| 447 | Application object &1: Results table of field groups is empty |
| 448 | Application object &1: Results table of field group texts is empty |
| 449 | Application object &1: Results table of VCT usages is empty |
| 450 | Application object &1: Results table of object parts is empty |
| 451 | Application object &1: Results table of object part texts is empty |
| 452 | Appl. object &1: Results table of object part applic. assignment is empty |
| 453 | Appl. object &1: Results table of object part view assignment is empty |
| 454 | Application object &1: Results table of object part grouping is empty |
| 455 | Application object &1: Results table of obj. part grouping texts is empty |
| 456 | Appl. obj.&1: Results table obj.part grp. - obj.part assignment is empty |
| 457 | Appl. obj.&1: Results table obj.part group -scrn sequ. assignmnt is empty |
| 458 | Application object &1: Results table of data sets is empty |
| 459 | Application object &1: Results table of data set texts is empty |
| 460 | Application obj. &1: Results table of obj.part data set assgnmnt is empty |
| 461 | Applic. object &1: Results table of obj.part-scrn sequ. assignmt is empty |
| 462 | Application object &1: Results table of BDT applications is empty |
| 463 | Application object &1: Results table of BDT - application texts is empty |
| 464 | Application object &1: Results table of BDT activities is empty |
| 465 | Application object &1: Results table of BDT activity texts is empty |
| 466 | Application object &1: Results table of BDT table is empty |
| 467 | Events for application object &1 and BDT object &2 do not exist |
| 468 | Multiple application objects passed |
| 469 | Configured screen sequences defined for screen sequence category &1 |
| 470 | Error in assignment of screen sequence using table TBZ6 |
| 471 | External partner number &1 is ambiguous |
| 472 | Print format &1 does not exist |
| 474 | Higher-node role &1 may not be hidden |
| 499 | No texts exist |
| 501 | Too many places after decimal comma |
| 510 | No data passed |
| 511 | Passed table is too big |
| 512 | View &1 must be manually assigned to section &2 |
| 517 | Client &1 application object &2 screen &3: section &4: too many views |
| 518 | Client &1 appl. object &2 screen &3: too many sections |
| 519 | Client &1 appl. object &2 screen &3: Could not create dynpro container |
| 520 | Client &1 appl. object &2 screen &3: Error generating dynpro container |
| 525 | * BP roles: Customizing & dialog |
| 526 | BP role category &1 is still in use and cannot be deleted |
| 527 | BP view &1 is still in use and cannot be deleted |
| 528 | Role &1 is assigned to exclusion group &2 and must be updated |
| 529 | Role not updated if a role category is not assigned |
| 530 | Enter a BP role |
| 531 | BP role &1 not permitted |
| 532 | Transition from BP role &1 to BP role &2 already exists |
| 533 | Do not enter a disallowed transition |
| 534 | BP role &1 already assigned to BP role exclusion group &2 |
| 535 | BP role exclusion group must contain at least two BP roles |
| 536 | Only update-relevant BP roles can be assigned |
| 537 | &1 &2 in BP role &3 is &4 |
| 538 | BP role category &1 not assigned to a transaction |
| 539 | BP role category &1 not assigned to transaction &2 |
| 540 | BP roles not assigned to relationship category &1 |
| 541 | Relationship category &1 with assigned BP role &2 does not exist |
| 542 | BP role &1 not assigned to any of the relevant BP role categories |
| 543 | Only BP role grouping categories may be entered for SAP transactions |
| 544 | Only BP role categories may be entered for SAP transactions |
| 545 | Cannot simultaneously enter BP role grouping categ. and BP role grouping |
| 546 | Cannot simultaneously enter BP role category and BP role |
| 547 | BP role grouping category &1 not assigned to BP role grouping &2 |
| 548 | No BP role grouping category or BP role grouping passed |
| 549 | Field grouping does not exist for BP role &1 |
| 550 | BP role &1 may not be deleted |
| 551 | No BP role exists |
| 552 | Text for BP role &1 does not exist in language &2 |
| 553 | No BP roles exist with BP role category &1 |
| 554 | No BP role categories exist |
| 555 | BP role category &1 does not exist |
| 556 | Text for BP role category &1 does not exist in language &2 |
| 557 | BP role &1 is not update-relevant |
| 558 | Transition to identical BP role &1 not possible |
| 559 | BP role grouping &1 does not exist |
| 560 | No BP role grouping exists with BP role grouping category &1 |
| 561 | Text for BP role grouping &1 does not exist in language &2 |
| 562 | Text for BP role grouping category &1 does not exist in language &2 |
| 563 | BP role grouping category &1 does not exist |
| 564 | No BP role groupings exist |
| 565 | No BP role grouping categories exist |
| 566 | No assignment exists for BP role grouping &1 |
| 567 | BP role &1 is not assigned to a BP role grouping |
| 568 | No BP role exclusion groups exist |
| 569 | BP role exclusion group &1 does not exist |
| 570 | Text for BP role exclusion group &1 does not exist in language &2 |
| 571 | No assignment exists for BP role exclusion group &1 |
| 572 | BP role &1 not assigned to a BP role exclusion group |
| 573 | No permitted transitions exist from BP role &1 |
| 574 | No permitted transitions exist to BP role &1 |
| 575 | No standard assignment defined for BP role category &1 |
| 576 | Item number &1 already assigned for BP role &2 |
| 577 | Select a BP role |
| 578 | No assignment of BP role grouping categories to BP roles exists |
| 579 | No valid BP roles exist for partner &2 at time &1 |
| 580 | Conflict between BP role grouping &1 and BP role exclusion group &2 |
| 581 | A valid BP view is not assigned to BP role &1 |
| 582 | Move or change date 01.01.0001 is not allowed |
| 583 | No assignments of BP role exclusion group to BP roles exist |
| 584 | At least one initial role must be defined |
| 585 | Do not define BP role &1 as an initial role |
| 586 | Assignment of BP role &1 not permitted because of disallowed transition |
| 588 | Validity of BP role &1 restricted to date &2 |
| 589 | BP role &1 deleted (&2 is valid BP role) |
| 590 | BP role &1 not created as subsequent role for &2 with start date &3 |
| 591 | No BP roles exist with BP view &1 |
| 592 | No BP role categories exist with differentiation type &1 |
| 593 | BP roles of the BP role category &1 are mutually exclusive |
| 594 | BP roles of the BP role category &1 already exist for partner &2 |
| 595 | No changes were made to BP role &1 for partner &2 |
| 596 | BP role &1 already assigned to status number &2 |
| 597 | Table &1 converted successfully |
| 598 | &1 records inserted in table &2 |
| 599 | &1 records changed in table &2 |
| 600 | Archive indicator not set for business partner &1 |
| 601 | Select filter and/or restrict BP selection |
| 602 | Not all time-dependent data has already been distributed for partner &1 |
| 603 | Setting a system status without deletion/archiving check not allowed |
| 604 | New archive file could not be created |
| 605 | Error when reading address usage |
| 650 | * BP Roles: BAPIs/ APIs |
| 651 | "All BP roles" indicator allowed only in connection with BP role category |
| 652 | Do not pass a BP role category or a BP role |
| 653 | BP role &1 already exists for partner &2 |
| 654 | Differentiation according to BP role &1 is not intended |
| 655 | No BP roles exist for partner &1 |
| 656 | BP role category &1 not assigned to BP role &2 |
| 657 | BP role &1 does not exist for partner &2 |
| 658 | Cannot delete BP role &1 |
| 659 | Deletion of all BP roles only without entering differentiation type value |
| 660 | BP role &1 w. differentiation type value &3 does not exist for partner &2 |
| 661 | BP role &1 w. differentiation type value &3 already exists for partner &2 |
| 662 | No BP role was passed |
| 663 | No BP roles with BP role category &2 exist for partner &1 |
| 664 | BP role grouping category &1 already assigned to BP role grouping &2 |
| 665 | BP role &1 still in use; change to validity not allowed |
| 666 | BP role &1 still in use; deletion not allowed |
| 667 | Change type &1 of the BP role is not intended |
| 700 | Object &1 flagged for transport |
| 777 | No Authorization To Delete Partner without Authorization group &1 |
| 800 | Enter selections |
| 801 | Key field &1 may not be changed in the case of an update / change |
| 802 | Table &2 must have the same number of lines as &1 |
| 850 | There is no standard address |
| 851 | Validity start is after validity end |
| 852 | Address for address usage does not exist |
| 853 | Validity period for the address usage not compatible with address |
| 854 | A standard address is not always specified |
| 855 | Standard usage has not been maintained for all required points in time |
| 856 | Card cannot be created; SAP Digital Payments add-on not active |
| 857 | Configuration of SAP Digital Payments add-on is incomplete |
| 858 | It is not possible to create cards that support digital payment |