SAP ABAP Message Class CVI_MAPPING (Error from CVI Assignment Objects)
Basic Data
Hierarchy
☛
SAP_APPL (Software Component) Logistics and Accounting
⤷
AP-MD-BF-SYN (Application Component) Master Data Synchronization
⤷
CVI_MAPPING (Package) Customer Vendor Integration: Mapping
⤷
⤷
Attributes
| Message class | CVI_MAPPING | |
| Short Description | Error from CVI Assignment Objects | |
| Changed On | 20100310 | |
| Last Changed At | 144711 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 | Test | The short text describes the object sufficiently | ||
| 2 | Invalid task &1 for object &2 with identification &3 | The short text describes the object sufficiently | ||
| 3 | Industry &1 for object &2 with ID &3 could not be assigned | The short text describes the object sufficiently | ||
| 4 | It is not possible to map bank details for partner &1 with current state | The short text describes the object sufficiently | ||
| 5 | It is not possible to map bank details for customer &1 with current state | The short text describes the object sufficiently | ||
| 6 | It is not possible to map bank details for vendor &1 with current state | The short text describes the object sufficiently | ||
| 7 | Customer number was not filled during external number assignment | The short text describes the object sufficiently | ||
| 8 | Vendor number was not filled during external number assignment | The short text describes the object sufficiently | ||
| 9 | Error when writing to the table: &1 | The short text describes the object sufficiently | ||
| 10 | Database has been changed | The short text describes the object sufficiently | ||
| 11 | No changes have been made | The short text describes the object sufficiently | ||
| 12 | Customer number is not the same as the business partner number | Space: object requires documentation | ||
| 13 | Business partner number is set as customer number | Space: object requires documentation | ||
| 14 | No customer number may be transferred during internal number assignment | The short text describes the object sufficiently | ||
| 15 | You do not have the authorization to start the report | Space: object requires documentation | ||
| 16 | The function requested is not available | The short text describes the object sufficiently | ||
| 17 | No assigment function is possible for object type &1 | The short text describes the object sufficiently | ||
| 18 | There are no links to be deleted between object &1 and &2 | The short text describes the object sufficiently | ||
| 19 | The number ranges for account group &1 and grouping &2 are different | The short text describes the object sufficiently | ||
| 20 | No BP role category has been maintained for BP role &1 in Customizing | Space: object requires documentation | ||
| 21 | No customer is required | The short text describes the object sufficiently | ||
| 22 | No vendor is required | The short text describes the object sufficiently | ||
| 23 | Customer is automatically assigned | The short text describes the object sufficiently | ||
| 24 | Vendor is automatically assigned | The short text describes the object sufficiently | ||
| 25 | Business partner &1 already has customer &2 assigned to it | The short text describes the object sufficiently | ||
| 26 | Business partner &1 already has vendor &2 assigned to it | The short text describes the object sufficiently | ||
| 27 | Field '&1' is not allowed to be empty | The short text describes the object sufficiently | ||
| 28 | Select at least one attribute to transfer | The short text describes the object sufficiently | ||
| 29 | Report cannot be executed; see program documentation | The short text describes the object sufficiently | ||
| 30 | Vendor number is not the same as the business partner number | Space: object requires documentation | ||
| 31 | Business partner number is set as vendor number | Space: object requires documentation | ||
| 32 | You cannot transfer a vendor number when assigning numbers internally | The short text describes the object sufficiently | ||
| 33 | There is no assignment mapping defined for payment card type '&1' | Space: object requires documentation | ||
| 34 | Account group &1 does not exist | The short text describes the object sufficiently | ||
| 35 | No number range has been assigned to account group &1 | The short text describes the object sufficiently | ||
| 36 | Number range &1 for account group &2 does not exist | The short text describes the object sufficiently | ||
| 37 | Business partner grouping &1 does not exist | The short text describes the object sufficiently | ||
| 38 | No number range has been assigned to business partner grouping &1 | The short text describes the object sufficiently | ||
| 39 | Number range &1 for business partner grouping &2 does not exist | The short text describes the object sufficiently | ||
| 40 | You are not permitted to use grouping &1 with identical numbers | The short text describes the object sufficiently | ||
| 41 | You are only permitted to use grouping &1 with identical numbers | The short text describes the object sufficiently | ||
| 42 | Enter a business partner grouping | The short text describes the object sufficiently | ||
| 43 | Customer &1 already exists | The short text describes the object sufficiently | ||
| 44 | Vendor &1 already exists | The short text describes the object sufficiently | ||
| 45 | Customer number is not within interval &1 - &2 | The short text describes the object sufficiently | ||
| 46 | Vendor number is not within interval &1 - &2 | The short text describes the object sufficiently | ||
| 47 | Address data is not synchronized, validity is in the future | The short text describes the object sufficiently |
History
| Last changed on/by | 20100310 | SAP | |
| SAP Release Created in | 600 |