UJY_EXCEPTION - BPC: Message class for planning
The following messages are stored in message class UJY_EXCEPTION: BPC: Message class for planning.
It is part of development package UJY in software component EPM-BPC-NW. This development package consists of objects that can be grouped under "Planning Functions ( DDB, AVA,MOF)".
It is part of development package UJY in software component EPM-BPC-NW. This development package consists of objects that can be grouped under "Planning Functions ( DDB, AVA,MOF)".
Message Nr ▲ | Message Text |
---|---|
001 | Driver &1 do not exist |
002 | Fail to generate dynamic DDIC table |
003 | Fail to activate dynamic DDIC table |
004 | Fail to delete dynamic DDIC table |
005 | Name of table for driver &1 is too long |
006 | Fail to check the existence of driver table |
007 | Generated driver table &1 is not recorded for drive &2 |
008 | Dimension &1 does not exist |
009 | Fail to calculate dimension member |
010 | No driver table is generated for driver &1 |
011 | No member entered or found for the dimension &1 of driver &2 |
012 | Driver &1's dynamic table &2 not found in the system |
013 | Failed to get the information of environment &1 |
014 | Environment &1 cannot be deleted because driver &2 is using it |
015 | No qualified dimension for driver &1 |
016 | Driver data table is not generated for driver &1 |
017 | Driver entry table is not generated for driver &1 |
018 | Priority table is not generated for driver &1 |
019 | Entry table of driver &1 has duplicated items with same ID &2 |
020 | Two entries affect on the value of driver &1 |
021 | No head priority record for driver &1 |
022 | Multiple head priority record for driver &1 |
023 | No tail priority_record for driver &1 |
024 | Multiple tail priority record for driver &1 |
025 | Identical base driver data derives from multiple unrelated entries |
026 | Duplicated entries occured for driver &1 |
101 | System formula &1 cannot be deleted |
102 | Formula &1 do not exist |
103 | Environment &1 cannot be deleted because customer formula &2 is using it. |
104 | &1 is not valid operand. Operand should start with a letter from A to Z. |
105 | Formula &1 is invalid. A formula should start with an operand,"(" or "-". |
106 | Formula &1 is invalid. A formula should end with an operand or ")". |
107 | "(" is missing in formula &1. |
108 | ")" is missing in formula &1. |
109 | Formula &1 is invalid. Elements sequence in the formula is not correct. |
201 | Rule &1 does not exist |
202 | Rule &1 is using the model &2 |
203 | Environment &1 cannot be deleted because rule &2 is using it |
204 | "&1" is not a valid member of dimension "&2" in scope definition |
205 | |
301 | Operand &1 does not exist |
302 | Target value should be configured to transactional data only |
303 | &1 is not a member of dimension &2 in the definition of operand &3 |
401 | Condition &1 does not exist |
501 | Comparator &1 does not exist |
601 | Environment parameter 'ENABLE_DISAGGREGATION' in IMG not set as 'X' |
602 | Invalid value for parameter "ENABLE_DISAGGREGATION" |
603 | Cannot enable Disaggregation since HANA accelerator is not switched on |
604 | Disaggregation failed: SQL code: &1; &2&3&4 |