SAP ABAP Message Class RESCSU (Error Texts for Settlement Unit)
Basic Data
Hierarchy
☛
EA-FIN (Software Component) EA-FIN
⤷ RE-FX-SC (Application Component) Service Charge Settlement
⤷ RE_SC_SU (Package) SCS: Settlement Unit
⤷ RE-FX-SC (Application Component) Service Charge Settlement
⤷ RE_SC_SU (Package) SCS: Settlement Unit
Attributes
Message class | RESCSU | |
Short Description | Error Texts for Settlement Unit | |
Changed On | 20130531 | |
Last Changed At | 105152 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 001 | You cannot use purpose &1 for settlement unit. | Space: object requires documentation | |
2 | 002 | Maintain measurement type | Space: object requires documentation | |
3 | 003 | Settlement unit &1 was assigned to more than one DME settlement unit | Space: object requires documentation | |
4 | 004 | SU &1 period &2 is used in multiple settlements | Space: object requires documentation | |
5 | 005 | Sum of apportionment shares for purpose &1 is &2, not 100% | Space: object requires documentation | |
6 | 006 | Only one entry is allowed for purpose &1, but there are &2 | Space: object requires documentation | |
7 | 007 | Measurement type &1 not found | Space: object requires documentation | |
8 | 008 | Settlement unit is not a master settlement unit | The short text describes the object sufficiently | |
9 | 009 | Settlement unit is a master settlement unit | The short text describes the object sufficiently | |
10 | 010 | Tenancy law for settlement unit and business entity differ | The short text describes the object sufficiently | |
11 | 011 | Check on validity period of SU deactived when deletion indicator set | Space: object requires documentation | |
12 | 012 | A participation group was not assigned to the settlement unit | The short text describes the object sufficiently | |
13 | 013 | Assignment of first participation group not the same as start of SU | Space: object requires documentation | |
14 | 014 | Key of assigned participation group incomplete | The short text describes the object sufficiently | |
15 | 015 | System could not find participation group &1 | The short text describes the object sufficiently | |
16 | 016 | Participation group &1 is not allowed to be assigned to SU &2 | The short text describes the object sufficiently | |
17 | 017 | No apportionment rule exists for date &1 | The short text describes the object sufficiently | |
18 | 018 | SU for costs posted directly to REC/RO, therefore apport. rule invalid | Space: object requires documentation | |
19 | 019 | Internal error related to apportionment rule on date &1 | Space: object requires documentation | |
20 | 020 | Required field &1 has no entry | Space: object requires documentation | |
21 | 021 | &1 must not be changed | Space: object requires documentation | |
22 | 022 | &1 '&2' does not exist | The short text describes the object sufficiently | |
23 | 023 | No settlement variant assigned to settlement unit | Space: object requires documentation | |
24 | 024 | The apportionment factor percentage has to be greater than 0 | The short text describes the object sufficiently | |
25 | 025 | The apportionment factor percentage cannot be greater than 100 | The short text describes the object sufficiently | |
26 | 026 | &1 does not allow vacancy percentage other than 100% - you entered &2 | Space: object requires documentation | |
27 | 027 | Vacancy percentage has to be greater than 0 | Space: object requires documentation | |
28 | 028 | Vacancy percentage is not allowed to be more than 100 percent | The short text describes the object sufficiently | |
29 | 029 | Enter purpose of apportionment | The short text describes the object sufficiently | |
30 | 030 | No participating SUs are assigned to master settlement unit | Space: object requires documentation | |
31 | 031 | Key of assigned settlement unit is incomplete | The short text describes the object sufficiently | |
32 | 032 | System could not find settlement unit &1 | The short text describes the object sufficiently | |
33 | 033 | Assigning SU &1 to SU &2 not allowed | The short text describes the object sufficiently | |
34 | 034 | You cannot assign a master SU to another master SU | The short text describes the object sufficiently | |
35 | 035 | Equivalence number is not greater than 0 (&2) for SU &1 | The short text describes the object sufficiently | |
36 | 036 | Percentage for share has to be greater than 0 | Space: object requires documentation | |
37 | 037 | Percentage for share is not allowed to be greater than 100.00 percent | The short text describes the object sufficiently | |
38 | 038 | You did not enter remainder object - remaining share is &1 | The short text describes the object sufficiently | |
39 | 039 | System could not find remainder object &1 | The short text describes the object sufficiently | |
40 | 040 | System could not determine settlement periods for SU &1 | Space: object requires documentation | |
41 | 041 | Gap exists between settlement periods &1 and &2 | The short text describes the object sufficiently | |
42 | 042 | Settlement periods &1 and &2 overlap | The short text describes the object sufficiently | |
43 | 043 | A settlement variant is assigned on the date of &1 | Space: object requires documentation | |
44 | 044 | A participation group is assigned on the date of &1 | The short text describes the object sufficiently | |
45 | 045 | SU &1 and SU &2 have different settlement periods | Space: object requires documentation | |
46 | 046 | Assignment of first settlement variant differs from start of SU | Space: object requires documentation | |
47 | 047 | Enter a service charge key | The short text describes the object sufficiently | |
48 | 048 | Enter a settlement unit | The short text describes the object sufficiently | |
49 | 049 | Deletion flag not set for SU &1 | Space: object requires documentation | |
50 | 050 | SU &1 already settled for period &2 by &3 | Space: object requires documentation | |
51 | 051 | Selected period is not current settlement period of SU &1 | Space: object requires documentation | |
52 | 052 | System could not determine settlement period for SU &1 | Space: object requires documentation | |
53 | 053 | SU is subordinate to other SUs (number: &1) | Space: object requires documentation | |
54 | 054 | SU has subordinate SUs (number: &1) | Space: object requires documentation | |
55 | 055 | SU has cost collectors that cannot be deleted (number: &1) | Space: object requires documentation | |
56 | 056 | Cost object SU &1 is not assigned to an SU | Space: object requires documentation | |
57 | 057 | System could not determine remainder object &1 &2 | Space: object requires documentation | |
58 | 058 | Cost object SU is not allowed for apportionment rule | Space: object requires documentation | |
59 | 059 | There are still assigned settlement units (number: &1) | Space: object requires documentation | |
60 | 060 | Cost object SU is not assigned to another SU | Space: object requires documentation | |
61 | 061 | Measurement type &1 is not relevant for apportionment | Space: object requires documentation | |
62 | 062 | No attributes were defined for service charge key &1 | Space: object requires documentation | |
63 | 063 | Remaining share is negative - current value &1 | Space: object requires documentation | |
64 | 064 | Total for settlement unit is 0 | Space: object requires documentation | |
65 | 065 | Total for settlement unit is negative - current value &1 | Space: object requires documentation | |
66 | 066 | SU &1 is for directly assigned costs - SU &3 already exists for RO &2 | Space: object requires documentation | |
67 | 067 | Valid-from &1 is not within period &2 | Space: object requires documentation | |
68 | 068 | A cost object SU does not have its own apportionment rule | Space: object requires documentation | |
69 | 069 | SU is settled externally, therefore apportionment rule is invalid | Space: object requires documentation | |
70 | 070 | SC key &1 is for directly posted costs: data exchange not possible | Space: object requires documentation | |
71 | 071 | SC key &1 is for directly posted costs: not allowed to be used in &2 | Space: object requires documentation | |
72 | 072 | Settlement not allowed for SU &1 | Space: object requires documentation | |
73 | 073 | There are still assigned SUs w/o deletion flag (number: &1) | Space: object requires documentation | |
74 | 074 | &1 not allowed because deletion indicator or flag is set | Space: object requires documentation | |
75 | 075 | There is still at least one settlement unit for BE &1 | Space: object requires documentation | |
76 | 076 | There are postings in the current settlement period | Space: object requires documentation | |
77 | 077 | Assigned SU AE &1 ends on &2 - period assignment is until &3 | The short text describes the object sufficiently | |
78 | 078 | SU &1 - allocation rule is invalid on &2 | The short text describes the object sufficiently | |
79 | 079 | End date of SU &1 is before settlement period &2 | The short text describes the object sufficiently | |
80 | 080 | End date of SU &1 is within settlement period &2 | The short text describes the object sufficiently | |
81 | 081 | Allocation rule from &1 of SU &2 is invalid for period &3 | The short text describes the object sufficiently | |
82 | 082 | Service charge keys have to be selected | The short text describes the object sufficiently | |
83 | 083 | &1 was created | The short text describes the object sufficiently | |
84 | 084 | &1 of &2 settlement units were created | The short text describes the object sufficiently | |
85 | 085 | Enter valid-from date of new settlement units | The short text describes the object sufficiently | |
86 | 086 | Business entities must be different | The short text describes the object sufficiently | |
87 | 087 | 'Apportionment by consumption' indicator not set for measurement type &1 | The short text describes the object sufficiently | |
88 | 088 | 'Apportionment by consumption' indicator is set for measurement type &1 | The short text describes the object sufficiently | |
89 | 089 | Object &1 of type &2 not allowed to be assigned to master SU | The short text describes the object sufficiently | |
90 | 090 | No settlement parameters consider the vacancy percentage | Space: object requires documentation | |
91 | 091 | Per G/L account with account property &1, you can post to &3 | Space: object requires documentation | |
92 | 092 | Consumption remainder is not allowed to be negative for a SU | The short text describes the object sufficiently | |
93 | 093 | Consumption remainder can only be negative when meters used | The short text describes the object sufficiently | |
94 | 094 | Determining consumption using assigned ROs only possible for SU | The short text describes the object sufficiently | |
95 | 095 | 'Consumption Using Assigned RO' indicator not supported | The short text describes the object sufficiently | |
96 | 096 | Creating a settlement unit is not allowed in company code &1 | The short text describes the object sufficiently | |
97 | 097 | Apportionment with purpose '&1' not allowed | The short text describes the object sufficiently | |
98 | 098 | There are active meters (number: &1) | The short text describes the object sufficiently | |
99 | 099 | Object assigned in contracts w/o deletion flag (number: &1) (&2 &3) | The short text describes the object sufficiently | |
100 | 100 | Object is included in a settlement | The short text describes the object sufficiently | |
101 | 101 | Company-code-independent master SUs not allowed to have CO-SUs | The short text describes the object sufficiently | |
102 | 102 | Do not enter business entity | The short text describes the object sufficiently | |
103 | 103 | Funct. for company-code-independent master SUs not active in Customizing | The short text describes the object sufficiently | |
104 | 104 | Indicator for company-code-independent SU can only be set on master SUs | The short text describes the object sufficiently | |
105 | 105 | Cost object SUs not allowed for master SUs, to which master SUs assigned | The short text describes the object sufficiently | |
106 | 106 | Settlement unit &1 was already assigned | The short text describes the object sufficiently | |
107 | 107 | Cost collector &1 of SU &2 &3 &4 not yet settled or has balance | The short text describes the object sufficiently | |
108 | 108 | &1 does not have apportionment rule for date &2 | The short text describes the object sufficiently | |
109 | 109 | From-date of cost object SU not allowed to be before that of parent SU | The short text describes the object sufficiently | |
110 | 110 | From-date of cost object SU not allowed to be within settlement period | The short text describes the object sufficiently | |
111 | 111 | To-date of cost object SU not allowed to be greater than parent SU | The short text describes the object sufficiently | |
112 | 112 | To-date of cost object SU is within the settlement period | The short text describes the object sufficiently | |
113 | 113 | &1 is still being used in &2 as remainder object | The short text describes the object sufficiently | |
114 | 114 | &1 not allowed as remainder object since deletion flag or indicator set | The short text describes the object sufficiently | |
115 | 115 | &1 &2 does not yet contain object | The short text describes the object sufficiently | |
116 | 116 | Cost collector(s) from apportionment rule &1 already in a settlement | The short text describes the object sufficiently | |
117 | 117 | Service charge key &1 is obsolete | Space: object requires documentation | |
118 | 149 | Deletion flag not set for SU &1 | The short text describes the object sufficiently | |
119 | 172 | Settlement not allowed for SU &1 | The short text describes the object sufficiently | |
120 | 550 | SCS Accrual: SU &1 is already being settled for period &2 by &3 | Space: object requires documentation |
History
Last changed on/by | 20130531 | SAP | |
SAP Release Created in | 110 |