SAP ABAP Message Class FMCF (FMCF)
Basic Data
Hierarchy
☛
EA-PS (Software Component) SAP Enterprise Extension Public Services
⤷ PSM-FM-CL (Application Component) Closing Operations
⤷ FMCF (Package) FM: Year End Procedure
⤷ PSM-FM-CL (Application Component) Closing Operations
⤷ FMCF (Package) FM: Year End Procedure
Attributes
Message class | FMCF | |
Short Description | ||
Changed On | 20131127 | |
Last Changed At | 183957 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 005 | Read note &1 | The short text describes the object sufficiently | |
2 | 008 | You cannot enter a fund; fund is not active in Customizing | Space: object requires documentation | |
3 | 010 | No pre-selected fund found for &1 | Space: object requires documentation | |
4 | 011 | Funds have already been pre-selected for &1 | Space: object requires documentation | |
5 | 012 | There is no pre-selection in FM area &1 | Space: object requires documentation | |
6 | 013 | Year &1, carryforward parameter &2: No suitable rule maintained | Space: object requires documentation | |
7 | 014 | Carryforward of partial amounts not allowed in commitment carryforward | Space: object requires documentation | |
8 | 015 | Carryforward not allowed (distribution percentage is 0,00%) | The short text describes the object sufficiently | |
9 | 017 | Fund &1 is not set for the balance carryforward | Space: object requires documentation | |
10 | 020 | Exceeds maximum amount that can be carried forward | Space: object requires documentation | |
11 | 021 | Amount must be positive | Space: object requires documentation | |
12 | 022 | Budget carryforward not permitted for this year of cash effectivity | Space: object requires documentation | |
13 | 023 | Execute or delete the carryforward first (RFFMCF26) | Space: object requires documentation | |
14 | 030 | Long text is only saved when approval is saved | Space: object requires documentation | |
15 | 031 | Long text is not saved until application is saved | Space: object requires documentation | |
16 | 040 | Maintenance is blocked for all commitment items | Space: object requires documentation | |
17 | 050 | No receiver address could be determined | The short text describes the object sufficiently | |
18 | 100 | Carryforward for amount 0 is only permitted for single documents | Space: object requires documentation | |
19 | 101 | Automatic carryforward is only allowed for amount 0 | Space: object requires documentation | |
20 | 102 | Posting in fis. yr &1 is not possible; in FM open doc. &2 in fis. yr &3 | Space: object requires documentation | |
21 | 103 | Change in fis. yr &1 not pos.;Doc. &2, fis. yr &3 cannot be carried forw. | Space: object requires documentation | |
22 | 104 | Not necessary to execute program in FM area &1 | Space: object requires documentation | |
23 | 105 | No valid value types found for the commitment carryforward in FM area & | Space: object requires documentation | |
24 | 106 | No automatic fiscal year change: Receiver year before sender year | Space: object requires documentation | |
25 | 107 | The acct assignment from FYC is different from the derived acct assgnmt | Space: object requires documentation | |
26 | 108 | Reassignment of account assignment element &2 not possible | Space: object requires documentation | |
27 | 109 | Reassignment not possible with automatic commitment carryforward | Space: object requires documentation | |
28 | 110 | The document item was reassigned after the cmmt carryforward in year &1 | Space: object requires documentation | |
29 | 111 | Line item &1 &2 &3 was temporarily reassigned | The short text describes the object sufficiently | |
30 | 112 | The currency was changed after the commitment carryforward in year &1 | Space: object requires documentation | |
31 | 113 | Sequence number for item &1 &2 &3 changed with reassignment | Space: object requires documentation | |
32 | 150 | You cannot change the carryforward rule for &4 | Space: object requires documentation | |
33 | 152 | Target entry still contains old rules | Space: object requires documentation | |
34 | 153 | Carryforward parameter is inconsistent | Space: object requires documentation | |
35 | 200 | No open items to be carried forward found | Space: object requires documentation | |
36 | 201 | No more error messages exist for document &1 item &2 | Space: object requires documentation | |
37 | 202 | No error messages exist for document &1 item &2 | Space: object requires documentation | |
38 | 203 | Specify a fiscal year | Space: object requires documentation | |
39 | 205 | Select an item in the error log | Space: object requires documentation | |
40 | 210 | Multiple sel. FM acct assgmts can have a negative effect on performance | Space: object requires documentation | |
41 | 212 | Multiple sel. with background processing is only possible with variant | Space: object requires documentation | |
42 | 215 | Process with dialog is not possible with background processing | Space: object requires documentation | |
43 | 216 | Process with dialog is only possible if you select detail list as well | Space: object requires documentation | |
44 | 220 | There are documents containing errors; they are not carried forward | Space: object requires documentation | |
45 | 221 | Select at least one item for processing | Space: object requires documentation | |
46 | 222 | It is not possible to display & documents; there are too many documents | Space: object requires documentation | |
47 | 224 | No follow-on document posted for YC document &1 in FM area &2 | Space: object requires documentation | |
48 | 230 | Document is in fiscal year change from &1 to &2 | Space: object requires documentation | |
49 | 231 | Not possible to undo: Item has no commitment carryforward | Space: object requires documentation | |
50 | 240 | Processing terminated; &1 documents locked by user &2 | Space: object requires documentation | |
51 | 241 | Error occured during locking of document number &1 | Space: object requires documentation | |
52 | 250 | Error during parallel processing; &1 task: &2 message: &3 &4 | Space: object requires documentation | |
53 | 251 | RFC error in reassignment of travel documents | Space: object requires documentation | |
54 | 252 | Reassignment of travel documents not possible | Space: object requires documentation | |
55 | 261 | No FYC document has been posted yet for the selection parameters | Space: object requires documentation | |
56 | 270 | Carryforward level reset | Space: object requires documentation | |
57 | 280 | Enter a document number or an entry date | Space: object requires documentation | |
58 | 281 | Restriction according to entry date not possible for trip receipts | Space: object requires documentation | |
59 | 282 | Carryforward not possible; & open items selected | Space: object requires documentation | |
60 | 291 | No receiver account assignment selected (document &1 / item &2 | Space: object requires documentation | |
61 | 292 | It is only possible to select receiver account assignments in dialog | Space: object requires documentation | |
62 | 293 | Receiver account assignment for document &1/item &2 cannot be selected | Space: object requires documentation | |
63 | 294 | No unique receiver account assignment could be determined | Space: object requires documentation | |
64 | 295 | Receiver account assignment must be unique | Space: object requires documentation | |
65 | 296 | No unique receiver account assignment could be determined; strategy & | Space: object requires documentation | |
66 | 297 | It is not possible to delete strategy &1; assignments exist | Space: object requires documentation | |
67 | 298 | It is not possible to delete strategy &1; assignments exist | The short text describes the object sufficiently | |
68 | 299 | Value &1 not allowed for strategy | The short text describes the object sufficiently | |
69 | 300 | No items found for the reversal of the commitment carryforward in year &1 | Space: object requires documentation | |
70 | 301 | Inconsistency in commitment carryforward data. See note 1557032 | The short text describes the object sufficiently | |
71 | 302 | Missing entry in &1: Year &2, ledger &3, amount type 300, trans. no. &4 | The short text describes the object sufficiently | |
72 | 303 | Missing entry in &1: Year &2, ledger &3, amount type 350, trans. no. &4 | The short text describes the object sufficiently | |
73 | 305 | Item was already posted in year &3 | Space: object requires documentation | |
74 | 310 | Fiscal year change document not found (&1/&2/&3) | Space: object requires documentation | |
75 | 320 | No Customizing data found for FM area & | Space: object requires documentation | |
76 | 350 | Approval process is not active | Space: object requires documentation | |
77 | 351 | The two-step approval procedure is only possible with BCS | Space: object requires documentation | |
78 | 352 | No items found for approval | Space: object requires documentation | |
79 | 400 | Automatic deletion not possible; transaction &1 is not supported | Space: object requires documentation | |
80 | 401 | No items to be closed found | Space: object requires documentation | |
81 | 402 | FM account assignment &1 &2 is not in the selection (item/acct assgmt &3) | Space: object requires documentation | |
82 | 403 | You are not allowed to close value type &1 in FM area &2 | Space: object requires documentation | |
83 | 404 | FM account assignment of item/acct assgmt &1 is not in multiple selection | Space: object requires documentation | |
84 | 405 | There are open follow-on documents for sales document &1 | The short text describes the object sufficiently | |
85 | 406 | Sales line itm &1 &2 does not have follow-on docs (reason for rejectn &3) | Space: object requires documentation | |
86 | 415 | Reason for rejection & is not defined | Space: object requires documentation | |
87 | 416 | No rejection reason relevant to commitment is maintained | Space: object requires documentation | |
88 | 420 | There are documents with errors; they will not be closed | Space: object requires documentation | |
89 | 500 | No year dependency for multi-year budgets | Space: object requires documentation | |
90 | 501 | Year-dependent master data maintenance active in FM area & | Space: object requires documentation | |
91 | 502 | Commitment carryforward not supported in multi-year budget | Space: object requires documentation | |
92 | 503 | & using fiscal year-based encumbrance tracking of value type & | Space: object requires documentation | |
93 | 504 | Reassignment only in multi-year budget | Space: object requires documentation | |
94 | 505 | Program & not supported in multi-year budget | Space: object requires documentation | |
95 | 506 | No derivation strategy (FM area &1 fiscal year &2 &3 &4) | Space: object requires documentation | |
96 | 507 | Multi-year budget not supported for profile &1 | Space: object requires documentation | |
97 | 700 | Messages in document chain | Space: object requires documentation | |
98 | 701 | Automatic zero carryforward not allowed for document chain cmmt carryfwds | Space: object requires documentation | |
99 | 702 | Assign document chain &1 to a processing type | Space: object requires documentation | |
100 | 703 | Processing type &1 is not allowed for document chain &2 | Space: object requires documentation | |
101 | 704 | Assign a processing type to the document chain first | Space: object requires documentation | |
102 | 705 | Year of cash effectivity &1 is later than fiscal year &2 | The short text describes the object sufficiently | |
103 | 706 | Docs cannot be posted subsequently; cmmt carryforward with chains active | Space: object requires documentation | |
104 | 707 | Preceding document &2 cannot be assigned for document &1 | Space: object requires documentation | |
105 | 708 | Total amounts cannot be determined; see error message(s) | Space: object requires documentation | |
106 | 709 | Carryforward not possible; different FM accnt assgmts in doc. chain &1 | Space: object requires documentation | |
107 | 710 | Assignment of processing type &2 to document chain &1 is not allowed | Space: object requires documentation | |
108 | 712 | Value type &1 for the commitment carryforward does not have chains | Space: object requires documentation | |
109 | 716 | Both budget categories must be processed at the same time | The short text describes the object sufficiently | |
110 | 717 | Different receiver addresses in the budget categories | The short text describes the object sufficiently | |
111 | 718 | Incomplete document chain. Document &1 is missing | Space: object requires documentation | |
112 | 720 | No data found requiring processing | The short text describes the object sufficiently | |
113 | 721 | Invoice item &1&2 refers to invalid document &3 &4 | The short text describes the object sufficiently | |
114 | 722 | Down payment request &1&2 refers to invalid documemnt &3 &4 | The short text describes the object sufficiently | |
115 | 730 | Document cannot be carried forward in this system | Space: object requires documentation | |
116 | 739 | Choose at least one option for chains with completely reduced documents | Space: object requires documentation | |
117 | 740 | Reference document &1 could not be read | The short text describes the object sufficiently | |
118 | 741 | CFSTAT indicator inconsistent for document &1 | The short text describes the object sufficiently | |
119 | 742 | CFSTAT &1 indicator inconsistent for document &2 | The short text describes the object sufficiently | |
120 | 743 | Deleted document chains option only with expert mode | The short text describes the object sufficiently | |
121 | 744 | Document &1 is already in approval procedure with lot &2 | The short text describes the object sufficiently | |
122 | 745 | FM area &1 does not use commitment carryforward with document chains | The short text describes the object sufficiently | |
123 | 746 | Document chain interrupted between &1 and &2 | The short text describes the object sufficiently | |
124 | 747 | Documents in the chain were merged (Research & Node 1). | The short text describes the object sufficiently | |
125 | 748 | Document deleted | The short text describes the object sufficiently | |
126 | 749 | Chain contains deleted documents | The short text describes the object sufficiently | |
127 | 750 | Amount was changed | Space: object requires documentation | |
128 | 751 | Part of earmarked fund &1 cannot be processed | Space: object requires documentation | |
129 | 752 | Current document in previous year | The short text describes the object sufficiently | |
130 | 753 | Current document in following year | The short text describes the object sufficiently | |
131 | 760 | Entry in Table for Approval Procedure Does Not Exist | The short text describes the object sufficiently | |
132 | 800 | Strategy & has not been created yet | Space: object requires documentation | |
133 | 801 | Enter a percentage or last target object as a target field | Space: object requires documentation | |
134 | 802 | Function cannot be carried out with derived funds center &1 | Space: object requires documentation | |
135 | 803 | The value BLANK/SPACE is not valid; acct assgmt element &1 (strategy &2) | Space: object requires documentation | |
136 | 804 | The derivation steps of strategy &1 are not included in the transport | Space: object requires documentation | |
137 | 805 | Processing cancelled, execute RFFMCCF_UPD_RECEIVER | Space: object requires documentation | |
138 | 806 | Reassignment of documents of value type & not possible | Space: object requires documentation | |
139 | 807 | Line item display not possible for funds balances | Space: object requires documentation | |
140 | 808 | Account assgmt element &1 can only be derived independently of element &2 | Space: object requires documentation | |
141 | 809 | Closing operation is not possible with the derived target acct assgnmt | Space: object requires documentation | |
142 | 810 | Item category of sender and receiver item &1/&2 is different | Space: object requires documentation | |
143 | 811 | Reassigning documents of type & is not possible | Space: object requires documentation | |
144 | 812 | Count up the current number for source account assignment & without gaps | Space: object requires documentation | |
145 | 813 | Total of percentages (&1) is larger than 100 (source account assgmt &2) | Space: object requires documentation | |
146 | 814 | Not possible to reassign to statistical commitment item &1 | The short text describes the object sufficiently | |
147 | 815 | Percentage must not be negative | The short text describes the object sufficiently | |
148 | 850 | G/L account & is not a balance sheet account (chart of accounts &) | The short text describes the object sufficiently | |
149 | 851 | Posting not possible; Acct is a reconciliation account (rcncltn ind. &2) | Space: object requires documentation | |
150 | 852 | No &1 could be derived (&2) for posting to trustee fund | Space: object requires documentation | |
151 | 853 | &1 (&2) cannot be changed in the document lines created automatically | The short text describes the object sufficiently | |
152 | 854 | Account assignment element &1 was subsequently changed from &2 to &3 (&4) | Space: object requires documentation | |
153 | 855 | Purchase order &1 is in changed version in SRM | Space: object requires documentation | |
154 | 860 | Fund type &2 (&1) is assigned to derivation strategies &3 and &4 | The short text describes the object sufficiently | |
155 | 865 | Parallel setting only import. for items open at closing if MYBE active | The short text describes the object sufficiently | |
156 | 890 | You may have to reconstruct the FYC tables later | Space: object requires documentation |
History
Last changed on/by | 20131127 | SAP | |
SAP Release Created in |