SAP ABAP Message Class VC (SD Customizing)
Basic Data
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ VS0C (Package) Customizing R/3 Sales and Distribution master data
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ VS0C (Package) Customizing R/3 Sales and Distribution master data
Attributes
Message class | VC | |
Short Description | SD Customizing | |
Changed On | 20110908 | |
Last Changed At | 172038 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 000 | ******* 001-009 : hierarchical display of product hierarchy ******* | ||
2 | 001 | The product hierarchy is too long, please shorten it | ||
3 | 002 | Definition of hierarchy levels for the product hierarchy is not valid | ||
4 | 003 | Please enter a product hierarchy without empty groups | ||
5 | 004 | Please maintain the Group definition & (level: &) | ||
6 | 005 | Please select the entry to be copied | ||
7 | 006 | Select one entry only | ||
8 | 007 | First delete the dependent subgroups for hierarchy & | ||
9 | 008 | You must select a line for this function | ||
10 | 009 | Country & in shipping point & and country & in the address do not match | ||
11 | 010 | 'Item rel. for delivery' only allowed from item categories A and B | Space: object requires documentation | |
12 | 011 | Check the country key for the address | Space: object requires documentation | |
13 | 012 | There are no hierarchy nodes available for display! | Space: object requires documentation | |
14 | 013 | Specify restrictions for nodes (or country) | Space: object requires documentation | |
15 | 014 | ******** 015-099: Customer hierarchy ********************************** | ||
16 | 015 | You have no authorization to change hierarchy data | Space: object requires documentation | |
17 | 016 | You have no authorization to display hierarchy data | Space: object requires documentation | |
18 | 020 | ******* 021-099 : Customer hierarchy ***** | ||
19 | 021 | Sales area & & & is not defined for customer | ||
20 | 022 | Higher-level sales area & & & not defined for customer | ||
21 | 023 | Specify dependent and higher-level sales area | ||
22 | 024 | You only have authorization for displaying class & | ||
23 | 025 | You have no authorization for Classification & | ||
24 | 026 | Data can only be displayed because it is blocked by another user | ||
25 | 027 | System error blocking Table & | ||
26 | 028 | Data has been saved | ||
27 | 029 | Hierarchy type &: There are no active assignments for & | ||
28 | 030 | No errors were found in the assignments | ||
29 | 031 | Inconsistent sales areas cannot be assigned | ||
30 | 032 | Errors have been found in the assignments | ||
31 | 033 | No assignments have been changed | ||
32 | 034 | Error inserting Assignment & | ||
33 | 035 | Error deleting Assignment & | ||
34 | 036 | Hierarchy type is missing: Assignments cannot be made | ||
35 | 037 | Error updating Assignment & | ||
36 | 038 | Node cannot be deleted: invalid assignments would occur | ||
37 | 039 | Customer & for Sales area & & & does not exist | ||
38 | 040 | Validity date is missing: Hierarchy will be determined for today's date | ||
39 | 041 | Selection date lies in the past: Data will only be displayed | ||
40 | 042 | Customer & has not been created | ||
41 | 043 | Assignment of customer & to & is not defined | ||
42 | 044 | Sales area (VKORG/VTWEG/SPART) is incomplete | ||
43 | 045 | Sales area without customer number is not defined | ||
44 | 046 | Specify customer number | ||
45 | 047 | Assignment cannot be made: Higher-level customer & does not exist | ||
46 | 048 | Assignment of sales areas is not defined (THIOZ) | ||
47 | 049 | Assignment cannot be made: Higher-level sales area is incomplete | ||
48 | 050 | Valid-from date cannot lie in the past | ||
49 | 051 | Validity period is not allowed (From-date lies after the to-date) | ||
50 | 052 | The assignment is also active outside of the given time period | ||
51 | 053 | The assignment is already active in the given time period | ||
52 | 054 | Different higher-level assignments exist outside of the given time period | ||
53 | 055 | Incorrect assignments cannot be processed | ||
54 | 056 | Select hierarchy node | ||
55 | 057 | Assignment not possible: Customer & does not exist | ||
56 | 058 | Node & will be assigned to the same level | ||
57 | 059 | Select hierarchy header nodes for higher-level assignment | ||
58 | 060 | Selected sub-hierarchy contains all nodes and cannot be extended | ||
59 | 061 | Nodes cannot be added: unpermitted assignments would occur | ||
60 | 062 | Hierarchy contains no allowed alternative higher-level assignments | ||
61 | 063 | Higher-level node already maintained as a subordinate node | ||
62 | 064 | Assigned node is also a higher-level node | ||
63 | 065 | You cannot assign node to itself | ||
64 | 066 | Assignment has different attributes outside of the given time period | ||
65 | 067 | No authorization for displaying customers | ||
66 | 068 | No authorization for maintaining customers | ||
67 | 069 | No display authorization for Customer & in Sales area & & & | ||
68 | 070 | No maintenance authorization for Customer & in Sales area & & & | ||
69 | 071 | Partner determination error: Function not possible | ||
70 | 072 | Customer & is not created for Sales area & & & | ||
71 | 073 | There are no hierarchy nodes to be displayed | ||
72 | 074 | Function not possible: Maximum number of hierarchy steps (26) exceeded | ||
73 | 075 | Lowest hierarchy level reached (26): lower steps will be ignored | ||
74 | 076 | Hierarchy node cannot be removed as invalid assignments would arise | ||
75 | 077 | Selected hierarchy node is a header node: subhierarchy cannot be removed | ||
76 | 078 | Select incorrect hierarchy nodes | ||
77 | 079 | Pricing and rebate indicators updated | ||
78 | 080 | Attributes (pricing, rebate) are up-to-date for all assignments | ||
79 | 081 | Date cannot be changed (inconsistent validity periods) | ||
80 | 082 | Hierarchy type & is not defined | ||
81 | 083 | Node & is not active or not available for selection date | ||
82 | 084 | Node & is not available in the hierarchy | ||
83 | 085 | Hierarchy level & cannot be transferred due to inconsistencies | ||
84 | 086 | Hierarchy level assignment(s) updated | ||
85 | 087 | Hierarchy level assignment not updated or not updated for all points | ||
86 | 088 | Assignment not allowed: incorrect hierarchy structure assignment | ||
87 | 089 | 'Reassigning' can lead to inconsistencies in the hierarchy lvl assignmnt | ||
88 | 090 | Initial Date Limit(s): a new validity period has been proposed | ||
89 | 091 | Existing assignments for new nodes are being checked. | ||
90 | 092 | Node & & & & cannot be allocated, so it has not been selected | ||
91 | 093 | Assign. can only be displayed: transportation points & & & & not selected | ||
92 | 094 | Processing subtree for nodes & & & & not possible | ||
93 | 095 | Processing nodes & & & & not possible because not selected | ||
94 | 096 | Selection date is in the past: Please select new date | ||
95 | 097 | Error when posting the customer hierarchy data | ||
96 | 098 | Please specify selected nodes for node-specific display | ||
97 | 100 | Sales document types control | ||
98 | 101 | Saving is not necessary: no changes were made | ||
99 | 102 | Parameters for Document type & & have been changed | ||
100 | 103 | Document type & & created | ||
101 | 104 | Error & blocking &: & & | ||
102 | 105 | Document & already exists | ||
103 | 106 | Item category & changed | ||
104 | 107 | Error & changing &: & & | ||
105 | 108 | Error & planning &: & & | ||
106 | 109 | Error & deleting &: & & | ||
107 | 110 | New schedule line categories should begin with 'Z' | ||
108 | 111 | Combination not allowed | ||
109 | 112 | Item usage 'TEXT' is only allowed for item category group 'Blank' | ||
110 | 113 | Table & cannot be blocked | ||
111 | 114 | Document type & & deleted | ||
112 | 115 | Item category & & deleted | ||
113 | 116 | Schedule line category & & deleted | ||
114 | 117 | Default indicator for & & & & cannot be reset | ||
115 | 118 | The new default item category for & & & is & | ||
116 | 119 | The new default schedule line category for & & is & | ||
117 | 120 | Default indicator for & & & cannot be reset | ||
118 | 121 | The new default item category for & & is & | ||
119 | 122 | Deletion unnecessary: no assignments exist | ||
120 | 123 | Enter a usage for structure configuration for BOM explosion | ||
121 | 124 | Internal error creating assignment table: Item categ & (ret code &) | ||
122 | 125 | No changes made to item category assignments | ||
123 | 126 | Changed item category assignments saved | ||
124 | 127 | Partner group & does not contain any payers who cannot be changed | ||
125 | 128 | Entry & & & missing in table & | ||
126 | 129 | Item usage must be specified for item category group 'Blank' | ||
127 | 130 | Defaults for Item category & & changed | ||
128 | 131 | Customer-specific document types should begin with 'Z or Y' | ||
129 | 132 | Customer-specific item categories should begin with 'Z or Y' | ||
130 | 133 | Item category & already exists | ||
131 | 134 | Item category & & has been created | ||
132 | 135 | No changes made to the schedule line category assignments | ||
133 | 136 | Changes to schedule line category assignments have been saved | ||
134 | 137 | System blocking error for Table & | ||
135 | 138 | If a storage location is required, a batch check must be carried out | ||
136 | 139 | Related tables have not been transferred into the transfer order | Space: object requires documentation | |
137 | 140 | The selected table entries have been transferred to correction | ||
138 | 141 | A condition type's access sequence in the pricing procedure is incorrect | ||
139 | 142 | Enter item category | Space: object requires documentation | |
140 | 143 | An assignment for & already exists | ||
141 | 144 | Item category & is not allowed as a higher-level item category | ||
142 | 145 | Possible entries can only be displayed once the doc.type has been entered | ||
143 | 146 | Possible entries can only be displayed if a matl item category exists | ||
144 | 147 | Schedule line category & deleted from Table TVEP: please enter it again | ||
145 | 148 | Defaults for schedule line category & & changed | ||
146 | 149 | Schedule line category & & has been created | ||
147 | 150 | Schedule line category & already exists | ||
148 | 151 | Availability check without transfer of requirements is not allowed | ||
149 | 152 | Only condition types used for 'Pricing' are allowed | ||
150 | 153 | The entry & & cannot be deleted | ||
151 | 154 | No assignment possible as business data are not allowed | ||
152 | 155 | Deactivation not possible as billing plan is assigned | ||
153 | 156 | Billing plan only possible if business data active at item | ||
154 | 157 | The sales document indicator & is not allowed | Space: object requires documentation | |
155 | 158 | Item categories 7, J, T and g are provided for deliveries | Space: object requires documentation | |
156 | 159 | The date proposal is not allowed for delivery orders | Space: object requires documentation | |
157 | 160 | Enter a condition for the individual items overall | Space: object requires documentation | |
158 | 161 | The conditions must be different | Space: object requires documentation | |
159 | 162 | Document type & is not allowed as an alternative sales document type | Space: object requires documentation | |
160 | 163 | Alternative sales document type & is the same as current document type | Space: object requires documentation | |
161 | 164 | No allowed alternative order types could be determined | Space: object requires documentation | |
162 | 165 | The system status '&' is not available. | Space: object requires documentation | |
163 | 166 | The user status '&' for the diagram '&' is not available. | Space: object requires documentation | |
164 | 167 | Please maintain at first with number '&'. | Space: object requires documentation | |
165 | 168 | Delivery item numbers could be too big | Space: object requires documentation | |
166 | 169 | Enter schedule line category | Space: object requires documentation | |
167 | 170 | Country and transportation zone copied from the address data | Space: object requires documentation | |
168 | 171 | Address data maintenance only possible in the detail screen | Space: object requires documentation | |
169 | 172 | External capacity planning is not allowed for item category &1 | The short text describes the object sufficiently | |
170 | 200 | Text control | ||
171 | 201 | Please select a text object | ||
172 | 202 | You can only select one text object | ||
173 | 203 | System error occurred reading Internal table ( & ) | ||
174 | 204 | The entry already exists | ||
175 | 205 | Text determination procedure & has not been specified | ||
176 | 206 | Sales document type & does not exist | ||
177 | 207 | System error posting an internal table ( & ) | ||
178 | 208 | Access sequence & does not exist | ||
179 | 209 | Item category & does not exist | ||
180 | 210 | Delivery type & does not exist | ||
181 | 211 | Billing type & does not exist | ||
182 | 212 | Account group & does not exist | ||
183 | 213 | Text type & not yet created | Space: object requires documentation | |
184 | 214 | The language must be clearly specified | ||
185 | 215 | Include & does not exist | ||
186 | 216 | No access sequences can be defined for text object '&' | Space: object requires documentation | |
187 | 217 | Only text types can be defined for contact persons | ||
188 | 218 | No separate text procedures can be defined for text object '&' | Space: object requires documentation | |
189 | 219 | Deletion not allowed (text ID & used in procedure &, client &) | Space: object requires documentation | |
190 | 220 | Only special text objects are allowed | ||
191 | 221 | The language does not come from the partner function AG for MVKE | ||
192 | 222 | This combination (&,&) already exists | ||
193 | 223 | Language & is not defined | ||
194 | 224 | Partner function & not defined | ||
195 | 225 | This combination (&,&) is not defined | ||
196 | 226 | Access generated | ||
197 | 227 | Text determination procedure & already exists | ||
198 | 228 | Enter a number for the text determination procedure | ||
199 | 229 | Access sequence & already exists | ||
200 | 230 | Enter a number for the access sequence | ||
201 | 231 | Copying control module & does not exist | ||
202 | 232 | Text ID & in Procedure & & does not exist in TTXID | ||
203 | 233 | Text determination procedure & does not exist in Table & | ||
204 | 234 | Text ID & is already present in the text determination procedure | Space: object requires documentation | |
205 | 235 | A unit must be assigned to the time period entered | ||
206 | 236 | Please maintain the unit only in the existing time period | ||
207 | 237 | Calendar ID and time period cannot be maintained at the same time | ||
208 | 238 | Calendar ID and time period cannot be maintained at the same time | ||
209 | 239 | The cancellation period can only be assigned a positive value | ||
210 | 240 | Deleting not allowed: the entry is being used in another position | ||
211 | 241 | There are no pop-up windows for billing document texts | ||
212 | 242 | The FORM routine & is not active or not available | ||
213 | 243 | 'Last of month' field and calendar ID cannot be maintained at one time | ||
214 | 244 | The rule for the contract start date refers to the contract start date | ||
215 | 245 | The rule for the contract end date refers to the contract end date | ||
216 | 246 | The cancellation base date cannot result from the contract end date | ||
217 | 247 | Please process table entry transfer manually | ||
218 | 248 | Text type & is not defined for text determination procedure & | Space: object requires documentation | |
219 | 249 | No text edit control possible for order type & | Space: object requires documentation | |
220 | 250 | Partner control | ||
221 | 251 | Please select a partner object | ||
222 | 252 | You have selected more than one object: please select only one | ||
223 | 253 | System error occurred reading Internal table ( & ) | ||
224 | 254 | The entry already exists | ||
225 | 255 | Partner determination procedure & does not exist | ||
226 | 256 | Sales document type & does not exist | ||
227 | 257 | System error posting an internal table ( & ) | ||
228 | 258 | Partner determ. procedure & already used in partner object & | ||
229 | 259 | Item category & does not exist | ||
230 | 260 | Transport into delivery system is only possible using & | ||
231 | 261 | Maintaining new partner functions in & is only possible in central functn | ||
232 | 262 | Please process table entry transfer manually | ||
233 | 263 | Partner function & has not been created | ||
234 | 264 | Partner function & cannot be used for partner procedures | ||
235 | 265 | Only customer partner functions can be defined as sources | ||
236 | 266 | Origin & is not provided for partner type & | Space: object requires documentation | |
237 | 267 | Partner function does not exist in the customer partner determtn procdr | ||
238 | 268 | Origin & is not permitted for partner function & | Space: object requires documentation | |
239 | 269 | Deletion not allowed: Function & is used elsewhere | ||
240 | 270 | Partner determination procedure & not defined for customer master | ||
241 | 271 | Partner determination procedure & not defined for sales document headers | ||
242 | 272 | Partner determination procedure & not defined for sales document items | ||
243 | 273 | Partner determination procedure & is not defined for deliveries | ||
244 | 274 | Partner determination procedure & not defined for billing header(s) | ||
245 | 275 | Partner determination procedure & is not defined for billing items | ||
246 | 276 | Partner determination procedure & is not defined for sales activities | ||
247 | 277 | Partner determination procedure & is not available for shipments | Space: object requires documentation | |
248 | 278 | Shipping type & not yet created | Space: object requires documentation | |
249 | 279 | Shipments must have a forwarding agent | Space: object requires documentation | |
250 | 280 | Sales documents require a sold-to party that cannot be changed | ||
251 | 281 | Sales document items may not have a sold-to party | ||
252 | 282 | Deliveries require a ship-to party that cannot be changed | ||
253 | 283 | Billing items may not have a payer | ||
254 | 284 | A payer which cannot be changed is required for billing documents | ||
255 | 285 | 'Ship-To Party' is a mandatory partner function for outbound deliveries | Space: object requires documentation | |
256 | 290 | Assignment only makes sense for customer functions | ||
257 | 291 | Another partner function has already been converted to & | ||
258 | 292 | Function & is not used in Procedure & | ||
259 | 293 | Function & is a higher-level function than Function & | ||
260 | 294 | Partner function & does not exist | ||
261 | 295 | Object & cannot be blocked: It will be displayed | ||
262 | 296 | Entries saved | ||
263 | 297 | Partner & is not defined | ||
264 | 298 | Please maintain the field 'Sequence' | Space: object requires documentation | |
265 | 299 | Sort sequences of previously determined partners are inconsistent | Space: object requires documentation | |
266 | 300 | Conditions, Pricing | ||
267 | 301 | Function & does not exist | ||
268 | 302 | Initialization error for View & | ||
269 | 303 | Maintenance error for view & | ||
270 | 304 | Both groups need to be defined | ||
271 | 305 | Procedure & requires two groups | ||
272 | 306 | Date function no available for partner type & | Space: object requires documentation | |
273 | 310 | Accrual billing document type & does not exist | ||
274 | 311 | Only accrual billing document types w/o cancellation billing type allowed | ||
275 | 319 | Number range & is an internal number range | Space: object requires documentation | |
276 | 320 | Number range & is not available | ||
277 | 321 | Number range & is an external number range | ||
278 | 322 | The most recently used billing date is & | ||
279 | 323 | Every date in the billing due list is less than & | ||
280 | 350 | Copy control, Graphics | ||
281 | 351 | Table & is blocked. It can only be displayed. | ||
282 | 352 | ABEND due to system error | ||
283 | 400 | Incompletion log | ||
284 | 401 | Procedure & does not exist | ||
285 | 402 | Procedure & already exists | ||
286 | 403 | Procedure & saved | ||
287 | 404 | Procedure & deleted | ||
288 | 405 | Procedure & referred to elsewhere | ||
289 | 406 | & | ||
290 | 407 | Procedure & is already assigned to item category & | ||
291 | 408 | Procedure & is already assigned to Schedule line category & | ||
292 | 409 | Procedure & is already assigned to Partner function & | ||
293 | 410 | Procedure & already has texts assigned to it | ||
294 | 411 | Procedure & is already assigned to Sales document type & | ||
295 | 412 | Procedure & will be deleted when you press 'Enter' | ||
296 | 413 | Select one object only for processing | ||
297 | 414 | Enter an incompletion procedure for editing | ||
298 | 415 | Incompletion procedure & is already defined for another object | ||
299 | 416 | Enter an incompletion procedure | ||
300 | 417 | Incompletion procedure & is not defined for sales document types | ||
301 | 418 | Incompletion procedure & is not defined for items | ||
302 | 419 | Incompletion procedure & is not defined for schedule lines | ||
303 | 420 | Changes will not be saved when you press 'Enter' | ||
304 | 421 | Procedure is still being used: Object & cannot be blocked | ||
305 | 422 | Procedure is still being used: usages will be deleted | ||
306 | 423 | Incompletion procedure & is not defined for sales activities | ||
307 | 424 | Status group & does not exist | ||
308 | 449 | * 450-499 Direct-Input Cusotmer | Space: object requires documentation | |
309 | 450 | Currency & does not exist (TCURC) | Space: object requires documentation | |
310 | 451 | Currency & is no longer valid (TCURC) | Space: object requires documentation | |
311 | 452 | You do not have authorization for mass changes of currencies | Space: object requires documentation | |
312 | 453 | No customer data found for the selection criteria | Space: object requires documentation | |
313 | 454 | The new currency must differ from the old currency | Space: object requires documentation | |
314 | 455 | The selected customers could not be blocked | Space: object requires documentation | |
315 | 456 | Select customers and / or sales organizations | Space: object requires documentation | |
316 | 457 | Conversion to currency & successfully completed | Space: object requires documentation | |
317 | 458 | There are no data for currency conversion. | Space: object requires documentation | |
318 | 459 | There is no master data for currency conversion available. | Space: object requires documentation | |
319 | 460 | Currency conversion finished | Space: object requires documentation | |
320 | 461 | For non-specified vendors it is only possible to have an old currency | Space: object requires documentation | |
321 | 462 | Vendor & could not be blocked | Space: object requires documentation | |
322 | 463 | You can only enter an old currency if the customer is not registered | Space: object requires documentation | |
323 | 500 | Route definition/determination | ||
324 | 501 | Leg & and leg & are not compatible | ||
325 | 502 | Leg & is not defined | ||
326 | 503 | Leg & is already part of the route | ||
327 | 504 | Leg & already exists | ||
328 | 505 | Legs are not compatible - please correct | ||
329 | 506 | Warning: Incorrect leg saved in the route | ||
330 | 507 | Warning: No shipping conditions exist | ||
331 | 508 | Warning: No transportation groups exist | ||
332 | 509 | Shipping point & is not defined | ||
333 | 510 | Shipping point &2 cannot be used for plant &1 | Space: object requires documentation | |
334 | 511 | Office of exit & is not specified | ||
335 | 512 | Please process table entry transfer manually | ||
336 | 513 | No routes found for the selection specified. | ||
337 | 551 | Maintain Table TFRM | ||
338 | 552 | Only group numbers up to 99 are allowed for routines in this class | ||
339 | 553 | Text module & could not be created | ||
340 | 554 | Place the cursor on a valid group number | ||
341 | 555 | There is no long text | ||
342 | 556 | All routines have been successfully activated | ||
343 | 557 | You can only delete deactivated routines | ||
344 | 558 | Include number & either does not exist or is not active | ||
345 | 559 | You can only make changes in client 0 | ||
346 | 560 | You do not have the authorization to create SAP standard routines | ||
347 | 561 | TADIR entry could not be created | ||
348 | 570 | Choose an entry | Space: object requires documentation | |
349 | 590 | Text modules have been changed to document text modules | ||
350 | 600 | ******* 500-550 : EDI in SD ****************************************** | ||
351 | 601 | New key assignment for partner type & has not been maintained | ||
352 | 602 | Enter a customer number | ||
353 | 603 | Standard partner function & cannot be deleted | ||
354 | 604 | Partner function & is not defined for use in EDI | ||
355 | 650 | ************************ Contracts processing *************************** | ||
356 | 651 | Maintain either percentage rate or percentage rate table access | ||
357 | 652 | Please maintain condition type | ||
358 | 653 | Please maintain the baseline date rule for the price increase cycle | ||
359 | 654 | Please maintain the price increase cycle | ||
360 | 700 | ******************** Product hierarchy 700 - 720 ************************ | ||
361 | 701 | The product hierarchy structure has an unallowable number of levels | ||
362 | 702 | The template should contain only ' ' or separators other than ' ' | ||
363 | 703 | The template is smaller than a possible value entry | ||
364 | 704 | Node is followed by spaces: not allowed | ||
365 | 705 | Please create the preceding node first | ||
366 | 706 | A product hierarchy node cannot contain spaces | ||
367 | 707 | The node cannot be inserted | ||
368 | 708 | Please delete the succeeding node first | ||
369 | 709 | You have created too many levels (a maximum of 9 levels is allowed) | ||
370 | 710 | The data element must have the prefix 'PRODH' | ||
371 | 711 | The node includes editing mask characters | ||
372 | 712 | The mask is too long, layout does not look good | ||
373 | 713 | Deletions will be saved immediately to the data bank | ||
374 | 714 | The product hierarchy struture length is &, but must be & | ||
375 | 715 | Account assignment group &1 does not exist | ||
376 | 721 | ************* Scheduled shipping date 721 - 750 ************************* | ||
377 | 722 | The function is not possible without a number range | ||
378 | 751 | ************* Potential planning 751 - 770 ****************************** | ||
379 | 752 | Client & is not a competitor | ||
380 | 753 | Please maintain routine POTENTIAL_PROT_SET in program & | ||
381 | 754 | Select a valid line | ||
382 | 771 | ************* Repairs processing 771-820 ******************************** | Space: object requires documentation | |
383 | 772 | You must also enter a procedure for the point in time | Space: object requires documentation | |
384 | 773 | A repair indicator can only be assigned once per point in time | Space: object requires documentation | |
385 | 774 | Repair indicator &2 is not required at time &1 | Space: object requires documentation | |
386 | 775 | Procedure -&1- only possible manually | Space: object requires documentation | |
387 | 776 | Manual flag only possible in combination with the report back indicator | Space: object requires documentation | |
388 | 800 | No value help supported for this field | Space: object requires documentation | |
389 | 801 | Access sequence exists for text & in text determination procedure & | Space: object requires documentation | |
390 | 802 | Text edit control does not work for & ! | Space: object requires documentation | |
391 | 803 | Pricing date proposal C only needed if contract data are allowed | Space: object requires documentation | |
392 | 804 | Valid from date is proposed from the contract data | Space: object requires documentation | |
393 | 821 | ****** _Reference det. for consumer master 821 - 850 ****************** | Space: object requires documentation | |
394 | 822 | No company code exists for sales area &1 &2 &3 | Space: object requires documentation | |
395 | 823 | Problems when executing out dialog boxes | Space: object requires documentation | |
396 | 824 | Problems when reading the sales area data | Space: object requires documentation | |
397 | 825 | Problems when adding a reference customer to the company code | Space: object requires documentation | |
398 | 826 | Problems when reading the customer master data | Space: object requires documentation | |
399 | 827 | The reference customer & cannot be a consumer | Space: object requires documentation | |
400 | 828 | Company code & does not exist | Space: object requires documentation | |
401 | 829 | Company code & does not exist with reference customer & | Space: object requires documentation | |
402 | 830 | Problems when reading the sales area data | Space: object requires documentation | |
403 | 831 | No reference customer maintained | Space: object requires documentation | |
404 | 832 | Reference customer &2 already exists for company code &1 | Space: object requires documentation | |
405 | 833 | Enter the sales organization | Space: object requires documentation | |
406 | 834 | Enter the distribution channel | Space: object requires documentation | |
407 | 835 | Customer &1 for sls org. &2 dist. chnl &3 division &4 not created | Space: object requires documentation | |
408 | 836 | Problems deleting the sales area data | Space: object requires documentation | |
409 | 837 | Problems deleting the company code data | Space: object requires documentation | |
410 | 838 | Reference customer is not current reference customer ->not deleted | Space: object requires documentation | |
411 | 839 | Problems inserting the reference customers for the sales area | Space: object requires documentation | |
412 | 840 | At least one sales area should be maintained for reference customer & | Space: object requires documentation | |
413 | 841 | At least one company code must be maintained for reference customer & | Space: object requires documentation | |
414 | 842 | Reference customer & does not exist | Space: object requires documentation | |
415 | 843 | Reference customer & deleted | Space: object requires documentation | |
416 | 844 | Reference customer & created | Space: object requires documentation | |
417 | 845 | A reference customer has been created | Space: object requires documentation | |
418 | 847 | Reference customer & will not be deleted | Space: object requires documentation | |
419 | 848 | & can not be used as a reference customer | Space: object requires documentation | |
420 | 849 | Transaction VOTX is outdated. Use VOTXN instead | Space: object requires documentation | |
421 | 860 | Text ID & already exists. Enter a new text ID | Space: object requires documentation | |
422 | 861 | Run number & already exists. Enter a new run number | Space: object requires documentation | |
423 | 862 | Enter both run number and text ID | Space: object requires documentation | |
424 | 863 | First enter a run number and a text ID | Space: object requires documentation | |
425 | 864 | Enter a text ID | Space: object requires documentation | |
426 | 865 | Enter a run number | Space: object requires documentation |
History
Last changed on/by | 20110908 | SAP | |
SAP Release Created in |