Message Number list used by SAP ABAP Class CX_CACS_STL_TRANSMISSION (Exception Class for Transfer of Settlement)
SAP ABAP Class CX_CACS_STL_TRANSMISSION (Exception Class for Transfer of Settlement) is using
# Object Type Object Name Object Description Note
     
1 Message Number  B2 - 001 Local logical system is not defined
2 Message Number  CACS_SE - 257 RFC connection error for target system &1 - &2
3 Message Number  CACS_SE - 225 Posting of transfer terminated with errors
4 Message Number  CACS_SE - 226 Tax calculation for gross amount terminated with errors
5 Message Number  CACS_SE - 227 Tax calculation for net amount terminated with errors
6 Message Number  CACS_SE - 229 Copy service error for assignment time-spot &1, source &1 and target &3
7 Message Number  CACS_SE - 231 No account assignment type for settlement type &1 was specified
8 Message Number  CACS_SE - 248 Cannot determine splitting of settlement document &1 &2
9 Message Number  CACS_SE - 249 No valid bank details found for business partner &1
10 Message Number  CACS_SE - 250 Business partner &1 is invalid
11 Message Number  CACS_SE - 254 Transfer must only be posted in update mode
12 Message Number  CACS_SE - 256 Combination of RFC destination and logical service is invalid
13 Message Number  CACS_SE - 223 Remuneration type &1 is invalid
14 Message Number  CACS_SE - 259 No internal (temporary) settlement document number was specified
15 Message Number  CACS_SE - 260 Field "&1" is missing in "&2" structure
16 Message Number  CACS_SE - 261 Transfer structure "&1" is not available
17 Message Number  CACS_SE - 262 No resetting information found for payment reference &1 &2
18 Message Number  CACS_SE - 263 No business partner found for one-time customer
19 Message Number  CACS_SE - 264 Field "&1" of transfer structure "&2" is not available
20 Message Number  CACS_SE - 265 RFC update only possible without update mode
21 Message Number  CACS_SE - 266 Function module "&1" does not exist - target system is "&2"
22 Message Number  CACS_SE - 267 Posting to general ledger is not possible
23 Message Number  CACS_SE - 268 Settlement is not allowed for one-time customer
24 Message Number  CACS_SE - 273 No settlement items for posting to FS-CD
25 Message Number  CACS_SE - 212 Invalid account type &1 for transfer to FI
26 Message Number  CACS_SE - 200 Parameter &1 is not specified - transfer is canceled
27 Message Number  CACS_SE - 201 No information for transfer was supplied
28 Message Number  CACS_SE - 202 Settlement type &1 is invalid
29 Message Number  CACS_SE - 203 No target system is specified for settlement type &1
30 Message Number  CACS_SE - 204 There is no BAdI implementation for transfer
31 Message Number  CACS_SE - 205 There is no adapter (class &1) for transfer; target system is &2
32 Message Number  CACS_SE - 206 Method &1 of adapter &2 is missing or is incorrectly implemented
33 Message Number  CACS_SE - 207 BAdI implementation for definition &1 is incorrectly implemented
34 Message Number  CACS_SE - 208 Invalid sort criteria &1
35 Message Number  CACS_SE - 209 Invalid identification of logical target system of settlement &1
36 Message Number  CACS_SE - 210 Database conversion of settlement is incomplete
37 Message Number  CACS_SE - 224 Check of transfer terminated with errors
38 Message Number  CACS_SE - 213 No CPD processing for account type &1 is allowed
39 Message Number  CACS_SE - 214 No authorization for RFC connection for function group &1
40 Message Number  CACS_SE - 215 There is no BAdI implementation for definition &1
41 Message Number  CACS_SE - 216 No active version of generated table &1 exists
42 Message Number  CACS_SE - 217 Invalid standard contract '&1' for commission contract &2
43 Message Number  CACS_SE - 218 Determination process terminated with errors
44 Message Number  CACS_SE - 219 More than one determination result found
45 Message Number  CACS_SE - 220 Determination returned no results
46 Message Number  CACS_SE - 221 Identification of account assignment type &1 is invalid
47 Message Number  CACS_SE - 222 Account assignment type for remuneration type &1 was not specified