FSBP_CC - Message Class for Business Partner Data Cleansing Case Core
The following messages are stored in message class FSBP_CC: Message Class for Business Partner Data Cleansing Case Core.
It is part of development package FS_BP_FND_CLEANSING_APPL_LOGIC in software component FS-BP. This development package consists of objects that can be grouped under "Application Logic for FS Business Partner Cleansing".
It is part of development package FS_BP_FND_CLEANSING_APPL_LOGIC in software component FS-BP. This development package consists of objects that can be grouped under "Application Logic for FS Business Partner Cleansing".
Message Nr ▲ | Message Text |
|---|---|
| 000 | No data cleansing case with ID &1 exists |
| 001 | Data cleansing case with GUID &1 does not exist |
| 002 | Data cleansing case with ID &1 and GUID &2 does not exist |
| 003 | Data cleansing case with invalid combination ID &1 and GUID &2 |
| 005 | Data cleansing case processed |
| 006 | Data cleansing case simulated |
| 007 | Data cleansing case rejected |
| 008 | Data cleansing case was reset |
| 009 | Business partner &1 of data cleansing case was reset |
| 010 | Select one target business partner only |
| 011 | Status &2 is not permitted for business partner &1 with this action |
| 012 | No target business partner |
| 013 | No duplicate exists |
| 014 | You cannot set this status for business partner &1 |
| 015 | You can only reset the target BP if you reset the entire cleansing case |
| 016 | Completed data cleansing case not permitted without duplicate |
| 017 | Completed data cleansing case must have one target partner only |
| 020 | No data cleansing case exists for specified selection criteria |
| 021 | Start date &1 must not be after end date &2 |
| 022 | Numbers of the data cleansing cases do not make a valid interval |
| 024 | Cannot process data cleansing case |
| 025 | Warnings occurred while processing the data cleansing case |
| 026 | Messages were returned while merging the partners |
| 027 | Cleansing case is relevant for release |
| 028 | Partner data merge processed |
| 029 | Release process terminated |
| 030 | An internal error occurred |
| 031 | Set of rules not found; contact your administrator |
| 032 | Set of rules contains errors; contact your system administrator |
| 033 | No image exists of the data for business partner &1 |
| 034 | Business partner &1 changed; release not possible |
| 035 | Priority &1 has not been defined in Customizing |
| 036 | Business partner relationship &1 has been changed and cannot be released |
| 037 | Data cleansing case &1 released |
| 040 | Error while changing partner &1 |
| 041 | Error while changing business partner relationship &1 |
| 050 | You are not authorized to perform this action |
| 051 | You are not authorized to change the data cleansing case |
| 052 | You are not authorized to change the business partner status |
| 053 | You are not authorized to simulate the data cleansing case |
| 054 | You are not authorized to execute the data cleansing case |
| 055 | You are not authorized to reject the data cleansing case |
| 056 | You are not authorized to release the data cleansing case |
| 057 | You are not authorized to reset the data cleansing case |
| 058 | You are not authorized to display the data cleansing case |
| 059 | You are not authorized to create the data cleansing case |
| 060 | You are not authorized to delete the data cleansing case |
| 061 | Data cleansing case locked |
| 062 | Data cleansing case &1 is currently locked by you |
| 063 | Data cleansing case &1 is currently locked by &2 |
| 064 | At least one relationship of business partner &1 is locked |
| 065 | Data cleansing case &1 not locked |
| 066 | Reject data cleansing case because it contains locked business partners |
| 100 | Operation is not possible in the current status |
| 101 | You cannot change the business partner status in the current status |
| 102 | You cannot make a proposal for business partner status in current status |
| 103 | You cannot execute data cleansing in the current status |
| 104 | You cannot reject data cleansing in the current status |
| 105 | You cannot reset data cleansing in the current status |
| 106 | You cannot simulate data cleansing in the current status |
| 107 | Release actions are not possible in the current status |
| 108 | Release cannot be approved in the current status |
| 109 | Release cannot be rejected in the current status |
| 110 | Release cannot be returned for correction in the current status |
| 802 | Enter an adapter class for the release |