Id | Title |
---|---|
USMD6499 | * Messages 500 - 899 reserved for eSOA |
USMD6500 | * Messages 500 - 899 reserved for SOA |
USMD6501 | Service processing &1 for pkg. &2, step &3, target system &4 started |
USMD6502 | Data selection for package &1, step &2 successfully finished |
USMD6503 | Field mapping for package &1, step &2 successfully finished |
USMD6504 | BAdI calls for package &1, step &2 started |
USMD6505 | Proxy calls for package &1, step &2, service class &3 started |
USMD6506 | Message for chart of accounts &1 sent to outbound proxy |
USMD6507 | Error in call of outbound proxy for service &1, chart of accounts &2 |
USMD6508 | Initialized status entries created for package &1, step &2, system &3 |
USMD6509 | Error during SMT mapping &1, mapping step &2, target structure &3 |
USMD6510 | &1 messages sent for package &2, step &3, system &4 |
USMD6511 | Error during initial status update for package &1, step &2, system &3 |
USMD6512 | Error during update of status tables due to competing access |
USMD6513 | No status entry found for message with GUID &1 |
USMD6514 | Status entry of message &1 has incorrect target system (&2 instead of &3) |
USMD6515 | Status entry of message &1 has invalid reference GUID (&2 instead of &3) |
USMD6516 | Status entry of message &1 has incorrect status (&2 instead of &3) |
USMD6517 | Entry of a From-edition (&1) not possible when distribution complete |
USMD6518 | Period information cannot be derived from editions &1 and &2 |
USMD6519 | Error while creating instance of SMT mapping &1, mapping step &2 |
USMD6520 | Error in status update of messages for edition &1, package &2, system &3 |
USMD6521 | Error in update of aggregate status f. edtn &1, pkg &2, sys &3, step &4 |
USMD6522 | Customizing error: No SMT mapping created for data model &1 |
USMD6523 | A maximum of 10 characters is allowed for accounts (entity type &1) |
USMD6524 | Bulk message sent to outbound proxy |
USMD6525 | Error while calling outbound proxy for service &1 |
USMD6526 | Bulk message contains &1 individual messages |
USMD6527 | Processing terminated (error in data selection for package &1, step &2) |
USMD6528 | BAdI call(s) for package &1, step &2, chart of accounts &3 started |
USMD6529 | BAdI call(s) for package &1, step &2, fin. reporting structure &3 started |
USMD6530 | Error while reading message &1 (edition &2, package &3, system &4) |
USMD6531 | &1 &2 &3 &4 |
USMD6532 | &1 &2 &3 |
USMD6533 | &1 &2 |
USMD6534 | Message for financial reporting structure &1 sent to outbound proxy |
USMD6535 | Error during call to outbound proxy for service &1, fin.rep.structure &2 |
USMD6536 | Error during status update for edition &2, package &2, system &3, step &4 |
USMD6537 | Blank bulk message in package &1, step &2; processing terminated |
USMD6538 | No customer BAdI implemented for service processing &1 |
USMD6539 | No data found for package &1, step &2; processing &3 terminated |
USMD6540 | Service processing &1 started |
USMD6541 | Inbound mapping for service &1 started |
USMD6542 | Inbound mapping for service &1 ended |
USMD6543 | Error in inbound mapping for service &1 |
USMD6544 | Status update for service &1, message &2 started |
USMD6545 | Error in status update for message &1 (edition &2, package &3, system &4) |
USMD6546 | BAdI call for service processing &1 started (if BAdI implemented) |
USMD6547 | No SMT mapping found for entity type &1 in package &2, step &3 |
USMD6548 | Updating status of distrib. monitor (edtn &1, pkg. &2, sys. &3, step &4) |
USMD6549 | Mandatory attribute "Category_Code" is blank for &1 |
USMD6550 | No hierarchy-bearing entity type found for distribution of package &1 |
USMD6551 | &1 |
USMD6552 | Starting distribution step &1 of master data package &2 (edtn &3, sys.&4) |
USMD6553 | No authorization for distribution of master data package &1 to system &2 |
USMD6554 | Consolidation area is still blank in replication message for &1 |
USMD6555 | Status successfully updated for message &1 (edtn &2, package &3, sys. &4) |
USMD6556 | Delta distribution not possible for entity type &1 |
USMD6557 | Updating status of distribution monitor (edt.&1, app.&2, sys.&3, step &4) |
USMD6558 | Error while updating aggregate status f. edt.&1, app.&2, sys.&3, step &4 |
USMD6559 | Error while updating status of notification f. edition &1, app.&2, sys.&3 |
USMD6560 | Errors occured during the distribution; check the appropriate log |
USMD6561 | No application has been created in Customizing |
USMD6562 | This edition contains no data to be distributed |
USMD6563 | Master data package &1 does not exist in Customizing |
USMD6564 | No distribution step assigned to master data package &1 |
USMD6565 | No target system assigned to master data package &1 in Customizing |
USMD6566 | Master data package &1 has no distribution step &2 in Customizing |
USMD6567 | Application &1 does not exist |
USMD6568 | Application &2 does not have a distribution step &1 |
USMD6569 | Outbound implementation &1 does not exist |
USMD6570 | Business system &1 does not exist |
USMD6571 | Field name &1 no longer exists in active data model &2 |
USMD6572 | No object type code assigned to entity type &1 of data model &2 |
USMD6573 | Change request &1 does not contain objects to be replicated |
USMD6574 | Change request &1, OTC &2: Error &3 while generating structure |
USMD6575 | Change request &1 cannot be directly replicated |
USMD6576 | You are not authorized to distribute all master data packages |
USMD6S000 | Error &1 &2 &3 &4 |
USMD6S001 | Selection condition &3 for data model &1/entity type &2 does not exist |
USMD6S002 | Selection condition &3 for data model &1/entity type &2 already exists |
USMD6S003 | Hierarchy node &1: &2 does not exist in hierarchy &3 |
USMD7000 | Specify a data model |
USMD7001 | Specify a package |
USMD7002 | Package &1 does not exist |
USMD7003 | Specify a valid Customizing request |
USMD7004 | Change request &1 does not exist |
USMD7005 | Enter a name for the transport request |
USMD7006 | Target group &1 does not exist |
USMD7007 | Validation not yet started |
USMD7008 | Validation not yet ended |
USMD7009 | Validation results are no longer valid |
USMD7010 | Error in BAdI USMD_RULE_SERVICE: &1 &2 &3 &4 |
USMD7011 | Data object &1 in trigger function &2 not suitable to data model |
USMD7012 | Data object &1 does not adhere to naming convention |
USMD7013 | Master data entry of entity type &1 changed from &2 to &3 |
USMD7014 | Key was modified during derivation for entity type &1 |
USMD7015 | &1 in trigger function &2 is not a valid predefined data object |
USMD7016 | Entity type &1 is being used in validation |
USMD7017 | Attribute &1 of entity type &2 is being used in validation |