CRM_ORDER_DEDUP - Deduplication Messages
The following messages are stored in message class CRM_ORDER_DEDUP: Deduplication Messages.
It is part of development package CRM_ORDER_DEDUP in software component CRM-BTX-BF-DUP. This development package consists of objects that can be grouped under "Deduplicate Order Objects".
It is part of development package CRM_ORDER_DEDUP in software component CRM-BTX-BF-DUP. This development package consists of objects that can be grouped under "Deduplicate Order Objects".
Message Nr ▲ | Message Text |
|---|---|
| 000 | &1 |
| 001 | A similar lead (ID &1) was found by the duplicate check |
| 002 | Illegal search criterion for duplicate check encountered |
| 003 | Name '&1' is not permitted for this class |
| 004 | Deduplication is not active for transaction type &1 |
| 005 | Newly created duplicate &1/&2 (GUID = &3) successfully deleted |
| 006 | Newly created duplicate &1/&2 (GUID = &3) could not be deleted |
| 007 | Order object with GUID &1 successfully deleted |
| 008 | Order object with GUID &1 could not be deleted |
| 009 | Lead is a duplicate and was merged into lead ID &1 |
| 010 | Deduplication is not possible for duplicates |
| 011 | Order object with ID &1 is marked for deletion |
| 012 | Deduplication is not possible for different transaction types |
| 013 | Merge not possible; prime lead (ID &1) is currently locked by user &2 |
| 014 | Lead ID &1 is a duplicate, has been merged with lead ID &2 and deleted |
| 015 | Lead ID &1 is a duplicate and cannot be merged |
| 016 | Prime lead search stopped after &1 found leads; click again to proceed |
| 017 | Deduplication customizing not maintained for transaction type &1 |
| 101 | No partner in partner function &1 available |
| 102 | No partner in partner function category &1 available |
| 103 | Duplicate search aborted due to missing sales prospect |
| 104 | No value for search criteria &1 available |
| 200 | Deduplication starts for lead &1 |
| 201 | Deduplication ends for new lead |
| 202 | Method &1 returned: &2: &3 |
| 203 | Duplicate search found &1 duplicates |
| 204 | Lead &1 determined as prime lead |
| 205 | Logging starts for new lead |
| 206 | Duplicate search class is &1 |
| 207 | Deduplication ends for new lead |
| 208 | Deduplication: method SEARCH starts |
| 209 | Deduplication: method SEARCH ends |
| 210 | Deduplication: method MERGE starts |
| 211 | Deduplication: method MERGE ends |
| 212 | Deduplication: method PROCESS starts |
| 213 | Deduplication: method PROCESS ends |
| 700 | *** Message-no's 701-799: Notification-related messages *** |
| 701 | Start notification |
| 702 | Notifications were sent sucessfully |
| 703 | Start processing duplicate object &1 |
| 704 | Error while reading duplicate object &1 |
| 705 | No prime object found for duplicate object &1 |
| 706 | More than one prime object found for duplicate object &1 |
| 707 | No user exists for business partner &1; notification is not sent to him |
| 708 | Error during user determination for business partner &1 |
| 709 | Duplicate object &1 is excluded from this notification process |
| 710 | Error while reading business partners for duplicate or prime object |
| 711 | Error while using the reporting framework |
| 712 | Error while starting notification for business partner &1 |
| 713 | Error while searching for duplicate objects |
| 714 | Error while preparing notifications |
| 715 | Error while sending notifications |
| 716 | Error while removing status "Notification required" |
| 717 | No duplicate objects found for notification |
| 718 | No partner function category was selected for notification receiver |
| 719 | Business partner does not exist |
| 720 | No user was notified about merging of duplicate object &1 |
| 800 | *** Message-no's 801-810: Performance-related messages *** |
| 801 | &1 -> &2: &3 microseconds |
| 802 | Detailed runtime analysis done; use SE30 for evaluation |