CACS_SE - Settlement
The following messages are stored in message class CACS_SE: Settlement.
It is part of development package CACSS10 in software component ICM. This development package consists of objects that can be grouped under "ICM Settlement: Released DDIC".
It is part of development package CACSS10 in software component ICM. This development package consists of objects that can be grouped under "ICM Settlement: Released DDIC".
Message Nr ▲ | Message Text |
|---|---|
| 000 | "Settlement" process started |
| 001 | "Reset Settlement" process started |
| 002 | "Settlement" process completed (run number &1) |
| 003 | "Reset Settlement" process completed (run number &1) |
| 004 | No authorization for "Settlement" process |
| 005 | No authorization for "Reset Settlement" process |
| 006 | Invalid call of method &1 in class &2 |
| 007 | BAdI &1 (method &2) will be executed |
| 008 | No authorization for process |
| 009 | Invalid call of method &1 in class &2 |
| 010 | Contracts in the interval of &1 to &2 will be edited |
| 011 | Commission contract &1 is being processed |
| 012 | Post clearing information: Update to DB table &1 failed |
| 013 | No valid contracts were found for the selection |
| 014 | No settlement agreement exists for contract &1 |
| 016 | Cannot read agreement &2 &3 for commission contract &1 |
| 017 | Invalid call of method to read individual settlement agreement |
| 018 | Invalid call of method to generate individual settlement agreement |
| 019 | Invalid call of method to calculate settlement |
| 020 | Period rule for settlement type (&1) either not found or invalid |
| 021 | Calculation from &1 to &2 |
| 022 | Cannot determine any periods for period &1 to &2 |
| 023 | Period &1 (&2): calculation of &3 to &4 |
| 024 | Settlement agreement &1 |
| 025 | No period found for period rule &1 (&2) and date &3 |
| 026 | Settlement amount &1 &2 |
| 027 | No settlement document created for settlement amount &1 |
| 028 | Cannot create settlement document; one parameter is blank |
| 029 | No remuneration types exist for settlement type (&1) |
| 030 | Period rule &3 period &4 will not be reset |
| 031 | Data for period rule &3 and period &4 was reset |
| 032 | Settlement type &1 |
| 033 | Contract &1 |
| 034 | Invalid call of method of individual agreement |
| 035 | No parallel processing Customizing for appl. &1 and mass activity &2 |
| 036 | Error while calling target system; the next period will be edited |
| 037 | Error while calling target system; the next document will be processed |
| 038 | Last open period was adjusted |
| 039 | No log exists |
| 040 | Error while reading threshold values for settlement |
| 041 | Error while reading target system of settlement type (&1) |
| 042 | Error while reading target system for logical target system (TRIGID &1) |
| 043 | Error while reading comm.remuneration ID for target system (PAYEE_ID &1) |
| 044 | Error while reading standard agreement &1 |
| 045 | Number of settlement lines after BAdI is different from before |
| 046 | A key was changed during enrichment of settlement documents |
| 047 | Call transfer |
| 048 | No remuneration types for settlement type &1 |
| 049 | Enter posting date |
| 050 | No due settlement items exist for contract |
| 051 | Settlement amount is below threshold values that are to be settled |
| 052 | Errors have occurred during processing of commission contract &1 |
| 053 | Run administration information for run number &1 was written |
| 054 | Error while processing individual settlement agreement &1 (stt.rule &2) |
| 055 | No line items for contract &1 and settlement date &2 |
| 056 | Error during posting due to inconsistent transfer data |
| 057 | Error while removing documents from internal buffer of settlement |
| 058 | Call correspondence |
| 059 | No due settlement items for this settlement rule |
| 060 | BAdI to enrich settlement document will be executed (BAdI &1) |
| 061 | BAdI to exclude settlement types will be executed (BAdI &1) |
| 062 | BAdI to determine whether to settle minimum amounts will be executed |
| 063 | BAdI to exclude remuneration indicators will be executed (BAdI &1) |
| 064 | BAdI to exclude remuneration types will be executed (BAdI &1) |
| 065 | Header data of settlement document |
| 066 | Settlement items of settlement document |
| 067 | Originally due settlement items |
| 068 | Account assignment information for settlement document |
| 069 | At least one partner has to be excluded from settlement |
| 070 | No follow-on period exists for period &1 (&2), period rule &3 (&4) |
| 071 | Remuneration type &1 is used in different settlement types |
| 072 | Stt.type AccAss Determination for Doc.ID &1 and stt.line &2 started |
| 073 | Rem.type AccAss Determination for Doc.ID &1 and stt.line &2 started |
| 100 | No authorization for settlement run |
| 131 | Error while executing BAdI &1 and its method &2 |
| 200 | Parameter &1 is not specified - transfer is canceled |
| 201 | No information for transfer was supplied |
| 202 | Settlement type &1 is invalid |
| 203 | No target system is specified for settlement type &1 |
| 204 | There is no BAdI implementation for transfer |
| 205 | There is no adapter (class &1) for transfer; target system is &2 |
| 206 | Method &1 of adapter &2 is missing or is incorrectly implemented |
| 207 | BAdI implementation for definition &1 is incorrectly implemented |
| 208 | Invalid sort criteria &1 |
| 209 | Invalid identification of logical target system of settlement &1 |
| 210 | Database conversion of settlement is incomplete |
| 211 | Check routine for this target system &1 is switched off |
| 212 | Invalid account type &1 for transfer to FI |
| 213 | No CPD processing for account type &1 is allowed |
| 214 | No authorization for RFC connection for function group &1 |
| 215 | There is no BAdI implementation for definition &1 |
| 216 | No active version of generated table &1 exists |
| 217 | Invalid standard contract '&1' for commission contract &2 |
| 218 | Determination process terminated with errors |
| 219 | More than one determination result found |
| 220 | Determination returned no results |
| 221 | Identification of account assignment type &1 is invalid |
| 222 | Account assignment type for remuneration type &1 was not specified |
| 223 | Remuneration type &1 is invalid |
| 224 | Check of transfer terminated with errors |
| 225 | Posting of transfer terminated with errors |
| 226 | Tax calculation for gross amount terminated with errors |
| 227 | Tax calculation for net amount terminated with errors |
| 228 | An internal error has occurred |
| 229 | Copy service error for assignment time-spot &1, source &1 and target &3 |
| 230 | Error whle generating new UUID |
| 231 | No account assignment type for settlement type &1 was specified |
| 232 | Transfer of settlement was initialized |
| 233 | Compression of transfer was started |
| 234 | Check of transfer to target system &1 was started |
| 235 | Transfer will be started in simulation mode |
| 236 | Transfer will be started in production mode |
| 237 | Update task of transfer is active |
| 238 | Update task of transfer is not active |
| 239 | Offsetting entry of settlement was initialized |
| 240 | Transfer to &1 was started |
| 242 | Transfer will be executed using FI adapter for vendors |
| 243 | Transfer will be executed using FI adapter for customers |
| 244 | Splitting of FI line item is set for &1 |
| 245 | Compression of transfer to &1 was started |
| 246 | Check of transfer to &1 was started |
| 247 | Posting of transfer to &1 was started |
| 248 | Cannot determine splitting of settlement document &1 &2 |
| 249 | No valid bank details found for business partner &1 |
| 250 | Business partner &1 is invalid |
| 251 | Settlement posting will be edited |
| 252 | Settlement offsetting entry will be edited |
| 253 | Offsetting entry of transfer was started |
| 254 | Transfer must only be posted in update mode |
| 255 | Payment reference &1 was determined for FI document (split &2) |
| 256 | Combination of RFC destination and logical service is invalid |
| 257 | RFC connection error for target system &1 - &2 |
| 258 | Offsetting entry of transfer to &1 was started |
| 259 | No internal (temporary) settlement document number was specified |
| 260 | Field "&1" is missing in "&2" structure |
| 261 | Transfer structure "&1" is not available |
| 262 | No resetting information found for payment reference &1 &2 |
| 263 | No business partner found for one-time customer |
| 264 | Field "&1" of transfer structure "&2" is not available |
| 265 | RFC update only possible without update mode |
| 266 | Function module "&1" does not exist - target system is "&2" |
| 267 | Posting to general ledger is not possible |
| 268 | Settlement is not allowed for one-time customer |
| 269 | Payment reference &1 was determined for PY document |
| 270 | Messages (FS-CD): |
| 271 | &1&2&3&4 |
| 272 | FS-CD - Message number &2 message class &1 message type &3 |
| 273 | No settlement items for posting to FS-CD |
| 300 | No time-stamped line items were found for settlement document |
| 301 | Error while getting old document data; next document will be processed |
| 302 | Settlement items with zero amounts will not be transferred |
| 303 | Settlement items with zero amounts exist |
| 305 | &1 |
| 400 | Wild card * is not allowed for settlement type |
| 401 | Specify minimum contract, document no., settlement type or run no. |
| 402 | No data was found for the selection conditions |
| 600 | * Database Conversion Account Assignment Types ************************** |
| 601 | Test run conversion of account assignment types without database update |
| 602 | Update run of conversion of account assignment types with database update |
| 603 | No account assignment types found in Customizing for application &1 |
| 604 | Error when reading the field catalog |
| 605 | No active version of conversion table &1 found |
| 606 | No entries found in table &1 for conversion |
| 607 | An error has occurred in processing unit &1 |
| 608 | Account assignment type &1 (version &2) transferred to table &3 |
| 609 | No conversions were made |
| 610 | Error during database operation (table &1) |
| 611 | Test run of conversion of account assignment types is completed |
| 612 | Update run of conversion of account assignment types is completed |
| 613 | Conversion was canceled due to missing event information |
| 614 | Conversion is currently running or has already run; no restart possible |
| 615 | Processing is complete; see log |
| 616 | Function module &1 does not exist |