SAP ABAP Message Class CACS_STD (Higher Level Messages for Standard Contract)
Basic Data
Hierarchy
☛
EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials
⤷ ICM (Application Component) Incentive and Commission Management (ICM)
⤷ CACSC8 (Package) ICM: Standard Contract: Global Types
⤷ ICM (Application Component) Incentive and Commission Management (ICM)
⤷ CACSC8 (Package) ICM: Standard Contract: Global Types
Attributes
Message class | CACS_STD | |
Short Description | Higher Level Messages for Standard Contract | |
Changed On | 20100310 | |
Last Changed At | 195947 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 001 | Cannot determine a system name | Space: object requires documentation | |
2 | 002 | Method CL_CACS_XH_ADMIN~CREATE cannot be executed without APPL | The short text describes the object sufficiently | |
3 | 010 | *** 1-10 Reserved for System Messages | The short text describes the object sufficiently | |
4 | 015 | Invalid call of method &1 | The short text describes the object sufficiently | |
5 | 016 | Error while generating data reference using RTTS | Space: object requires documentation | |
6 | 017 | Implementation of BAdI CACS_STDAGR_FACTORY contains errors | Space: object requires documentation | |
7 | 018 | No agreement assignment of contract &1 to &4 &3 exists | The short text describes the object sufficiently | |
8 | 019 | Agreement assignment of contract &1 for &4 &3 was not activated | The short text describes the object sufficiently | |
9 | 020 | Application &1 does not exist | The short text describes the object sufficiently | |
10 | 021 | Enter at least one standard contract or a range | Space: object requires documentation | |
11 | 022 | Enter at least one contract type or a range | The short text describes the object sufficiently | |
12 | 023 | Error while writing to database; changes are not saved | The short text describes the object sufficiently | |
13 | 024 | &1 data record(s) modified with origin &2 | The short text describes the object sufficiently | |
14 | 030 | Error in SQL statement of search help | The short text describes the object sufficiently | |
15 | 040 | Database accessing error | The short text describes the object sufficiently | |
16 | 041 | Method &1: Reading of database table &2 returned no hits | The short text describes the object sufficiently | |
17 | 042 | Method &1: Error while deleting database table &2 | The short text describes the object sufficiently | |
18 | 043 | Method &1: Error during MODIFY of database table &2 | The short text describes the object sufficiently | |
19 | 044 | Method &1: Error during dynamic SQL access of database table &2 | The short text describes the object sufficiently | |
20 | 100 | ****** Version Management | The short text describes the object sufficiently | |
21 | 101 | Version object has no inactive version | The short text describes the object sufficiently | |
22 | 102 | Assign error (source field &1, field symbol &2) | The short text describes the object sufficiently | |
23 | 103 | No valid version exists at time-spot &1 (tech. &2) | The short text describes the object sufficiently | |
24 | 104 | Object does not exist on the database; no read generation is possible | The short text describes the object sufficiently | |
25 | 105 | Error in versioning; note following messages | The short text describes the object sufficiently | |
26 | 106 | Cannot resolve database table &1 | The short text describes the object sufficiently | |
27 | 107 | Error in SQL statement | The short text describes the object sufficiently | |
28 | 108 | Database key is not filled | The short text describes the object sufficiently | |
29 | 111 | No effectively valid version exists on date &1 | The short text describes the object sufficiently | |
30 | 112 | No effectively valid version at technical time-spot &1 | The short text describes the object sufficiently | |
31 | 120 | Error while assigning general type &1 to standard agreement | Space: object requires documentation | |
32 | 121 | Effective validity of agreement &1 of type &2 (&3) is too short | The short text describes the object sufficiently | |
33 | 124 | Date &1 is not allowed for this process | The short text describes the object sufficiently | |
34 | 130 | ***** Text Class | The short text describes the object sufficiently | |
35 | 131 | No key data | The short text describes the object sufficiently | |
36 | 132 | Text does not exist on the database | The short text describes the object sufficiently | |
37 | 133 | No control data found in table DD03L for text table &1 | The short text describes the object sufficiently | |
38 | 134 | Key for long text is too long | The short text describes the object sufficiently | |
39 | 140 | *** Messages from Customizing | The short text describes the object sufficiently | |
40 | 141 | No implementation exists for context &1 | The short text describes the object sufficiently | |
41 | 142 | No control data for standard contract exists for ICM application &1 | The short text describes the object sufficiently | |
42 | 143 | Cannot determine domain for table &1 field &2 | The short text describes the object sufficiently | |
43 | 144 | Cannot determine domain for data element &1 | The short text describes the object sufficiently | |
44 | 145 | No domain &1 exists | The short text describes the object sufficiently | |
45 | 146 | Value &1 for domain &2 is not allowed | The short text describes the object sufficiently | |
46 | 147 | Contract type &1 does not exist | The short text describes the object sufficiently | |
47 | 148 | No agreement types are assigned to contract type &1 in application &2 | The short text describes the object sufficiently | |
48 | 149 | Agreement type &1 in application &2 is not assigned to contract type &3 | The short text describes the object sufficiently | |
49 | 150 | Agreement type &1 is not assigned to application &2 | The short text describes the object sufficiently | |
50 | 151 | No agreement types are assigned to application &1 | The short text describes the object sufficiently | |
51 | 152 | Choose a context | The short text describes the object sufficiently | |
52 | 153 | No transport application exists for application &1 | The short text describes the object sufficiently | |
53 | 156 | No active version of contract &1 exist on database | The short text describes the object sufficiently | |
54 | 200 | ************* Facade | The short text describes the object sufficiently | |
55 | 201 | Contract &1 already exists in application &2; it cannot be created again | The short text describes the object sufficiently | |
56 | 202 | Cannot generate object for contract &1 in application &2 | The short text describes the object sufficiently | |
57 | 203 | Error in log; Processing was canceled | The short text describes the object sufficiently | |
58 | 204 | Contract &1 does not exist in application &2; no read access possible | The short text describes the object sufficiently | |
59 | 205 | Contract &1 (appl. &2) is not in buffer; Open in editing mode | The short text describes the object sufficiently | |
60 | 206 | No application specified | The short text describes the object sufficiently | |
61 | 207 | Choose a template | The short text describes the object sufficiently | |
62 | 208 | Error while saving contract &1 (application &2) | The short text describes the object sufficiently | |
63 | 209 | Error while activating contract &1 (application &2) | The short text describes the object sufficiently | |
64 | 210 | Error while editing agreement assignment &1 (&2) in contract &3 | The short text describes the object sufficiently | |
65 | 211 | Error while editing descriptive text for contract &1 | The short text describes the object sufficiently | |
66 | 212 | Transferred version & is not valid | The short text describes the object sufficiently | |
67 | 213 | Either the version is inactive or inactive subobjects exist | The short text describes the object sufficiently | |
68 | 214 | Contract &1 (application &2) was activated | The short text describes the object sufficiently | |
69 | 215 | Wildcards characters ( *, ? ) are not allowed | The short text describes the object sufficiently | |
70 | 216 | You are not authorized to change standard contract &1 | The short text describes the object sufficiently | |
71 | 217 | Standard contract &1 does not exist | The short text describes the object sufficiently | |
72 | 218 | Standard contract &1 does not have the required validity period | The short text describes the object sufficiently | |
73 | 219 | Agreement &1/&2 does not have the required validity period | The short text describes the object sufficiently | |
74 | 220 | Standard contract &1 (appl. &2) is locked (transport request &3) | Space: object requires documentation | |
75 | 221 | Error in data consistency | The short text describes the object sufficiently | |
76 | 222 | Error while deleting ctr &1 (appl. &2); Note any subsequent messages | The short text describes the object sufficiently | |
77 | 223 | Error while ending ctr &1 (applic. &2); Note any subsequent messages | The short text describes the object sufficiently | |
78 | 224 | Standard contract &1 already exists; choose another ID | The short text describes the object sufficiently | |
79 | 225 | Standard contract &1 in application &2 has no inactive parts | The short text describes the object sufficiently | |
80 | 226 | Contract &1 (application &2) ends on &3 | The short text describes the object sufficiently | |
81 | 227 | Contract &1 (application &2) was deleted | The short text describes the object sufficiently | |
82 | 228 | &1 is not a valid date | The short text describes the object sufficiently | |
83 | 229 | No values for this selection in application &1 | The short text describes the object sufficiently | |
84 | 230 | You have no authorization for standard contract &1 (application &2) | The short text describes the object sufficiently | |
85 | 231 | Authorization check was called with initial parameters | The short text describes the object sufficiently | |
86 | 232 | You have no authorization for std contracts of contract type &1 (appl.&2) | The short text describes the object sufficiently | |
87 | 233 | You have no authorization for area &1 of standard contracts (appl. &2) | The short text describes the object sufficiently | |
88 | 234 | User in front end &1 is different from user in back end &2 | Space: object requires documentation | |
89 | 235 | The applications defined for the user are inconsistent | Space: object requires documentation | |
90 | 236 | Standard contracts cannot be changed in system &1 | Space: object requires documentation | |
91 | 237 | Rule characteristics cannot be changed in system &1 | Space: object requires documentation | |
92 | 238 | Error while checking system settings in the authorization check | The short text describes the object sufficiently | |
93 | 239 | No application is defined for user & | The short text describes the object sufficiently | |
94 | 240 | Agreement assignment &1 &2 was deleted | The short text describes the object sufficiently | |
95 | 241 | Cannot delete agreement assignment &1 &2 | The short text describes the object sufficiently | |
96 | 242 | Agreement type &1 is not allowed for method &2 | The short text describes the object sufficiently | |
97 | 243 | Error in Customizing (table &1, application &2) | The short text describes the object sufficiently | |
98 | 244 | Rule characteristics for contract &1 cannot be edited in this system (&2) | The short text describes the object sufficiently | |
99 | 245 | Cannot read data for standard contract &1 (application &2) | The short text describes the object sufficiently | |
100 | 246 | No agreement is assigned to agreement type &1 | The short text describes the object sufficiently | |
101 | 247 | Select a standard contract | The short text describes the object sufficiently | |
102 | 248 | Standard contract &1 (application &2) was imported | The short text describes the object sufficiently | |
103 | 249 | Contract &1 (application &2) was exported | The short text describes the object sufficiently | |
104 | 250 | Unexpected status of RFC layer: Object &1 in &2 | Space: object requires documentation | |
105 | 251 | Effective internal &1 - &2 is not allowed | The short text describes the object sufficiently | |
106 | 252 | Error while changing rule characteristics | The short text describes the object sufficiently | |
107 | 253 | No rule characteristics exist in Customizing for agreement rule &1 | The short text describes the object sufficiently | |
108 | 254 | Effective dates of contract &1 (application &2) were extended up to &3 | The short text describes the object sufficiently | |
109 | 255 | The system cannot continue the process | The short text describes the object sufficiently | |
110 | 256 | Inactive aspects of contract &1 (application &2) were deleted | The short text describes the object sufficiently | |
111 | 257 | No authorization for &3 standard contract &1 (application &2) | The short text describes the object sufficiently | |
112 | 258 | Choose the change interval within the contract validity | The short text describes the object sufficiently | |
113 | 259 | Contract has inactive aspects: Only change interval &1 to &2 is possible | Space: object requires documentation | |
114 | 260 | Contract &1 is (partially) inactive; no termination is possible | Space: object requires documentation | |
115 | 261 | Contract &1 contains functional inconsistencies; it cannot be activated | Space: object requires documentation | |
116 | 262 | Agreement &1 (type &2: &3) is incorrect; no rule charas can be edited | The short text describes the object sufficiently | |
117 | 263 | You have not changed any values | The short text describes the object sufficiently | |
118 | 264 | Cannot determine application for user & | The short text describes the object sufficiently | |
119 | 265 | No event was entered for agreement type &1 (application &2) | Space: object requires documentation | |
120 | 266 | Contract is already valid at time-spot &1; moving forward is not possible | The short text describes the object sufficiently | |
121 | 267 | Contract &1 is (partially) inactive; moving forward is not possible | The short text describes the object sufficiently | |
122 | 268 | Error while moving forward contract &1; changes are not activated | The short text describes the object sufficiently | |
123 | 269 | Extended date &1 is too short: extension of contract &2 is not possible | The short text describes the object sufficiently | |
124 | 270 | Contract &1 is (partially) inactive; it cannot be extended | The short text describes the object sufficiently | |
125 | 271 | Error while extending contract &1; changes were not activated | The short text describes the object sufficiently | |
126 | 272 | Contract &1 (application &2) was moved forward to &3 | The short text describes the object sufficiently | |
127 | 273 | Error while casting of exception &1 | The short text describes the object sufficiently | |
128 | 274 | Contract &1 (application &2) was saved | The short text describes the object sufficiently | |
129 | 275 | Contract starts &1; ending contract on &2 is not possible | The short text describes the object sufficiently | |
130 | 276 | Contract end &1; ending contract on &2 is not possible | The short text describes the object sufficiently | |
131 | 277 | Entries exist, as parked | The short text describes the object sufficiently | |
132 | 278 | Contract &1 (application &2) was saved as parked version | The short text describes the object sufficiently | |
133 | 279 | More than one calculation tool exists in same agreement | The short text describes the object sufficiently | |
134 | 280 | No condition records have been maintained | The short text describes the object sufficiently | |
135 | 281 | No entry point determined for determination | The short text describes the object sufficiently | |
136 | 282 | Cannot read determination mode | The short text describes the object sufficiently | |
137 | 283 | Sample contract &1 has no remuneration type | The short text describes the object sufficiently | |
138 | 284 | No LOS tool found | The short text describes the object sufficiently | |
139 | 285 | More than one decision for remuneration type table &1 | The short text describes the object sufficiently |
History
Last changed on/by | 20100310 | SAP | |
SAP Release Created in | 700 |