SAP ABAP Message Class FMKU (FM budgeting, kernel utilities)
Basic Data
Hierarchy
☛
EA-PS (Software Component) SAP Enterprise Extension Public Services
⤷
PSM-FM-BCS-BU (Application Component) Budgeting
⤷
FMBPA_E (Package) New budgeting: FM application part
⤷
⤷
Attributes
| Message class | FMKU | |
| Short Description | FM budgeting, kernel utilities | |
| Changed On | 20130531 | |
| Last Changed At | 121307 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 | Doc. &1 in FM area &2 and year &3 not saved (problems when writing to &4) | Space: object requires documentation | ||
| 2 | Document &1 does not exist in year &2 and FM area &3 | Space: object requires documentation | ||
| 3 | Original document &1 does not exist in year &2 and FM area &3 | Space: object requires documentation | ||
| 4 | Document &1 in year &2 and FM area &3 is reversed or a reversal | Space: object requires documentation | ||
| 5 | Document &1 in year &2 and FM area &3 is not a posted document | Space: object requires documentation | ||
| 6 | Document &1 in FM area &2 and year &3 is not a preposted document | Space: object requires documentation | ||
| 7 | Document has not been posted (problems when accessing &1) | Space: object requires documentation | ||
| 8 | Held document &1 does not exist for user &2 and FM area &3 | Space: object requires documentation | ||
| 9 | Held document &1 already exists for user &2 and FM area &3 | Space: object requires documentation | ||
| 10 | Original document or reversal proposal is missing | Space: object requires documentation | ||
| 11 | Enter a posting date | Space: object requires documentation | ||
| 12 | Enter a document date | Space: object requires documentation | ||
| 13 | Long text indicator has no valid value | Space: object requires documentation | ||
| 14 | Enter at least one document line | The short text describes the object sufficiently | ||
| 15 | Enter a non-zero amount for at least one period | Space: object requires documentation | ||
| 16 | Problem when deleting in database | Space: object requires documentation | ||
| 17 | Period &1 is not valid | Space: object requires documentation | ||
| 18 | Process &1 does not exist | Space: object requires documentation | ||
| 19 | Budgetary ledger is active in FM area &1, enter a posting date | Space: object requires documentation | ||
| 20 | Budgetary ledger is not active in FM area &1, do not enter a posting date | Space: object requires documentation | ||
| 21 | Fiscal year &1 does not correspond to the posting date entered | Space: object requires documentation | ||
| 22 | &1 item not allowed for this budget process | The short text describes the object sufficiently | ||
| 23 | Period &1 does not correspond to the posting date entered | Space: object requires documentation | ||
| 24 | Only one budgeting period should be used | Space: object requires documentation | ||
| 25 | Enter a document type | Space: object requires documentation | ||
| 26 | Specify &1 | Space: object requires documentation | ||
| 27 | For the carryover, enter 2 fiscal years | Space: object requires documentation | ||
| 28 | Use of &1 not allowed | Space: object requires documentation | ||
| 29 | Enter a fiscal year | Space: object requires documentation | ||
| 30 | Enter an FM area | Space: object requires documentation | ||
| 31 | Enter a funds center | Space: object requires documentation | ||
| 32 | Enter a commitment item | Space: object requires documentation | ||
| 33 | Budgeting not allowed for commitment item &1/&2 | Space: object requires documentation | ||
| 34 | No matching commitment item found for budgeting | Space: object requires documentation | ||
| 35 | Sender or receiver posting period should correspond to posting date | The short text describes the object sufficiently | ||
| 36 | For process &1 only one fiscal year is permitted for line items | Space: object requires documentation | ||
| 37 | There is a conflict in input data for calculation of the grouping key | Space: object requires documentation | ||
| 38 | The fiscal years of sender and receiver must be consecutive | Space: object requires documentation | ||
| 39 | The process on the line level is empty | Space: object requires documentation | ||
| 40 | There are too many different processes on the line items | Space: object requires documentation | ||
| 41 | The currency must be &1 | Space: object requires documentation | ||
| 42 | Line items and totals are consistent | The short text describes the object sufficiently | ||
| 43 | Substitution: field &1 is substituted by initial value 0 or BLANK | Space: object requires documentation | ||
| 44 | Additional lines: the target field &1 is initial 0 or BLANK | Space: object requires documentation | ||
| 45 | Process &1 is not supported for entry document | Space: object requires documentation | ||
| 46 | The document status must be filled | Space: object requires documentation | ||
| 47 | &1 should not be the only process on the line | Space: object requires documentation | ||
| 48 | Document status &1 is incorrect | Space: object requires documentation | ||
| 49 | Only one commitment item category is allowed for the process | Space: object requires documentation | ||
| 50 | No document corresponds to the selection criteria | Space: object requires documentation | ||
| 51 | Space: object requires documentation | |||
| 52 | Data locked by user &1 | Space: object requires documentation | ||
| 53 | Document must be balanced (&1) | Space: object requires documentation | ||
| 54 | Use the PRINT icon of the SAP List Viewer | Space: object requires documentation | ||
| 55 | The technical organization &1 is not supported | Space: object requires documentation | ||
| 56 | You are not allowed to delete budget data in version &1 | Space: object requires documentation | ||
| 57 | Carryover documents cannot be deleted | Space: object requires documentation | ||
| 58 | Documents with external references cannot be deleted | Space: object requires documentation | ||
| 59 | No matching functional area found | Space: object requires documentation | ||
| 60 | Enter a version | The short text describes the object sufficiently | ||
| 61 | Enter a budget category | The short text describes the object sufficiently | ||
| 62 | Enter an external document number | The short text describes the object sufficiently | ||
| 63 | Enter an external document number between &1 and &2 | The short text describes the object sufficiently | ||
| 64 | This external document number is already in use | Space: object requires documentation | ||
| 65 | Do not enter external doc number: number range is for internal doc number | The short text describes the object sufficiently | ||
| 66 | External document number should not be filled for held document | Space: object requires documentation | ||
| 67 | For carryover select both processes CORV and COSD | Space: object requires documentation | ||
| 68 | For transfer select both processes RECV and SEND | Space: object requires documentation | ||
| 69 | Some documents have other process/budget type combination | Space: object requires documentation | ||
| 70 | Rule &1 is not valid for line generation | The short text describes the object sufficiently | ||
| 71 | Invalid input (value type &1, process &2) | Space: object requires documentation | ||
| 72 | Process &1 is not supported with value type &2 | Space: object requires documentation | ||
| 73 | The value type used is not supported with document type &1 | Space: object requires documentation | ||
| 74 | Value type &1 does not exist | The short text describes the object sufficiently | ||
| 75 | Release is not active. Document type &1 is not supported | The short text describes the object sufficiently | ||
| 76 | Some documents contain a value type for budgeting and not only release | Space: object requires documentation | ||
| 77 | You can only carry over the budget using the same grouping key | Space: object requires documentation | ||
| 78 | In the transfer the grouping key for &1 must be unique | Space: object requires documentation | ||
| 79 | Delete budget entry documents: AWORG and AWTYP should always be filled | Space: object requires documentation | ||
| 80 | Delete budget entry documents: either fill AWREF or flag "delete all" | Space: object requires documentation | ||
| 81 | The release is not allowed for the &1 &2 | Space: object requires documentation | ||
| 82 | Release and budget amounts are inconsistent | Space: object requires documentation | ||
| 83 | The budget amount is not sufficient for release | Space: object requires documentation | ||
| 84 | You cannot create an additional line with &1 initial 0 or BLANK | Space: object requires documentation | ||
| 85 | You cannot carry over a budget if the budgetary ledger is active | Space: object requires documentation | ||
| 86 | The FM Area of the document &1 is different from the one in input: &2 | The short text describes the object sufficiently | ||
| 87 | Release not allowed using a fund with the status of automatic release | The short text describes the object sufficiently | ||
| 88 | Period &1 is not opened for budgeting | Space: object requires documentation | ||
| 89 | Total budget for address &1 in fiscal year &2 should not be negative | Space: object requires documentation | ||
| 90 | Consumable budget for address &1 should not exceed the total budget | The short text describes the object sufficiently | ||
| 91 | Document must be balanced | The short text describes the object sufficiently | ||
| 92 | The release functionality is not available for the budget category &1 | Space: object requires documentation | ||
| 93 | The processes &1 and &2 cannot be used with the budget category &3 | Space: object requires documentation | ||
| 94 | The budget category &1 is not supported for closing operations | The short text describes the object sufficiently | ||
| 95 | Line items and totals are reconstructed | The short text describes the object sufficiently | ||
| 96 | The document number &1 in year &2 and FM Area &3 cannot be treated | Space: object requires documentation | ||
| 97 | The Client of the document &1 is different from the one in input: &2 | The short text describes the object sufficiently | ||
| 98 | The FM Area of the document &1 is different from the one in input: &2 | The short text describes the object sufficiently | ||
| 99 | Error during selection from database table &1 | Space: object requires documentation | ||
| 100 | Budget category &1 does not exist | The short text describes the object sufficiently | ||
| 101 | Requested transaction, program, or report is not available | Space: object requires documentation | ||
| 102 | Check the general process and the processes on the level of the lines | Space: object requires documentation | ||
| 103 | The commitment item category is wrong | Space: object requires documentation | ||
| 104 | Enter the name of the person responsible | Space: object requires documentation | ||
| 105 | Enter a header text | Space: object requires documentation | ||
| 106 | Enter a standard text | Space: object requires documentation | ||
| 107 | Enter a reporting year for cohort | Space: object requires documentation | ||
| 108 | Enter a public law | Space: object requires documentation | ||
| 109 | Enter a type of legislation | Space: object requires documentation | ||
| 110 | Enter a long text | Space: object requires documentation | ||
| 111 | Enter a line text | Space: object requires documentation | ||
| 112 | Migration has been succesfully carried out | Space: object requires documentation | ||
| 113 | Errors occurred during migration. See application log | Space: object requires documentation | ||
| 114 | Number of error messages: &1 | Space: object requires documentation | ||
| 115 | Number of migrated records: &1 | Space: object requires documentation | ||
| 116 | No data corresponding to your selection for fund &1 | Space: object requires documentation | ||
| 117 | The time horizon of the fund &1 is different in FB and BCS Customizing | Space: object requires documentation | ||
| 118 | There are inconsistencies between Customizing of FB and the database | Space: object requires documentation | ||
| 119 | Creation of documents for Revenues Increasing the Budget not allowed | Space: object requires documentation | ||
| 120 | Data already exists for fund &1, version &2. Migration not allowed | Space: object requires documentation | ||
| 121 | Value type &1 not supported for migration | Space: object requires documentation | ||
| 122 | Budget type &1 not supported for migration | Space: object requires documentation | ||
| 123 | The amounts for overall and annual budget are different | Space: object requires documentation | ||
| 124 | There is no annual amount that corresponds to the overall amount | Space: object requires documentation | ||
| 125 | Differing value types are derived from the assignment tables | Space: object requires documentation | ||
| 126 | Inconsistencies in assignment tables in Customizing | Space: object requires documentation | ||
| 127 | Annual amount differs from the sum of the period values | Space: object requires documentation | ||
| 128 | Error in distribution. Amount assigned to period &1 | Space: object requires documentation | ||
| 129 | Preposted data not migrated for fund &1 fiscal year &2 | Space: object requires documentation | ||
| 130 | No authorization for FM area &1 document type &2 activity &3 | Space: object requires documentation | ||
| 131 | No authorization for FM area &1 version &2 budget categ. &4 activity &3 | Space: object requires documentation | ||
| 132 | No authorization for FM area &1 authorization group &2 activity &3 | Space: object requires documentation | ||
| 133 | Document &1 has already been migrated to version &2 | Space: object requires documentation | ||
| 134 | Unexpected situation in migration report (&1) | Space: object requires documentation | ||
| 135 | Parked document &1 cannot be migrated | The short text describes the object sufficiently | ||
| 136 | Reversal document of document &1 is parked. Migration not allowed | The short text describes the object sufficiently | ||
| 137 | No annual data for fund &1 between &2 and &3. Overall amount not migrated | The short text describes the object sufficiently | ||
| 138 | BCS document &1 year &2 has been reversed | Space: object requires documentation | ||
| 139 | Data already migrated via documents for fund &1 fiscal year &2 | The short text describes the object sufficiently | ||
| 140 | Previous BCS documents for document &1 cannot be deleted anymore | The short text describes the object sufficiently | ||
| 141 | Unexpected budget memo type &1 for cover pool &2 | The short text describes the object sufficiently | ||
| 142 | Rules for receiver account assignment &1 &2 not migrated | The short text describes the object sufficiently | ||
| 143 | Unexpected budget memo type &1 for receiver address &2 &3 | The short text describes the object sufficiently | ||
| 144 | Unexpected budget memo type &1 for sender address &2 &3 | The short text describes the object sufficiently | ||
| 145 | Error when accessing members of the cover pool &1 | The short text describes the object sufficiently | ||
| 146 | Commitment item &1 is not allowed as source for balanced increase | Space: object requires documentation | ||
| 147 | Commitment item &1 is not allowed as target for balanced increase | Space: object requires documentation | ||
| 148 | The amounts of the source and the target must be equal | Space: object requires documentation | ||
| 149 | The amounts of source and target must be equal for cash year &1 | The short text describes the object sufficiently | ||
| 150 | Posting date should correspond either to sender year or receiver year | The short text describes the object sufficiently | ||
| 151 | Checks based on database values are missing in test mode. | The short text describes the object sufficiently | ||
| 152 | Status of document &1 &2 &3 is not correct | Space: object requires documentation | ||
| 153 | No authorization for certain FM Account Assignments activity &1 | The short text describes the object sufficiently | ||
| 154 | Option 'No Availability Control' not supported - see note 1037571 | The short text describes the object sufficiently | ||
| 155 | The budget line &1 with process &2 is not equal to zero. Migration fails | The short text describes the object sufficiently | ||
| 156 | The budget line &1 with process &2 is not migrated | The short text describes the object sufficiently | ||
| 157 | You can only select an original BCS Entry Document | The short text describes the object sufficiently | ||
| 158 | Not allowed to post using the document type &1 customized for workflow | The short text describes the object sufficiently | ||
| 159 | Some documents cannot be displayed (see long text) | Space: object requires documentation | ||
| 160 | Order of hierarchy levels invalid; change the order | Space: object requires documentation | ||
| 161 | Select a node or item of the tree | The short text describes the object sufficiently | ||
| 162 | You are not authorized to display the data of all budget addresses | Space: object requires documentation | ||
| 163 | Function is only supported for a single budget document | The short text describes the object sufficiently |
History
| Last changed on/by | 20130531 | SAP | |
| SAP Release Created in | 462A |