SAP ABAP Message Class EPS (Payment Scheme)
Basic Data
Hierarchy
☛
IS-UT (Software Component) SAP Utilities/Telecommunication
⤷ IS-U-IN (Application Component) Invoicing
⤷ EE25 (Package) IS-U: Budget Billing Amounts
⤷ IS-U-IN (Application Component) Invoicing
⤷ EE25 (Package) IS-U: Budget Billing Amounts
Attributes
Message class | EPS | |
Short Description | Payment Scheme | |
Changed On | 20131127 | |
Last Changed At | 165154 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 001 | Error (&1) whilst reading table &2 | Space: object requires documentation | |
2 | 002 | Payment scheme has not been customized | Space: object requires documentation | |
3 | 003 | Budget billing procedure not defined in contract account &1 | Space: object requires documentation | |
4 | 004 | BB procedure in contract account &1 is not from the payment scheme cat. | Space: object requires documentation | |
5 | 005 | Contract &1 does not participate in payment scheme due to BB cycle 00 | Space: object requires documentation | |
6 | 006 | Contract account &1 for contract &2 does not qualify for payment scheme | Space: object requires documentation | |
7 | 007 | There are BB doc. lines with different subtransactions for contract &1 | Space: object requires documentation | |
8 | 008 | There are BB document lines with different tax determ.codes for contr. &1 | Space: object requires documentation | |
9 | 009 | There are bill.doc.lines with a net amount < zero for contract &1 | Space: object requires documentation | |
10 | 010 | There are bill.document lines with a credit subtransaction for contr. &1 | Space: object requires documentation | |
11 | 011 | A payment scheme already exists for contract &1 | Space: object requires documentation | |
12 | 012 | Enter a payment scheme | Space: object requires documentation | |
13 | 013 | Error in event R511: Negative amounts are not permitted in the PS | Space: object requires documentation | |
14 | 014 | Error in event R511: Credit subtransactions are not permitted in PS | Space: object requires documentation | |
15 | 015 | Extrap. document (&1) currency does not correspond to currency in PS (&2) | Space: object requires documentation | |
16 | 016 | Contract &1 an optional contract | Space: object requires documentation | |
17 | 017 | Enter a date in all date fields | The short text describes the object sufficiently | |
18 | 018 | Cannot find contract account &1 for contract &2 | The short text describes the object sufficiently | |
19 | 019 | Data inconsistencies in bill amount fields of payment scheme | Space: object requires documentation | |
20 | 020 | Unexpected exception &2 while calling subprogram &1 | Space: object requires documentation | |
21 | 021 | No budget billing plans found in function module &1 | Space: object requires documentation | |
22 | 022 | System cannot find payment scheme for these selection criteria | Space: object requires documentation | |
23 | 023 | System cannot find payment schemes for creating budget billing lines | Space: object requires documentation | |
24 | 024 | Data inconsistency in line &1 of payment scheme &2 | Space: object requires documentation | |
25 | 025 | No number range defined for object &1 (&2) | Space: object requires documentation | |
26 | 026 | No subtransactions defined for main transaction &1 in table TE305 | Space: object requires documentation | |
27 | 027 | No entry in table TE305 for key &1 &2 &3 &4 | Space: object requires documentation | |
28 | 028 | Credit subtransaction (&1) not permitted in payment scheme | Space: object requires documentation | |
29 | 029 | Negative amounts are not permitted in the payment scheme | Space: object requires documentation | |
30 | 030 | Lines for payment scheme &1 created with document number &2 | Space: object requires documentation | |
31 | 031 | Error when creating budget billing requests for PS &1 in func. module &2 | Space: object requires documentation | |
32 | 032 | Internal error: Module &1 called without contract and payment scheme | The short text describes the object sufficiently | |
33 | 033 | Different currencies in print document lines | Space: object requires documentation | |
34 | 034 | Cannot print change notification for payment scheme &1 | Space: object requires documentation | |
35 | 035 | Unexpected error in subprogram &1 | Space: object requires documentation | |
36 | 036 | Payment scheme &1 (start.date line: )adjusted from amount &3 to &4 | Space: object requires documentation | |
37 | 037 | Payment scheme &1 (start.date line: ) not adjusted | Space: object requires documentation | |
38 | 038 | Start date of PS sample line incorrectly determined in event R513 | Space: object requires documentation | |
39 | 039 | Payment scheme &1 for contract &2 successfully adjusted | Space: object requires documentation | |
40 | 040 | Input parameters &1, &2 and &3 required in function module &4 | Space: object requires documentation | |
41 | 041 | Factory calendar missing in portion &1 | Space: object requires documentation | |
42 | 042 | Cannot create PS for contract &1 because PS &2 already exists | Space: object requires documentation | |
43 | 043 | No due items for meter reading unit &1, cannot create PS for contract &2 | Space: object requires documentation | |
44 | 044 | Payment date cannot be later than the 28th day of a month | Space: object requires documentation | |
45 | 045 | Start date and first payment date must be before the end of billing per. | Space: object requires documentation | |
46 | 046 | Payment scheme cannot be activated (customer-specific) | Space: object requires documentation | |
47 | 047 | You do not have authorization for this activity | The short text describes the object sufficiently | |
48 | 048 | Exception &1 occured in module &2 | Space: object requires documentation | |
49 | 049 | There is more than one active payment scheme for contract &1 on &2 | Space: object requires documentation | |
50 | 050 | Move-out date &1 in contract &2 is different to date &3 in funct. mod. &4 | Space: object requires documentation | |
51 | 051 | There is more than one cancelled payment scheme for contract &1 | Space: object requires documentation | |
52 | 052 | Contract &1 has already been finally invoiced | Space: object requires documentation | |
53 | 053 | Error in module &1: Parameter &2 was not transferred | Space: object requires documentation | |
54 | 054 | Error in module &1: Payment scheme &2 does not belong to contract &3 | Space: object requires documentation | |
55 | 055 | Payment scheme cannot be created because the date is invalid | Space: object requires documentation | |
56 | 056 | Different portions in a mandatory group are not permissible | Space: object requires documentation | |
57 | 057 | A payment scheme with start date &2 already exists for contract &1 | Space: object requires documentation | |
58 | 058 | Cannot create payment scheme for contract &1 (rate category &2) | Space: object requires documentation | |
59 | 059 | Last payment day already elapsed; PS &1 cannot be reversed | Space: object requires documentation | |
60 | 060 | Less than &3 days between &1 and next payment date in payment scheme &2 | Space: object requires documentation | |
61 | 061 | There are already paid BB amounts for payment scheme &1 | Space: object requires documentation | |
62 | 062 | Reversal date &1 comes after the first payment date &2; Cannot reverse | Space: object requires documentation | |
63 | 063 | Line &1 for payment scheme &2 does not exist | The short text describes the object sufficiently | |
64 | 064 | No reference line exists for line &2 of payment scheme &1 | Space: object requires documentation | |
65 | 065 | Reference line &1 of payment scheme &2 is incorrect | The short text describes the object sufficiently | |
66 | 066 | Invalid weekday for weekly/fortnightly payment frequency | Space: object requires documentation | |
67 | 067 | For contract &1, extrapoltion documents are missing for payment scheme | The short text describes the object sufficiently | |
68 | 068 | Payment scheme start date comes before the move-in date of contract &1 | Space: object requires documentation | |
69 | 069 | ** do not use ** | Space: object requires documentation | |
70 | 070 | Payment scheme &1 for contract &2 is still active | Space: object requires documentation | |
71 | 071 | Cannot determine end of the billing period | Space: object requires documentation | |
72 | 072 | Documents with clearing restriction &1 cannot be reversed using trans. &3 | Space: object requires documentation | |
73 | 073 | An active payment scheme exists. Cannot change to BB procedure 0. | Space: object requires documentation | |
74 | 074 | Payment scheme for contract &1 completely deleted | Space: object requires documentation | |
75 | 075 | Processing terminated by user | Space: object requires documentation | |
76 | 076 | Request lines were not generated for the selected payment schemes | Space: object requires documentation | |
77 | 077 | You must retain the payment scheme when reversing print document &1 | The short text describes the object sufficiently | |
78 | 078 | An active payment scheme &1 exists. Budg.billing cycle 0 is not possible. | Space: object requires documentation | |
79 | 079 | Deactivation and account maintenance are not possible. Payment scheme: &1 | Space: object requires documentation | |
80 | 080 | Internal error: Pay.scheme &1, line &2: Active Lines with TVORG &3 | The short text describes the object sufficiently | |
81 | 081 | No PS adjustment: No billing document exists for contract account &1 | Space: object requires documentation | |
82 | 082 | Allocation to the collective bill is not possible for payment schemes | The short text describes the object sufficiently | |
83 | 083 | Payment scheme &1 not active. Clearing reset not possible for &2 | Space: object requires documentation | |
84 | 084 | Payment scheme &1 not active. Use option '2' or '3' for returns | Space: object requires documentation | |
85 | 085 | Payment scheme &1 not active. Document &2 cannot be reversed | The short text describes the object sufficiently | |
86 | 095 | No pymt.scheme adjustment for pymt.scheme &1, unsuitable extrapol.period | The short text describes the object sufficiently | |
87 | 096 | Pymt order or debit memo notification for &1 &2; processing after payment | The short text describes the object sufficiently | |
88 | 100 | Payment scheme &1 does not exist | Space: object requires documentation | |
89 | 101 | Payment scheme already exists for contract &1 on &2 | The short text describes the object sufficiently | |
90 | 102 | No payment scheme exists for contract &1 on &2 | The short text describes the object sufficiently | |
91 | 103 | All payment schemes already exist for contract account &1 on &2 | The short text describes the object sufficiently | |
92 | 104 | No payment scheme exists for contract account &1 on &2 | The short text describes the object sufficiently | |
93 | 105 | All payment schemes already exist for business partner &1 | The short text describes the object sufficiently | |
94 | 106 | There are no payment schemes for business partner &1 | The short text describes the object sufficiently | |
95 | 107 | Budget billing plan &1 is not a 'payment scheme' | The short text describes the object sufficiently | |
96 | 108 | Contract &1 is not available | The short text describes the object sufficiently | |
97 | 109 | Payment scheme not created because contract &1 a prepayment category | Space: object requires documentation | |
98 | 110 | Contract &1 closed on &2; No payment scheme possible after &3 | The short text describes the object sufficiently | |
99 | 111 | All contracts for contract &1 already closed by &2 | The short text describes the object sufficiently | |
100 | 112 | All contracts for business partner &1 are already closed by &2 | The short text describes the object sufficiently | |
101 | 113 | Contract accounts for business partner &1 not qualified for paym.scheme | The short text describes the object sufficiently | |
102 | 114 | Contract account &1 does not exist; change your entry | The short text describes the object sufficiently | |
103 | 115 | Cleared payment scheme requests still exist for payment scheme &1 | Space: object requires documentation | |
104 | 116 | Credit/receivables items with clearing rest. 'R' still exist for PS &1 | Space: object requires documentation | |
105 | 117 | Tax jurisdiction code is not permitted for payment scheme procedure | The short text describes the object sufficiently | |
106 | 118 | Multi-level tax determination is not allowed for the payment scheme | The short text describes the object sufficiently | |
107 | 119 | Item &1 has the settlement restriction 'R', Reversal Not Possible | Space: object requires documentation | |
108 | 120 | Payment scheme items can only be cleared against each other | The short text describes the object sufficiently | |
109 | 200 | Impermissible setting for payment scheme category &1 | Space: object requires documentation | |
110 | 201 | Recovery rate for payment schemes are incompatible | Space: object requires documentation | |
111 | 202 | Reference data for payment scheme &1 insufficient for amount validation | Space: object requires documentation | |
112 | 203 | Enter data in all required entry fields | Space: object requires documentation | |
113 | 300 | Enter an start date for the payment scheme | Space: object requires documentation | |
114 | 301 | Enter a first payment date for the payment scheme | The short text describes the object sufficiently | |
115 | 302 | Enter the payment frequency for the payment scheme | The short text describes the object sufficiently | |
116 | 303 | The first payment date &1 must come after start date &2 | The short text describes the object sufficiently | |
117 | 304 | Inactive payment scheme during payment period &1 not possible | Space: object requires documentation | |
118 | 305 | A payment scheme can only created inactive for direct debit payers | The short text describes the object sufficiently | |
119 | 306 | No contract specified for payment scheme to be created | Space: object requires documentation | |
120 | 307 | First payment date &1 is too far after start date &2 | The short text describes the object sufficiently | |
121 | 308 | Choose &1 as the first payment date for this data | Space: object requires documentation | |
122 | 310 | Inconsistencies in the mandatory group for contract &1 | Space: object requires documentation | |
123 | 311 | Creation of payment scheme for contract &1 terminated | Space: object requires documentation | |
124 | 312 | Internal error: Start date for payment scheme &1 line &2 is empty | Space: object requires documentation | |
125 | 313 | Internal error: Finish date of payment scheme &1 line &2 is before start | Space: object requires documentation | |
126 | 314 | Intenal error: First pay. date of pay. scheme &1, line &2 is before start | Space: object requires documentation | |
127 | 315 | Internal error: No paymetn date for payment scheme &1, line &2 | Space: object requires documentation | |
128 | 316 | Internal error: No paymetn date for payment scheme &1, line &2 | The short text describes the object sufficiently | |
129 | 317 | Internal error: Function module &1 called up without contract | Space: object requires documentation | |
130 | 318 | All payment schemes already exist for mandatory group from contract &1 | Space: object requires documentation | |
131 | 319 | Payment scheme cannot start before current date | Space: object requires documentation | |
132 | 320 | Start date too far in the future | Space: object requires documentation | |
133 | 321 | Customer-specific conflict in creation status of payment scheme | Space: object requires documentation | |
134 | 322 | Payment scheme could not be created | Space: object requires documentation | |
135 | 323 | Start date &1 not permitted as start date of a new sample line | Space: object requires documentation | |
136 | 324 | Payment scheme cannot be activated for a time in the past | Space: object requires documentation | |
137 | 325 | Fields &3 and &4 are inconsistent in payment scheme line &1, &2 | Space: object requires documentation | |
138 | 326 | Invalid selection of open items and credit items | Space: object requires documentation | |
139 | 327 | Payment scheme(s) created for contract account &1 | Space: object requires documentation | |
140 | 328 | A deactivated payment scheme exists for contract &1 up to &2 | Space: object requires documentation | |
141 | 329 | A deactivated payment scheme exists for contract &1 up to &2 | Space: object requires documentation | |
142 | 330 | Payment schemes exist for contract &1 that have not yet been completed | The short text describes the object sufficiently | |
143 | 331 | You Cannot Invoice Periodic and Interim Billings Together | Space: object requires documentation | |
144 | 332 | Billing Transaction &1 Is Not Permitted | Space: object requires documentation | |
145 | 400 | Not all data for creating a payment scheme available | Space: object requires documentation | |
146 | 401 | Payment scheme category &1 is not intended, payment scheme is not created | Space: object requires documentation | |
147 | 402 | Internal error: Module &1 called without payment scheme object | Space: object requires documentation | |
148 | 403 | Internal error: Module &1 called without open items | Space: object requires documentation | |
149 | 404 | Inconsistent data transferred to module &1 | Space: object requires documentation | |
150 | 405 | No adjustable due dates found before the next periodic bill | Space: object requires documentation | |
151 | 406 | A payment date has not been found in the period to &2 for pay. scheme &1 | Space: object requires documentation | |
152 | 500 | There are no sample lines for the payment scheme for contract &1 | The short text describes the object sufficiently | |
153 | 501 | There is already a payment scheme for contract &1 | The short text describes the object sufficiently | |
154 | 502 | There is no payment scheme header for sample lines &1 | The short text describes the object sufficiently | |
155 | 503 | Internal error: Sample line &1 with index &2 already exists | The short text describes the object sufficiently | |
156 | 504 | Payment scheme &1, index &2 incorrect: Subtrans. does not match amount | The short text describes the object sufficiently | |
157 | 505 | Internal error: No payment scheme number for contract &1 | The short text describes the object sufficiently | |
158 | 506 | Internal error: There are several payment schemes for contract &1 | The short text describes the object sufficiently | |
159 | 507 | Internal error: There are only payment scheme lines for contract &1 | The short text describes the object sufficiently | |
160 | 508 | Internal error while sorting lines for scheme &1 | The short text describes the object sufficiently | |
161 | 509 | Internal error: Inconsistent amounts in &1 | The short text describes the object sufficiently | |
162 | 510 | Enter a start date for the changes | The short text describes the object sufficiently | |
163 | 511 | Enter a new first payment date | Space: object requires documentation | |
164 | 512 | Enter a new payment period | The short text describes the object sufficiently | |
165 | 513 | Weekly of fortnightly payment not permitted for direct debit payers | Space: object requires documentation | |
166 | 514 | Internal error: There is no contract for payment scheme &1 | The short text describes the object sufficiently | |
167 | 515 | Sample line dates for payment scheme &1 are inconsistent | The short text describes the object sufficiently | |
168 | 516 | Internal error: Inconsistent line numbering for payment scheme &1 | The short text describes the object sufficiently | |
169 | 517 | There are no sample lines that can be changed for contract &1 | The short text describes the object sufficiently | |
170 | 518 | Payment scheme &1 cannot not be exited before &2 | Space: object requires documentation | |
171 | 519 | Internal error: Change date &1 not permitted | Space: object requires documentation | |
172 | 520 | Payment scheme &1 for &2 already exited | Space: object requires documentation | |
173 | 521 | Payment scheme succesfully activated | Space: object requires documentation | |
174 | 522 | Change date &1 for payment scheme is too far in the future | The short text describes the object sufficiently | |
175 | 523 | Payment scheme already activ. | The short text describes the object sufficiently | |
176 | 524 | Payment scheme &1 cannot be completed for &2 (event R516) | Space: object requires documentation | |
177 | 525 | Internal error: There is no sample line &2 for payment scheme &1 | Space: object requires documentation | |
178 | 526 | Payment frequency in payment scheme &1, line &2 not permitted | Space: object requires documentation | |
179 | 527 | Payment scheme inactive; Request lines have not been created | The short text describes the object sufficiently | |
180 | 528 | Payment scheme &1 cannot be reactivated, KZABSVER=0 in account &2 | Space: object requires documentation | |
181 | 529 | Payment scheme &1 cannot be reactivated. BB cycle = 0 in contract &2 | Space: object requires documentation | |
182 | 530 | Payment Scheme &1 exited at &2 | Space: object requires documentation | |
183 | 531 | Payment scheme &1 cannot be changed before &2 | Space: object requires documentation | |
184 | 532 | Intenal error: Not all changes affect paymetn scheme &1 / contract &2 | Space: object requires documentation | |
185 | 533 | Internal error: No changeable lines for payment schmee &1 /contract &2 | Space: object requires documentation | |
186 | 534 | Payment scheme &1 does not have a payment date after &2 | Space: object requires documentation | |
187 | 535 | Inpermissible changes to SAP data elements for payment scheme &1 in R526 | Space: object requires documentation | |
188 | 536 | Desired change to payment scheme category is not possible (table TE638) | Space: object requires documentation | |
189 | 537 | Cannot change payment scheme category to &1 (possible: &2 or &3) | Space: object requires documentation | |
190 | 538 | Request lines have already been created for this payment scheme | Space: object requires documentation | |
191 | 539 | Payment scheme &1 cannot be changed before &2 | Space: object requires documentation | |
192 | 540 | The change you want to make is not permitted (&1) | Space: object requires documentation | |
193 | 560 | Start of changes to &1, item &2 cannot be before &3 | The short text describes the object sufficiently | |
194 | 561 | The modified amount from payment scheme &1, line &2, must be at least &3 | The short text describes the object sufficiently | |
195 | 562 | Enter a start date when changing payment scheme &1, line &2 | The short text describes the object sufficiently | |
196 | 563 | Changes to &1, &2 must start before &3 | The short text describes the object sufficiently | |
197 | 564 | Changes to payment schemes for contract &1 not before &2 | Space: object requires documentation | |
198 | 565 | First payment date &1 cannot be before change start date &2 | Space: object requires documentation | |
199 | 601 | Error &2 when displaying payment scheme &1 | Space: object requires documentation | |
200 | 602 | Error &2 when creating a payment scheme for contract &1 | Space: object requires documentation | |
201 | 603 | Payment scheme &1 cannot be completed by &2 | Space: object requires documentation | |
202 | 604 | Internal error when terminating payment scheme &1 | Space: object requires documentation | |
203 | 605 | Unexpected error in module &1 | Space: object requires documentation | |
204 | 606 | You do not have the authorization to activate a payment scheme | Space: object requires documentation | |
205 | 607 | Object locked by another processor | Space: object requires documentation | |
206 | 608 | Error &1 when changing payment scheme &2 | Space: object requires documentation | |
207 | 609 | Change to payment scheme &1 cancelled | Space: object requires documentation | |
208 | 610 | You cannot change the status of the sample line to &1 | Space: object requires documentation | |
209 | 700 | Content to be migrated from field PSTYPE does not corresp. to spec. TE638 | Space: object requires documentation | |
210 | 701 | Mandatotry contract is inconsistent | Space: object requires documentation | |
211 | 702 | The fields BETRWTOT, BETRWBILLACT and BETRWBILL are inconsistent | Space: object requires documentation | |
212 | 703 | Error while writing to database (EABP) | Space: object requires documentation | |
213 | 704 | Error while writing to database (EABPL) | Space: object requires documentation | |
214 | 705 | The payment scheme amount must be more than 0 | Space: object requires documentation | |
215 | 706 | Payment scheme to be migrated for contract &1 already available | Space: object requires documentation | |
216 | 707 | Interim and periodic bill. docs exist in mandatory group for contract &1 | Space: object requires documentation |
History
Last changed on/by | 20131127 | SAP | |
SAP Release Created in | 464 |