MDG_BS_BP_DATAREPL - Messages for Business Partner Data Replication
The following messages are stored in message class MDG_BS_BP_DATAREPL: Messages for Business Partner Data Replication.
It is part of development package MDG_BS_BP_DATAREPLICATION in software component CA-MDG-APP-BP. This development package consists of objects that can be grouped under "MDG: Business Partner - Data Replication".
It is part of development package MDG_BS_BP_DATAREPLICATION in software component CA-MDG-APP-BP. This development package consists of objects that can be grouped under "MDG: Business Partner - Data Replication".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Supplier &1 seems to be duplicate of supplier &2 (similarity &3%) |
| 001 | Only 1 subclass of &1 is supported |
| 002 | No relationship data is provided |
| 003 | Business partner replication is not finished yet |
| 004 | ID of the local system cannot be determined |
| 005 | ID of the remote system is missing |
| 006 | ID of the local object is missing |
| 007 | ID of the remote object is missing |
| 008 | Key mapping cannot be updated |
| 009 | ID and UUID of the business partner are missing |
| 010 | Error during writing to staging area; processing not possible |
| 011 | &1 additional business partner(s) added to BP replication |
| 012 | &1 relationship(s) excluded from BP replication |
| 013 | Receiver system does not support time dependency for table &1 |
| 014 | No valid record found for current time slot |
| 015 | No unused business partner number could be determined |
| 016 | Business partner with internal ID &1 created for business partner &2 |
| 017 | Business partner &1 created |
| 018 | Business partner &1 updated |
| 019 | Business partner &1 locked in staging (ID &2); processing not possible |
| 020 | A fatal error occurred when processing partner &1 |
| 021 | Fatal error when processing the relationship &3 &4 of &1 and &2 |
| 022 | BP with temporary ID &1 saved for BP &2 in change request &3 |
| 023 | BP with internal ID &1 saved for BP &2 in change request &3 |
| 024 | Business partner &1 saved in change request &2 |
| 025 | Business partners of type &1 cannot be uploaded into staging |
| 026 | Error occurred for partner &1; passed on to Forward Error Handling |
| 027 | Error for relationship &3 &4 of &1 and &2; passed on to FEH |
| 028 | Relationships cannot be uploaded into staging |
| 029 | Simulation run for business partner relationship not possible |
| 030 | Relationship &3 &4 of partners &1 and &2 created |
| 031 | Relationship &3 &4 of partners &1 and &2 updated |
| 032 | No record contained in the file |
| 033 | Object &1 &2 successfully checked |
| 034 | Relationship &3 &4 of &1 and &2 successfully checked |
| 035 | Change request type must not be initial |
| 036 | Error during calculation of a temporary address number |
| 037 | Error during calculation of a temporary business partner number |
| 038 | Error during outbound mapping; processing not possible |
| 039 | Action code &1 is invalid. |
| 040 | Due to errors, the staging process has been triggered for &1 &2 |
| 041 | Due to errors, the staging process has been triggered |
| 042 | BP with temporary ID &1 saved for customer &2 in change request &3 |
| 043 | BP with internal ID &1 saved for customer &2 in change request &3 |
| 044 | Business partner with internal ID &1 created for customer &2 |
| 045 | Relationship of category &1 saved for BPs &2 and &3 in change request &4 |
| 046 | Error occurred for partner &1 |
| 047 | Consolidation started for Businss Partner &1 |
| 048 | Consolidation started for Businss Partner |
| 049 | CTI state &1 not supported with provided data for entity node &2 |
| 050 | Inconsistent data: CTI state &1 is provided but entity node &2 is missing |
| 052 | BP with temporary ID &1 saved for supplier &2 in change request &3 |
| 053 | BP with internal ID &1 saved for supplier &2 in change request &3 |
| 054 | Business partner with internal ID &1 created for supplier &2 |
| 056 | Grouping is missing for Partner &1. |
| 057 | Error for relationship &3 &4 of &1 and &2 |
| 060 | Replication models &1 and &2 cannot be active at the same time |
| 062 | BP with temporary ID &1 saved in change request &2 |
| 063 | BP with internal ID &1 saved in change request &2 |
| 064 | Business partner with internal ID &1 created |
| 065 | Business partner &1 is not available for sender business system &2. |
| 066 | Please enter the business partner ID. |
| 067 | Please enter the sender business system ID. |
| 069 | Sender business system ID &1 is not supported. |
| 070 | Mapping error for address version &1: missing name fields &2 |
| 071 | Business partner &1 not sent due to pending message |
| 072 | Unexpected AIF error &1 &2 &3 &4 |
| 100 | No business system ID assigned to logical system &1 |
| 101 | Partner &1 has already been processed and cannot be changed |
| 102 | Rel.ship &3 &4 of partners &1 and &2 already processed; not changeable |
| 103 | &1&2&3 |
| 110 | Function is not supported in this release |
| 111 | &1 operation for table &2 failed |
| 112 | Error while creating confirmation message: &1 |
| 121 | Ratings transferred in two different nodes of service message type |
| 122 | Creditworthiness data transferred in two diff. nodes of service msg type |
| 123 | Please implement BAdI &. See note 2858939 |
| 124 | Sending of & was deactivated |
| 125 | Processing of incoming & was deactivated |