SAP ABAP Message Class FSBP_CC (Message Class for Business Partner Data Cleansing Case Core)
Basic Data
Hierarchy
☛
SAP_BS_FND (Software Component) SAP Business Suite Foundation
⤷
FS-BP (Application Component) Business Partner
⤷
FS_BP_FND_CLEANSING_APPL_LOGIC (Package) Application Logic for FS Business Partner Cleansing
⤷
⤷
Attributes
| Message class | FSBP_CC | |
| Short Description | Message Class for Business Partner Data Cleansing Case Core | |
| Changed On | 20140121 | |
| Last Changed At | 111008 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 | No data cleansing case with ID &1 exists | The short text describes the object sufficiently | ||
| 2 | Data cleansing case with GUID &1 does not exist | The short text describes the object sufficiently | ||
| 3 | Data cleansing case with ID &1 and GUID &2 does not exist | The short text describes the object sufficiently | ||
| 4 | Data cleansing case with invalid combination ID &1 and GUID &2 | The short text describes the object sufficiently | ||
| 5 | Data cleansing case processed | The short text describes the object sufficiently | ||
| 6 | Data cleansing case simulated | The short text describes the object sufficiently | ||
| 7 | Data cleansing case rejected | The short text describes the object sufficiently | ||
| 8 | Data cleansing case was reset | The short text describes the object sufficiently | ||
| 9 | Business partner &1 of data cleansing case was reset | The short text describes the object sufficiently | ||
| 10 | Select one target business partner only | The short text describes the object sufficiently | ||
| 11 | Status &2 is not permitted for business partner &1 with this action | The short text describes the object sufficiently | ||
| 12 | No target business partner | The short text describes the object sufficiently | ||
| 13 | No duplicate exists | The short text describes the object sufficiently | ||
| 14 | You cannot set this status for business partner &1 | The short text describes the object sufficiently | ||
| 15 | You can only reset the target BP if you reset the entire cleansing case | Space: object requires documentation | ||
| 16 | Completed data cleansing case not permitted without duplicate | Space: object requires documentation | ||
| 17 | Completed data cleansing case must have one target partner only | The short text describes the object sufficiently | ||
| 18 | No data cleansing case exists for specified selection criteria | The short text describes the object sufficiently | ||
| 19 | Start date &1 must not be after end date &2 | The short text describes the object sufficiently | ||
| 20 | Numbers of the data cleansing cases do not make a valid interval | The short text describes the object sufficiently | ||
| 21 | Cannot process data cleansing case | The short text describes the object sufficiently | ||
| 22 | Warnings occurred while processing the data cleansing case | The short text describes the object sufficiently | ||
| 23 | Messages were returned while merging the partners | The short text describes the object sufficiently | ||
| 24 | Cleansing case is relevant for release | The short text describes the object sufficiently | ||
| 25 | Partner data merge processed | The short text describes the object sufficiently | ||
| 26 | Release process terminated | The short text describes the object sufficiently | ||
| 27 | An internal error occurred | The short text describes the object sufficiently | ||
| 28 | Set of rules not found; contact your administrator | The short text describes the object sufficiently | ||
| 29 | Set of rules contains errors; contact your system administrator | The short text describes the object sufficiently | ||
| 30 | No image exists of the data for business partner &1 | The short text describes the object sufficiently | ||
| 31 | Business partner &1 changed; release not possible | The short text describes the object sufficiently | ||
| 32 | Priority &1 has not been defined in Customizing | The short text describes the object sufficiently | ||
| 33 | Business partner relationship &1 has been changed and cannot be released | The short text describes the object sufficiently | ||
| 34 | Data cleansing case &1 released | The short text describes the object sufficiently | ||
| 35 | Error while changing partner &1 | The short text describes the object sufficiently | ||
| 36 | Error while changing business partner relationship &1 | The short text describes the object sufficiently | ||
| 37 | You are not authorized to perform this action | The short text describes the object sufficiently | ||
| 38 | You are not authorized to change the data cleansing case | The short text describes the object sufficiently | ||
| 39 | You are not authorized to change the business partner status | The short text describes the object sufficiently | ||
| 40 | You are not authorized to simulate the data cleansing case | The short text describes the object sufficiently | ||
| 41 | You are not authorized to execute the data cleansing case | The short text describes the object sufficiently | ||
| 42 | You are not authorized to reject the data cleansing case | The short text describes the object sufficiently | ||
| 43 | You are not authorized to release the data cleansing case | The short text describes the object sufficiently | ||
| 44 | You are not authorized to reset the data cleansing case | The short text describes the object sufficiently | ||
| 45 | You are not authorized to display the data cleansing case | The short text describes the object sufficiently | ||
| 46 | You are not authorized to create the data cleansing case | The short text describes the object sufficiently | ||
| 47 | You are not authorized to delete the data cleansing case | The short text describes the object sufficiently | ||
| 48 | Data cleansing case locked | The short text describes the object sufficiently | ||
| 49 | Data cleansing case &1 is currently locked by you | The short text describes the object sufficiently | ||
| 50 | Data cleansing case &1 is currently locked by &2 | The short text describes the object sufficiently | ||
| 51 | At least one relationship of business partner &1 is locked | The short text describes the object sufficiently | ||
| 52 | Data cleansing case &1 not locked | The short text describes the object sufficiently | ||
| 53 | Reject data cleansing case because it contains locked business partners | The short text describes the object sufficiently | ||
| 54 | Operation is not possible in the current status | The short text describes the object sufficiently | ||
| 55 | You cannot change the business partner status in the current status | The short text describes the object sufficiently | ||
| 56 | You cannot make a proposal for business partner status in current status | The short text describes the object sufficiently | ||
| 57 | You cannot execute data cleansing in the current status | The short text describes the object sufficiently | ||
| 58 | You cannot reject data cleansing in the current status | The short text describes the object sufficiently | ||
| 59 | You cannot reset data cleansing in the current status | The short text describes the object sufficiently | ||
| 60 | You cannot simulate data cleansing in the current status | The short text describes the object sufficiently | ||
| 61 | Release actions are not possible in the current status | The short text describes the object sufficiently | ||
| 62 | Release cannot be approved in the current status | The short text describes the object sufficiently | ||
| 63 | Release cannot be rejected in the current status | The short text describes the object sufficiently | ||
| 64 | Release cannot be returned for correction in the current status | The short text describes the object sufficiently | ||
| 65 | Enter an adapter class for the release | The short text describes the object sufficiently |
History
| Last changed on/by | 20140121 | SAP | |
| SAP Release Created in | 400 |