FDT_HRF - FDT: HRF
The following messages are stored in message class FDT_HRF: FDT: HRF.
It is part of development package SFDT_HRF in software component BC-SRV-BR. This development package consists of objects that can be grouped under "BRFplus: HANA RUle Framework (HRF)".
It is part of development package SFDT_HRF in software component BC-SRV-BR. This development package consists of objects that can be grouped under "BRFplus: HANA RUle Framework (HRF)".
Message Nr ▲ | Message Text |
---|---|
030 | HRF does not support n:m associations |
031 | &1 is not a DB Vocabulary |
032 | ID &1 is not a function |
033 | ID &1 is not a rule |
034 | ID &1 is not an application |
035 | Object type &1 is not valid; use either function, rule, or application |
036 | Failed to compile function. |
037 | Ruleset is not valid. |
038 | Column &1 is not valid. |
039 | Cell in row &1 and column &2 is not valid. |
040 | Expression is not valid. |
041 | &1: Cell in row &2 and column &3 is not valid. |
042 | &1: Column &2 is not valid. |
043 | Result data object is not valid. |
044 | Object name &1 must be unique in the expression language allowed objects |
045 | Result columns &1 were added to the decision table |
046 | Result columns &1 were deleted from the decision table |
047 | No changes are required in the decision table columns |
048 | No Result Data Object assigned to the decision table |
049 | Result Data Object type is not supported for this action |
050 | URL &1 does not start with base pattern &2 |
051 | Creation of folder &1 was not successful (status code &2, reason &3) |
052 | Info retrieval for &1 was not successful (status code &2, reason &3) |
053 | URL is empty |
054 | Package name &1 does not end with a UUID |
055 | Deletion of folder &1 was not successful (status code &2, reason &3) |
056 | Activation of resource &1 failed (status code &2, reason &3) |
057 | Activation of package with path &1 failed (status code &2, reason &3) |
058 | Deletion of file &1 was not successful (status code &2, reason &3) |
059 | RFC creation failed with sy-subrc &1 |
060 | BRFplus standard XS RFC destination already exists with wrong type |
061 | Error occurred while updating RFC destination &1 |
062 | Error occurred while creating RFC destination &1 |
063 | Creation of resource &1 was not successful (status code &2, reason &3) |
064 | Check of resource &1 failed (status code &2, reason &3) |
065 | Check of package with path &1 failed (status code &2, reason &3) |
066 | Error in server communication &1. RFC destination &2 |
067 | Version was not found |
068 | Invalid rule ID &1 |
069 | HRF server communication using RFC destination &1 is valid |
077 | Object was already changed by another user |
080 | Error accessing CDS object &1 |
081 | Output name missing; provide an output name |
082 | Empty output field list is not allowed |
085 | Empty field name in output &1 is not allowed |
086 | Field name &2 in output &1 is not unique |
087 | Output name &1 is not unique |
088 | Field name &2 in output &1 not allowed when ID is supplied |
089 | Field name &2 in output &1; no JSON supplied |
090 | Output name &1; no JSON and no ID supplied |
091 | Output name &1; &2 is not a data object |
092 | Output name &1; &2 is neither a structure nor an element |
093 | Output name &1; only elements allowed in &2 |
094 | Output name &1; type amount is not allowed for &2 |
095 | Output name &1; type quantity is not allowed for &2 |
096 | Output name &1; only time, date, or timestamp are allowed for &2 |
097 | Output name &1; unnamed &2 is not allowed |
098 | Output name &1; type boolean is not allowed for &2, use type number |
099 | No entity path for CDS document &1 provided |
100 | No CDS document defined |
101 | CDS documents have been defined |
102 | CDS documents have been changed |
104 | Aliases have been defined |
105 | Aliases have been changed |
106 | Outputs have been defined |
107 | Outputs have been changed |
111 | Output &1: length exceeds maximum length of 256 characters |
112 | No vocabulary assigned |
113 | No data source defined |
114 | Structured parameter (&1) is not allowed in a rule service |
115 | Unnamed DB parameters are not allowed |
116 | DB Parameter name &1 is used multiple times |
117 | &1 is not a data object |
118 | Only elements allowed in &1 |
119 | Type amount is not allowed for &1 |
120 | Type quantity is not allowed for &1 |
121 | Only time, date, or timestamp are allowed for &1 |
122 | Output name &1 does not exist in DB vocabulary &2 |
123 | Only 8 letters are allowed for parameters of type table (&1) |
124 | CDS document &1 contains key fields from multiple tables |
125 | CDS document &1 does not contain any key fields |
126 | CDS document &1 contains calculated keys |
128 | In database mode, set result with method SET_DB_OUTPUT |
129 | In database mode, set context with method SET_DB_PARAMETERS |
130 | Set application before assigning DB Output |
131 | Set DB Vocabulary before assigning DB Output |
132 | Result &1 is deleted, marked for deletion, or obsolete |
133 | Result &1 does not match DB output &2 |
134 | Mismatch of DB output &1 with DB vocabulary &2 |
135 | Cannot create/update result because of locked object &1 |
136 | The object is locked by another user |
138 | Unregistered service URL (&1) received from HRF |
139 | Unspecified HTML error |
140 | |
141 | Not supported association is removed: &1 |
142 | Only analytical functions are supported |
151 | Latest measurement - process &1 between &2 and &3 rows: duration ratio &4 |
152 | Process &1 with &2 rows on &3: duration &4 is much longer than average &5 |
153 | Input parameter &1; type amount is not allowed |
154 | Input parameter &1; type quantity is not allowed |
155 | Input parameter &1; data element assignment is missing |
156 | Input parameter &1; time point &2 is not allowed |
157 | Assigned element &1 and view parameter &2 are of different types |
198 | &1 Functions with &2 DB Vocabularies, same DB Vocabulary required |
199 | No function assigned |
200 | Empty DB rule |
201 | New DB rule has been created |
202 | DB rule body changed |
203 | Function assignment changed |
204 | No function assigned |
205 | Assigned function requires database mode to be used in DB rules |
206 | Function &1 requires database mode to be used in DB rules |
207 | Maintain expression content for filter or delete it in workbench |
208 | Maintain content for alias &1 or delete it in workbench |
209 | Maintain content for static expression &1 or delete it |
210 | Assigned functions need to have the same output |
211 | No Result Data Object assigned to the function |
212 | Data Object &1 is not database bound |
213 | Association &1 differs from cds |
214 | Target type &1 of association &2 not supported. |
215 | Association &2 not created; cardinality &1 not supported in data objects |
216 | Association &2 not created; operator &1 not supported in data objects |
217 | Association &2 not created; operator &1 not supported in data objects |
218 | Field &1 of association &2 not found in source data object &3 |
219 | Field &1 of association &2 not found in target data object &3 |
220 | Name of data object &1 is not unique in db context |
221 | Duplicate association name &1 found on db context |
222 | Column &1 doesn't contain a valid value |
223 | Association &1 skipped; filter conditions not supported in data objects |
224 | Rule &1 is being edited by user &2 |
225 | Rule &1 has been changed while your editing |
226 | There are no changes in rule &1 |
227 | Rule &1 was not opened for editing |
228 | Project ID is empty |
229 | Result Data Object &1 does not exist in vocabulary |
230 | Column ID is empty |
231 | Row ID is empty |
232 | Column ID &1 already exists |
233 | Row ID &1 already exists |
234 | Column ID &1 does not exist |
235 | Row ID &1 does not exist |
236 | Wrong column sequence provided |
237 | Wrong row sequence provided |
238 | Rule &1 is consistent |
239 | Column Type is empty |
240 | Object &1 was not opened for editing |
241 | Wrong source row ID provided |
242 | To create cells, the row ID mapping reference must be provided |