SAP ABAP Message Class R111 (Business Partner Messages (Package: BUPA))
Basic Data
Hierarchy
☛
SAP_ABA (Software Component) Cross-Application Component
⤷
AP-MD-BP (Application Component) SAP Business Partner
⤷
BUPA (Package) SAP Business Partner
⤷
⤷
Attributes
| Message class | R111 | |
| Short Description | Business Partner Messages (Package: BUPA) | |
| Changed On | 20141121 | |
| Last Changed At | 230116 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 | * ab 001 BAPI/API | The short text describes the object sufficiently | ||
| 2 | Enter an indentification type or an identification category | The short text describes the object sufficiently | ||
| 3 | Determined ID type &1 does not correspond to transferred ID type &2 | The short text describes the object sufficiently | ||
| 4 | ID type &1 already exists for partner | The short text describes the object sufficiently | ||
| 5 | Industry data cannot be maintained for the BP category &1 | The short text describes the object sufficiently | ||
| 6 | Field &1 is obsolete and should therefore not be filled | Space: object requires documentation | ||
| 7 | Filter is not valid; enter a valid filter | The short text describes the object sufficiently | ||
| 8 | You cannot reset the function "IBAN without account number" | The short text describes the object sufficiently | ||
| 9 | No business partners with this selection criteria were found | The short text describes the object sufficiently | ||
| 10 | Bank details ID &1 is already in the table BUT0BK_SHD | The short text describes the object sufficiently | ||
| 11 | Address language can only be maintained for one organization | The short text describes the object sufficiently | ||
| 12 | You cannot activate the function "IBAN without account number" | The short text describes the object sufficiently | ||
| 13 | Could not find address versions for the organization | The short text describes the object sufficiently | ||
| 14 | The mask for the payment card has already been reset | The short text describes the object sufficiently | ||
| 15 | Partner & with Guid & and Sender ID & are not same | The short text describes the object sufficiently | ||
| 16 | &1 is not a semantic ID type | The short text describes the object sufficiently | ||
| 17 | &1 is not a technical ID type | The short text describes the object sufficiently | ||
| 18 | Automatic Debit Authorization indicator cannot be set to '&1' | The short text describes the object sufficiently | ||
| 19 | Enter a valid bank account number | The short text describes the object sufficiently | ||
| 20 | No address found (&2) for communication type &1 | Space: object requires documentation | ||
| 21 | No business partner entered as input | The short text describes the object sufficiently | ||
| 22 | No partners found for stated selection | The short text describes the object sufficiently | ||
| 23 | User does not have authorizations to &1 a partner | The short text describes the object sufficiently | ||
| 24 | Business partner &1 purpose is completed and is blocked | The short text describes the object sufficiently | ||
| 25 | Business partner &1 has ongoing business in system &2 and application &3 | The short text describes the object sufficiently | ||
| 26 | Business partner &1 purpose is completed | The short text describes the object sufficiently | ||
| 27 | Business partner &1 has ongoing business in application &2 | The short text describes the object sufficiently | ||
| 28 | Business partner &1 is unblocked and can be used | The short text describes the object sufficiently | ||
| 29 | Business partner &1 can be unblocked | The short text describes the object sufficiently | ||
| 30 | No ILM policy maintained for Application Object CA_BUPA(Business Partner) | The short text describes the object sufficiently | ||
| 31 | Only one entry is allowed | The short text describes the object sufficiently | ||
| 32 | IS_NOTICE is initial | The short text describes the object sufficiently | ||
| 33 | Application object is empty | The short text describes the object sufficiently | ||
| 34 | Table field is empty | The short text describes the object sufficiently | ||
| 35 | Enter appropriate data | The short text describes the object sufficiently | ||
| 36 | Data Privacy for business partners is not active | The short text describes the object sufficiently | ||
| 37 | Deactivating the indicator &1 is not allowed | The short text describes the object sufficiently | ||
| 38 | A number of BP are not yet converted indicator &1 can not be used | The short text describes the object sufficiently | ||
| 39 | Business partner & 1 has ongoing business activities | The short text describes the object sufficiently | ||
| 40 | Type &1 of identification number &2 is blocked | The short text describes the object sufficiently | ||
| 41 | You have blocked type &1 of identification number &2 | The short text describes the object sufficiently | ||
| 42 | Type &1 of identification number &2 is blocked by &3 | The short text describes the object sufficiently | ||
| 43 | Unblock request for business partner &1 has been created | The short text describes the object sufficiently | ||
| 44 | Unblock request for business partner &1 has already been created | The short text describes the object sufficiently | ||
| 45 | No business partners are blocked | The short text describes the object sufficiently | ||
| 46 | No. of max. processes should not exceed selected no. of business partner | The short text describes the object sufficiently | ||
| 47 | System failure or comm. failure for processing partner from & to & | The short text describes the object sufficiently | ||
| 48 | Resource failure occurring for processing partner from & to & | The short text describes the object sufficiently | ||
| 49 | Partner from & to & processing failed | The short text describes the object sufficiently | ||
| 50 | Business partner &1 is rejected | The short text describes the object sufficiently | ||
| 51 | Business partner &1 can be rejected | The short text describes the object sufficiently | ||
| 52 | IRM rule group Customizing is incorrect | The short text describes the object sufficiently | ||
| 53 | Move date &1 is not in the validity period of the source object | The short text describes the object sufficiently |
History
| Last changed on/by | 20141121 | SAP | |
| SAP Release Created in | 710 |