SAP ABAP Message Class VT (SD Tables)
Basic Data
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷ CRM-BF (Application Component) Basic Functions
⤷ VA0C (Package) Customizing R/3 sales
⤷ CRM-BF (Application Component) Basic Functions
⤷ VA0C (Package) Customizing R/3 sales
Attributes
Message class | VT | |
Short Description | SD Tables | |
Changed On | 20140121 | |
Last Changed At | 105429 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 000 | *** General messages for sales and distribution tables | ||
2 | 001 | Source = A forbids specification of subsequent screen group and panel | ||
3 | 002 | Source = & forbids specification of subsequent parameters | ||
4 | 003 | Source = & requires specification of subsequent parameters | ||
5 | 004 | Source = & allows only saving operations that are not negative | ||
6 | 005 | The storage operation '0' allowed for Source=A has been set | ||
7 | 006 | Source = & requires a subsequent FCode. Is BLANK allowed? | ||
8 | 007 | Source = F requires a FORM routine without subsequent parameters | ||
9 | 008 | Source was set on F because only one FORM routine was specified | ||
10 | 009 | Source = & not defined | ||
11 | 010 | Source = Z requires a storage operation not equal to 0 | ||
12 | 011 | Source = & allows only negative storage operations | Space: object requires documentation | |
13 | 012 | Please use transaction 'VFBS' to maintain next screen processing | Space: object requires documentation | |
14 | 013 | Maintaining this table is currently forbidden | Space: object requires documentation | |
15 | 014 | Substitution of serviceable item matl with service product not consistent | Space: object requires documentation | |
16 | 015 | For safety reasons deletion is only allowed in a work area | ||
17 | 016 | For safety reasons deletion is only allowed in a screen group | ||
18 | 017 | Changes were not adopted, because no correction was entered | ||
19 | 018 | Billing quantity G or H is not permitted for billing relevant M | Space: object requires documentation | |
20 | 020 | In language & the conversion & already exists for & | ||
21 | 021 | Sales document type & is not defined | Space: object requires documentation | |
22 | 022 | Order type '&' is not defined for sales area <'&','&','&'> | Space: object requires documentation | |
23 | 023 | Sales area conversion table has been updated | Space: object requires documentation | |
24 | 024 | System error when updating sales areas | Space: object requires documentation | |
25 | 099 | Required entry not made | Space: object requires documentation | |
26 | 100 | In table & there is no field & | ||
27 | 109 | No processing location specified | ||
28 | 110 | Only one of the & fields may be filled | ||
29 | 111 | Do not make multiple entries for the processing location | ||
30 | 112 | The screen in the function module requires the input of a routine | ||
31 | 120 | Transaction & code not defined | Space: object requires documentation | |
32 | 121 | Screen & does not exist | Space: object requires documentation | |
33 | 122 | Menu & not defined in TSTC | ||
34 | 160 | The entered number range & does not exist | ||
35 | 161 | Internal and external number ranges may not be identical | ||
36 | 162 | Number range & not defined for external number assignment | ||
37 | 163 | Number range & not defined for internal number assignment | ||
38 | 164 | Number range object & does not exist | ||
39 | 165 | Functional area is not possible for account assignment category &1 | Space: object requires documentation | |
40 | 200 | Transaction type & already exists | ||
41 | 269 | Account assignment category & has not been defined | Space: object requires documentation | |
42 | 300 | Sales organization & is not defined | Space: object requires documentation | |
43 | 301 | Dunning type & not defined in company code & | ||
44 | 302 | Table & could not be locked | ||
45 | 303 | Copying control module & newly created | ||
46 | 304 | Copying control module & successfully created | ||
47 | 305 | Copying control module & does not exist | ||
48 | 306 | Item category and classification type are defined | ||
49 | 307 | End of list screen has been reached | ||
50 | 308 | Beginning of list screen has been reached | ||
51 | 309 | New table entry generated | ||
52 | 310 | Sales document type & is not available | Space: object requires documentation | |
53 | 311 | Checking is in process: Entry & & & is missing from TVCPA | ||
54 | 312 | Check completed | ||
55 | 313 | Delivery type '&' is not available | Space: object requires documentation | |
56 | 314 | The text ID & already defined for this text group | ||
57 | 315 | Text object & does not have the text ID &. | ||
58 | 316 | Text object & not defined | ||
59 | 317 | Combination not allowed | ||
60 | 318 | Plant is already allocated to company code & | ||
61 | 319 | The combination (text object &, text ID &) is not defined | ||
62 | 320 | You can only enter one original language | ||
63 | 321 | The probability must be between 0 and 100% | ||
64 | 322 | A probability of < 100% is only allowed in inquiries and quotations | ||
65 | 323 | The combination of ( & , & ) is missing from Table TVKOV | ||
66 | 324 | The referenced distribution channel & cannot be converted | ||
67 | 325 | Schedule line category & is not defined | ||
68 | 326 | Output type & not defined | ||
69 | 327 | Distribution channel is proposed | ||
70 | 328 | Referenced sales org. & and distribution channel & do not exist | ||
71 | 329 | Referenced sales org & and division & do not exist | ||
72 | 330 | Referenced division & cannot be changed | ||
73 | 331 | Sales organization & does not exist | ||
74 | 332 | The reference sales organization & cannot be converted | ||
75 | 333 | Plant & is not defined | ||
76 | 334 | Please set the print parameters in Customizing | ||
77 | 335 | Sales areas are blocked by other users: You can only display them | ||
78 | 336 | System error: Blocking unsuccessful, can only be displayed | ||
79 | 337 | No addresses maintained up to now | ||
80 | 338 | Sales organization & is referenced by sales organiz.& | ||
81 | 339 | Distribution channel & is referenced by distribution channel & | ||
82 | 340 | Division & is referenced by division & | ||
83 | 341 | Distribution channel & is still required as a customer distrib. channel | ||
84 | 342 | Division & is still required as a customer division | ||
85 | 343 | The customer for inter-company billing missing in SOrg & | ||
86 | 344 | Organizational data for inter-company billing missing in plant & | ||
87 | 345 | SOrg belongs to CCode & and the plant to CCode & | ||
88 | 346 | Sales organization & is still required for conversion | ||
89 | 347 | Sales organization & is still used for division conversion | ||
90 | 348 | Sales organization & is still used for distribution channel conversion | ||
91 | 349 | Sales organization & is used for sales area conversion | ||
92 | 350 | Partner function & does not exist | ||
93 | 351 | Enter either a sales document or billing type only | ||
94 | 352 | The sales org. is part of company code &, plant & is part of comp.code & | ||
95 | 353 | The combination ( & , & ) is missing in TVKOS | ||
96 | 354 | Only enter an order type for assembly types '2' or '3' | Space: object requires documentation | |
97 | 355 | Component avail.check/dialog control only allowed for assembly processing | ||
98 | 356 | Order type $ is not defined | ||
99 | 357 | If necessary, enter a configuration strategy | ||
100 | 358 | A configuration strategy is not necessary when | ||
101 | 359 | Configuration strategy & is not defined in Table 476 | ||
102 | 360 | Manual application/alternative is only allowed for struct.scope = A/B | ||
103 | 361 | Order type $ contains category $ which is not allowed | ||
104 | 362 | Order type $ has external number assignment | ||
105 | 363 | Assembly requires assignment category E or D or valuated special stock | Space: object requires documentation | |
106 | 364 | Control for type matching is only allowed if scope of structure = D | ||
107 | 365 | Avail.and action f.configur.mats.only poss. when type matching is active | ||
108 | 366 | You need to enter an order type for assembly types '2' and '3' | Space: object requires documentation | |
109 | 367 | Enter either an assembly type or order change management only | Space: object requires documentation | |
110 | 368 | Sub-items for manual strategy are not supported | ||
111 | 369 | Account assignment category & has not been defined | ||
112 | 370 | In autom. single-segment planning, the transfer of requir. must be active | ||
113 | 371 | Autom. individual requ. planning requires an account assignment category | ||
114 | 372 | Account assignment category & does not result in make-to-order production | ||
115 | 373 | Assembly type '2' does not allow unit or product costing | ||
116 | 374 | Switching to assembly type &1 is not valid | ||
117 | 375 | Issue of a warning is not supported for product selection | ||
118 | 376 | The development class of condition table & & is local | ||
119 | 377 | Automatic calculation only possible if calculation is allowed | Space: object requires documentation | |
120 | 378 | Automatic calculation only possible with a calculation variant | Space: object requires documentation | |
121 | 379 | Calculation variant is not valid for automatic calculation | Space: object requires documentation | |
122 | 380 | Automatic costing is only valid for product costing | Space: object requires documentation | |
123 | 381 | The costing variant is not valid for this costing method | Space: object requires documentation | |
124 | 382 | Transfer of preliminary costing only permitted for stat. assembly | Space: object requires documentation | |
125 | 383 | Variant &2 has not been defined for transaction &1 | Space: object requires documentation | |
126 | 384 | Order type &1 is not permitted | Space: object requires documentation | |
127 | 385 | If default item cat. activated: Target billing type must be credit memo | Space: object requires documentation | |
128 | 386 | If default item category activated: Billing quantity must be E or F | Space: object requires documentation | |
129 | 387 | Only special stock with separate valuation can be marked. | Space: object requires documentation | |
130 | 388 | Condition type & can only be used once per country. | Space: object requires documentation | |
131 | 400 | The entry has been saved | ||
132 | 401 | Check the existing conversion for distribution channel and division | ||
133 | 402 | If configuration is copied, you are not permitted to explode BOM | Space: object requires documentation | |
134 | 500 | *** Conditions: Control tables *** | ||
135 | 501 | Maintain the item data | ||
136 | 502 | Maximum number of 999 accesses in module pool & already reached | ||
137 | 503 | Condition maintenance for application & has not been defined | ||
138 | 504 | Enter a subtotal between 1 and 7 for step & | ||
139 | 505 | Condition type & may only be used once | ||
140 | 506 | Table & is not defined | ||
141 | 507 | Defaults adopted from the Data Dictionary | ||
142 | 508 | Table & not defined | ||
143 | 509 | Field & not defined | ||
144 | 510 | Select a document field for & | Space: object requires documentation | |
145 | 511 | Data division (T685&) not defined for usage | ||
146 | 512 | The numeric constant entered is longer than the target field | ||
147 | 513 | Please do not set a source value for the initial value indicator | ||
148 | 514 | System error: Entry & missing from table & | ||
149 | 515 | System error: Entry & & & missing from table & | ||
150 | 516 | Please use transactions VK01, VK02 or VK03 | ||
151 | 517 | All access sequences successfully generated | ||
152 | 518 | Activate only between 0.00 and 8.00 | Space: object requires documentation | |
153 | 519 | Entry & & & missing in table & | ||
154 | 520 | Condition type & not defined | ||
155 | 521 | Usage & not defined | ||
156 | 522 | Application & not defined | ||
157 | 523 | Usage & and application & not defined | ||
158 | 524 | There are no access sequences to optimize | ||
159 | 525 | Requirement & not defined | Space: object requires documentation | |
160 | 526 | Formula & not defined | ||
161 | 527 | Condition type & is not defined | ||
162 | 528 | Item & is already listed. | ||
163 | 529 | Item & & is already listed | ||
164 | 530 | Error found in access sequence & | ||
165 | 531 | The condition types are being processed: They can only be displayed | ||
166 | 532 | Access sequences are being processed: They can only be displayed | ||
167 | 533 | Pricing procedures are being processed: They can only be displayed | ||
168 | 534 | All access sequences are already active | ||
169 | 535 | Unexpected FCODE = & | ||
170 | 536 | Referenced by pricing procedure &: Cannot be deleted | ||
171 | 537 | Referenced by access sequence &: Cannot be deleted | ||
172 | 538 | Referenced by condition type &: Cannot be deleted | ||
173 | 539 | Unit of measure & not defined | ||
174 | 540 | Please do not enter a unit of measure for a value scale | ||
175 | 541 | Access sequence & only reads the pre-step | ||
176 | 542 | Cursor not properly positioned on a condition type | ||
177 | 543 | There are no access sequences for condition type & | ||
178 | 544 | Access sequences defined by the user must begin with Y or Z | ||
179 | 545 | Please test with new entries only in module pool 'T' | ||
180 | 546 | Condition type & already listed | ||
181 | 547 | Initialization error for view & | ||
182 | 548 | Maintenance error for view & | ||
183 | 549 | Access sequence lies in the customer sector: It can only be displayed | ||
184 | 550 | Access sequence & is not defined | ||
185 | 551 | Procedure & is not defined | ||
186 | 552 | Enter a table | ||
187 | 553 | Account key & not defined | ||
188 | 554 | System error: Object could not be blocked | ||
189 | 555 | Enter a condition type | ||
190 | 556 | Access sequence & is within the SAP sector: It can only be displayed | ||
191 | 557 | SAP access sequences cannot begin with Y or Z | ||
192 | 558 | Please enter a module pool between 'A' and 'M' | ||
193 | 559 | Please enter a module pool between 'N' and 'Z'. | ||
194 | 560 | Output type & does not require any mail texts | ||
195 | 561 | A text already exists for output category &, language & | ||
196 | 562 | No text exists in language & for output & | ||
197 | 563 | An access sequence is not defined for the header condition | ||
198 | 564 | Access sequence & for output & is revoked | ||
199 | 565 | Tax determination procedure & does not exist | ||
200 | 566 | Do not use scale formulas for subsequent refunds | ||
201 | 567 | Output type & requires a message title | ||
202 | 568 | Access sequence & lies in the SAP sector. | ||
203 | 569 | Access sequence & lies in the customer sector. | ||
204 | 570 | Access sequences cannot be changed in the delivery system | ||
205 | 571 | Referenced by condition type & in client &: Cannot be deleted | ||
206 | 572 | %A No maintenance authorization for usage & application & | ||
207 | 573 | %A No display authorization for usage & application & | ||
208 | 574 | Enter a unit of measure | ||
209 | 575 | Group condition with calculat.type 'B' and grp.cond.routine not defined | ||
210 | 576 | Access sequence is not defined for condition category | ||
211 | 577 | GrpCndRoutine without rounding diff. not defined for calculation rule & | Space: object requires documentation | |
212 | 578 | Calculation & is not defined for application | ||
213 | 579 | Calculation type or scale basis is not defined for condition class | ||
214 | 580 | Calculation type or scale basis is not defined for group conditions | ||
215 | 581 | Scale basis and calculation type must be identical | ||
216 | 582 | Unit of measure & is not defined for scale basis | ||
217 | 583 | Billing quantity & is not defined for delivery-related billing | ||
218 | 584 | Billing quantity & is not defined for the pro forma invoice | ||
219 | 585 | Qty/value pos/neg & not defined for billing type & | ||
220 | 586 | Condition update is not defined for condition class & | ||
221 | 587 | Condition update is not defined for calculation type & | ||
222 | 588 | Data field "Quantity/Value pos/neg" has the value ' ' | ||
223 | 589 | '+' or '-' only allowed in connection with completion rule for item cat. | ||
224 | 590 | Be careful when using Pricing type & | ||
225 | 591 | Condition class & has not been designed for structure condition & | ||
226 | 592 | Calculation type & has not been designed for structure condition & | ||
227 | 593 | Structure condition & should not be a header condition | ||
228 | 594 | Group condition routines not designed for structure condition & | ||
229 | 595 | You cannot change values manually for structure condition & | ||
230 | 596 | Structure condition & does not have an access sequence | ||
231 | 597 | Structure condition & should not be a group condition | ||
232 | 598 | You cannot enter & manually for structure condition & | ||
233 | 599 | Cumulation condition & should be a statistical value | ||
234 | 600 | Sales function & & & not defined | ||
235 | 601 | Condition type & should be assigned to calculation type 36 | ||
236 | 602 | Structure condition & should be a group condition | ||
237 | 603 | Condition category & only valid for condition class & | ||
238 | 604 | Condition category & has not been desigend for structure condition & | ||
239 | 605 | You cannot specify a pricing procedure for condition category & | ||
240 | 606 | The Field From &1 must be smaller than the current level number &2 | ||
241 | 607 | The field To &1 must be smaller than the current level number &2 | ||
242 | 608 | For milestone billing, the system only allows pricing types D, G and K | Space: object requires documentation | |
243 | 609 | You should use the counter only for manual item conditions | ||
244 | 610 | Condition category & is not valid for condition class & | ||
245 | 611 | Unfavorable sequence of fields - Possible performance problems | Space: object requires documentation | |
246 | 612 | Exclusion group & does not only contain group conditions | Space: object requires documentation | |
247 | 613 | Inv. corr. requests with sls doc. cat. K must have pricing det. type 'E' | Space: object requires documentation | |
248 | 614 | During inv. correction requests, second item must be a debit memo item | Space: object requires documentation | |
249 | 615 | An invoice correction request must be created with ref. to an invoice | Space: object requires documentation | |
250 | 616 | Rounding difference is always settled for group cond. w/o grp key rout. | Space: object requires documentation | |
251 | 617 | Inv. corr. requests with sls doc cat L must have pricing det. type 'F' | Space: object requires documentation | |
252 | 618 | During inv. correction requests, first item must be a credit memo item | Space: object requires documentation | |
253 | 619 | Only characteristic ' ' and G can be used as price source | Space: object requires documentation | |
254 | 620 | Quantity/value pos/neg field must be ' ' for credit memos to billing docs | Space: object requires documentation | |
255 | 621 | The assignment and reference number fields must be ' ' or E | Space: object requires documentation | |
256 | 622 | Scale type 'D' cannot be used for group condition 'X' | Space: object requires documentation | |
257 | 623 | The system selects several records because they have the same evaluation | Space: object requires documentation | |
258 | 624 | Enter a priority for the field marked as free | Space: object requires documentation | |
259 | 625 | The same evaluation is not possible for accesses for volume-based rebates | Space: object requires documentation | |
260 | 626 | For rebates, each field must be relevant to the access | Space: object requires documentation | |
261 | 627 | A release block is not possible for condition class & | Space: object requires documentation | |
262 | 628 | Access type C is not defined for key fields | Space: object requires documentation | |
263 | 629 | Standard proposal for CTyp &1 Req = &2, Calfor = &3 Basfor = &4 | Space: object requires documentation | |
264 | 630 | Standard proposal for CTyp &1, Manu = X Subtot = &2, Req =&3 Calfor =&4 | Space: object requires documentation | |
265 | 631 | Standard proposal for CTyp &1 stat = X, Subtot = &2 Req = &3, Basfor=&4 | Space: object requires documentation | |
266 | 632 | Standard proposal for CTyp &1 Mand = X Req = &2 Basfor = &3 AccKey = &4 | Space: object requires documentation | |
267 | 633 | Standard proposal for CTyp &1, Stat = X Req = &2 Acckey = &3 | Space: object requires documentation | |
268 | 634 | Determined values can only be transmitted in & | Space: object requires documentation | |
269 | 635 | Pricing type & is not defined in application & | Space: object requires documentation | |
270 | 636 | Enter calculation type (condition type has calc. type &2, period &3) | Space: object requires documentation | |
271 | 637 | Enter calculation type (condition type has calculation type &2) | Space: object requires documentation | |
272 | 638 | Maintain separate max. values for accruals (cond. type &1, calc. type A) | Space: object requires documentation | |
273 | 639 | Calculation type not allowed (valid values &2 and A) | Space: object requires documentation | |
274 | 640 | This function is not supported in maintaining access sequences | Space: object requires documentation | |
275 | 641 | Access sequence is still being used in procedure '&' ! | Space: object requires documentation | |
276 | 642 | Procedure '&' is not set up for text object '&' | Space: object requires documentation | |
277 | 643 | You cannot choose 'Display' and 'Mandatory text' for the same text | Space: object requires documentation | |
278 | 644 | The function has terminated | Space: object requires documentation | |
279 | 645 | The system does not save the data | Space: object requires documentation | |
280 | 646 | Table & is blocked by user &: Display only | Space: object requires documentation | |
281 | 647 | Processing status & does not exist | Space: object requires documentation | |
282 | 648 | Update document flow for quantity-related completion | Space: object requires documentation | |
283 | 649 | Enter a valid name for the procedure | Space: object requires documentation | |
284 | 650 | Different calculation type not allowed (cond. type &1 has calc.type &2) | Space: object requires documentation | |
285 | 651 | Different calculation type not allowed (cond. type &1 has calc.type &2) | Space: object requires documentation | |
286 | 652 | Period calculation rule &1 not supported for this application | Space: object requires documentation | |
287 | 653 | Scale base type &1 not supported for this application | Space: object requires documentation | |
288 | 654 | Choose a condition exclusion procedure | The short text describes the object sufficiently | |
289 | 655 | Maintain both condition exclusion groups | The short text describes the object sufficiently | |
290 | 656 | Maintain two different condition exclusion groups | The short text describes the object sufficiently | |
291 | 657 | Only fill one cond. exclusion group with this cond. exclusion procedure | The short text describes the object sufficiently | |
292 | 658 | Fill condition exclusion group 1 | The short text describes the object sufficiently | |
293 | 659 | Hierarchical access combined with customer hierarchies not possible | Space: object requires documentation | |
294 | 660 | Access sequence &1 inconsistent; target field &3 missing in access &2 | Space: object requires documentation | |
295 | 661 | Hierarchical access combined with target field &3 not possible | Space: object requires documentation | |
296 | 662 | Internal error &2 when saving access sequence &1 (see long text) | Space: object requires documentation | |
297 | 663 | Do you want access to table field &1 with the initial direct value? | The short text describes the object sufficiently | |
298 | 664 | Access sequence A not possible (access sequence &1, access &2, field &3) | Space: object requires documentation | |
299 | 665 | Pricing for condition type &1, access sequence &2 not possible | The short text describes the object sufficiently | |
300 | 666 | You are not authorized to execute the report | The short text describes the object sufficiently | |
301 | 667 | Access sequence does not exist (check your entries) | The short text describes the object sufficiently | |
302 | 668 | Error updating table T682V | The short text describes the object sufficiently | |
303 | 669 | A total of &1 records were updated | The short text describes the object sufficiently | |
304 | 670 | Could not calculate group conditions using CPF | The short text describes the object sufficiently | |
305 | 671 | Calculation type "T" cannot be used with CPF | The short text describes the object sufficiently | |
306 | 676 | Access type A is not available (access sequence &1, access &2) | Space: object requires documentation | |
307 | 677 | Multi-value attributes are not supported | Space: object requires documentation | |
308 | 678 | Data determination in the access is not supported: Condition &1 | Space: object requires documentation | |
309 | 700 | The use of partners is not allowed for output not dependent on partners | ||
310 | 800 | Group is used in sales documents, so the sold-to party cannot be changed | ||
311 | 801 | Group is used in deliveries, so the ship-to party cannot be changed | ||
312 | 802 | Group is used in billing, so the payer cannot be changed | ||
313 | 803 | Partner grp & doesn't contain any sold-to parties which can't be changed | ||
314 | 804 | Partner grp & doesn't contain any ship-to parties which can't be changed | ||
315 | 805 | Partner group & does not contain any payers which cannot be changed | ||
316 | 806 | The cost center is not defined | ||
317 | 807 | Maintain in Customizing SD: Functions: Partner Determination (TCODE VOPA) | ||
318 | 808 | Function module ZZ_SD_USEREXIT_PARTNER does not exist | ||
319 | 809 | Account assignment category & is invalid | ||
320 | 810 | Cost center &1 does not belong to company code &2 | Space: object requires documentation | |
321 | 811 | The flag Extend Data must not be selected | Space: object requires documentation | |
322 | 812 | Acc. assignment category &1 only allowed for valuated sales order stock | Space: object requires documentation | |
323 | 813 | Account assignmt cat. &1 is not permitted for evaluated sales order stock | Space: object requires documentation | |
324 | 814 | The pricing procedure for account determination must be empty. | Space: object requires documentation | |
325 | 815 | No errors were found in Customizing. | Space: object requires documentation | |
326 | 816 | Billing quantity 'F' must be used for item category billing relevance 'F' | Space: object requires documentation | |
327 | 817 | For delivery-related billing, the field 'Quantity pos/neg' must be '+'. | Space: object requires documentation | |
328 | 818 | If access sequence not available, scale type 'D' not possible. | Space: object requires documentation | |
329 | 819 | A maximum of 99 condition supplements are permitted in pricing procedure. | Space: object requires documentation | |
330 | 820 | Calculation type reference cond. type not equal to calc. type cond. type | Space: object requires documentation | |
331 | 821 | Final Settlement and Correction flds must be maint. in rebate settlement | Space: object requires documentation | |
332 | 822 | Relevant billing type for final settlement must be: Final settlement='A' | Space: object requires documentation | |
333 | 823 | Relevant billing type for final settlement must be: Rel. to rebate ='X' | Space: object requires documentation | |
334 | 824 | Canc. of billing type for final settlement must be: Rel. to rebate ='X' | Space: object requires documentation | |
335 | 825 | Relevant billing type for correctin must be: Relevant to rebate ='B' | Space: object requires documentation | |
336 | 826 | Relevant billing type for correction must be: Relevant to rebate ='X' | Space: object requires documentation | |
337 | 827 | Canc. of billing type for correction must be: Relevant to rebate ='X' | Space: object requires documentation | |
338 | 828 | Relevant billing type for partial settlement must be: Rel.to rebate = 'C' | Space: object requires documentation | |
339 | 829 | Relevant billing type for partial settlement must be: Rel.to rebate = 'X' | Space: object requires documentation | |
340 | 830 | Canc. of billing type for partial settlement must be: Rel.to rebate = 'X' | Space: object requires documentation | |
341 | 831 | Relevant billing type for manual accrual must be: Rel. to rebate ='D' | Space: object requires documentation | |
342 | 832 | Relevant billing type for manual accrual must be: Rel. to rebate ='X' | Space: object requires documentation | |
343 | 833 | Canc.of bill.type for man.accr.sal.ord.type must be: Rel. to rebate ='X' | Space: object requires documentation |
History
Last changed on/by | 20140121 | SAP | |
SAP Release Created in |