R111 - Business Partner Meldungen (Paket: BUPA)
The following messages are stored in message class R111: Business Partner Meldungen (Paket: BUPA).
It is part of development package BUPA in software component AP-MD-BP. This development package consists of objects that can be grouped under "SAP Business Partner".
It is part of development package BUPA in software component AP-MD-BP. This development package consists of objects that can be grouped under "SAP Business Partner".
Message Nr ▲ | Message Text |
|---|---|
| 000 | * ab 001 BAPI/API |
| 001 | Enter an indentification type or an identification category |
| 002 | Determined ID type &1 does not match the passed ID type &2 |
| 003 | ID type &1 already exists for partner |
| 004 | Industry data cannot be maintained for the BP category &1 |
| 005 | The field &1 is obsolete; do not fill it |
| 006 | Filter is not valid; enter a valid filter |
| 007 | You cannot reset the function "IBAN without account number" |
| 008 | No business partners with this selection criteria were found |
| 009 | Bank details ID &1 is already in the table BUT0BK_SHD |
| 010 | Address language can only be maintained for one organization |
| 011 | You cannot activate the function "IBAN without account number" |
| 012 | Could not find address versions for the organization |
| 013 | The mask for the payment card has already been reset |
| 014 | Partner & with Guid & and Sender ID & are not same |
| 015 | &1 is not a semantic ID type |
| 016 | &1 is not a technical ID type |
| 017 | Automatic Debit Authorization indicator cannot be set to '&1' |
| 018 | Enter a valid bank account number |
| 019 | No address found (&2) for communication type &1 |
| 020 | Enter a business partner |
| 021 | No business partner found |
| 022 | You are not authorized to block/unblock data; see long text. |
| 023 | Business partner &1 is blocked |
| 024 | Business partner &1 is not blocked; is used in system &2, application &3 |
| 025 | Business partner &1 can be blocked |
| 026 | Business partner &1 is not blocked; used in application &2 |
| 027 | Business partner &1 was unblocked |
| 028 | Business partner &1 can be unblocked |
| 029 | ILM policy does not exist for business partner; see long text |
| 030 | Only one entry is permitted |
| 031 | IS_NOTICE is initial |
| 032 | Application object is empty |
| 033 | Table field is empty |
| 034 | Enter suitable data |
| 035 | Business function BUPA_ILM_BF is not activated; see long text |
| 036 | Deactivating the indicator &1 is not allowed |
| 037 | A number of BPs are not yet converted and indicator &1 cannot be used |
| 038 | Business activity not ended for business partner &1; see long text |
| 039 | Selected partners cannot be processed. See long text. |
| 040 | Type &1 of identification number &2 is blocked |
| 041 | You have blocked type &1 of identification number &2 |
| 042 | Type &1 of identification number &2 is blocked by &3 |
| 043 | Request to unblock business partner &1 was submitted |
| 044 | Request to unblock business partner &1 has already been submitted |
| 045 | Business partner cannot be blocked; see long text |
| 046 | No. of max. processes exceeds no. of business partners; see long text |
| 047 | Error while transferring data; see long text |
| 048 | Resource error while transferring the data; see long text |
| 049 | Error while processing the business partner; see long text |
| 050 | Unlocking of business partner &1 was rejected. |
| 051 | Unlocking of business partner &1 can be rejected. |
| 052 | IRM rule group Customizing is incorrect |
| 053 | XPCPT flag not set due to error in partner &1, system &2 |
| 054 | &1 business partners cannot be unblocked |
| 055 | System error in system &1 for function module &2 |
| 056 | Business partner &1 is still being used by application &2 |
| 057 | You are not authorized to request a block |
| 058 | You are not authorized to approve/reject |
| 059 | Only one function can be active at any given time |
| 060 | Blocking approval request has been created for business partner &1 |
| 061 | BP &1 is not unblocked; used in system &2, application &3 |
| 062 | BP &1 cannot be unblocked; used in system &2, application &3 |
| 063 | Pending blocking approval request found for business partner &1 |
| 064 | No blocking function is active for business partner &1 |
| 065 | Application &1 belongs to application component &2 |
| 066 | Unable to determine application component of application &1 |
| 067 | The unblocking requests for &1 business partners were already transferred |
| 068 | The unblocking requests for &1 business partners were transferred |
| 069 | Unblocking requests for &1 business partners were created |
| 070 | &1 business partners could not be unblocked |
| 071 | Error while deleting data from table &1 |
| 072 | Error while updating table &1 |
| 073 | Error while inserting data into table &1 |
| 074 | Change to policy have an impact on data for the locked BP |
| 075 | Application rule variant for BUP and BUB cannot be maintained |
| 076 | Do not maintain rule variants for applications BUB and BUP |
| 077 | Delete the existing entries for applications BUB and BUP |
| 078 | Enter the description for the reason code |
| 079 | Retention date of business partner "&1" is in the future. |
| 080 | Customer and/or supplier roles are blocked for this business partner |
| 081 | SEPA mandates are not available due to multiple SEPA applications |
| 082 | BP &1 cannot be edited due to missing SoRT entry |
| 083 | BP &1 cannot be edited because the next check date is later than today |
| 084 | No BP found to approve/reject unlock request |
| 085 | Operation is not supported; see long text |
| 086 | You are not authorized to unlock data. Please read the long text. |
| 087 | No request to unlock business partner &1 exists |
| 088 | You are the requester for unlocking business partner &1 |
| 089 | Business activities for BP &1 in application &2 not found |
| 090 | Gender '&1' does not match form of address '&2' |
| 091 | Gender was set to &1 by default |
| 092 | No selection made |
| 093 | System error in logical port &1 for &2 &3 |
| 094 | You cannot approve or reject this request. |
| 095 | No authorization to maintain ID data. Please see long text. |
| 096 | Please enter at least one data controller. |
| 097 | Data controller &1 already exists for the partner. |
| 098 | Unlock request was not created. See long text. |
| 099 | No data controller is assigned to business partner &1. |
| 100 | Data controller &1 is already assigned. |
| 101 | Data controller &2 is not available for business partner &1. |
| 102 | Data controller &1 is invalid. |
| 103 | Bank details and bank account alias cannot be maintained together. |
| 104 | Bank data record with GUID &1 already exists |
| 105 | Bank data record with GUID &1 does not exist for partners |
| 106 | One million logs reached. Please choose "application log". |
| 107 | Unlocking in system &1 is not triggered by the leading system |
| 108 | Standard address already exists for address application &1 |
| 110 | No business partner available for archiving; entered filter &1. |
| 111 | Business partner &1 is not used in system &2, application &3. |
| 112 | Purpose of business partner &1 in system &2, application &3 is completed. |
| 200 | Enter at least one international location number. |
| 201 | Please enter the ILN details. |
| 203 | Enter an address for international location number &1. |
| 204 | Address is already assigned to an ILN. Please enter a different address. |
| 205 | Shared maintenance of address-dependent/independent ILN is not possible. |
| 704 | The move date &1 is not in the validity range of the source object |
| 705 | Change date is not after valid-from date of source bank ID |
| 706 | You are not authorized to execute report &1 |
| 707 | &1&2&3&4 |