FMKU - FM budgeting, kernel utilities

The following messages are stored in message class FMKU: FM budgeting, kernel utilities.
It is part of development package FMBPA_E in software component PSM-FM-BCS-BU. This development package consists of objects that can be grouped under "New budgeting: FM application part".
Message Nr
Message Text
001Doc. &1 in FM area &2 and year &3 not saved (problems when writing to &4)
002Document &1 does not exist in year &2 and FM area &3
003Original document &1 does not exist in year &2 and FM area &3
004Document &1 in year &2 and FM area &3 is reversed or a reversal
005Document &1 in year &2 and FM area &3 is not a posted document
006Document &1 in FM area &2 and year &3 is not a preposted document
007Document has not been posted (problems when accessing &1)
008Held document &1 does not exist for user &2 and FM area &3
009Held document &1 already exists for user &2 and FM area &3
010Original document or reversal proposal is missing
011Enter a posting date
012Enter a document date
013Long text indicator has no valid value
014Enter at least one document line
015Enter a non-zero amount for at least one period
016Problem when deleting in database
017Period &1 is not valid
018Process &1 does not exist
019Budgetary ledger is active in FM area &1, enter a posting date
020Budgetary ledger is not active in FM area &1, do not enter a posting date
021Fiscal year &1 does not correspond to the posting date entered
022&1 item not allowed for this budget process
023Period &1 does not correspond to the posting date entered
024Only one budgeting period should be used
025Enter a document type
026Specify &1
027For the carryover, enter 2 fiscal years
028Use of &1 not allowed
029Enter a fiscal year
030Enter an FM area
031Enter a funds center
032Enter a commitment item
033Budgeting not allowed for commitment item &1/&2
034No matching commitment item found for budgeting
035Sender or receiver posting period should correspond to posting date
036For process &1 only one fiscal year is permitted for line items
037There is a conflict in input data for calculation of the grouping key
038The fiscal years of sender and receiver must be consecutive
039The process on the line level is empty
040There are too many different processes on the line items
041The currency must be &1
042Line items and totals are consistent
043Substitution: field &1 is substituted by initial value 0 or BLANK
044Additional lines: the target field &1 is initial 0 or BLANK
045Process &1 is not supported for entry document
046The document status must be filled
047&1 should not be the only process on the line
048Document status &1 is incorrect
049Only one commitment item category is allowed for the process
050No document corresponds to the selection criteria
051Type of legislation &1 is not valid
052Data locked by user &1
053Document must be balanced (&1)
054Use the PRINT icon of the SAP List Viewer
055The technical organization &1 is not supported
056You are not allowed to delete budget data in version &1
057Carryover documents cannot be deleted
058Documents with external references cannot be deleted
059No matching functional area found
060Enter a version
061Enter a budget category
062Enter an external document number
063Enter an external document number between &1 and &2
064This external document number is already in use
065Do not enter external doc number: number range is for internal doc number
066External document number should not be filled for held document
067For carryover select both processes CORV and COSD
068For transfer select both processes RECV and SEND
069Some documents have other process/budget type combination
070Rule &1 is not valid for line generation
071Invalid input (value type &1, process &2)
072Process &1 is not supported with value type &2
073The value type used is not supported with document type &1
074Value type &1 does not exist
075Release is not active. Document type &1 is not supported
076Some documents contain a value type for budgeting and not only release
077You can only carry over the budget using the same grouping key
078In the transfer the grouping key for &1 must be unique
079Delete budget entry documents: AWORG and AWTYP should always be filled
080Delete budget entry documents: either fill AWREF or flag "delete all"
081The release is not allowed for the &1 &2
082Release and budget amounts are inconsistent
083The budget amount is not sufficient for release
084You cannot create an additional line with &1 initial 0 or BLANK
085You cannot carry over a budget if the budgetary ledger is active
086The FM area of the document &1 is different from the one in input: &2
087Release not allowed using a fund with the status of automatic release
088Period &1 is not opened for budgeting
089Total budget for address &1 in fiscal year &2 should not be negative
090Consumable budget for address &1 should not exceed the total budget
091Document must be balanced (&1)
092The release function is not available for budget category &1
093Processes &1 and &2 cannot be used with budget category &3
094Budget category &1 is not supported for closing operations
095Line items and totals are reconstructed
096Document number &1 in year &2 and FM area &3 cannot be processed
097Client of document &1 is different from the one in input: &2
098The FM area of the document &1 is different from the one in input: &2
099The receiver fiscal year should be greater then sender fiscal year
100Error during selection from database table &1
101Budget category &1 does not exist
102Change history not active for the FM area &1
103Save the changes before you undo this preposted document
104Save the changes before you post this preposted document
105Request already approved
106Request already rejected
107Request &1 already exists for user &2 and FM area &3
108Request already submitted
133Requested transaction, program, or report is not available
134Check the general process and the processes on the level of the lines
135The commitment item category is wrong
136Enter the name of the person responsible
137Enter a header text
138Enter a standard text
139Enter a reporting year for cohort
140Enter a public law
141Enter a type of legislation
142Enter a long text
143Enter a line text
144Migration has been succesfully carried out
145Errors occurred during migration. See application log
146Number of error messages: &1
147Number of migrated records: &1
148No data corresponding to your selection for fund &1
149The time horizon of the fund &1 is different in FB and BCS Customizing
150There are inconsistencies between Customizing of FB and the database
151Creation of documents for Revenues Increasing the Budget not allowed
152Data already exists for fund &1, version &2. Migration not allowed
153Value type &1 not supported for migration
154Budget type &1 not supported for migration
155The amounts for overall and annual budget are different
156There is no annual amount that corresponds to the overall amount
157Differing value types are derived from the assignment tables
158Inconsistencies in assignment tables in Customizing
159Annual amount differs from the sum of the period values
160Error in distribution. Amount assigned to period &1
161Preposted data not migrated for fund &1 fiscal year &2
162No authorization for FM area &1 document type &2 activity &3
163No authorization for FM area &1 version &2 budget categ. &4 activity &3
164No authorization for FM area &1 authorization group &2 activity &3
165Document &1 has already been migrated to version &2
166Unexpected situation in migration report (&1)
167Parked document &1 cannot be migrated
168Reversal document of document &1 is parked. Migration not allowed
169No annual data for fund &1 between &2 and &3. Overall amount not migrated
170BCS document &1 year &2 has been reversed
171Data already migrated using documents for fund &1 fiscal year &2
172Previous BCS documents for document &1 cannot be deleted anymore
173Unexpected budget memo type &1 for cover pool &2
174Rules for receiver account assignment &1 &2 not migrated
175Unexpected budget memo type &1 for receiver address &2 &3
176Unexpected budget memo type &1 for sender address &2 &3
177Error when accessing members of the cover pool &1
178Commitment item &1 is not allowed as source for balanced increase
179Commitment item &1 is not allowed as target for balanced increase
180The amounts of the source and the target must be equal
181The amounts of source and target must be equal for cash year &1
182Posting date should correspond either to sender year or receiver year
183Checks based on database values are missing in test mode.
184Enter a transfer agency
185Enter a transfer account
186Enter a trading partner
187Enter a US government field
188Status of document &1 &2 &3 is not correct
189No authorization for certain FM Account Assignments activity &1
190Option 'No Availability Control' not supported - see note 1037571
191Budget line &1 with process &2 is not equal to zero. Migration fails
192Budget line &1 with process &2 is not migrated
193Document &1 contains the budget category &2 not in selection criteria
195Specify &1
200You can only select an original budget entry document
201Not allowed to post using the document type &1 customized for workflow
210Some documents cannot be displayed (see long text)
211The application calling BCS does not give correct references &1 &2 &3
212Order of hierarchy levels invalid; change the order
213Select a node or item of the tree
214You are not authorized to display the data of all budget addresses
215Function is only supported for a single budget document
300The subdivision ID &1 is not consistent with field &2 containing value &3
301Posting subdivisions &1,&2,&3,&4 without Commitment Item is not allowed
302Posting subdivisions &1,&2,&3,&4 without Funds Center is not allowed
303Posting subdivisions &1,&2,&3,&4 without Fund is not allowed
304Posting subdivisions &1,&2,&3,&4 without Functional Area is not allowed
305Document cannot be posted with Functional Area &1 w/o its subdivision ID
306Document cannot be posted with Fund &1 without its subdivision ID
307Document cannot be posted with Funds Center &1 without its subdivision ID
308Document cannot be posted with Commitment Item &1 w/o its subdivision ID
Privacy Policy