J# - ALM Error Messages
The following messages are stored in message class J#: ALM Error Messages.
It is part of development package JBRA in software component FIN-FSCM-TRM-AN. This development package consists of objects that can be grouped under "Risk Management: Asset/Liability Management".
It is part of development package JBRA in software component FIN-FSCM-TRM-AN. This development package consists of objects that can be grouped under "Risk Management: Asset/Liability Management".
Message Nr ▲ | Message Text |
|---|---|
| 001 | **** ALM Error Messages************************************************ |
| 002 | An error occurred when preparing the simulated transactions |
| 003 | An error occurred during the gap evaluation for simulated transactions |
| 004 | Choose only one permitted simulation type (not &) |
| 005 | Simulation type & is not processed for the specified sim. category & |
| 006 | The product type specified & cannnot be used with simulation category & |
| 007 | The product type specified & does not exist |
| 008 | The specified scenario progression & does not exist or is empty |
| 009 | Sim. cat. 110 (fixed-term deposits) is permitted for BS positions only |
| 010 | Enter a term longer than 0 |
| 011 | No interest could be determined for some simulated transactions |
| 012 | No transactions were simulated due to lack of input in node &1 |
| 013 | Serious errors occured during simulation. Run terminated. |
| 014 | Simulation succesfully completed |
| 015 | The following messages are related to an ALM simulation run: |
| 016 | Simulation completed successfully (Check the warnings) |
| 017 | Simulation category 120 in connection with capital-related CFs |
| 018 | Non-standard selection of liquidity levels (not 'actual' or 'none') |
| 019 | The specified CF type & has the wrong CF indicator & (instead of &) |
| 020 | The specified CF type & does not exist |
| 021 | Processing ended without changes |
| 022 | Changes saved successfully |
| 023 | An error occurred when the data was being saved. Processing terminated |
| 024 | The specified valuation rule & does not exist |
| 025 | Error while converting CF indicator to CF type |
| 026 | Error when saving table & |
| 027 | An error occurrred when writing data to the database. Return code & |
| 028 | Error in &. See long text |
| 029 | The following messages refer to fictitious transactions in ALM |
| 030 | **** ALM error messages: Interest/interest reference/scenarios |
| 031 | No yield curve type was found for evaluation type & |
| 032 | No definition was found for yield curve (&;&) |
| 033 | No market data found |
| 034 | No scenario data found |
| 035 | Scenario progression & not found |
| 036 | No interest rate was found for simulated transaction; Start & end & |
| 037 | No interest found for yield curve (& &) |
| 038 | Unable to determine the interest for the date constellation |
| 039 | Interest reference could be determined for the simulated transaction |
| 040 | The forward curve and the simulated transaction have different currencies |
| 041 | Forward curve not maintained for the reference interest rate |
| 042 | A serious error occured during individual simulation |
| 043 | Error during currency translation for a simulated transaction |
| 044 | The planning variant contains a currency parameter that is not permitted |
| 045 | Choose a valid scenario progression (use F4) |
| 046 | Enter a company code, otherwise the P+L cannot be simulated |
| 047 | Standard interest calculation method act/365 used |
| 048 | Write-down rule & does not exist |
| 050 | ********Error messages for write-down calculation********************** |
| 051 | No settings for write-down rule &1 in evaluation type &2 |
| 052 | No key figures exist for the financial object |
| 053 | The book value in transaction currency not found |
| 054 | The book value in local currency was not found |
| 055 | The purchase price in transaction currency was not found |
| 056 | Purchase price in local currency not found |
| 057 | Error when calculating the depreciation risks |
| 058 | Error when calculating the depreciation risks |
| 059 | Base portfolio &1 in company code &2 has no key figures |
| 060 | Error occurred when calculating the market value in P+L simulation |
| 061 | Error during currency translation in P+L simulation |
| 070 | ********* Interest determination in ALM ********************************* |
| 071 | Unable to determine the yield curve |
| 072 | Maintain the parameters |
| 073 | Maintain either the reference interest rate or the index |
| 074 | Enter the weighting |
| 075 | The total weighting must equal 100% |
| 076 | The value you entered does not exist. Check your entry |
| 077 | Unable to save the parameters |
| 078 | Parameters saved |
| 079 | Unable to calculate the market price weighting |
| 080 | The yield curve does not contain any grid points that match the term |
| 081 | Market price weightings are deleted if the simulation uses floaters |
| 082 | Check the entries you made for the yield curve |
| 100 | **** ALM Error Messages************************************************ |
| 101 | Simulation category & not appropriate for gap evaluation & |
| 102 | The 'date from' (&) must be earlier than or the same as the 'date to' (&) |
| 103 | No data was entered, therefore no transactions were saved |
| 104 | The saving of data was terminated by the user |
| 105 | Internal error when saving the data - see the error log |
| 106 | Error when generating program sections |
| 107 | Error during automatic creation of financial objects |
| 108 | Simulated transactions successfully saved |
| 109 | View &V1& and PH &V2& belong to planning variant &V3&; see long text |
| 110 | Maturity band is not absolute; choose an absolute maturity band |
| 111 | Planning variant & for view & and PH & was deleted |
| 112 | Simulation based on all transactions in evaluation currency |
| 113 | Simulation is not possible on this node |
| 114 | You cannot maintain characteristics on this node |
| 115 | Simulation category & not currently supported |
| 116 | Simulation category & is not currently supported in individual simulation |
| 117 | The simulated transactions/positions were saved under sim. run no. &. |
| 118 | Error when processing fictitious transactions |
| 119 | Start of the term should be earlier than or equal to the end of the term |
| 120 | Only transaction category 100/200 is allowed for this trans., not & |
| 121 | Enter EITHER the fixed interest rate OR the reference interest rate |
| 122 | & transaction(s) flagged for simulation |
| 123 | End of term set to & |
| 124 | Unable to determine an interest rate |
| 125 | The quota must be in the range between 1 and 100 |
| 126 | The quota must not be greater than 100 |
| 127 | & & & & |
| 128 | Error when determining payment amount based on exchange rate and amount |
| 129 | Error when determining the exchange rate from payment amounts |
| 130 | The entered payment amounts and exchange rates do not correspond |
| 131 | The entered payment amounts and exchange rates do not correspond |
| 132 | For forward exch.transactions the term start must equal the eval.date (&) |
| 133 | Unable to determine an exchange rate |
| 134 | Error when converting to the enhanced risk object |
| 135 | Error when determining the simulated positions and their items |
| 136 | Error when saving simulated transactions/positions to the database |
| 137 | Error when generating the financial objects for the simulated positions |
| 138 | Error during extended maintenance of characteristic values |
| 139 | No new simulation run number could be read |
| 140 | Select a node before you enter data |
| 141 | Barrier options must have exercise type 'European' |
| 142 | 'Close from' date must be before 'Close to' date |
| 143 | Enter all the information required |
| 144 | Cannot determine exchange rate (&/&) on & |
| 145 | & records saved/updated successfully |
| 146 | Test run. No changes were made to the database |
| 150 | Enter a date that is after or on the horizon date of the evaluation |
| 160 | Enter a view, a portfolio hierarchy, and a PH node |
| 161 | You do not have authorization for the transaction & |
| 200 | ******** Planning variants ********************************************** |
| 201 | Choose a different portfolio hierarchy |
| 202 | Select one entry only |
| 203 | Select an entry |
| 204 | The sequence number in the parameter records must be unique |
| 205 | The sequence number must be greater than 0 |
| 206 | The planning variant does not match the view and/or portfolio hierarchy |
| 207 | Default settings are missing in the planning variant |
| 208 | The maturity band determined is relative |
| 209 | Internal error - inform the system administrator |
| 210 | The simulated transactions cannot be saved without a planning variant |
| 211 | Characteristics co.code and summarization rule were set to default (&, &) |
| 212 | The market price weighting does not match the view + portfolio hierarchy |
| 213 | Planning variant &1 is being edited |
| 214 | Enter the transaction category, interest calculation method and volume |
| 215 | There is no planning variant with the name &1 |
| 216 | Planning variant &1 is not unique. Enter the view and portfolio hierarchy |
| 217 | No data was saved because no data was changed |
| 218 | Data was saved |
| 219 | The data was not saved (error in table &1, subr = &2) |
| 220 | Make an entry in all fields |
| 221 | Planning variant &1 with view &2 and portfolio &3 already exists |
| 222 | Portfolio hierarchy &1 does not exist in view &2 |
| 223 | No data was deleted because table &1 is locked |
| 224 | No data was deleted when &1 was locked due to a system error |
| 225 | Due to an error that occurred when locking &1 no data was deleted |
| 226 | The planning variants (table JBAPLANVT) are being converted |
| 227 | There are no old planning variants for conversion |
| 228 | Error during DELETE of table JBAPLANVT in the database |
| 229 | The planning variants were successfully converted |
| 230 | Error during INSERT of table JBAPLANVT in the database |
| 231 | Error when generating the portfolio hierarchy |
| 232 | Portfolio hierarchy &1 &2 is deactivated, and cannot be used in variants |
| 233 | Error when saving the planning variant |
| 234 | Serious error occurred when saving the planning variant |
| 235 | Unknown error occurred when saving the planning variant |
| 236 | Unable to copy planning variant; it contains no planning parameters |
| 237 | Elasticity may only have values between 0 and 1 |
| 238 | The selected simulation run was already deleted |
| 239 | The planning variant was deleted |
| 240 | No planning parameters exist on this node |
| 250 | Key figure category &1 is not a percentage value |
| 251 | Evaluation type should be key date position (01) or average position (05) |
| 300 | **** ALM error messages: Log |
| 301 | No term-dependent simulation parameters exist |
| 400 | Due date scenario &1 already exists |
| 401 | Due date scenario &1 does not exist |
| 402 | Creation of due date scenario &1 with template terminated |
| 403 | Due date scenario &1 already exists |
| 404 | Due date period &1 already exists |
| 405 | Creation of due date period &1 with template terminated |
| 406 | Due date period &1 does not exist |
| 407 | Error when deleting due date scenario &1 from the database |
| 408 | Due date scenario &1 was deleted |
| 409 | Error occurred when saving changes to the database |
| 410 | Due date scenario &1 successfully changed |
| 411 | Error when saving due date scenario &1 |
| 412 | Due date scenario &1 was saved successfully |
| 413 | An error occurred when deleting due date period &1 from the database |
| 414 | Due date period &1 deleted |
| 415 | Error occurred when saving changes to the database |
| 416 | Due date period &1 was changed successfully |
| 417 | Error occurred when saving due date period &1 |
| 418 | Due date period &1 saved successfully |
| 419 | Short description &1 already exists for another due date scenario |
| 420 | Short description &1 already exists for another due date period |
| 421 | The due date scenario is already being processed |
| 422 | There is already an entry with sequential number &1 |
| 423 | Specify a name for the due date period |
| 424 | Specify a name for the due date scenario |
| 425 | Position &1 was created for fictitious risk objects |
| 426 | Due date scenario &1 was transported |
| 427 | Choose a smaller time unit for the subincrement (&1) |
| 428 | Choose a smaller subincrement (&1) |
| 429 | Combination of base amount + time unit for subincrement is not permitted |
| 430 | Creation of due date scenario &1 was canceled |
| 431 | Combination of inflow and time unit for subincrement is invalid |
| 599 | ********* ALM List tool ************************************************* |
| 600 | The data cannot be displayed: the maximum list width was reached |
| 601 | Error during dynamic callup of the ALV tool |
| 602 | Error when generating program sections |
| 603 | Error in list column control |
| 604 | Error in ABAP List Viewer |
| 605 | Select at least one column |