With this load, business rules can be written into a Jedox In-Memory (OLAP) database.
The data source must contain the following 4 columns:
|Target connection||Connection to a Jedox In-Memory (OLAP) database|
|Target cube||Cube in the Jedox In-Memory (OLAP) database|
The following modes are available:
This structure is analogous to the organization of the rule extract. Rules that are read with the help of extracts from a Jedox database or manually created can therefore be written directly by referencing the data source. It is also possible to build a data source that adheres to this structure for rules with the desired extracts and transforms. As rules are matched based on the definition of the rule, it is important for modes “insert” and “delete” to use exactly the same rule syntax as in the OLAP database.
Note: load mode “update” cannot be used when the source rule extract has been filtered for generated rule instances. This is because update mode deletes all existing rules in the target cube. Rule instances cannot run without rules or rule templates, and so the load cannot run and you will receive a warning message “Instance rule cannot be loaded in mode update”. The same behavior is achieved with the load mode “delete” when the source rule extract has been filtered by generated rule instances. The load cannot run and you will receive a warning message “Instance rules can not be deleted.”