Framework:Imports
Data definition
Here, the data source is a CoPlanner data definition. Primarily, this type of imports is used to transfer actual data to plan (data wizard).
You can also define filters in the filter area. This filters also can be used in SQL Queries. You can use them like <Filtername.Ausdruck> where "Filtername" has to be replaced by the name of the filter you want to use. If you want to set a Filter Lookup Special to a session variable, you have to use Transform=. E.g. Transform=Session_Entity_ID@
| Hinweis A timeout occurs if the query of the SQL statement takes more than 10 minutes. This timeout can be set with the parameter DBCommandTimeout in the svrconfig.xml . |
Table assignment
The following steps are identical for all three data sources.
The table on the left contains the source objects, the table on the right contains the target objects. Highlight a source object, then a target object, and press the “New” button. A connection between the two objects is established. Double-clicking on the assignment respectively navigating in the tree will get you to the detail view of the assignment.
When the table assignment is performed, you can also view data of the source or of the target. In the source/target table, click with the right mouse button on the desired object.
In the context menu, click preview. A dialog containing the data shows up.
Field assignment
The object assignments have been made. Now you need to define which field of the source is to be written to which field of the target.
Just like with the table assignment, there are again two tables. On the left, there are the columns of the source object, on the right those of the target object. Select a source column and a target column and press the “New” button. Double-clicking on the assignment respectively navigating in the tree will take you to the detail view.
| Hint Use “Automatic” to automatically match all fields whose source and target names are identical. |
| Hint For dimension elements, it is necessary to state in Field assignment - detail via which target field the assignment is made in the dimension. This field describes the column that is comparable with the source table. When importing from previous systems, this is usually the vs_key field, when transferring between CoPlanner tables it is usually the COPSYS_ID column. If the KST (cost center) column of the source table contains the value 4711 and if this same key is found in the vs_key field of the PC/KST (cost center) dimension, then the “vs_key” field will be selected here. |
Starting Import
If all settings are saved (no button red any more), press the “Start import” button or select “Open” from the context menu in the object administration. In the tree you can watch in Import progress whether the import was successful respectively which partial steps were executed.
Details about Data definition import
As mentioned before, importing serves the purpose of transferring actual data to CoPlanner in plan tables, or the purpose of transferring data from plan A to plan B. For this, it is often required to create a data matrix with more than two axes as the source. To speed up the creation of the matrix, an optimization routine was implemented on the server. It is activated if:
- at least one axis has “none” as alignment
- no subset is used as an axis
Furthermore, if there is an import to a lookup column, an assignment via a key column is needed (for instance to be able to infer the CoPlanner dimension element via a pre-system key). If the key column is the COPSYS_ID column (default for data definition import and recommended), the dimension information is not loaded on the server side and the match IDs are taken as they are (1:1). This also makes it faster.
