CRM_BUPA_MAPPING - CRM GP Mapping Gesch�ftspartner auf Kundenstamm im R/3
The following messages are stored in message class CRM_BUPA_MAPPING: CRM GP Mapping Gesch�ftspartner auf Kundenstamm im R/3.
It is part of development package CRM_BUPA_MAPPING in software component CRM-MD-BP-IF. This development package consists of objects that can be grouped under "CRM BP Mapping Business Partner to Customer Master in R/3".
It is part of development package CRM_BUPA_MAPPING in software component CRM-MD-BP-IF. This development package consists of objects that can be grouped under "CRM BP Mapping Business Partner to Customer Master in R/3".
Message Nr ▲ | Message Text |
|---|---|
| 001 | No business partner is assigned to customer &1 |
| 002 | No customer is assigned to business partner &1 |
| 003 | No contact person is assigned to business partners &1 and &2 |
| 004 | No business partners are assigned to contact person &1 |
| 005 | Account group &1 does not exist in table CRMC_BUT_MAPPG1 |
| 006 | Classification &1 does not exist in table CRMC_BUT_MAPPG2 |
| 007 | There is no entry in table CRMC_BUT_MAPPG1 |
| 008 | There is no entry in table CRMC_BUT_MAPPG2 |
| 009 | No contact person is assigned to person &1 |
| 010 | Errors occurred during processing of BDOCs |
| 011 | Number &1 is not in interval "&2" to "&3" |
| 012 | Data has been successfully posted |
| 013 | No sendbits could be evaluated for structure &1 |
| 014 | It is not necessary to post data into the CRM system |
| 015 | Error calling function module &1 |
| 016 | Insertion in table &1 was not successful. Error: &2 |
| 017 | The target system for customer upload is not maintained correctly |
| 018 | No customer number was found for business partner &1 |
| 019 | The address of the business partner could not be read |
| 020 | The sendbits for telephone data could not be determined |
| 021 | The sendbits for fax data could not be determined |
| 022 | The sendbits for teletext data could not be determined |
| 023 | The sendbits for telex data could not be determined |
| 024 | The sendbits for eMail addresses could not be determined |
| 025 | The sendbits for addresses could not be determined |
| 026 | The sendbits for customers could not be determined |
| 027 | The ERP key is not maintained for sales organization &1 |
| 028 | The sendbits for sales data could not be determined |
| 029 | Error when calling key gen |
| 030 | The inbound adapter could not be called |
| 031 | The sendbits for customers could not be determined |
| 032 | The sendbits for partner functions could not be determined |
| 033 | No business partner number could be found in the target system |
| 034 | Mapping of business partner &1 |
| 035 | BDOC &1 created |
| 036 | No distribution is defined for business partner &1 |
| 037 | Messages for customer &1 |
| 038 | Messages for contact person &1 |
| 039 | The send bits for bank data could not be determined |
| 040 | There are no sales areas for business partner maintenance |
| 041 | The sales areas are not consistent with the lines of business settings |
| 042 | Mapping for business partner download is incorrectly maintained |
| 043 | Lines of business settings are not consistent |
| 044 | Flow definition for object &1 has not yet been generated |
| 045 | All other customers in this block are successfully updated |
| 046 | Business partner &1 is not assigned a HR master record |
| 047 | No customer in this block has been updated |
| 048 | Internal error: General data not available |
| 049 | The request for customer &1 is started |
| 050 | An error has occurred during the starting of the request for customer &1 |
| 051 | An RFC link is not maintained in the Middleware |
| 052 | Error during determination of the queue names from the ERP system |
| 053 | Error during determination of consumer from the CDB |
| 054 | A tolerence limit does not exist for the initial download |
| 055 | A reference business partner is already maintained |
| 056 | Tax number type &1 does not exist |
| 057 | All other contact persons in this block are successfully updated |
| 058 | No contact person in this block is updated |
| 059 | Regional structure exists in OLTP system only from Release 4.5 |
| 101 | Select at least one set |
| 102 | No business partner could be selected |
| 103 | You have selected &1 business partner/s |
| 210 | The business partner number &1 has been converted |
| 211 | The business partner GUID &1 has been converted |
| 212 | The customer number &1 has been converted |
| 213 | The partner number in the BDOC does not agree with that from the DB |
| 214 | Business partner with GUID &1 is already assigned to a customer number |
| 215 | Customer number &1 is already assigned to a business partner |
| 216 | Organization &1 and person &2 are already assigned to a partner number |
| 217 | Partner number &1 is already assigned to a contact partner relationship |
| 300 | A reference business partner is already maintained |
| 301 | A technical error has occured |
| 302 | Could not create reference business partner |
| 303 | Could not determine site definition for ERP system |
| 304 | Could not determine site definition for CRM system |
| 305 | No reference customer maintained in ERP system |
| 306 | Reference customer already downloaded |
| 307 | ERP system does not support consumers |
| 400 | ERP system cannot be uniquely determined: Several site definitions exist |
| 401 | Error when reading data from ERP system |
| 402 | Number range exceeded for business partner relationships |
| 403 | Error during mass update of database table & |