SAP ABAP Message Class CACS_SE (Settlement)
Basic Data
Hierarchy
☛
EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials
⤷
ICM (Application Component) Incentive and Commission Management (ICM)
⤷
CACSS10 (Package) ICM Settlement: Released DDIC
⤷
⤷
Attributes
| Message class | CACS_SE | |
| Short Description | Settlement | |
| Changed On | 20130531 | |
| Last Changed At | 104852 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 | "Settlement" process started | The short text describes the object sufficiently | ||
| 2 | "Reset Settlement" process started | The short text describes the object sufficiently | ||
| 3 | "Settlement" process completed (run number &1) | The short text describes the object sufficiently | ||
| 4 | "Reset Settlement" process completed (run number &1) | The short text describes the object sufficiently | ||
| 5 | No authorization for "Settlement" process | The short text describes the object sufficiently | ||
| 6 | No authorization for "Reset Settlement" process | The short text describes the object sufficiently | ||
| 7 | Invalid call of method &1 in class &2 | The short text describes the object sufficiently | ||
| 8 | BAdI &1 (method &2) will be executed | The short text describes the object sufficiently | ||
| 9 | No authorization for process | The short text describes the object sufficiently | ||
| 10 | Invalid call of method &1 in class &2 | The short text describes the object sufficiently | ||
| 11 | Contracts in the interval of &1 to &2 will be edited | The short text describes the object sufficiently | ||
| 12 | Commission contract &1 is being processed | The short text describes the object sufficiently | ||
| 13 | Post clearing information: Update to DB table &1 failed | The short text describes the object sufficiently | ||
| 14 | No valid contracts were found for the selection | The short text describes the object sufficiently | ||
| 15 | No settlement agreement exists for contract &1 | The short text describes the object sufficiently | ||
| 16 | Cannot read agreement &2 &3 for commission contract &1 | The short text describes the object sufficiently | ||
| 17 | Invalid call of method to read individual settlement agreement | The short text describes the object sufficiently | ||
| 18 | Invalid call of method to generate individual settlement agreement | The short text describes the object sufficiently | ||
| 19 | Invalid call of method to calculate settlement | The short text describes the object sufficiently | ||
| 20 | Period rule for settlement type (&1) either not found or invalid | The short text describes the object sufficiently | ||
| 21 | Calculation from &1 to &2 | The short text describes the object sufficiently | ||
| 22 | Cannot determine any periods for period &1 to &2 | The short text describes the object sufficiently | ||
| 23 | Period &1 (&2): calculation of &3 to &4 | The short text describes the object sufficiently | ||
| 24 | Settlement agreement &1 | The short text describes the object sufficiently | ||
| 25 | No period found for period rule &1 (&2) and date &3 | The short text describes the object sufficiently | ||
| 26 | Settlement amount &1 &2 | The short text describes the object sufficiently | ||
| 27 | No settlement document created for settlement amount &1 | The short text describes the object sufficiently | ||
| 28 | Cannot create settlement document; one parameter is blank | Space: object requires documentation | ||
| 29 | No remuneration types exist for settlement type (&1) | The short text describes the object sufficiently | ||
| 30 | Period rule &3 period &4 will not be reset | The short text describes the object sufficiently | ||
| 31 | Data for period rule &3 and period &4 was reset | The short text describes the object sufficiently | ||
| 32 | Settlement type &1 | The short text describes the object sufficiently | ||
| 33 | Contract &1 | The short text describes the object sufficiently | ||
| 34 | Invalid call of method of individual agreement | The short text describes the object sufficiently | ||
| 35 | No parallel processing Customizing for appl. &1 and mass activity &2 | The short text describes the object sufficiently | ||
| 36 | Error while calling target system; the next period will be edited | The short text describes the object sufficiently | ||
| 37 | Error while calling target system; the next document will be processed | The short text describes the object sufficiently | ||
| 38 | Last open period was adjusted | The short text describes the object sufficiently | ||
| 39 | No log exists | The short text describes the object sufficiently | ||
| 40 | Error while reading threshold values for settlement | Space: object requires documentation | ||
| 41 | Error while reading target system of settlement type (&1) | The short text describes the object sufficiently | ||
| 42 | Error while reading target system for logical target system (TRIGID &1) | The short text describes the object sufficiently | ||
| 43 | Error while reading comm.remuneration ID for target system (PAYEE_ID &1) | The short text describes the object sufficiently | ||
| 44 | Error while reading standard agreement &1 | The short text describes the object sufficiently | ||
| 45 | Number of settlement lines after BAdI is different from before | Space: object requires documentation | ||
| 46 | A key was changed during enrichment of settlement documents | Space: object requires documentation | ||
| 47 | Call transfer | The short text describes the object sufficiently | ||
| 48 | No remuneration types for settlement type &1 | The short text describes the object sufficiently | ||
| 49 | Enter posting date | The short text describes the object sufficiently | ||
| 50 | No due settlement items exist for contract | The short text describes the object sufficiently | ||
| 51 | Settlement amount is below threshold values that are to be settled | Space: object requires documentation | ||
| 52 | Errors have occurred during processing of commission contract &1 | The short text describes the object sufficiently | ||
| 53 | Run administration information for run number &1 was written | The short text describes the object sufficiently | ||
| 54 | Error while processing individual settlement agreement &1 (stt.rule &2) | The short text describes the object sufficiently | ||
| 55 | No line items for contract &1 and settlement date &2 | The short text describes the object sufficiently | ||
| 56 | Error during posting due to inconsistent transfer data | The short text describes the object sufficiently | ||
| 57 | Error while removing documents from internal buffer of settlement | The short text describes the object sufficiently | ||
| 58 | Call correspondence | The short text describes the object sufficiently | ||
| 59 | No due settlement items for this settlement rule | The short text describes the object sufficiently | ||
| 60 | BAdI to enrich settlement document will be executed (BAdI &1) | The short text describes the object sufficiently | ||
| 61 | BAdI to exclude settlement types will be executed (BAdI &1) | The short text describes the object sufficiently | ||
| 62 | BAdI to determine whether to settle minimum amounts will be executed | Space: object requires documentation | ||
| 63 | BAdI to exclude remuneration indicators will be executed (BAdI &1) | Space: object requires documentation | ||
| 64 | BAdI to exclude remuneration types will be executed (BAdI &1) | The short text describes the object sufficiently | ||
| 65 | Header data of settlement document | The short text describes the object sufficiently | ||
| 66 | Settlement items of settlement document | The short text describes the object sufficiently | ||
| 67 | Originally due settlement items | The short text describes the object sufficiently | ||
| 68 | Account assignment information for settlement document | The short text describes the object sufficiently | ||
| 69 | At least one partner has to be excluded from settlement | The short text describes the object sufficiently | ||
| 70 | No follow-on period exists for period &1 (&2), period rule &3 (&4) | Space: object requires documentation | ||
| 71 | Remuneration type &1 is used in different settlement types | Space: object requires documentation | ||
| 72 | Stt.type AccAss Determination for Doc.ID &1 and stt.line &2 started | The short text describes the object sufficiently | ||
| 73 | Rem.type AccAss Determination for Doc.ID &1 and stt.line &2 started | The short text describes the object sufficiently | ||
| 74 | No authorization for settlement run | The short text describes the object sufficiently | ||
| 75 | Error while executing BAdI &1 and its method &2 | The short text describes the object sufficiently | ||
| 76 | Parameter &1 is not specified - transfer is canceled | The short text describes the object sufficiently | ||
| 77 | No information for transfer was supplied | The short text describes the object sufficiently | ||
| 78 | Settlement type &1 is invalid | Space: object requires documentation | ||
| 79 | No target system is specified for settlement type &1 | The short text describes the object sufficiently | ||
| 80 | There is no BAdI implementation for transfer | Space: object requires documentation | ||
| 81 | There is no adapter (class &1) for transfer; target system is &2 | The short text describes the object sufficiently | ||
| 82 | Method &1 of adapter &2 is missing or is incorrectly implemented | The short text describes the object sufficiently | ||
| 83 | BAdI implementation for definition &1 is incorrectly implemented | The short text describes the object sufficiently | ||
| 84 | Invalid sort criteria &1 | The short text describes the object sufficiently | ||
| 85 | Invalid identification of logical target system of settlement &1 | Space: object requires documentation | ||
| 86 | Database conversion of settlement is incomplete | The short text describes the object sufficiently | ||
| 87 | Check routine for this target system &1 is switched off | The short text describes the object sufficiently | ||
| 88 | Invalid account type &1 for transfer to FI | The short text describes the object sufficiently | ||
| 89 | No CPD processing for account type &1 is allowed | The short text describes the object sufficiently | ||
| 90 | No authorization for RFC connection for function group &1 | The short text describes the object sufficiently | ||
| 91 | There is no BAdI implementation for definition &1 | The short text describes the object sufficiently | ||
| 92 | No active version of generated table &1 exists | The short text describes the object sufficiently | ||
| 93 | Invalid standard contract '&1' for commission contract &2 | The short text describes the object sufficiently | ||
| 94 | Determination process terminated with errors | The short text describes the object sufficiently | ||
| 95 | More than one determination result found | The short text describes the object sufficiently | ||
| 96 | Determination returned no results | The short text describes the object sufficiently | ||
| 97 | Identification of account assignment type &1 is invalid | The short text describes the object sufficiently | ||
| 98 | Account assignment type for remuneration type &1 was not specified | The short text describes the object sufficiently | ||
| 99 | Remuneration type &1 is invalid | Space: object requires documentation | ||
| 100 | Check of transfer terminated with errors | The short text describes the object sufficiently | ||
| 101 | Posting of transfer terminated with errors | The short text describes the object sufficiently | ||
| 102 | Tax calculation for gross amount terminated with errors | The short text describes the object sufficiently | ||
| 103 | Tax calculation for net amount terminated with errors | The short text describes the object sufficiently | ||
| 104 | An internal error has occurred | The short text describes the object sufficiently | ||
| 105 | Copy service error for assignment time-spot &1, source &1 and target &3 | The short text describes the object sufficiently | ||
| 106 | Error whle generating new UUID | The short text describes the object sufficiently | ||
| 107 | No account assignment type for settlement type &1 was specified | The short text describes the object sufficiently | ||
| 108 | Transfer of settlement was initialized | The short text describes the object sufficiently | ||
| 109 | Compression of transfer was started | The short text describes the object sufficiently | ||
| 110 | Check of transfer to target system &1 was started | The short text describes the object sufficiently | ||
| 111 | Transfer will be started in simulation mode | The short text describes the object sufficiently | ||
| 112 | Transfer will be started in production mode | The short text describes the object sufficiently | ||
| 113 | Update task of transfer is active | The short text describes the object sufficiently | ||
| 114 | Update task of transfer is not active | The short text describes the object sufficiently | ||
| 115 | Offsetting entry of settlement was initialized | The short text describes the object sufficiently | ||
| 116 | Transfer to &1 was started | The short text describes the object sufficiently | ||
| 117 | Transfer will be executed using FI adapter for vendors | The short text describes the object sufficiently | ||
| 118 | Transfer will be executed using FI adapter for customers | The short text describes the object sufficiently | ||
| 119 | Splitting of FI line item is set for &1 | The short text describes the object sufficiently | ||
| 120 | Compression of transfer to &1 was started | The short text describes the object sufficiently | ||
| 121 | Check of transfer to &1 was started | The short text describes the object sufficiently | ||
| 122 | Posting of transfer to &1 was started | The short text describes the object sufficiently | ||
| 123 | Cannot determine splitting of settlement document &1 &2 | The short text describes the object sufficiently | ||
| 124 | No valid bank details found for business partner &1 | The short text describes the object sufficiently | ||
| 125 | Business partner &1 is invalid | The short text describes the object sufficiently | ||
| 126 | Settlement posting will be edited | The short text describes the object sufficiently | ||
| 127 | Settlement offsetting entry will be edited | The short text describes the object sufficiently | ||
| 128 | Offsetting entry of transfer was started | The short text describes the object sufficiently | ||
| 129 | Transfer must only be posted in update mode | The short text describes the object sufficiently | ||
| 130 | Payment reference &1 was determined for FI document (split &2) | The short text describes the object sufficiently | ||
| 131 | Combination of RFC destination and logical service is invalid | Space: object requires documentation | ||
| 132 | RFC connection error for target system &1 - &2 | The short text describes the object sufficiently | ||
| 133 | Offsetting entry of transfer to &1 was started | The short text describes the object sufficiently | ||
| 134 | No internal (temporary) settlement document number was specified | The short text describes the object sufficiently | ||
| 135 | Field "&1" is missing in "&2" structure | The short text describes the object sufficiently | ||
| 136 | Transfer structure "&1" is not available | The short text describes the object sufficiently | ||
| 137 | No resetting information found for payment reference &1 &2 | The short text describes the object sufficiently | ||
| 138 | No business partner found for one-time customer | The short text describes the object sufficiently | ||
| 139 | Field "&1" of transfer structure "&2" is not available | The short text describes the object sufficiently | ||
| 140 | RFC update only possible without update mode | The short text describes the object sufficiently | ||
| 141 | Function module "&1" does not exist - target system is "&2" | The short text describes the object sufficiently | ||
| 142 | Posting to general ledger is not possible | The short text describes the object sufficiently | ||
| 143 | Settlement is not allowed for one-time customer | The short text describes the object sufficiently | ||
| 144 | Payment reference &1 was determined for PY document | The short text describes the object sufficiently | ||
| 145 | Messages (FS-CD): | The short text describes the object sufficiently | ||
| 146 | &1&2&3&4 | The short text describes the object sufficiently | ||
| 147 | FS-CD - Message number &2 message class &1 message type &3 | The short text describes the object sufficiently | ||
| 148 | No settlement items for posting to FS-CD | The short text describes the object sufficiently | ||
| 149 | No time-stamped line items were found for settlement document | The short text describes the object sufficiently | ||
| 150 | Error while getting old document data; next document will be processed | The short text describes the object sufficiently | ||
| 151 | Settlement items with zero amounts will not be transferred | Space: object requires documentation | ||
| 152 | Settlement items with zero amounts exist | Space: object requires documentation | ||
| 153 | &1 | The short text describes the object sufficiently | ||
| 154 | Wild card * is not allowed for settlement type | The short text describes the object sufficiently | ||
| 155 | Specify minimum contract, document no., settlement type or run no. | The short text describes the object sufficiently | ||
| 156 | No data was found for the selection conditions | The short text describes the object sufficiently | ||
| 157 | * Database Conversion Account Assignment Types ************************** | The short text describes the object sufficiently | ||
| 158 | Test run conversion of account assignment types without database update | The short text describes the object sufficiently | ||
| 159 | Update run of conversion of account assignment types with database update | The short text describes the object sufficiently | ||
| 160 | No account assignment types found in Customizing for application &1 | Space: object requires documentation | ||
| 161 | Error when reading the field catalog | The short text describes the object sufficiently | ||
| 162 | No active version of conversion table &1 found | The short text describes the object sufficiently | ||
| 163 | No entries found in table &1 for conversion | The short text describes the object sufficiently | ||
| 164 | An error has occurred in processing unit &1 | Space: object requires documentation | ||
| 165 | Account assignment type &1 (version &2) transferred to table &3 | The short text describes the object sufficiently | ||
| 166 | No conversions were made | Space: object requires documentation | ||
| 167 | Error during database operation (table &1) | The short text describes the object sufficiently | ||
| 168 | Test run of conversion of account assignment types is completed | The short text describes the object sufficiently | ||
| 169 | Update run of conversion of account assignment types is completed | The short text describes the object sufficiently | ||
| 170 | Conversion was canceled due to missing event information | Space: object requires documentation | ||
| 171 | Conversion is currently running or has already run; no restart possible | Space: object requires documentation | ||
| 172 | Processing is complete; see log | The short text describes the object sufficiently | ||
| 173 | Function module &1 does not exist | Space: object requires documentation |
History
| Last changed on/by | 20130531 | SAP | |
| SAP Release Created in | 700 |