| CACSSESRUN012 |
Error while looking for contracts |
| CACSSESRUN013 |
No due settlement schedule items found for contract &1 up to &2 |
| CACSSESRUN014 |
Contract is locked and cannot be processed |
| CACSSESRUN015 |
It is not possible to lock a free number range for application &1 |
| CACSSESRUN016 |
No due settlement schedule items up to &2 exist for contract &1 |
| CACSSESRUN017 |
Commit counter &1 for application &2 read |
| CACSSESRUN018 |
Run log for run &2 completed |
| CACSSESRUN019 |
Due settlement schedule items up to &1 exist |
| CACSSESRUN020 |
Contract &1 |
| CACSSESRUN021 |
Test run; settlement schedule run for contract &1 started |
| CACSSESRUN022 |
Update run: settlement schedule run for contract &1 started |
| CACSSESRUN023 |
Test run; resetting of settlement schedule run for contract &1 started |
| CACSSESRUN024 |
Update run; resetting of settlement schedule run for contract &1 started |
| CACSSESRUN025 |
Update run for contract &1 completed |
| CACSSESRUN026 |
Test run for contract &1 completed |
| CACSSESRUN027 |
Stt.schedule log: ctrct &1 remun.type &2 run no. &3 date &4 (CACS_SESJO) |
| CACSSESRUN028 |
Document posting locked by another process |
| CACSSESRUN029 |
Test run with run number &1 started |
| CACSSESRUN030 |
No due settlement schedule items found up to key date &1 |
| CACSSESRUN031 |
Start of processing of remuneration type &1 |
| CACSSESRUN032 |
Due &1; remuneration &2; document &3, year &4; read |
| CACSSESRUN033 |
Settlement item &3 due &1 remuneration &2 |
| CACSSESRUN034 |
Stt.sched.log for ctrct &1, remuneration type &1 not written to database |
| CACSSESRUN035 |
No due settlement schedule items exist for contract &1 up to &2 |
| CACSSESRUN036 |
No due stt.schedule items exist up to &1 for the following contracts |
| CACSSESRUN037 |
No due settlement schedule items found up to &1 (&2) |
| CACSSESRUN038 |
Conversion of due settlement schedule items to settlement items |
| CACSSESRUN039 |
Selection of due settlement schedule items |
| CACSSESRUN040 |
Stt.schedule items successfully converted; settlement items generated |
| CACSSESRUN041 |
Contract &1 remuneration &2 remuneration amount &3 due date &4 |
| CACSSESRUN042 |
Error during posting; contact your technical support |
| CACSSESRUN043 |
Test run: delete operation for contract &1 is started |
| CACSSESRUN044 |
Update run: delete operation for contract &1 is started |
| CACSSESRUN045 |
Package CACS25 is not active in application &1 |
| CACSSESRUN050 |
Enter a run number |
| CACSSESRUN051 |
No runs exist for specified key date &1 |
| CACSSESRUN052 |
Settlement schedule run for run number &1 does not exist |
| CACSSESRUN053 |
No entry exists for general run log |
| CACSSESRUN054 |
Resetting of settlement schedule run &1 |
| CACSSESRUN100 |
No stt.schedule item converted to settlemen item exists for contract &1 |
| CACSSESRUN101 |
Settlement schedule items (contract &1) do not exist |
| CACSSESRUN102 |
Settlement schedule run contains errors; see log |
| CACSSESRUN103 |
Settlement schedule items for contract &1 (run &2) were not reset |
| CACSSESRUN104 |
Settlement schedule items for contract &1 (run &2) were reset |
| CACSSESRUN105 |
No open settlement item found for contract &1 |
| CACSSESRUN106 |
It is not possible to reset stt.schedule item &1 stt.item &2 |
| CACSSESRUN107 |
&1 settlement schedule items out of &2 could not be reset |
| CACSSESRUN108 |
Due date document(s) &1 / &2 / &3 cannot be reset |
| CACSSESRUN109 |
&1 settlement items out of &2 were successfully reset |
| CACSSESRUN110 |
Remuneration type &1 (converted settlement item &2 &3 ) reset on &4 |
| CACSSESRUN111 |
Remun.type &1 (converted settlement item &2 &3) cannot be reset on &4 |
| CACSSESRUN112 |
Stt.sched.item for remun.doc. &1 &2 with remun. &3 &4 reset |
| CACSSESRUN113 |
Stt.sched.item for remun.doc. &1 &2 with remun. &3 &4 not reset |
| CACSSESRUN114 |
Settlement schedule document &1 / &2 will be reset |
| CACSSESRUN115 |
Error while initializing resetting of settlement schedule run |
| CACSSESRUN116 |
Error while selecting settlement schedule documents for run &1 |
| CACSSESRUN117 |
Error during selection of settlement schedule items for run &1 |
| CACSSESRUN118 |
Cannot copy application log for contract &1 |
| CACSSESRUN119 |
Error in process for resetting settlement schedule run |
| CACSSESRUN120 |
Resetting of settlement schedule run contains errors; read log |
| CACSSESRUN200 |
Date must be at least &1 days previously |
| CACSSESRUN201 |
Application is not avaiflable in this system |
| CACSSESRUN202 |
No relevant settlement schedulels found for contract &1 |
| CACSSESRUN203 |
Settlement schedules identified for deletion: &1 |
| CACSSESRUN204 |
Release DB memory: &1 &2 |
| CACSSESRUN205 |
Settlement schedule items identified: &1 |
| CACSSESTD001 |
Error during posting of settlement schedules |
| CACSSESTD002 |
Error while resetting settlement schedules for remunerations in doc. &1 |
| CACSSESTD003 |
Error during status change of settlement schedule for remuneration &1 |
| CACSSESTD004 |
Entitlement &1 is considered to be disbursed; no scheduling required |
| CACSSESTD005 |
Remunerations in doc. &1 are considered to be disbursed; no scheduling |
| CACSSESTD006 |
Settlement scheduling for commission document &1 |
| CACSSESTD007 |
Error during transfer of scheduling notification to caller's log |
| CACSSESTD008 |
Error while reading DDIC for settlement schedule item in application &1 |
| CACSSESTD009 |
Error while reading settlement schedule &1 |
| CACSSESTD010 |
No data record exists in table &2 for key &1 |
| CACSSESTD011 |
Invalid function call to reverse settlement schedule |
| CACSSESTD012 |
New sequence number &1 invalid for settlement schedule &2 |
| CACSSESTD013 |
Settlement schedule &1 cleared with &2 item(s) |
| CACSSESTD014 |
&4 items deleted for remuneration &3 in settlement schedule &1 (&2) |
| CACSSESTD015 |
Error while deleting fulfillment levels for sequence &1 of schedule &2 |
| CACSSESTD016 |
Error while resetting settlement schedule &1 |
| CACSSESTD017 |
Settlement schedule for remuneration &1 was created without rules |
| CACSSESTD018 |
Scheduling rule &1 in version &2 is not valid at event &3 |
| CACSSESTD019 |
Recall of &1 in remuneration &2 on original due date |
| CACSSESTD020 |
Balance of stt.schedule items does not match entitlement in field &1 |
| CACSSESTD021 |
Error while preparing temporary numbering of settlement schedule |
| CACSSESTD022 |
Check of generated settlement schedule ended with an error; &1 |
| CACSSESTD023 |
Remuneration &1 has unexpected status &2 for settlement scheduling |
| CACSSESTD024 |
Error while creating fulfillment levels for sequence &1 of stt.sched. &2 |
| CACSSESTD025 |
Remuneration &1 is distributed in more than one settlement schedule |
| CACSSESTD026 |
Invalid call of function &1 without specifying &2 |
| CACSSESTD027 |
Error &1 while reading remuneration history for entitlement &2 |
| CACSSESTD028 |
Error while reserving number range for settlement schedule |
| CACSSESTD029 |
Number range &1 reserved for object &2 of settlement scheduling |
| CACSSESTD030 |
Error while determining posting year of settlement schedule &1 |
| CACSSESTD031 |
Error while extracting a new settlement schedule no. from number range &1 |
| CACSSESTD032 |
Inconsistent numbering of items for settlement schedule &1 |
| CACSSESTD033 |
Settlement schedule no. &1 from interval &2, &3 successfully assigned |
| CACSSESTD034 |
Termination of stt.schedule update due to unknown database operation &1 |