CACSVC - Provisionen: Bewertung, Verg�tung & Verteilung
The following messages are stored in message class CACSVC: Provisionen: Bewertung, Verg�tung & Verteilung.
It is part of development package CACSCC in software component ICM. This development package consists of objects that can be grouped under "ICM: Commission Case 'Light'".
It is part of development package CACSCC in software component ICM. This development package consists of objects that can be grouped under "ICM: Commission Case 'Light'".
Message Nr ▲ | Message Text |
---|---|
001 | No entries exist in table &2 (&3) |
002 | No valuation type determined for subobject &2/&3 |
003 | No valuation for valuation type & in object type ID &1/ &2 |
004 | Valuation could not be executed correctly |
005 | Input parameters for early cancellation liability are incorrect |
006 | No valuation history for object &1/&2, valuation type &3 |
007 | You cannot convert valuation for object &1/&2, valuation type &3 |
008 | No detail rows found for remuneration row &1/&2/&3 |
009 | Enter liability amount or quantity in remuneration &1/&2/&3 |
010 | Update category for &1/&2/&3, substep liability not successful |
011 | Calculation of earned share for liability rule &1 is incorrect |
012 | Calculation service for liability &1 cannot be determined |
013 | Remuneration object category &3 for object &1/&2 not found |
014 | Detail row for remuneration &1/&2/&3: Quantity and amount filled |
015 | Different valuation category for valuation type &1 subobject type &2 |
016 | Caution: Valuation type &1/ object type &2: New version &3, was &4 |
017 | Early cancellation liability: Recall/ results type 01 calculated |
018 | Early cancellation liability: Entitlmt remainder/results type 02 calcd |
019 | Early cancellation liability: Remainder liability/results type 03 calcd |
020 | Early cancellation liability: Earned share/results type 04 calculated |
021 | Early cancellation liability: No liab. earned share/results type 05 calc. |
022 | TObj &2: Calculation of valuation type '&1' |
023 | Different valuation category for valuation type &1 subobject type &2 |
025 | The following valuation types were determined for subobject &1/&2 |
026 | Valuation type: &1 (version &2) for subobject &3 |
027 | Early cancellation: update of rem.record not possible for rem.item &1 |
028 | Early cancellation: update of rem.share not possible for rem.item &1 |
029 | Corrected remuneration line &1 was not found |
050 | Liability type & is not stored in Customizing |
051 | Liability type & exists actively several times |
052 | Several liability types found for remuneration line & |
100 | Activity characteristic for object &2 method &3 was not found |
101 | Activity type for object &2 characteristic &3 was not found |
102 | No further data found for activity type &2 |
103 | Offsetting type &2 not found |
104 | Characteristic exists actively several times (object &2, method &3) |
105 | Offsetting type &2 exists actively several times |
106 | Activity type exists actively several times (object &2, char. &3) |
107 | Several active records found for activity type &2 |
108 | Activity group &2 not found |
109 | Activity group &2 exists actively several times |
170 | **** Distribution messages ********************* |
171 | Contract &1: Legal right plan &2 for remuneration type &3 |
172 | Legal right rules for &1 do not apply due to incorrect remuneration type |
199 | Plan for legal right "&1" not completely maintained |
200 | **** Remuneration messages *********************** |
201 | No remuneration types maintained actively for application & |
202 | Start of remuneration determination case &/& (&) |
203 | Commission case &/& (&) does not exist |
204 | Commission object & (&) does not exist |
205 | Activity & for object & (&) is not remunerated for contract & |
206 | Rule & (&) is not suitable for remuneration |
207 | Remuneration type & has an unknown valuation result category & |
208 | Commission document &/& does not exist |
209 | Commission case &/& does not belong to document &/& |
210 | Remuneration characteristic for remuneration type & is not maintained |
211 | Remuneration type & has not been marked in remuneration flow |
212 | Rule & (&) is not suitable for determination of liability type |
213 | Liability type for object & (&) could not be determined for contract & |
214 | No settlement types actively maintained for application & |
215 | Searching for remuneration types valuation object &1, cat. &2 |
216 | => Remuneration types found: &1 |
217 | Contract &2: Calculation of remuneration type '&1' |
218 | Valuation item &1 for valuation type &2 has been suspended |
300 | **** Detail Item Messages *********************** |
301 | Rem. diff. rate detail &1 for remun. &2 was determined from remun. &3 |
302 | Remun. diff. detail &1 for remun. &2 was determined from detail &3 |
303 | Detail &1 of remunDiffAmt for remun. &2 was determined from remun. &3 |
304 | RemDiffAmt detail &1 for remuneration &2 was determined from detail &3 |
305 | Remuneration determination possibly incorrect using remuneration rate |
306 | Remuneration dif. detail &1 for remun. &2 exceeds the max. value allowed |
323 | Enhancement category '&1' is not compatible with update category '&2' |
324 | Result type &1 is not maintained in Customizing (PS &2) |
325 | Update category &1 is not maintained in Customizing |
326 | Update category &1 is active in several places |
327 | Detail row for remuneration item & is not allowed and thus is deleted |
328 | Inconsistent document data; no update possible |
400 | ============== Messages on secondary liability |
401 | No remuneration row for determining secondary liability |
402 | No object category specified for selecting secondary liability |
403 | No remuneration row for secondary liability row provided |
404 | No historical remuneration for secondary liability correction |
405 | No results type provided for secondary liability correction |
406 | Complex valuation was started |
407 | Complex valuation was ended |
408 | Complexity "&1" is being processed |
409 | Tool for complex valuation type "&1" missing on "&2" at "&3" |
410 | Valuation type "&1" has more than one assignment to valuation type "&2" |
412 | Subprogram &1(&2) is obsolete and must not be used |