CRM_BUPA_CLEARING - Cleansing Tool: Cleansing of Service-Specific References
The following messages are stored in message class CRM_BUPA_CLEARING: Cleansing Tool: Cleansing of Service-Specific References.
It is part of development package CRM_BUPA_CLEARING in software component CRM-MD-BP. This development package consists of objects that can be grouped under "CRM BP Implementation Cleansing Tool".
It is part of development package CRM_BUPA_CLEARING in software component CRM-MD-BP. This development package consists of objects that can be grouped under "CRM BP Implementation Cleansing Tool".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Source account is of a different category as target account |
| 001 | Source refers to a different organizational element than target |
| 002 | Error during deactivation of existing Org. management entry |
| 003 | Source and target have different users (Org. management) |
| 004 | Source and target assigned to different positions |
| 005 | Invalid category of the organizational element; activity not carried out |
| 006 | Object cannot be copied |
| 007 | Attributes of the object were transferred |
| 008 | The modified business transaction cannot be saved |
| 009 | Not all transactions were changed |
| 010 | Cleansing case has status &1 |
| 011 | You can only move data to the master account |
| 012 | You need at least two accounts that are not rejected |
| 013 | Case cannot be rejected; merge has already started |
| 014 | Scheduling: specify a valid date and time |
| 015 | One account must be defined as 'Master' |
| 016 | &1 has been transferred from account &2 to account &3 |
| 017 | Attribute &1 of account &2 has been overwritten |
| 018 | Scheduled job has been finished successfully |
| 019 | A business partner can not get role consumer when persistent. |
| 020 | Define a realignment task (refer to note 900293) |
| 030 | Could not read cleansing class from table TBZ5B |
| 031 | Class &1 does not implement interface &2 |
| 032 | Account &1 has been merged with account &2 |
| 033 | Error occured during merge of account &1 to account &2 |
| 034 | Cleansing case number &1 has been skipped as status is &2 |
| 035 | Not able to identify the master account |
| 036 | Could not read node key &1 from table TBZ5 |
| 037 | Could not determine structure of node &1 |
| 040 | Customizing was reset successfully to SAP standard |
| 041 | Table CRMC_TBZ5 is empty; Reset of BUSWU01 is not possible |
| 042 | You cannot merge accounts connected with patients in the same institution |
| 043 | Status of the account with (provisional) patient data must be Master |
| 044 | Account with Source status has provisional patient data |
| 045 | Account with Source status must not have (provisional) patient data |
| 046 | Client-Specific patient identification is enabled in your SAP ERP system |
| 053 |