CRM_SALES - Output for Sales Set
The following messages are stored in message class CRM_SALES: Output for Sales Set.
It is part of development package CRM_SALES in software component CRM-BTX. This development package consists of objects that can be grouped under "CRM Sales Data".
It is part of development package CRM_SALES in software component CRM-BTX. This development package consists of objects that can be grouped under "CRM Sales Data".
Message Nr ▲ | Message Text |
|---|---|
| 001 | Initialization of sales data buffer was called up empty |
| 002 | Sales data for unique ID &1 could not be found |
| 003 | Error when creating sales data for reference unique ID &1 |
| 004 | No reference objects could be created for set unique ID &1 |
| 005 | Incorrect parameter transfer when calling up function module '&1' |
| 006 | Attachment assignment block is not visible |
| 007 | Notes assignment block is not visible |
| 014 | Date type &1 not contained in date profile &2 |
| 015 | No date profile assigned to the transaction/item category |
| 101 | Purchase order number &1 has already been used in business transaction &2 |
| 102 | Reference date &1 is in the future; check the reference date |
| 103 | Reference date &1 is far back in the past; check reference date |
| 104 | Transaction '&1' (&2) is not allowed |
| 105 | Reason for rejection '&1' is not defined in Customizing |
| 106 | Maintain reasons for rejection in system |
| 107 | Rejection reason code &1 isn't assigned to rejection reason profile &2. |
| 301 | Product GUID is blank; catalog details cannot be checked |
| 302 | Catalog details are incomplete |
| 303 | Catalog details are inconsistent |
| 304 | The product catalog &1 is not available |
| 305 | Catalog area &1 is not available |
| 306 | The catalog variant &1 is not available |
| 307 | Product &1 is not in the entered catalog/variant |
| 308 | A product with GUID &1 does not exist |
| 309 | Catalog area with GUID &1 does not exist |
| 310 | A catalog variant with GUID &1 does not exist |
| 400 | * *** Customizing *** |
| 401 | Customer group &1 is not available; enter a valid customer group |
| 402 | No desciption exists for customer group 1 &1 |
| 403 | Customer group &1 is not available; enter a valid customer group |
| 404 | No description exists for customer group 2 &1 |
| 405 | Customer group 3 &1 is not available; enter a valid customer group |
| 406 | No desciption exists for customer group 3 &1 |
| 407 | Customer group 4 &1 is not available; enter a valid customer group |
| 408 | No description exists for customer group 4 &1 |
| 409 | Customer group 5 &1 is not available; enter a valid customer group |
| 410 | No description exists for customer group 5 &1 |
| 411 | Usage &1 is not available; enter a valid usage |
| 412 | No desciption exists for usage indicator &1 |
| 413 | Sales district &1 is not available |
| 414 | No description exists for sales district &1 |
| 415 | Industry sector &1 is not available |
| 416 | No description exists for industry sector &1 |
| 417 | Reason for rejection &1 does not exist |
| 418 | No text is maintained in language '&2' for reason for rejection '&1' |
| 419 | No reasons for rejection are maintained in language '&1' |
| 420 | ATP exclusion indicator &1 not found |
| 421 | ATP search string &1 not found |
| 422 | No rejection reason assigned to rejection profile &1. |
| 430 | The invalid value &1 was entered, a conversion was not possible |
| 500 | No sold-to party exists; cannot check sold-to party profile &1 |
| 501 | Sold-to party profile &1 is not associated with business partner &2 |
| 502 | Profile &1 is not associated with bus. partner &2 and trans. type &3 |
| 800 | *** BAdI call - error messages *** |
| 801 | Error in BAdI method CRM_SALES_CHECK |
| 802 | Error, no data transfer from BAdI method CRM_SALES_MERGE |