CRM_PRIDOC_COM - Pricing Call
The following messages are stored in message class CRM_PRIDOC_COM: Pricing Call.
It is part of development package CRM_PRIDOC_COM in software component CRM-BTX-BF-PR. This development package consists of objects that can be grouped under "Integration of Pricing into the CRM Order".
It is part of development package CRM_PRIDOC_COM in software component CRM-BTX-BF-PR. This development package consists of objects that can be grouped under "Integration of Pricing into the CRM Order".
Message Nr ▲ | Message Text |
---|---|
000 | *************** Pricing-related messages ************ |
001 | Pricing document could not be created |
002 | Price agreements are incorrect |
003 | Application &1 does not fit in with the price agreements |
004 | Header conditions cannot be maintained manually. |
005 | Item is not relevant for pricing |
006 | Pricing document cannot be saved - obsolete |
007 | Price agreements cannot be changed |
008 | Errors occurred in the organizational data |
009 | Pricing document cannot be saved |
010 | Cross-item pricing disabled; item price does not incl. cross-item calc. |
110 | *************** Messages Related to Condition Maintenance *************** |
111 | There is no condition group assigned to transaction type &1 |
112 | There is no condition group assigned to item category &1 |
400 | ********* Customizing ***************** |
401 | Pricing procedure could not be determined |
402 | Pricing type could not be determined |
403 | Only use partner function type for object 'PARTNER' |
404 | Entry of partner function type obligatory for partner fields |
405 | Enter an object name |
406 | Enter a field name |
407 | Object &1 cannot be used. Use F4 help. |
408 | Field &1 does not exist for object &2. Use F4 help. |
409 | Pricing document could not be read |
410 | Condition type &1 already exists |
411 | Condition type &1 is not a header condition |
412 | Condition type &1 is not an item condition |
413 | Condition type &1 not found |
414 | Condition type &1 is not a manual condition |
415 | Condition type &1 is a group condition and is therefore not permitted |
416 | Enter a valid pricing procedure |
417 | Pricing procedure &1 not found |
418 | Use condition type &1 in accordance with sequence of pricing procedure &2 |
419 | Pricing procedure &1: Maintain without gaps from left to right |