SAP ABAP Message Class RO (Messages for (R)eferences between (O)bject numbers)
Basic Data
Hierarchy
☛
EA-FINSERV (Software Component) SAP Enterprise Extension Financial Services
⤷ FIN-FSCM-TRM-TM (Application Component) Transaction Manager
⤷ FTR (Package) Application development R/3 Treasury referencing (unit)
⤷ FIN-FSCM-TRM-TM (Application Component) Transaction Manager
⤷ FTR (Package) Application development R/3 Treasury referencing (unit)
Attributes
Message class | RO | |
Short Description | Messages for (R)eferences between (O)bject numbers | |
Changed On | 20130531 | |
Last Changed At | 105617 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 001 | Reference &1 &2 does not exist | Space: object requires documentation | |
2 | 002 | Enter at least 2 transactions --> see long text | Space: object requires documentation | |
3 | 003 | Reference category & unknown | Space: object requires documentation | |
4 | 004 | Number & already assigned | ||
5 | 005 | Reference &1 &2 already being processed by &3 | ||
6 | 006 | You are already processing reference &1 &2 | Space: object requires documentation | |
7 | 007 | System error occurred when reference blocked | ||
8 | 008 | Reference &1 &2 is not active | Space: object requires documentation | |
9 | 009 | No references & exist | Space: object requires documentation | |
10 | 011 | No object links exist | ||
11 | 012 | No object links of category & exist | ||
12 | 013 | Reference & created | ||
13 | 014 | Reference & changed | ||
14 | 015 | Reference & undone | ||
15 | 020 | Transaction &1 already in this reference | ||
16 | 021 | &1 &2 is already in reference &3 &4 | Space: object requires documentation | |
17 | 022 | Transaction &1 is not contained in any reference | Space: object requires documentation | |
18 | 026 | Enter reference category and number or data of involved object | Space: object requires documentation | |
19 | 029 | Reference was undone, no changes allowed | ||
20 | 030 | Only &2 allowed for reference &1 | ||
21 | 031 | Transaction &1 cannot be contained in a rollover | ||
22 | 032 | Forwarded to netting management | Space: object requires documentation | |
23 | 033 | Check carried out successfully | Space: object requires documentation | |
24 | 100 | Choose valid line | ||
25 | 101 | Function not supported for this object | ||
26 | 102 | Select end of block | ||
27 | 200 | *** 200 - 299 reserved for netting unit *** | ||
28 | 201 | Different company codes cannot be netted | ||
29 | 202 | Different counterparties cannot be netted | ||
30 | 203 | Different due dates cannot be netted | ||
31 | 204 | Different house bank data cannot be netted | ||
32 | 205 | Flow "&1 &2 &3" contains no payment methods | ||
33 | 206 | Include at least two transactions in netting | ||
34 | 207 | Unable to find flows for posting for transaction &1 and due date &2 | Space: object requires documentation | |
35 | 208 | No flows for posting found for transaction & | ||
36 | 209 | Netting & created | ||
37 | 210 | Netting & changed | ||
38 | 211 | Netting & undone | ||
39 | 212 | Transaction &1 with value date &2 is not netted | ||
40 | 213 | Transaction &1 with value date &2 is already netted | ||
41 | 214 | Transaction &1 is not netted | ||
42 | 215 | Transaction &1 is already netted | ||
43 | 216 | Flow "&1 &2 &3" must be able to generate payment request | Space: object requires documentation | |
44 | 217 | Flow "&1 &2 &3" is paid as gross amount, since single payment marked | ||
45 | 218 | Flow "&1 &2 &3" can only be combined if they have the same sign (+/-) | ||
46 | 219 | Transactions don't have the same currency/ies | ||
47 | 220 | Transaction &1 is already in this netting | ||
48 | 221 | Pamyent program cannot combine all flows with currency &1 | ||
49 | 222 | Flow "&1 &2 &3" is already posted, please check! | Space: object requires documentation | |
50 | 223 | Flow "&1 &2 &3" is blocked for posting, please check! | Space: object requires documentation | |
51 | 224 | Flow "&1 &2 &3" flagged for reversal, please check! | Space: object requires documentation | |
52 | 225 | Flow "&1 &2 &3" is reversed, please check! | Space: object requires documentation | |
53 | 226 | Enter netting number or data of involved object | ||
54 | 227 | Netting may not be changed, as flows already posted | ||
55 | 228 | Flows have different payer/payee data | ||
56 | 229 | Netting was undone, no changes allowed | ||
57 | 230 | Transaction &1 has no flows which can be netted... | ||
58 | 231 | Flows skipped, as they did not generate payment requests ... | Space: object requires documentation | |
59 | 232 | Flows with customer postings and G/L account postings contained | Space: object requires documentation | |
60 | 233 | Transaction &1 is not in this netting transact. - removal not possible | Space: object requires documentation | |
61 | 234 | Flow '&1 &2 &3' has no posting release; release manually | Space: object requires documentation | |
62 | 235 | Flow not posted, netting &4 cannot be settled | Space: object requires documentation | |
63 | 236 | Netting &4 cannot be settled because of payment request &3 | Space: object requires documentation | |
64 | 237 | Netting &1 was released for settlement | Space: object requires documentation | |
65 | 238 | Transactions exist with currencies that cannot be netted | The short text describes the object sufficiently | |
66 | 999 | Termination: & & & & |
History
Last changed on/by | 20130531 | SAP | |
SAP Release Created in |