| TU266 |
Budget billing amount entered in coll. bill. Print doc. of BB request: &3 |
| TU267 |
Extrapolation document &1 is inconsistent |
| TU268 |
INTERNAL: No entry in table SH_TAB for contract &1 |
| TU269 |
Budget billing item inconsistent after event R976 |
| TU270 |
VAT code &1 for determination code &2 not found |
| TU271 |
You have not specified a contract account (ISU_S_BBP_TAX_IN_INVOICING) |
| TU272 |
More than one VAT code for determination code &1 |
| TU273 |
Too many entries in table XT_EABPS |
| TU274 |
No entries in table XT_EABPS |
| TU275 |
Partial payment amount changed from &1 to &2 |
| TU276 |
Amount &1 &2 cannot be changed |
| TU277 |
Items &1, &2 and &3 not found |
| TU278 |
You cannot delete budget billing plan &1 (deregulation) |
| TU279 |
Budget billing plan &1 will be deleted despite dunned items |
| TU280 |
Date &1 that you entered is before the move-in date &2 |
| TU281 |
Internal: Delete function must not be active in display mode |
| TU282 |
You can only delete lines belonging to active contract &1 |
| TU283 |
You cannot deleted cleared items |
| TU284 |
Error converting internal transactions &1 &2 to external transactions |
| TU285 |
Error reading posting area &1 with key &2 |
| TU286 |
Budget billing request &1 was created |
| TU287 |
VAT indicator for posting area &1 (field &2) is not maintained |
| TU288 |
BB plan &1, contr. &2 cannot be adj. because standing BB amnt is active |
| TU289 |
Changes to budget billing request saved |
| TU290 |
Error saving; cannot update database |
| TU291 |
Contract account &1 is not an industry customer account (KZABSVER = &2) |
| TU292 |
No budget billing plan for industry customers for &1 |
| TU293 |
No budget billing plan with due date after &2 found for contract &1 |
| TU294 |
No budget billing plan with doc.number &1 and due date after &2 found |
| TU295 |
Contract &1 from document &2 &3 &4 does not exist |
| TU296 |
INTERNAL: Programming error in &1 |
| TU297 |
Error reading company code &1 |
| TU298 |
INTERNAL: Selection table &1 in function module &2 is empty |
| TU299 |
INTERNAL: Funcion module &1; backgr. mode is only supported when creating |
| TU300 |
Conversion to client &1 started |
| TU301 |
Conversion of table &1 in client &2 started |
| TU302 |
&2 new entries were made in table &3 in client &1 |
| TU303 |
&3 entries out of &2 sucessfully processed in client &1 |
| TU304 |
&2 entries converted to &3 in client &1 |
| TU305 |
Some entries in client &1 could not be converted - TEABSTVOR |
| TU306 |
Conversion of table &1 in client &2 completed successfully |
| TU307 |
Table &1 must be converted again |
| TU308 |
Change of contract accounts started in client &1 (FKKVKP: field KZABSVER) |
| TU309 |
Contract accts changed successfully in client &1 (FKKVKP: field KZABSVER) |
| TU310 |
Change of contract accts in client &1 (FKKVKP: field KZABSVER) terminated |
| TU311 |
Conversion in client &1 terminated |
| TU312 |
Client &1: No BB procedure specified in table TE500 -> no conversion |
| TU313 |
Document &1 is not a budget billing plan |
| TU314 |
Proration of budget billing plan &1 is not necessary |
| TU315 |
Proration of budget billing plan &1 not possible |
| TU316 |
Proration of budget billing plan &1 not possible |
| TU317 |
Select one object from the main selection parameters |
| TU318 |
Cannot find orders for selection |
| TU319 |
No changeable budget billing plans exist for change date &1 |
| TU320 |
No budget billing plans were prorated |
| TU321 |
&1 budget billing plans prorated in total |
| TU322 |
Budget billing plan &1 prorated |
| TU323 |
-> budget billing plan &1 created |
| TU324 |
&1 |
| TU325 |
Budget billing plan &1 subject to YAP: proration is not possible |
| TU326 |
Cannot print budget billing plan &1 - see error log |
| TU327 |
Budget billing plan &1 successfully printed |
| TU328 |
with contract &1 |
| TU329 |
Budget billing plan &1 contains advance payments: proration not possible |
| TU330 |
Budget billing plan must be deleted with budget billing procedure &1 |
| TU331 |
Budget billing plan &1 was not changed |
| TU332 |
No budget billing plans found for selection |
| TU333 |
&1 budget billing plans were adjusted |
| TU334 |
Budget billing plan &1 deactivated; proration is not possible |
| TU335 |
Conversion of budget billing plan &1 is not possible |
| TU336 |
Conversion of budget billing plan &1 is not necessary |
| TU337 |
Maintain all currency parameters |
| TU338 |
Budget billing plan &1 does not have currency &2 |
| TU339 |
No entry in table TFK042C for company code &2 and currency &3 |
| TU340 |
Error converting &1 to &2 on &3 |
| TU341 |
Different currencies in the header and items of budget billing plan &1 |
| TU342 |
Internal error: Entry in YAP database not found (budget billing plan &1) |
| TU343 |
Error in budget billing plan &1 |
| TU344 |
&1 budget billing plans created in new currency |
| TU345 |
New budget billing plans for contract account &1 |
| TU346 |
YAP object is not yet subject to payment lock in budget billing plan &1 |
| TU347 |
Budget billing plan &1 contains active YAP object |
| TU348 |
Budget billing plan &1 extended to &2 |
| TU349 |
BB plan &2 exists in the future for contract &1 |
| TU350 |
Enter a currency |
| TU351 |
You have canceled the function for budget billing plan processing |
| TU352 |
Error while deleting table &1 in client &2 |
| TU353 |
Conversion of table &1 started |
| TU354 |
Conversion of table &1 completed successfully |
| TU355 |
Data must be entered in at least one parameter of function module &1 |
| TU356 |
No entries found for selection |
| TU357 |
BB amount cannot be changed because YAP is cleared. Contract :&1 |
| TU358 |
XPRA can only run for add-on ID &1 when upgrading from Rel. &2 or earlier |
| TU359 |
To-date &1 is smaller than date in schedule record &2 |
| TU360 |
Extrapolation not executable as period up until &1 already billed |
| TU361 |
It is not necessary to adjust payment plan &1 |
| TU362 |
No payment plans were changed |
| TU363 |
Payment plan &1 was changed (ENDPERIOD old/new: &2 &3) |
| TU364 |
A total of &1 payment plans were changed |
| TU365 |
No changeable payment plans exist |