SAP ABAP Message Class FO (Cross-ISPS Functions)
Basic Data
Hierarchy
☛
EA-PS (Software Component) SAP Enterprise Extension Public Services
⤷
PSM-FM-BU (Application Component) Budgeting and Availability Control
⤷
FMOV (Package) Cover Eligibility and Collective Expenditures
⤷
⤷
Attributes
| Message class | FO | |
| Short Description | Cross-ISPS Functions | |
| Changed On | 20001211 | |
| Last Changed At | 103426 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 | Commitment item & cannot be posted | Space: object requires documentation | ||
| 2 | Generic entries not allowed | |||
| 3 | Only one generic entry allowed | |||
| 4 | Processing successfully completed | Space: object requires documentation | ||
| 5 | Deleted successfully: &1 | The short text describes the object sufficiently | ||
| 6 | Database error; data not deleted | The short text describes the object sufficiently | ||
| 7 | Control data of &2 for &3 already being processed by &1 | Space: object requires documentation | ||
| 8 | FM account assignment &2 / &3 / &4 already being processed by &1 | Space: object requires documentation | ||
| 9 | FM acct asst &1 / &2 / &3 is already being processed by &4 | Space: object requires documentation | ||
| 10 | No data exists | |||
| 11 | Budget increase or rule maintenance already being carried out | Space: object requires documentation | ||
| 12 | Data successfully saved | Space: object requires documentation | ||
| 13 | Deleting rules: & | Space: object requires documentation | ||
| 14 | Control data of &1 for &2 is already being processed by &3 | Space: object requires documentation | ||
| 15 | Default rule was copied from customizing | Space: object requires documentation | ||
| 16 | Function is not possible; there are no Customizing settings for RIB | Space: object requires documentation | ||
| 17 | Change of procedure for revenues increasing the budget not allowed | Space: object requires documentation | ||
| 18 | Data already exists | Space: object requires documentation | ||
| 19 | No rules for revenues increasing the budget exist | Space: object requires documentation | ||
| 20 | No assignments for revenues increasing the budget exist | Space: object requires documentation | ||
| 21 | Budget increase not possible; No revenues exist | Space: object requires documentation | ||
| 22 | Function is not possible; revenues increasing the budget are blocked | Space: object requires documentation | ||
| 23 | Double entries in database update | The short text describes the object sufficiently | ||
| 24 | Copying not possible; data already exists | The short text describes the object sufficiently | ||
| 25 | Procedure changes are not possible because of the different funds | Space: object requires documentation | ||
| 26 | You cannot change procedure because of generic entries for expdt. FMAA | Space: object requires documentation | ||
| 27 | You cannot change procedure because of generic entries for FMAA revenue | Space: object requires documentation | ||
| 28 | Procedure cannot be changed due to existing postings | Space: object requires documentation | ||
| 29 | Procedure cannot be changed due to non-completed documents | Space: object requires documentation | ||
| 30 | You cannot process payment and commitment budgets simultaneously | |||
| 31 | Budget transferred successfully | |||
| 32 | Processing completed successfully. Errors occurred, see list | |||
| 33 | There was no budget to be transferred | |||
| 34 | Program RFFMUD01 cannot be executed | Space: object requires documentation | ||
| 35 | Program RFFMUD11 cannot be executed | Space: object requires documentation | ||
| 36 | Collective expenditure distribution is already being carried out | |||
| 37 | System error when blocking collective budget administration distribution | |||
| 38 | Funds center & / & is not a top funds center | |||
| 39 | Funds center &/& has subordinate funds centers | |||
| 40 | Plan values were successfully integrated with the budget | |||
| 41 | Financial result successfully integrated with the budget | |||
| 42 | Actual and commitment values successfully integrated with the budget | |||
| 43 | No collective expenditure exists for FM area & and fiscal year & | |||
| 44 | Distribution of actual and commitment values successful in coll. expend. | Space: object requires documentation | ||
| 45 | Budget values exist for FM account assignment & / & / & | Space: object requires documentation | ||
| 46 | Posting documents exist for FM account assignment & / & / & | |||
| 47 | FM account assignment & / & / & belongs to a cover pool | |||
| 48 | FM account assignment & / & / & is blocked | |||
| 49 | Budget objects for collective expenditure were successfully generated | |||
| 50 | & / & / & / & cannot be a budget object | Space: object requires documentation | ||
| 51 | & / & / & / & cannot be a posting object | Space: object requires documentation | ||
| 52 | You have no authorization to maintain rules for revs increasing the bdgt | Space: object requires documentation | ||
| 53 | You have no authorization to maintain cover eligibility relationships | Space: object requires documentation | ||
| 54 | FM area &1 - no authorization for function &2 | The short text describes the object sufficiently | ||
| 55 | No number range has been assigned to FM area & | |||
| 56 | Number range & is not defined for object & | |||
| 57 | Number range object & is not defined in table TNRO | |||
| 58 | FM area &1 has external number assignment; enter a cover pool number | Space: object requires documentation | ||
| 59 | Enter a number between &1 and &2 | Space: object requires documentation | ||
| 60 | FM area & has internal number assignment; do not enter a number | Space: object requires documentation | ||
| 61 | Number range interval &1 does not exist | Space: object requires documentation | ||
| 62 | Cover pool &3 does not exist in FM area &1 and year &2 | Space: object requires documentation | ||
| 63 | Fund &1 is not allowed in cover pool &2 | Space: object requires documentation | ||
| 64 | No FM account assignments are assigned to the cover pool | |||
| 65 | The budget line types in commitment item and cover pool are different | |||
| 66 | The budget line type for the cover-liable commt item is not permitted | |||
| 67 | Different budget line types in the expenditure and revenue commt items | |||
| 68 | Target fiscal year must be later than the source year | Space: object requires documentation | ||
| 69 | No cover pool assigned to FM account assignment &/&/& | |||
| 70 | No cover pool for payment budget assigned to FM account assignment &/&/& | |||
| 71 | The FM acct asst is already assigned to a payment budget cover pool | |||
| 72 | No commitment budget cover pool is assigned to FM acct assgt &/&/& | Space: object requires documentation | ||
| 73 | The FM acct asst is already assigned to a cover pool for cmmt budget | Space: object requires documentation | ||
| 74 | The FM account assignment takes part in revenues increasing the budget | Space: object requires documentation | ||
| 75 | Enter a budget memo | |||
| 76 | Choose a budget memo for revenues increasing the budget | Space: object requires documentation | ||
| 77 | Budget memos for revenues and expenditures must be of the same type | Space: object requires documentation | ||
| 78 | Select a transferability memo | Space: object requires documentation | ||
| 79 | Choose budget memo type 11 (cover pool) | Space: object requires documentation | ||
| 80 | Select budget memo type 12 (subject to cover) | Space: object requires documentation | ||
| 81 | Select budget memo type 13 (entitled to cover) | Space: object requires documentation | ||
| 82 | Grouping characteristic &2 is not assigned to characteristic group &1 | Space: object requires documentation | ||
| 83 | Derived cmmt item &1/&2/&3 of the breakdown subsection does not exist | Space: object requires documentation | ||
| 84 | Cmmt item in the collective exp. break. subsection could not be derived | Space: object requires documentation | ||
| 85 | FM acct assignment may only take part in cover pool as entitled to cover | Space: object requires documentation | ||
| 86 | The expenditure acct asst is subject to cover in a cover relationship | |||
| 87 | The expenditure FM account assignment is not entitled to cover | Space: object requires documentation | ||
| 88 | Funds subject to cover and funds entitled to cover must be identical | Space: object requires documentation | ||
| 89 | No corresponding cover pool found | Space: object requires documentation | ||
| 90 | You are using an FM account assignment more than once | Space: object requires documentation | ||
| 91 | Grouping characteristic &1 not found | Space: object requires documentation | ||
| 92 | System has canceled entries | Space: object requires documentation | ||
| 93 | FM acct assgmt entitled to cover and FMAA subject to cover are identical | Space: object requires documentation | ||
| 94 | Text variable &1 not permitted for budget memo type 01,02,03,04,05 | Space: object requires documentation | ||
| 95 | Text variable &1 not permitted for budget memo types 12 and 13 | Space: object requires documentation | ||
| 96 | Text variable &1 not permitted for budget memo types 10 and 11 | Space: object requires documentation | ||
| 97 | Assignment not possible; Create a rule for revenues increasing the budget | Space: object requires documentation | ||
| 98 | Assgt not possible; Distribution procedure active for revs incr. budget | Space: object requires documentation | ||
| 99 | Assignment not possible; Budget categories do not match | Space: object requires documentation | ||
| 100 | Assignment not possible; acct assgmt already assigned using cover pool | Space: object requires documentation | ||
| 101 | Assignment not valid; Cover pool contains allocated account assignment | Space: object requires documentation | ||
| 102 | FM account assignment &1 is not entitled to unilateral cover with &2 | The short text describes the object sufficiently | ||
| 103 | FM account assignment &1 is not entitled to reciprocal cover with &2 | The short text describes the object sufficiently | ||
| 104 | FM account assignment &1 is not entitled to statistical cover with &2 | The short text describes the object sufficiently | ||
| 105 | Upper limit must be higher than zero | The short text describes the object sufficiently | ||
| 106 | Percentage for upper limit must be higher than zero | The short text describes the object sufficiently | ||
| 107 | Percentage for lower limit must be higher than zero | The short text describes the object sufficiently | ||
| 108 | Difference between upper and lower limit must be higher than zero | The short text describes the object sufficiently | ||
| 109 | Enter an amount larger than zero for the minimum revenue | The short text describes the object sufficiently | ||
| 110 | Interval type could not be interpreted | The short text describes the object sufficiently | ||
| 111 | Absolute interval must be larger than zero | The short text describes the object sufficiently | ||
| 112 | Enter minimum revenue as percentage if absolute interval is active | The short text describes the object sufficiently | ||
| 113 | Select a budget category | Space: object requires documentation | ||
| 114 | Enter a revenue commitment item | Space: object requires documentation | ||
| 115 | Total percentage (&) is more than 100 | |||
| 116 | Enter a positive percentage rate | Space: object requires documentation | ||
| 117 | Enter a positive minimum revenue | Space: object requires documentation | ||
| 118 | Upper limit for rev.incr.budget must be larger than minimum revenue | Space: object requires documentation | ||
| 119 | Enter an expenditure commitment item | Space: object requires documentation | ||
| 120 | Only one expenditure FM account assignment is allowed | |||
| 121 | Enter a percentage between 0% and 100% | Space: object requires documentation | ||
| 122 | You are using an FM acct assgt several times as expenditure FM acct assgt | |||
| 123 | Enter the surplus FM account assignment in full | Space: object requires documentation | ||
| 124 | Enter at least one expenditure FM account assignment | Space: object requires documentation | ||
| 125 | Enter the budget increase in percent | Space: object requires documentation | ||
| 126 | Budget has already been increased | Space: object requires documentation | ||
| 127 | Deletion is not possible because the budget has already been increased | The short text describes the object sufficiently | ||
| 128 | Calculation basis different for minimum revenue and upper limit | Space: object requires documentation | ||
| 129 | Enter percentage rate 0 or 100 | Space: object requires documentation | ||
| 130 | Expenditures FM account ass. are not considered for revs. incr. budget | Space: object requires documentation | ||
| 131 | No mininum revenue allowed for budget memo "revenue shortfalls" | Space: object requires documentation | ||
| 132 | An upper limit must exist for budget memo "minimum revenue" | Space: object requires documentation | ||
| 133 | Assign at least one expenditures FM account assignment or one cover pool | Space: object requires documentation | ||
| 134 | Deletion not permitted because budget has been transferred | The short text describes the object sufficiently | ||
| 135 | Enter FM account assignment to be managed in collective expenditure | |||
| 136 | Enter a funds center | Space: object requires documentation | ||
| 137 | Enter a collective expenditure posting FM account assignment | Space: object requires documentation | ||
| 138 | Funds center &/& has subordinate funds centers | |||
| 139 | Commitment item &1 used in collective expenditures | Space: object requires documentation | ||
| 140 | Additional revenues have already been distributed | Space: object requires documentation | ||
| 141 | Additional revenues have already been assigned | Space: object requires documentation | ||
| 142 | Commitment item &1 cannot be used for cover eligibility | Space: object requires documentation | ||
| 143 | The activity is not the same 30 (revenue, expense) for this cmmt item | The short text describes the object sufficiently | ||
| 144 | Call procedure for Release 4.02A not released | Space: object requires documentation | ||
| 145 | Call procedure not valid when using functional area | The short text describes the object sufficiently | ||
| 146 | Distribution procedure for revenue cover pools not possible | Space: object requires documentation | ||
| 147 | You cannot assign expenditures cover pools in the distribution procedure | Space: object requires documentation | ||
| 148 | FMAA (&1,&2,&3,&4) already has rules for revenues increasing the budget | Space: object requires documentation | ||
| 149 | Expenditures cover pool contains elements that are subject to cover | Space: object requires documentation | ||
| 150 | FM account assignment (&2, &3,&4) is part of a cover pool | Space: object requires documentation | ||
| 151 | Deletion not possible: Revenue cover pool still has rules | Space: object requires documentation | ||
| 152 | Revenue FM account assignment &1 has already been posted | Space: object requires documentation | ||
| 153 | FM account assignment cannot be removed from cover pool | Space: object requires documentation | ||
| 154 | Enter a revenues cover pool | Space: object requires documentation | ||
| 155 | Enter an expenditures cover pool | Space: object requires documentation | ||
| 156 | Commitment item not recognized; check your entry | The short text describes the object sufficiently | ||
| 157 | Additional revenue of revenue cover pool &1 has already been assigned. | Space: object requires documentation | ||
| 158 | Release the cross assignments that are assigned to cover pools first | The short text describes the object sufficiently | ||
| 159 | Initilization of budget line subelements complete | Space: object requires documentation | ||
| 160 | Subelement & of commitment item not maintained (see IMG) | Space: object requires documentation | ||
| 161 | Default initialization of budget line subelements | Space: object requires documentation | ||
| 162 | Data selection using logical database | Space: object requires documentation | ||
| 163 | Data Formatting | Space: object requires documentation | ||
| 164 | Output in simple list format | Space: object requires documentation | ||
| 165 | Output in SAP Script format | Space: object requires documentation | ||
| 166 | Output in online report format | Space: object requires documentation | ||
| 167 | Initialization | Space: object requires documentation | ||
| 168 | Transaction data selection | Space: object requires documentation | ||
| 169 | No entries found | Space: object requires documentation | ||
| 170 | Maximum permitted length ( & ) exceeded | Space: object requires documentation | ||
| 171 | &1 is an element of &2; set the start position to &3 | Space: object requires documentation | ||
| 172 | Start position must be maintained for & | Space: object requires documentation | ||
| 173 | Only numerical entries are permitted in field & | Space: object requires documentation | ||
| 174 | Invalid position; position occupied by element & | Space: object requires documentation | ||
| 175 | Element & has been changed. Check all elements | Space: object requires documentation | ||
| 176 | Length & ( & ) is longer than the superior element & length (&) | Space: object requires documentation | ||
| 177 | Position occupied by element &; check digit must be at the end | Space: object requires documentation | ||
| 178 | Element & not used | Space: object requires documentation | ||
| 179 | Incorrect commitment item category for commitment item & | Space: object requires documentation | ||
| 180 | "Display cover eligibility" only possible for receiver | Space: object requires documentation | ||
| 181 | Reading the change documents | |||
| 182 | Currency &2 assigned to FM area &1 is not supported! | |||
| 183 | Not all column headings are defined for the year &1 | |||
| 184 | The program cannot be executed without this information | |||
| 185 | Verify existence of FM area &1 | Space: object requires documentation | ||
| 186 | Processing complete (see log) | Space: object requires documentation | ||
| 187 | Posting of revenues increasing the budget in Funds Management canceled | Space: object requires documentation | ||
| 188 | Index &2 for table &1 exists in a different version | Space: object requires documentation | ||
| 189 | Cannot convert table FMCDRB for revenues increasing the budget | Space: object requires documentation | ||
| 190 | Cannot convert table FMCDRBE for revenues increasing the budget | Space: object requires documentation | ||
| 191 | Conversion of number range interval for cover pools is not required | Space: object requires documentation | ||
| 192 | Extension of number range intervals not possible for cover pools | Space: object requires documentation | ||
| 193 | Extending of number range intervals for cover pools was successful | Space: object requires documentation | ||
| 194 | Budget increasing data for the forecast of revenue successfully converted | |||
| 195 | Not possible to convert data increasing the budget for forecast of rev. | |||
| 196 | No budget increasing data exists for the forecast of revenue | |||
| 197 | Conversion of revenues increasing the budget is not necessary | Space: object requires documentation | ||
| 198 | It is not possible to convert revenues increasing the budget | Space: object requires documentation | ||
| 199 | Revenues increasing the budget were converted successfully | Space: object requires documentation | ||
| 200 | Errors in conversion of table &1; Start program RFFMXPR33 | Space: object requires documentation | ||
| 201 | Coversion of table &1 successful | Space: object requires documentation | ||
| 202 | Budget increasing data for recovery request successfully converted | |||
| 203 | Not possible to convert budget increasing data for recovery order | |||
| 204 | There is no budget-increasing data for the recovery request |
History
| Last changed on/by | 20001211 | SAP | |
| SAP Release Created in |