FIN_RE_PARSER - FIN Rule Engine Parser Messages
The following messages are stored in message class FIN_RE_PARSER: FIN Rule Engine Parser Messages.
It is part of development package FINS_GEN_RE_AST in software component FI-SL-VSR. This development package consists of objects that can be grouped under "Rule Engine Abstract Syntax Tree".
It is part of development package FINS_GEN_RE_AST in software component FI-SL-VSR. This development package consists of objects that can be grouped under "Rule Engine Abstract Syntax Tree".
Message Nr ▲ | Message Text |
|---|---|
| 001 | Source & is empty. |
| 002 | Syntax error: &. |
| 003 | Functionality & is not implemented. |
| 004 | Name of source (&1) and rule (&2) are not identical. |
| 005 | Parameter & is not unique. |
| 006 | Parameter & is not defined. |
| 007 | Type & is not defined. |
| 008 | Type & is not structured. |
| 009 | Element &1 in &2 is not defined. |
| 010 | Assign is only possible for elements of the target parameter &. |
| 011 | & is not a CDS View. |
| 012 | Element &1 in CDS View &2 cannot be mapped to structure &3. |
| 013 | Literaltype of & is not supported. |
| 014 | Path expression has to end with a field. |
| 015 | Association & has a cardinality of > 1. |
| 016 | Message & must be formated as [i|w|e]<msgno>(<msgid>). |
| 017 | Messages can have at most 4 arguments. |
| 018 | Type & is not supported. |
| 019 | Assignment is not supported in validations. |
| 020 | Context & is not defined. |
| 021 | Type &1 is not allowed in context &2. |
| 022 | Type &1 is not allowed as target structure in context &2. |
| 023 | Not allowed to write field &2 of &1 in context &3. |
| 024 | Not allowed to read field &2 of &1 in context &3. |
| 025 | Substitutions not allowed in context &. |
| 026 | Validations not allowed in context &. |
| 027 | ALPHA Conversion not possible on literal values longer then target field. |
| 028 | Filter condition for & does not limit the cardinality to 1. |
| 029 | Type & is not released. |
| 030 | Empty literals are not supported. |
| 031 | Value &1 is not allowed for field &2. |
| 032 | Function &1 is not defined |
| 033 | Too few parameters for function & |
| 034 | Function &1 expects only &2 parameters |
| 035 | Overwrite for field &2 of &1 not allowed in context &3. Use Initialize! |
| 036 | Wrong parameter name for type &1, expected &2 |
| 037 | Error in Conversion-Exit & |
| 038 | Error in Regular Expression: & |
| 039 | Regular Expression only possible on char-like types |
| 040 | Conditions of type &1 not allowed in &2 |
| 041 | Field &2 of &1 is internal usage only |
| 042 | Parameter &1 in function &2 not defined |
| 043 | Parameter &1 for function &2 not bound |
| 044 | Function &1 does not support named parameters |
| 045 | Function &1 requires named parameters |
| 046 | Restriction on field &1 is missing, &2 depends on this value |
| 047 | Non-Numeric value assigned to numeric field &1 |
| 048 | Only database columns supported on the left side of a comparison |
| 049 | Field &1 is too short, value is cut off. |
| 050 | Element &1 is deprecated, use &2 instead. |
| 051 | Element &1 is deprecated. |
| 052 | Function &1 does not implement the ABAP interface IF_FIN_RE_FUNCTION |
| 100 | Start parsing &. |
| 101 | Finished parsing &. |
| 102 | Start semantical analysis &. |
| 103 | Finished semantical analysis &. |
| 104 | Rule &1 is checked to SubVal version &2 |