Introduction

This article contains information regarding work with the Import data application in reference to the import of classifications and related level descriptions. The procedures describe the order of performing steps that should be observed when executing the import, as well as the information regarding possible requirements and results.

Classification structure presents principal and subordinate relations between objects. It specifies the order of objects in the system and can be composed of several levels. The classifications are composed of nodes which are interdependent. The parent node is always called folder. The node below the last folder is called leaf.

Detailed information regarding data import, including descriptions of fields and buttons, can be found in Data import article.

Classifications

A series of classifications is available in the system. One business object corresponds to each classification and reflects it, that’s why each classification must be imported separately. The classifications are composed of attributes.

With few exceptions, classifications have references to organizations and most of them handles the mechanism of replication for shared data. It means that for organization X, it is possible to specify that a given special classification will be handled by the parent organization Y. Technical codes for these classifications are composed of the following attributes: path + organizationalUnit or
parent + code + organizationalUnit. If a node is created for organization Y, it is automatically replicated for organization X. As in the case of the most of base data (except for items and partners), also the import process for each organization must be executed separately, so that it is possible to verify errors with the use of the application.

For the classifications subject to replication and whose data is shared by many organizations, the import process should be executed only in the organization handling data. For all inheriting organizations, nodes are created automatically.

Further attributes can be added to each classification. Classification data import file must also contain required extension attributes.

It is all possible to add own, customized classifications. They can be created, for example, by adding additional fields in Items application or parameters for production structures. The article contains also the description of the process of importing non-standard classifications.

Descriptions of levels can be assigned to each organization. They are imported in a separate file, independent from nodes and leaves.

Procedure

Below, the types of classifications import are presented:

• Import of classifications without extensions
• Extensions import
• Non-standard classifications import

select distinct h:guid, h:path from com.cisag.app.purchasing.obj.RequestForProposalHierarchy5 h
join com.cisag.app.multiorg.obj.Organization o on h:organizationalUnit=o:guid
where o:code=’00000′ order by h:path

Data import procedure

1. Open Import data application
2. Select filter or one of filters for the business object corresponding to a given classification. The list of business objects can be found in chapter Business objects of system classifications.
   Filter for importing data will be displayed in the application window.
3. Attributes selected for the filter are active. If needed, at this stage, it is possible to edit the attributes.
4. Click on [Import data] button on the standard toolbar.
   Import data window is opened.
5. In the opened dialog window, it is possible to configure the settings for file import. Detailed information regarding data import, including descriptions of fields and buttons, can be found in article Data import, in Data import chapter.
6. Click on [In batch] button in the displayed dialog window, in order to start the import.

Attributes required in import process

For each business unit it is necessary to indicate at least:

• Identification attribute (Secondary Key)
• Mandatory fields

Without identification attributes it is impossible to assign a business unit and in case there is no mandatory field, it is not possible to continue the process without edition correction. The list of mandatory fields and identification attributes of particular business objects can be found in chapter Import of system classifications without extensions.

There are also relations with other business objects which do not belong directly to the business unit of a given classification (relations through external keys, marked in italics in the filter). To activate such relations, it is necessary to select identification attributes of that business object in the filter. The data associated with external keys cannot be imported together. They must be already available in the system. If through the relation of an external key, attributes different that their identification attributes are indicated, they will be omitted.

If the base key of a business object is partially or fully composed of external keys, then in the import file, the business object associated with that external key must be activated through its identification attributes.

Order

It is important that in the import file, before selected node, there is parent node A or that it is already existing in the database.

Import of system classifications without extensions

In the import file, all identification and mandatory attributes of a given classification must be specified.

Tabulated summary

Identification fields and mandatory fields

Import of system classification extensions

This chapter contains instructions regarding import of extensions and description of what it is necessary to pay attention to when releasing extensions in Comarch ERP Enterprise.

Item price classification

The following elements belong the item price classification

• purchasing item price classification
• sales item price classification

In this extensions, one attribute is added to the data of business objects.  This attribute or external key association can be indicated in the same import file.

Tabulated summary

Item price classification extension

Inventory item classification 1

In this extension, two attributes are added to the business object. These attributes or external key associations can be indicated in the same import file.

Tabulated summary

Inventory item classification extension 1

Customer statistics classifications

The following elements belong to the customer statistics classifications:

• Purchasing item statistics classification
• Sales item statistics classification
• Supplier statistics classification
• Customer statistics classification
• Rotation statistics classification

In this extensions, one attribute is added to the data of business objects.  This attribute or external key association can be indicated in the same import file.

Tabulated summary

Statistics classification extension

Item account classification

In this extension, Account origin attribute is added to the business object. New attribute can be indicated in the same indicated in the same import file.

Tabulated summary

Item account classification extension

Non-standard classifications import

Non-standard classifications can be created, e.g., with the use of application Field types or Product configuration rules or through other fields. Classification metadata (e.g., classification name) is saved in business object com.cisag.app.general.extension.obj.Datatype and must be imported before importing non-standard classifications. Proper user data (classification nodes) are saved in business object com.cisag.app.general.extension.obj.EntityExtensionHierarchy.

Order

When importing data, the following order must be observed:

• Import of all required field types
• Business object: cisag.app.general.extension.obj.Datatype

• Non-standard classifications import
• Business object: cisag.app.general.extension.obj.EntityExtensionHierarchy

[Indicator]

It is possible to import all non-standard classification with the use of one file. Metadata must be already existing. Further modification in Classifications application is possible only for non-standard classification. For this reason, it is recommended to import each non-standard classification in a separate file. [/indicator]

Tabulated summary

Identification fields and mandatory fields

Business object
com.cisag.app.general.extension.obj.EntityExtensionHierarchy

Level descriptions import

The import of level descriptions is performed individually with the use of business object com.cisag.app.general.obj.ClassificationLevel. In the import file, all identification and mandatory attributes of the business object must be specified.

Order

Level attribute is set automatically on the basis of the order of specifying level descriptions in the import file.

To optimize the import process, it is necessary to import particular level descriptions, grouped by classification.

Tabulated summary: Identification fields and mandatory fields

Business objects of system classifications