Skip to main content
insightsoftware Documentation insightsoftware Documentation
{%article.title%}
Published:
Was this article helpful?
0 out of 0 found this helpful

Transformation Groups

Table of Contents

1 General Information on the Application of Transformation Groups

If the 'IMPORT' or 'CONDAT' applications are used to import data from an external system and if other keys are used in IDL.KONSIS than in the external system, this application can be used to determine how the external keys (external object ID) are to be implemented.

The following objects can currently be implemented within the 'IMPORT' application:

  • Data types
  • Companies
  • Business unit
  • Report incidents
  • Charts of accounts
  • Menu incidents
  • Charts of positions
  • Posting key
  • Various (debit/credit indicator, time reference)

All these objects can be combined into different groups, so that transformation can take place separately for each group. Individual objects are displayed on spreadsheets after opening a transformation group. The numbers behind the tab headings show how many object IDs are coded for transformation.

2 Setting Up a Transformation Group

When the application is invoked, a table with all previously defined transformation groups is displayed. If no data is defined yet, the table is empty.

Definition of the transformation group
When creating a new object, select the 'Star' (Create transfer group) in the right-hand menu bar. The wizard opens in which the individual attributes are to be filled out. The wizard can only be left when the mandatory information transfer group is filled in, valid from as description. If the conversion group is defined, one or more objects can now be assigned to this new group.
New setup of objects for conversion groups
Double clicking on the first column of the selected transformation group opens the dependent table with currently 10 tabs. In the individual table tabs, the 'internal object-Idents' present in IDL.KONSIS are displayed for each object (see table above), to which the 'external object ID's' can now be assigned. Double clicking on an 'internal ID' opens the wizard and the 'external ID' can be entered.
Adding objects to conversion groups
If further external object IDs are to be added to a transformation area (e.g. GES or FAC etc.), the desired 'internal object' from the list must be selected, which does not have an 'external ID assignment'. Often an existing object is tried as a 'template' and the wizard overwrites the data. However, it is not possible to change the key fields. The 'template' would be overwritten and would no longer exist. If you wish to make a change, you must first delete and create a new object ID.
Changing Objects
Data can be changed either with the 'Pen' from the toolbar (right mouse click) or with 'Table Cells Editable' (right mouse click). The fields that can be changed by 'editing in the table' appear in blue and can be changed by direct entry in the table.
Drag&Drop from the bottom of the table to the leading table (copy translations)
If assignments have already been defined for other transformation groups and these should also be applied in the new transformation group, the transformation group assignment can be copied into the new transformation group (in the leading table) by drag&drop from the dependent table (attributable objects).

3 Special Feature for the Objects Company and Business Unit

  • There are pre-systems in which the structures of the company are managed differently than in IDL.KONSIS. For example, branches in external systems are managed as companies or separate accounting circles, but in the legal group structure they must be managed as business units of a single company. In order to be able to business unit the 'branches' / booking circles from the external system in IDL.KONSIS, the external company IDs must be assigned to an internal business unit, which in turn is only assigned to one company. This can be achieved by entering '2. Transformation for Object ID' in the field. In the first transformation, the 'branch' is assigned to a company, and in the second transformation, a business unit.
  • Additionally, you can enter additional restrictions in the company/IC company area. This is useful, for example, if you only want to implement the company key and not the IC company key when taking over IC balances. If the external object ID to be implemented is identical for the company and for the IC company, a data record must be created and the field 'transformation object constraint' remains empty.

4 Use of Transformation Groups in the Application of CONDATE

The group sub-group Data Exchange (CONDAT) application allows data to be exchanged within groups. If data is to be exchanged within groups whose source data type differs from the target data type, the data types must be 'implemented'. For this purpose, it is necessary to define a transformation group for data types. It should be noted that in this case the 'internal object' is the object to which the data should be transferred and the 'external object' is the object from which the data comes.

In the group and sub-group Data Exchange (CONDAT) application, only the 'Data types' and 'Companies' objects can be 'implemented'.
Published:

Transformation Groups

Table of Contents

1 General Information on the Application of Transformation Groups

If the 'IMPORT' or 'CONDAT' applications are used to import data from an external system and if other keys are used in IDL.KONSIS than in the external system, this application can be used to determine how the external keys (external object ID) are to be implemented.

The following objects can currently be implemented within the 'IMPORT' application:

  • Data types
  • Companies
  • Business unit
  • Report incidents
  • Charts of accounts
  • Menu incidents
  • Charts of positions
  • Posting key
  • Various (debit/credit indicator, time reference)

All these objects can be combined into different groups, so that transformation can take place separately for each group. Individual objects are displayed on spreadsheets after opening a transformation group. The numbers behind the tab headings show how many object IDs are coded for transformation.

2 Setting Up a Transformation Group

When the application is invoked, a table with all previously defined transformation groups is displayed. If no data is defined yet, the table is empty.

Definition of the transformation group
When creating a new object, select the 'Star' (Create transfer group) in the right-hand menu bar. The wizard opens in which the individual attributes are to be filled out. The wizard can only be left when the mandatory information transfer group is filled in, valid from as description. If the conversion group is defined, one or more objects can now be assigned to this new group.
New setup of objects for conversion groups
Double clicking on the first column of the selected transformation group opens the dependent table with currently 10 tabs. In the individual table tabs, the 'internal object-Idents' present in IDL.KONSIS are displayed for each object (see table above), to which the 'external object ID's' can now be assigned. Double clicking on an 'internal ID' opens the wizard and the 'external ID' can be entered.
Adding objects to conversion groups
If further external object IDs are to be added to a transformation area (e.g. GES or FAC etc.), the desired 'internal object' from the list must be selected, which does not have an 'external ID assignment'. Often an existing object is tried as a 'template' and the wizard overwrites the data. However, it is not possible to change the key fields. The 'template' would be overwritten and would no longer exist. If you wish to make a change, you must first delete and create a new object ID.
Changing Objects
Data can be changed either with the 'Pen' from the toolbar (right mouse click) or with 'Table Cells Editable' (right mouse click). The fields that can be changed by 'editing in the table' appear in blue and can be changed by direct entry in the table.
Drag&Drop from the bottom of the table to the leading table (copy translations)
If assignments have already been defined for other transformation groups and these should also be applied in the new transformation group, the transformation group assignment can be copied into the new transformation group (in the leading table) by drag&drop from the dependent table (attributable objects).

3 Special Feature for the Objects Company and Business Unit

  • There are pre-systems in which the structures of the company are managed differently than in IDL.KONSIS. For example, branches in external systems are managed as companies or separate accounting circles, but in the legal group structure they must be managed as business units of a single company. In order to be able to business unit the 'branches' / booking circles from the external system in IDL.KONSIS, the external company IDs must be assigned to an internal business unit, which in turn is only assigned to one company. This can be achieved by entering '2. Transformation for Object ID' in the field. In the first transformation, the 'branch' is assigned to a company, and in the second transformation, a business unit.
  • Additionally, you can enter additional restrictions in the company/IC company area. This is useful, for example, if you only want to implement the company key and not the IC company key when taking over IC balances. If the external object ID to be implemented is identical for the company and for the IC company, a data record must be created and the field 'transformation object constraint' remains empty.

4 Use of Transformation Groups in the Application of CONDATE

The group sub-group Data Exchange (CONDAT) application allows data to be exchanged within groups. If data is to be exchanged within groups whose source data type differs from the target data type, the data types must be 'implemented'. For this purpose, it is necessary to define a transformation group for data types. It should be noted that in this case the 'internal object' is the object to which the data should be transferred and the 'external object' is the object from which the data comes.

In the group and sub-group Data Exchange (CONDAT) application, only the 'Data types' and 'Companies' objects can be 'implemented'.
For an optimal Community experience, Please view on Desktop
Powered by Zendesk