Import | eptos Dictionary Documentation

Overview

Dictionary Manager includes several import types, implemented for various types of structure elements, which allow introducing external data into the database with the help of different file formats. These files are structured according to rules defined in the individual file format specifications corresponding to each import type.

Staging tables

This import allows users to import original SAP tables for Dictionary data into a Sandbox. In a second step - see Dictionary - the data from the Sandbox will be transformed into eptos Dictionary Manager Structure Elements.

Option	Description
Sandbox	Allows users to input the name of the Sandbox where the SAP tables will be imported.
Zipped .MDB	Allows users to upload the zipped .mdb file containing the data to be imported.
Email for load report	Allows users to input the e-mail address where the import report will be sent.

Dictionary

This import allows users to import Dictionary Manager structure elements from original SAP dictionary tables. The options available in the import graphical user interface are described in the table below.

Option	Description
Sandbox	Allows users to select the Sandbox from which the SAP dictionary data will be imported.
Mandant	Allows users to enter the client (e.g. 010) from which the SAP dictionary data will be imported. Note: if the Sandbox contains only one client, it will be automatically set by the system.
What to import	Allows users to define which entities will be imported. The available options are: Entities not yet imported: only entities not imported yet will be imported Entities with error – retry: only entities which returned an error in a previous import attempt will be imported.
KLAH type	Allows users to define which class types will be imported. All unique entries from column KLART in class table KLAH will be offered for selection here. Unmarked class types will be ignored on import.
First record	Allows users to define which record is the first one to be imported. If no record is to be fixed, the value in this fields is to be left to default value 0.
Max records	Allows users to define which record is the last one to be imported. The default value of this field is 100000. In case the file contains more records, this number can be increased - otherwise, the import needs to be done in several steps until all records are imported.
Target dictionary	Allows users to select the dictionary in which the SAP data will be imported (e.g. SAP Dictionary).
Fallback language	Allows users to define a fallback language. In case entries are missing in one of the available content languages, the data will be imported in the defined fallback language.
Root of classification classes	Allows users to select the root of Classification Classes from the dictionary in which the SAP data will be imported. Note: the root will be pre-filled by the system based on the selected dictionary. All first level classes from KLAH will be imported under this root. Sub-level Classification Classes will be imported under their parent Classification Class, according to the information contained in the KSSK table.
Root of application classes	Allows users to select the root of Application Classes from the dictionary in which the SAP data will be imported. Note: the root will be pre-filled by the system based on the selected dictionary. For all leaf Classification Classes, an Application Class will be created. The Property assignments from KSML will be added to these Application Classes.
Application class type	Allows users to define the type (Basic/Advanced) of the Application Classes to be created. Note: since Basic Application Classes are used only in the ECLASS data model, select Advanced for this option.
Import keywords	Allows users to define if Keywords will be imported or not. The option is marked by default, meaning that Keywords indicated in the SWOR table will be imported. Note: the first entry in SWOR will be taken as the name of the class in KLAH.
Multi-parent classification classes	Read-only option with informative character. Shows if for classification classes having multiple parents all relations will be imported. The option is unmarked by default and is marked automatically by the system if multi-parent classifications are detected in the selected sandbox.
Property code will be generated during import (can be changed in SysConfig)	This entry has only informative character. A system configuration controls if the new SAP Properties will receive a code generated by the code generator or if ATNAM is used instead. By default this setting is set to "generate property code".
Value import: use PR primary unit when not set in SAP	Allows users to define if the primary unit of the Property will be set to a connected Value in case no unit is indicated in the SAP table CAWN for respective Values.
Value import: identification of value to change	Allows users to define how Values to be changed are identified. The available options are: BY_ATINN_ATZHL_AND_ADZHL_EXTENDED_ATTRIBUTES: this options means that the value will be identified by the combination of ATINN, ATZHL and ADZHL BY_ATWRT_OR_ATFLV_IN_ATINN: this option means that the value will be identified by the combination ATINN and ATWRT or ATINN and ATFLV
Value import: identification of linked property	Allows users to define how the Properties connected with the Value will be identified. The available options are: BY_ATINN_AS_EXTENDED_ATTRIBUTE: Property will be identified by the value stored in the extended attribute ATINN BY_ATINN_AS_LONG_REMOTE_ID: Property will be identified by the value stored in attributed Long Remote ID. BY_STRUCTURE_ELEMENT_SANDBOX: Property will be identified by ATINN value of table CABN.
Value import: put new values under VA folder with specified code (if exists)	In case of hierarchical values, this option allows users to define a parent Value folder for Values which do not have a proper parent specified.
SPRAS	Allows users to map SAP language codes to eptos languages, if the detection is not done automatically by the system (e.g. D → German, E → English etc.).

After defining the import settings, the import can be stared. The order of the import steps are the following:

Import SAP units/quantities
Load classes
Load keywords for classes
Load class parents
Create application classes
Load properties
Load used properties
Import SAP values

Keyword/Synonym

This import allows users to import Keywords and Synonyms, as well as their connection to Properties or Classes. The file format specification for the import can be found Excel Import-Export of Keywords and Synonyms (Version 2.0).

Option	Description
Release	Allows users to select in which release to import the Structure Elements contained in the import file.
Supplier	Allows users to select the data supplier (coder) for the new Structure Elements contained in the import file. Note: should be the supplier of the selected release
Allow update	When this option is checked,elements referenced by IRDI in the import file will be updated if existing, else it will be created with specified IRDI.
E-mail	Allows users to input the e-mail address where the import notification will be sent.
Import file	Allows users to upload the import file.

Import class types

This import allows users to import class types. The file format specification for the import can be found Excel Import of Class Types (Version 1.0).

Option	Description
Supplier	Allows users to select the data supplier (coder) for the class types contained in the import file.
E-mail	Allows users to input the e-mail address where the import notification will be sent.
Import file	Allows users to upload the import file.

Excel Import change requests

OntoML (EPTOS XML)

This import allows users to import Dictionary Manager structure elements using an eptos xml import file.

Option	Description
Import entities into release	Allows users to select in which release to import the Structure Elements contained in the import file.
Property class type supplier	Allows users to select the supplier for the property class types.
Update mode (only update texts)	Allows users to define if the import will create new elements or only import translations for existing elements in the content language contained in the import file. The option is unmarked by default (i.e. the import will create new elements). If only translations will be imported, the options needs to be marked by the user.
Import in single transaction (for rollback)	Allows users to define if the import will be done in one transaction allowing complete rollback in case of encountered errors or in separate transactions (note: in this case, inconsistent data could potentially remain in the dictionary in case errors are encountered during the import). The option is marked by default (import will be done in one transaction).
Ignore GUIDs	Obsolete. Option will be removed, cloning content is done via Adapt.
Use the equivalent unit in selected release for unit references.	Obsolete. Option will be removed, cloning content is done via Adapt.
Aposteriori mappings release to connect with	Obsolete. Option will be removed, cloning content is done via Adapt.
Filter Selector - Import all (no filter) / Activate filter	Allows users to define if the entire content of the import file will be imported or if only specific elements (e.g. Properties) will be considered on import. In case only specific elements are to be imported, these elements need to be selected via the Activate filter option.
E-mail	Allows users to input the e-mail address where the import notification will be sent.
Check only	Allows users to simulate the import without persisting the changes.

DIN4002 Dictionary

This import allows users to import Dictionary Manager structure elements using an Excel import file. The file format specifications for the import can be found Excel Import of Dictionary Elements (Version 2.1).

Option	Description
E-mail	Allows users to input the e-mail address where the import notification will be sent.
Release	Allows users to select in which release to import the Structure Elements contained in the import file.
Configure	simulate: Allows users to simulate the import without persisting the changes. Stop and rollback on errors: With this option checked, the import will stop when encountering errors and the changes will be rolled back. Inherit properties from superclass: With this option checked, Property assignments created for a superclass will be inherited to its subclasses.
Row from where values start	Allows users to define the row in the import file where the values to be imported start.
Import file	Excel import file
Import ClassesSheet	Allows users to select the appropriate sheet in the import file to import/edit Classes.
Import Value ListsSheet	Allows users to select the appropriate sheet in the import file to import/edit Value lists.
Import ValuesSheet	Allows users to select the appropriate sheet in the import file to import/edit Values.
Import PropertiesSheet	Allows users to select the appropriate sheet in the import file to import/edit Properties.
Import UnitsSheet	Allows users to select the appropriate sheet in the import file to import/edit Units.
Relations Class ClassSheet	Allows users to select the appropriate sheet in the import file to import/edit relations between Classes.
Relations Class PropertySheet	Allows users to select the appropriate sheet in the import file to import/edit relations between Classes and Properties.
Relations Property PropertySheet	Allows users to select the appropriate sheet in the import file to import/edit relations between Properties.
Relations Property ValueSheet	Allows users to select the appropriate sheet in the import file to import/edit relations between Properties and Values.
Relations Value List ValuesSheet	Allows users to select the appropriate sheet in the import file to import/edit relations between Value lists and Values.