SAP ABAP Message Class RECNSCS (Real Estate - General Contract - Service Charges)
Basic Data
Hierarchy
☛
SAP_FIN (Software Component) SAP_FIN
⤷ RE (Application Component) Real Estate Management
⤷ FVVICNZ (Package) Applic.Dev. R/3 Real Estate - Gen.Contract - Enhancements
⤷ RE (Application Component) Real Estate Management
⤷ FVVICNZ (Package) Applic.Dev. R/3 Real Estate - Gen.Contract - Enhancements
Attributes
Message class | RECNSCS | |
Short Description | Real Estate - General Contract - Service Charges | |
Changed On | 20000418 | |
Last Changed At | 152328 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 001 | You must specify the intended purpose of payments. | Space: object requires documentation | |
2 | 002 | Assign screens 'RECNC1' and 'RECNC2' to screen sequence & | Space: object requires documentation | |
3 | 003 | Service charges active -> Only objects of a company code are permitted | Space: object requires documentation | |
4 | 004 | Maintain apportionment unit & in data box for service charge assignment | Space: object requires documentation | |
5 | 005 | Assign condition type directly to SC key & or maintain it in Customizing | Space: object requires documentation | |
6 | 006 | Condition type of SC key & does not exist in contract | Space: object requires documentation | |
7 | 007 | The percentage share of SC key & must be lower than or equal to 100% | Space: object requires documentation | |
8 | 008 | Assign a settlement unit to service charge key & | Space: object requires documentation | |
9 | 009 | No settlement unit was found for service charge key & | Space: object requires documentation | |
10 | 010 | Partner &1 of settlement &2/&3 is not assigned to the contract | Space: object requires documentation | |
11 | 011 | Enter the name of the DDIC structure | Space: object requires documentation | |
12 | 012 | Structure & does not exist, or does not contain any fields | Space: object requires documentation | |
13 | 013 | The structure contains & relevant fields | Space: object requires documentation | |
14 | 014 | Service charge key &1 already exists on &2 | Space: object requires documentation | |
15 | 015 | Apportionment unit &1 already exists on &2 | Space: object requires documentation | |
16 | 016 | Condition type & may only be assigned to one service charge key | Space: object requires documentation | |
17 | 017 | You cannot change the purpose of an active contract. | Space: object requires documentation | |
18 | 018 | To post the settlement, you must first activate the contract | Space: object requires documentation | |
19 | 019 | Condition type cannot be changed for service charge key & | Space: object requires documentation | |
20 | 020 | Maintain tax code in item &1 of settlement &2 | Space: object requires documentation | |
21 | 021 | Settlement document &1/&2/&3 does not exist | Space: object requires documentation | |
22 | 022 | First reverse settlement document &1/&2/&3 | Space: object requires documentation | |
23 | 023 | Condition &: Partner & displays another vendor or customer | Space: object requires documentation | |
24 | 024 | No sales adjustment data available for & for condition '&' (&) | Space: object requires documentation | |
25 | 200 | Contract has no index agreements | Space: object requires documentation | |
26 | 201 | Contract has no index agreements for condition type &1 "&2" | Space: object requires documentation | |
27 | 202 | Adjustment date for condition type &1 '&2" cannot be determined | Space: object requires documentation | |
28 | 203 | Adjustment date &1 is not within contract term &2-&3 | Space: object requires documentation | |
29 | 204 | Contract does not allow &1 for &2 | Space: object requires documentation | |
30 | 205 | Contract has no index agreement for condition type &1 "&2" for &3 | Space: object requires documentation | |
31 | 206 | Adjustment run ID "&1" has already been assigned | Space: object requires documentation | |
32 | 207 | &1/&2 (&3) | Space: object requires documentation | |
33 | 208 | Contract is not activated | Space: object requires documentation | |
34 | 209 | Retroactive adj. (&1) of &3 "&4" not permitted -> Adj. on &2 | Space: object requires documentation | |
35 | 841 | Rule for automatic renewal must not be "subject to approval" | Space: object requires documentation | |
36 | 842 | You cannot enter a date here | Space: object requires documentation | |
37 | 843 | You cannot delete the date here | Space: object requires documentation | |
38 | 844 | Caution: rule "not subject to approval" is being used as an option! | Space: object requires documentation | |
39 | 879 | Rebasing table TIVAJINDXCON is empty, no check on rebasing | Space: object requires documentation | |
40 | 880 | Rebasing not necessary: index series &1 &2 chaining points &3 cond. &4 | Space: object requires documentation | |
41 | 881 | Rebasing is necessary: index series &1 &2 chaining points &3 cond. &4 | Space: object requires documentation | |
42 | 882 | Rebasing is necessary, but chaining points incorrect: &1 &2 &3 cond. &4 | Space: object requires documentation | |
43 | 883 | Contract is already rebased: &1 &2 &3 cond. &4 | Space: object requires documentation | |
44 | 884 | No date for points of first adjustment | Space: object requires documentation | |
45 | 885 | No index points for: &1 &2 &3 condition &4 | Space: object requires documentation | |
46 | 999 | & & & & | Space: object requires documentation |
History
Last changed on/by | 20000418 | SAP | |
SAP Release Created in |