FI_E - Message Class for FM English Developers
The following messages are stored in message class FI_E: Message Class for FM English Developers.
It is part of development package FMFS_E in software component PSM-FM. This development package consists of objects that can be grouped under "Updating/Integration Funds Management (master lang. english)".
It is part of development package FMFS_E in software component PSM-FM. This development package consists of objects that can be grouped under "Updating/Integration Funds Management (master lang. english)".
Message Nr ▲ | Message Text |
|---|---|
| 001 | Invalid financial transaction in commitment item &1 defined in account &2 |
| 002 | Account &1 in company code &2 in CO area &3 is a cost element |
| 003 | Value type missing in budgetary ledger interface table |
| 004 | Open items/actuals budget status customizing missing for FM area &1 |
| 005 | Debit/Credit posting keys missing in budgetary ledger for FI postings |
| 006 | Update profile & does not exist |
| 007 | Fiscal yr based encumbrance not activated. FM actuals already exist |
| 008 | Posting date must be used for update of value type &1 update profile &2 |
| 009 | Periodic Based Encumbrance Tracking will not be activated. |
| 010 | Fiscal Year Based Encumbrance Tracking will not be activated. |
| 011 | Cannot delete customization update profile & because FM actuals exist |
| 012 | Specified period(s) must be between 0 and &1 for FM area &2 |
| 013 | Specify a beginning period |
| 014 | You cannot specify &1 and &2 set at the same time |
| 015 | The dimension set does not exist |
| 016 | Open item rules saved successfully |
| 017 | An open interval cannot have more than & different authorization group |
| 018 | Period &1/Fiscal Year &2 for &3 not open for FM posting in value type &4 |
| 019 | FM posting will be blocked throughout all of fiscal year & |
| 020 | No open interval rules were defined |
| 021 | Cannot obtain subordinate funds center for FM area &1 fiscal year &2 |
| 022 | The 'to period' must be later than the 'from period' |
| 023 | For fiscal yr based encumbrance, the whole fiscal yr will be open |
| 024 | Rule will be based on all assignments in FM area & |
| 025 | Account collection customizing for budgetary ledger missing for &2 |
| 026 | Cannot post to year &1 which is before current year &2 of doc. item &3/&4 |
| 027 | Company code &1 in funds center &2 master record empty or differs from &3 |
| 028 | Specify a dimension type |
| 029 | Specify a dimension |
| 030 | Fiscal year is missing |
| 031 | The fiscal year & is invalid |
| 032 | Invalid expiration and/or cancellation dates for fund &1 in FM area &2 |
| 033 | Budget subtype is required for the budgetary ledger |
| 034 | At least one GL account was not derived by the budgetary ledger |
| 035 | Specified period(s) must be between &1 and &2 for grant year fund &3 |
| 036 | Revenue/Statistical and OI/Actual resource account missing 0/&1/&2/&3/&4 |
| 037 | Revenue/Statistical and OI/Actual resource account missing for FM area &1 |
| 038 | Open items/Actuals budget status account missing 0/&1/&2/&3/&4 |
| 039 | Fund type &1 does not exist for FM area &2 |
| 040 | Budgeting account missing 0/&1/&2/&3/&4 |
| 041 | No document(s) exists for given selection. |
| 042 | No fund type is defined in fund master record for fund &1 in FM area &2 |
| 043 | Invalid dimension type entry |
| 044 | At least one required field is missing in the BL interface table |
| 045 | FI-GL budgetary ledger document is not balanced. See long text |
| 046 | FI-GL account for the budgetary ledger document is missing |
| 047 | No invoice exists for selected documents |
| 048 | Do not enter a reason code |
| 049 | FM pstg year/per.&1/&2 cannot be earlier than orig pstg year/per.&3/&4 |
| 050 | Posting date/period &1/&2 is earlier than existing date/period &3/&4 |
| 051 | Statistical update in FM (see long text) |
| 052 | Company code(s) selection does/do not exist |
| 053 | No settings for G/L posting reports have been customized |
| 054 | Company code missing in funds center master record for &1 in FM area &2 |
| 055 | Both FM area and company code are missing in at least one document line |
| 056 | Budgeting account for budgetary ledger missing for FM area &1 |
| 057 | Fiscal year & adjusted in line with posting date & |
| 058 | Reason code '&1' is invalid. Enter a valid reason code |
| 059 | Document type &1 for BL does not exist. See long text |
| 060 | Invalid value type entry |
| 061 | Invalid budget type entry |
| 062 | FM posting date must lie in last normal period & if special period used |
| 063 | FM posting date's period does not match period defined |
| 064 | Update profile should use posting date for encumbrances |
| 065 | Encumbrances were posted into future periods (see long text) |
| 066 | Maintain reason code(s) and text(s). See long text |
| 067 | Make an option on commitment budget and/or payment budget |
| 068 | Object type in budgetary ledger interface table missing or more than one |
| 069 | Fund is required for US federal government budgetary ledger postings |
| 070 | Invalid overall budget posting. FM area &1, budget profile &2 |
| 071 | Invalid BL posting. Fund &1 in FM area &2 is either expired or cancelled |
| 072 | Error in filling data for value type and G/L accounts |
| 073 | Debit G/L account number must not be equal to Credit G/L account number |
| 074 | One value type occurs in more than one table entries |
| 075 | System error: Object type AWTYP in interface call missing |
| 076 | No entries in company code &1 |
| 077 | Penalty interest rates have not been maintained |
| 078 | Different grace days disallowed. See long text |
| 079 | Reason codes have not changed -> Nothing to update |
| 080 | Reason code(s) successfully saved/updated |
| 081 | Enter the number of days |
| 082 | Fiscal year selected in FM is different from the one posted in FI-GL |
| 083 | Funds center is a required field for the budgetary ledger |
| 084 | Company code &1 differs from &2 in funds center for &3 in FM area &4 |
| 085 | (Special) payment term error with PO line item no. &1 (see long text) |
| 086 | PO document will now have a payment term &1 |
| 087 | At least one item has special payment terms |
| 088 | Amounts not matching for payment term &1 |
| 089 | Invalid factory calendar or error in factory calendar |
| 090 | Period-Based Encumbrance Tracking is not active |
| 091 | No data found for processing |
| 092 | No penalty interest rate maintained for a date prior to &1 |
| 093 | This inter-company posting is not allowed in the budgetary ledger |
| 094 | Specify & |
| 095 | Line item number &1 does not exist for P.O. number &2 |
| 096 | The baseline date will be changed according to Prompt Payment Act rules |
| 097 | You either have no current value of funds rate or none for this period |
| 098 | FM area & is not active for budgetary ledger |
| 099 | It is not economically justified to take discount on run date of &1 |
| 100 | It is economically justified to take discount on run date of &1 |
| 101 | Invoice received date &1 precedes invoice (document) date &2. See details |
| 102 | No penalties calculated because penalty amount is < specifed minimum |
| 103 | Payment late by &1 days. A penalty will be calculated. |
| 104 | The penalty rate of interest is &1 % |
| 105 | Penalty of &1 &2 needs to be paid because calculated amount > maximum |
| 106 | A penalty of &2 &1 has resulted due to late payment |
| 107 | BL interface table contains no lines after account derivation |
| 108 | Inconsistencies found in the budgetary ledger interface table |
| 109 | This invoice line will not have any net due days adjustments |
| 110 | Split the vendor line items of this invoice. See details. |
| 111 | Negative net due days detected: net due days will be set to 0 |
| 112 | Do not enter an amount if you select manual or automatic split option |
| 113 | When the 'earliest pay' option is selected, you must enter an amount |
| 114 | You have not maintained customizing table for invoice lines. See details |
| 115 | An entry with the key &1 &2 &3 does not exist in your customizing table |
| 116 | Invoice payment term error for earliest pay. See details |
| 117 | Split the invoice lines manually |
| 118 | Enter a general ledger account number and/or a value type |
| 119 | Same G/L account-value type pair occurs in more than one table entry |
| 120 | Closeout rules not defined |
| 121 | Document &1 cannot be completed since line item &2 not in fiscal year &3 |
| 122 | No FM obligation closeout rules defined |
| 123 | Posting date is blank, fund status cannot be derived |
| 124 | Field "Object number" (ROBJNRZ) in table FMIT is not filled |
| 125 | Choose at least one flag from WBS element, cost center, and order number |
| 126 | Fast Pay maximum amount error. See details. |
| 127 | Goods received non-valuated flag error for Fast Pay. See details |
| 128 | Inactive FM update profile & does not exist |
| 129 | FM area is blank, fund status cannot be derived |
| 130 | Fiscal year variant empty for FM area &1 |
| 131 | Document type and value type cannot be generic simultaneously |
| 132 | Due to reconciliation problems, after creation, do not modify accounts |
| 133 | Debit/credit posting keys not customized for FI automatic postings |
| 134 | Adjusted net due days error. See details |
| 135 | Adjusted net due days &2 is less than the first discount days &1 |
| 136 | FI-GL Budgetary ledger document is not balanced. Check transaction BPACC |
| 137 | Budgeting document type is a required field for the budgetary ledger |
| 138 | Material group &1 cannot be used for Fast Pay. See details |
| 139 | Default vendor payment term &2 was changed. |
| 140 | Error occurred during the BL document posting. Check log with SLG1 |
| 141 | Maintain improper invoice reason code(s) and text(s). See long text |
| 142 | Company code is a required field for the encumbrances program |
| 143 | Fast/Accelerated Payment terms error |
| 144 | Payment type error. See details |
| 145 | Invoice &1 still contains improper reason code(s) |
| 146 | You changed from a normal payment term &1 to an Accelerated Pay term &2 |
| 147 | Negative net due days of &1 detected. Change baseline date manually to &2 |
| 148 | Invoice &1 does not contain a reference number |
| 149 | Invoice &1 already exists with reference number &2 |
| 150 | Either posting date or original date or both are blank |
| 151 | Posting date is earlier than the original commitment/obligation's date |
| 152 | Material group &1 cannot be used for special materials in Prompt Pay |
| 153 | This purchase order will now have a Fast Pay payment term of &1 |
| 154 | This invoice document has an Accelerated Pay payment term of &1 |
| 155 | >So, the adjusted net due date is &1 |
| 156 | >No penalties are due |
| 157 | >Late payment of &1 days over the adjusted net due date of &2 |
| 158 | SGL transaction code not found although line has been defined as relevant |
| 159 | The original baseline date &1 was set to the invoice receipt date &2 |
| 160 | Manually reverse corresponding BL document &1/&2/&3 as well |
| 161 | Fast Pay payment term and invoice line item handling conflict |
| 162 | Original payment term &1 changed to &2 because of special material |
| 163 | New payment term &1 has an unadjusted net due days figure of &2 days |
| 164 | Payment term &1 has an unadjusted net due days figure of &2 days |
| 165 | System error: No lines found in table BSEG for reversal |
| 166 | Data for the current posting is not available for &1 / &2 / &3 |
| 167 | No PO line items data found for PO &1 and line item &2 |
| 168 | No PO statistics are available for PO &1 and line item &2 |
| 169 | |
| 170 | Table &1 has no accounts for determination factor &2 and trans. code &3 |
| 171 | Table &1 has no accounts for SGL transaction code &2 |
| 172 | Goods acceptance date &2 of document &1 will be used for adjustments |
| 173 | An adjustment of &1&2 made to the net due days. New net due date &3 |
| 174 | &1 is not a business day; date adjusted forward to next business day &2 |
| 175 | Time lag and business day adjustment resulted in real due date of &1 |
| 176 | Final net due days is &3 which is &1 less baseline date of &2 |
| 177 | Budget type is required for the budgetary ledger |
| 178 | Material group - payment term mismatch for Fast Pay |
| 179 | Improper invoice adjust of &1&2 made to net due days. New net due date &3 |
| 180 | Too many Funds Management account assignments selected |
| 181 | Derived budgetary ledger line items not balanced. See long text |
| 182 | No BL account has been defined yet for SGL transaction code &1/&2 |
| 183 | No BL account has been defined yet for SGL determination factor &1/&2 |
| 184 | Required field &1 missing for US SGL budgetary ledger |
| 185 | Could not post into Budgetary Ledger. Uncheck the final indicator(s) |
| 186 | US SGL transaction code &1 is in SAP name space, use 'XYZ' |
| 187 | US SGL determination factor &1 is in SAP name space, use 'XYZ' |
| 188 | No relevant documents for discounts available. |
| 189 | No relevant documents for penalties available. |
| 190 | Multiple invoices &1 already exist with reference number &2 |
| 191 | Default Fast Pay payment term error |
| 192 | GL account for open items and actuals not derived. Read long text |
| 193 | GL account for old budgeting or BCS not derived. Read long text |
| 194 | Change of budget scope from overall to annual is not allowed |
| 195 | Change of budget scope from annual to overall is not recommended |
| 196 | The fund type is used in a fund. Entry cannot be deleted. |
| 197 | Invalid combination per the fund message derivation tool. See long text |
| 198 | Document with quantity difference not displayed because PPA is active |
| 199 | No invoices to release |
| 200 | Error in Funds Management document. See OSS note 658249. |
| 201 | This message prevents an inconsistency in FM. See OSS note 658249. |
| 202 | No change made to payment term |
| 203 | No suitable records found |
| 204 | & messages occurred during the process. Check the message log |
| 205 | Functional area &1 does not exist |
| 206 | Functional area &1 is not valid for &2 &3 |
| 207 | No Hierarchy Flag is only valid for German Local Authorities &1 |
| 208 | Derivation strategy &1 contains derivation rules |
| 209 | Derivation strategy &1 assigned to company code &2 |
| 210 | Company code &1 is not assigned to an FM derivation strategy |
| 211 | Treasury processing time has not been maintained |
| 212 | Derivation strategy &1 (Class:&2 SubClass:&3 Strategy:&4) does not exist |
| 213 | The selected derivation strategy does not exist |
| 214 | XXXXXXXXXXXXXXXXXXXXXXXx |
| 215 | Field &1 is not used in derivation strategy &2 |
| 216 | You do not have authorization to display derivation strategy &1 |
| 217 | Object type &1 cannot use selected field status for earmarked fund |
| 218 | Object type &1 must have field status customized for earmarked fund |
| 219 | Blank values not allowed for FM area and object type |
| 220 | Existing commitment data will not be deleted by the deactivation. |
| 221 | The selected derivation strategy &1 does not have any editable rule |
| 222 | The exclude flag has been updated on &1 invoice line items |
| 223 | Principle of prudence document types not supported for LIV documents |
| 224 | Document &1 was corrected but the inconsistency cannot be displayed. |
| 225 | Discount days have been adjusted for Treasury processing time |
| 226 | Periods must be between &1 and &2 |
| 227 | Improper invoice: return date not earlier than current date |
| 228 | Improper invoice: return date is mandatory |
| 229 | Previous returned invoice &1 &2 is not in 'Park' status |
| 230 | Same reference document &1 exists in the other invoice |
| 231 | Previous returned invoice &1 &2 does not exist |
| 232 | Improper invoice: return date must not be blank if improper reasons exist |
| 233 | Invoice recpt date &1 must be later than last invoice return date &2 |
| 234 | No long text available |
| 235 | Note: all uncleared lines in document will receive same update |
| 236 | No change history to display |
| 237 | No authorization for rule of der. strategy &1, activity &2, auth. obj. &3 |
| 238 | No authorization for derivation strategy &1, activity &2, auth. obj. &3 |
| 239 | Reason code '&1' in document &2 is invalid. Enter a valid reason code |
| 240 | PPA is not active in company code &1 |
| 241 | No Accelerated Pay payment term has been maintained |
| 242 | Payment term &1 has been changed to Accelerated Pay payment term &2 |
| 243 | Amount Splitting can only be used with Manual Splitting. |
| 244 | Original payment term &1 changed to &2 due to Pay at the Earliest setting |
| 245 | The baseline date and the PPA net due date are more than &1 days apart |
| 246 | The PPA calendar ID has not been maintained |
| 247 | Entries have not yet been saved |
| 248 | PCARD basis points are greater than CVFR. Payment term changed to &1 |
| 249 | Payment term changed from &1 to the most advantageous payment term &2 |
| 250 | Performance in processing over 100,000 records will be low |
| 251 | &1 |
| 252 | Choose another FM closing operation |
| 253 | No strategy assigned to FM area &1,sender year &2,closing operation &3 |
| 254 | No data available for the input fields selected. Select other fields. |
| 255 | Select at least one source object by checking the relevant checkbox |
| 256 | Selected &1 do not exist in the master data. Enter valid selections. |
| 257 | No balancing account customized for company code &1 |
| 258 | Cancellation date must not be earlier than the expiration date |
| 259 | See SAP Note 2118110 for more information |
| 260 | Cannot delete the application logs |
| 261 | Amount is too large; leads to amount field overflow. |
| 262 | No trace data available for display. |
| 263 | Action not valid on this line. |
| 264 | Trace log data deleted successfully |
| 265 | No trace log data to delete |
| 266 | No strategies available for tracing due to missing authorizations |
| 270 | Negative net due days of &1 detected. Baseline date changed from &2 to &3 |
| 271 | PO &1 and line item &2 cannot be used for Fast Pay invoice PO reference |
| 272 | PO &1 and line item &2 are not referenced on any FP invoice line item |
| 273 | Invoice document &1 &2 released |
| 274 | Invoice document &1 &2 was not released |
| 275 | Goods movement created for PO &1 and line item &2 |
| 276 | No invoices released for PO &1 and line item &2 |
| 277 | Automatic transfer lines only for invoices with one vendor line |
| 278 | Automatic transfer lines only for same vendor in DP and invoice |
| 279 | Payment term changed from an Accelerated Payment term |
| 280 | Tax is not supported for automatic transfer lines |
| 281 | Due to the auto-clearing, there are already 999 line items. See long text |
| 282 | Trading Partner &1 does not exist |
| 283 | The minimum amount must be less than the maximum amount |
| 284 | Payment Type must be Accelerated Pay |
| 285 | Accelerated payment term &1 has already been used |
| 286 | Accelerated pay criteria has been met but a payment term does not exist |
| 287 | No automatic Down Payment Clearing because of different currency |
| 290 | Original terms of payment &1: &2 |
| 298 | Groups are not allowed as conditions |
| 299 | Enter a controlling or FM area |
| 300 | Original purchase order FM account assignment changed incorrectly |
| 301 | Enter &1 as a source field or define a condition for &2 |
| 302 | Document: &1, Line Item: &2 |
| 304 | Any kind of Sets are not allowed as target fields |
| 305 | Your lock overlaps with the lock of user &1 set on &2, &3 |
| 306 | &1 is not a valid entry |
| 307 | Controlling area or company code mandatory if certain SETs are used |
| 308 | Inconsistencies found for locks of derivation tables (rules) |
| 309 | Enter a range for the selection of data. Wildcards are allowed. |
| 310 | Data are overlapping with a lock from user &1 set on &2, &3 |
| 311 | There are &1 lines with empty targets |
| 312 | There are overlaps between source fields. Correct this. |
| 313 | If you enter a set, leave the fields for the set content empty |
| 314 | The whole line is initial. Enter some data. |
| 315 | Line overlaps with an already existing line on the database (&1) |
| 316 | Lock on Set &1 failed (database table &2) |
| 317 | Set is locked by user &1 since &2, &3 |
| 319 | Deletion of data container failed. Lock will not be removed |
| 320 | An entry is mandatory if you enter a set (&1) |
| 321 | Current document must follow the PPA Exclude Ind as EF &1 &2 |
| 332 | Updating table &1 |
| 333 | Found &1 derivation rules |
| 334 | Found &1 derivation rules which are using SETs |
| 335 | Nothing to do for table &1 |
| 336 | Starting at &1 |
| 337 | Finished at &1 (&2 millisec) |
| 338 | Strategy: &1, Env: &2, step number: &3 |
| 339 | Inconsistencies found for derivation strategy processing. Use &1. |
| 370 | Simulation successful |
| 371 | Simulation failed |
| 380 | Combination of GR/IR control not allowed in FM for external services |
| 381 | Mandatory FM field '&1' is not updated |
| 382 | Replaced with FICUSTOM352 |
| 383 | Multi-Year GR posting not confirmed (SAP Note 2118110) |
| 390 | FMDERIVE:Invalid format for field &1 / &2 in call to Function &3 |
| 400 | Fiscal year &1 has no hierarchy assigned in FM area &2 |
| 401 | CI &1: comparison fails for &2 |
| 402 | CI &1 in FM area &2 will be created as year independent. |
| 403 | CI &1 in FM area &2 has no hierarchy entry in year &3 |
| 404 | FC &1 added as top FC, FM area &2, hierarchy variant &3 |
| 405 | Existence interval of funds center &1 changed in FM area &2 |
| 406 | Hierarchy variant &1 is the new year-independent hierarchy variant |
| 407 | FC &1: comparison of parent FC, hierarchy variant &2, fails |
| 408 | FM Area is blank -> Enter FM Area |
| 409 | Reference Fiscal Year is blank -> Enter Reference Fiscal Year |
| 410 | Hierarchy variant entries are currently blocked |
| 411 | |
| 432 | Invalid expiration and/or cancellation dates for fund &2/&1 BP &3 pair |
| 440 | External maintenance of FM account assignment is not allowed |
| 441 | External maintenance of FM account assignment element &1 is not allowed |
| 500 | **** Messages for Invoice Stages **** |
| 501 | No change history records found |
| 502 | Data not changed |
| 503 | Invoice status saved |
| 504 | Status update failed |
| 505 | No records were selected |
| 506 | Invoice Stages feature is not active in company code &1 |
| 507 | Invoice status &1 not allowed |
| 508 | Status for document &1 was not updated and was reset to original value &2 |
| 509 | &1 &2 &3 &4 |
| 510 | Messages were issued during the update process. Check application log. |
| 580 | With Funds Management active, SO line item numbers cannot exceed '99999'! |
| 581 | Funds Management active - condition counter cannot exceed '99' at line &1 |
| 617 | Entered amount for down payment &1 exceeds clearable amount of &2 &3. |
| 618 | Entered amount for down payment &1 exceeds invoice amount |
| 619 | Only enter amounts equal to zero or greater than zero |
| 620 | Entered amounts referencing &1 &2 exceed invoice amount referencing &1 &2 |
| 621 | No errors found |
| 751 | Current configuration to read on line item level is not recommended |
| 752 | Function only available in transfer program RFFMTTTOBL |
| 753 | Incomplete configuration to transfer program RFFMTTTOBL |
| 754 | More than nine derivation calls are not supported |
| 792 | Application of funds &1 &2 not valid on &3 for fund &4 |
| 800 | --------------- XPRA Messages ----------------- |
| 801 | Error when converting table &1 for the strategy &2 &3 &4 |
| 802 | Strategy &1 &2 &3 (client &4) sucessfully converted |
| 850 | --------------- S4H Messages -------------------------------- |
| 851 | FM01X settings to control FMDERIVE are no longer supported |
| 852 | Invalid Commitment Item for the GR/IR Clearing Account line |