# |
Message |
Message Short Text |
Documentation status |
Authorization check |
1 |
001 |
System is productive, test program cannot be executed |
The short text describes the object sufficiently |
|
2 |
100 |
--- Invoice Creation --- |
The short text describes the object sufficiently |
|
3 |
101 |
Credit-side invoice created for &1: Amnt: &2, Ref: &3, &4 |
The short text describes the object sufficiently |
|
4 |
102 |
Debit-side invoice created for &1: Amnt: &2 Ref: &3,&4 |
The short text describes the object sufficiently |
|
5 |
103 |
&1. Invoice being posted. Transaction messages: |
The short text describes the object sufficiently |
|
6 |
104 |
--- End of Invoice Creation --- |
The short text describes the object sufficiently |
|
7 |
160 |
--- PEXR2002 Send IDoc to Head Office --- |
The short text describes the object sufficiently |
|
8 |
161 |
IDoc &1 will be copied and resent |
The short text describes the object sufficiently |
|
9 |
162 |
New IDoc &1 is sent to head office |
The short text describes the object sufficiently |
|
10 |
163 |
IDoc &1 with PID &2 was successfully sent to head office |
The short text describes the object sufficiently |
|
11 |
164 |
Error sending IDoc &1 (PID: &2) |
The short text describes the object sufficiently |
|
12 |
165 |
Creation of IDoc for payment run &1 on &2 |
The short text describes the object sufficiently |
|
13 |
166 |
Payment run &1 (on &2) was not found |
The short text describes the object sufficiently |
|
14 |
167 |
Job for payment run &1 (on &2) is not type 'E' |
The short text describes the object sufficiently |
|
15 |
168 |
Job for payment run &1 on &2 was found. Name: &3, counter: &4 |
The short text describes the object sufficiently |
|
16 |
169 |
Creation of IDoc for current payment run |
The short text describes the object sufficiently |
|
17 |
170 |
You have not started a new payment run |
The short text describes the object sufficiently |
|
18 |
171 |
Maximum &1 seconds wait for new job |
The short text describes the object sufficiently |
|
19 |
172 |
Job &1/&2 has status &3. Still running, deleted or terminated |
The short text describes the object sufficiently |
|
20 |
173 |
IDoc creation for payment run &1 on &2 is being started. IBAN Flag: &3 |
The short text describes the object sufficiently |
|
21 |
174 |
No IDoc was generated |
The short text describes the object sufficiently |
|
22 |
175 |
IDoc &3 with PID &4 was sent for payment run &1 on &2 |
The short text describes the object sufficiently |
|
23 |
200 |
--- Creation of Internal Bank Statement Was Started --- |
The short text describes the object sufficiently |
|
24 |
201 |
FINSTA IDoc &1 will be resent |
The short text describes the object sufficiently |
|
25 |
202 |
FINSTA IDoc &1 was created |
The short text describes the object sufficiently |
|
26 |
203 |
FINSTA IDoc &1 is being reprocessed |
The short text describes the object sufficiently |
|
27 |
204 |
FINSTA IDoc &1 has been processed |
The short text describes the object sufficiently |
|
28 |
205 |
A new internal bank statement is being created |
The short text describes the object sufficiently |
|
29 |
206 |
Error in bank area &1 while determining the posting date: |
The short text describes the object sufficiently |
|
30 |
207 |
Error in BKK_GET_NEXT_POSTDATE; bank area: &1, posting date: &2 |
The short text describes the object sufficiently |
|
31 |
208 |
Posting date &2 cannot be set for bank area &1: |
The short text describes the object sufficiently |
|
32 |
209 |
New posting date &2 was set for bank area &1 |
The short text describes the object sufficiently |
|
33 |
210 |
Bank statement creation for account &1/&2 was started, date: &2 |
The short text describes the object sufficiently |
|
34 |
211 |
--- Creation of Internal Bank Statement Was Ended --- |
The short text describes the object sufficiently |
|
35 |
230 |
--- Creation/Import of External Bank Statement --- |
The short text describes the object sufficiently |
|
36 |
231 |
An external bank statement is being created |
The short text describes the object sufficiently |
|
37 |
232 |
Bank statement format &1 is not permitted |
The short text describes the object sufficiently |
|
38 |
233 |
Name of bank statement file is empty |
The short text describes the object sufficiently |
|
39 |
234 |
Name of the turnover file is empty |
The short text describes the object sufficiently |
|
40 |
235 |
Local FI data is used |
The short text describes the object sufficiently |
|
41 |
236 |
House bank &2 in company code &1 is not available |
The short text describes the object sufficiently |
|
42 |
237 |
House bank account &3 in house bank &2 (company code &1) is not available |
The short text describes the object sufficiently |
|
43 |
238 |
FI data is retrieved via RFC destination &1 |
The short text describes the object sufficiently |
|
44 |
239 |
House bank account found; company code :&1, house bank: &2, account: &3 |
The short text describes the object sufficiently |
|
45 |
240 |
Amount from original invoice(s) is used |
The short text describes the object sufficiently |
|
46 |
241 |
&1 statement items are generated |
The short text describes the object sufficiently |
|
47 |
242 |
Statement data is saved in file &1 |
The short text describes the object sufficiently |
|
48 |
243 |
Line item data is saved in file &1 |
The short text describes the object sufficiently |
|
49 |
244 |
Error saving statement file; message to follow |
The short text describes the object sufficiently |
|
50 |
245 |
Error while saving line item file; message to follow |
The short text describes the object sufficiently |
|
51 |
246 |
Statement file successfully stored |
The short text describes the object sufficiently |
|
52 |
247 |
Line item file successfully stored |
The short text describes the object sufficiently |
|
53 |
248 |
Last bank statement is deleted |
The short text describes the object sufficiently |
|
54 |
249 |
Target client: &1 |
The short text describes the object sufficiently |
|
55 |
250 |
Searching for bank statement with sender &1 and ID &2 |
The short text describes the object sufficiently |
|
56 |
251 |
No bank statement was found with the specified keys |
The short text describes the object sufficiently |
|
57 |
252 |
Last bank statement was deleted |
The short text describes the object sufficiently |
|
58 |
253 |
Bank statement is imported |
The short text describes the object sufficiently |
|
59 |
254 |
The bank statement is not posted |
The short text describes the object sufficiently |
|
60 |
255 |
The bank statement is posted immediately |
The short text describes the object sufficiently |
|
61 |
256 |
Bank statement processing was started |
The short text describes the object sufficiently |
|
62 |
260 |
--- Creation of Payment Orders --- |
The short text describes the object sufficiently |
|
63 |
261 |
Internal payment orders are created; number: &1 |
The short text describes the object sufficiently |
|
64 |
262 |
External payment orders are created, number: &1 |
The short text describes the object sufficiently |
|
65 |
263 |
Foreign payment orders are generated; number: &1 |
The short text describes the object sufficiently |
|
66 |
264 |
&1 payment orders are posted; messages to follow: |
The short text describes the object sufficiently |
|
67 |
265 |
--- Creation of Payment Orders Ended --- |
The short text describes the object sufficiently |
|
68 |
500 |
Internal error while reading |
The short text describes the object sufficiently |
|
69 |
501 |
Error in payment order |
The short text describes the object sufficiently |
|
70 |
502 |
Error in start status |
The short text describes the object sufficiently |
|
71 |
503 |
Error writing the status |
The short text describes the object sufficiently |
|
72 |
504 |
Error in end status |
The short text describes the object sufficiently |
|
73 |
505 |
Invalid start status |
The short text describes the object sufficiently |
|
74 |
506 |
Invalid end status |
The short text describes the object sufficiently |
|
75 |
507 |
Invalid action list |
The short text describes the object sufficiently |
|
76 |
508 |
Error in DDIC |
The short text describes the object sufficiently |
|
77 |
509 |
&& status & / & is started with action & |
The short text describes the object sufficiently |
|
78 |
510 |
Error in ALV grid |
The short text describes the object sufficiently |
|