Topic overview

The Classifications application allows creating a multi-level classification tree structure with primary and subordinate nodes that make it possible to classify data and business entities in Comarch ERP Enterprise. Based on the defined structure, data subject to user analysis is ordered. With the use of classifications, data can be grouped and summed at multiple structure levels.

Business entities from all system areas are subject to classification.

Classifications represent primary and subordinate relations between objects and determine hierarchy in the system. They can be composed of one or more levels and of interdependent nodes. A primary node is defined as folder, while the node placed below the last folder is called leaf.

Procedures for handling classifications, e.g. the methods of creating and editing them, can be found in the article Procedures: Classifications.

The Classifications application is composed of a header, containing the standard toolbar, and a work pane with a line item editor. The application header is the same for each view. However, the work pane changes depending on the selected view.

The Classifications application can be used in one of the two views:

• Nodes and leaves
• Level descriptions

Header

The following field is available in the application header:

• Classification – it allows selecting a classification whose structure should be displayed in the work pane. The list of classifications is available under the [Value assistant] button.

Customized classifications can be defined in different applications, e.g. Items, by creating a field of the Classification type on the Other fields tab.

Work pane

The fields displayed in the work pane depend on the selected view.

Nodes and leaves view

The work pane of the Nodes and leaves view is composed of the toolbar, classification structure view, and line item editor.

The number of levels is limited by the maximum classification path length of 125 line items. This way, it is possible to enter up to 20 levels (a description can be composed of up to 5 characters: digits, letters, and some special characters, e.g. dots).

Toolbar

The toolbar contains buttons allowing the management of the classification structure:

• [New nodes at the same level] – it creates a new node (folder) equivalent to the row which is currently selected on the classification tree. The button is only available if a node is selected on the classification tree.
• [Duplicate in nodes at the same level] – it copies a selected node at the same level. The original node’s description is copied to the new one. The button is only available if a node is selected on the classification tree.
• [New subordinate nodes] – it creates a new node subordinate to the node which is currently selected on the classification tree. If no node is selected, the new node will be created at the highest level.
• [Duplicate in subordinate nodes] – it copies a selected node subordinately

• [Delete] – it deletes a selected node. Administrator authorizations are required to perform this action.

• [Mark for deletion] – it marks a selected node for deletion. The button is available for nodes that have not been marked for deletion yet. Nodes marked for deletion are deleted after the Reorganize classifications application is run.

• [Unmark for deletion] – it removes deletion markers for nodes marked for deletion
• [Edit] – it allows editing a node (its name, description, and hierarchy level)
• [Search] – it allows searching for and highlighting a node on the classification tree whose description has been entered in the Description field

View selection in the Classifications application

For classifications created with the use of the editor, it is possible to move nodes and leaves to lower levels. This way, empty nodes are created within the structure.

The Classifications application allows selecting a required view in order to facilitate the analysis:

• Without empty nodes – the view contains the full classification structure with all created nodes
• With empty nodes – the view presents a structure according to the value specified in the Level field

Classification structure view

The structure of a given classification is presented under the toolbar. It is a node structure displayed as folders and leaves along with their identifications and descriptions.

The folder icon indicates that there are further subordinate nodes. At the lowest level, there can be only leaves (sheet icon).

Depending on the object and application, it is possible to select either only a leaf, or both a leaf and classification node.

Line item editor

Trees for particular classifications are created and edited in the line item editor. The editor’s layout depends on the selected classification. The table below contains the list of classifications and editors corresponding to them. For classifications originating from other fields of applications, the editor of the first type is used.

Line item editor 1

The toolbar of the line item editor contains the following buttons/fields:

• [Show/hide] – it shows/hides the line item editor
• [Accept] – it accepts changes made in the line item editor and moves the edited item to the classification structure
• [Validate] – it verifies the correctness of the entered data
• Parent – it presents a parent node, if available

Editable fields available in the line item editor include:

• Node – the identification of a classification node. The identification must be unique within the folder; it can be changed at any time. The identification can be composed of up to 5 characters: digits, letters, some special characters (e.g. dots), and their combinations. Node identifications are used to recognize and apply correct nodes in other applications and queries.
• Description – it is an additional description of a classification node. Meaningful descriptions facilitate searching for nodes in other applications.

Line item editor 2

The toolbar of the line item editor contains the following buttons/fields:

• [Show/hide] – it shows/hides the line item editor
• [Accept] – it accepts changes made in the line item editor and moves the edited item to the classification structure
• [Validate] – it verifies the correctness of the entered data
• Parent – it presents a parent node, if available

Editable fields available in the line item editor include:

• Node – the identification of a classification node. The identification must be unique within the folder; it can be changed at any time. The identification can be composed of up to 5 characters: digits, letters, some special characters (e.g. dots), and their combinations. Node identifications are used to recognize and apply correct nodes in other applications and queries.
• Description – it is an additional description of a classification node. Meaningful descriptions facilitate searching for nodes in other applications.
• Unit – it is the unit in which threshold quantities can be defined for purchase prices or sales prices when applying discounts covering all items

Line item editor 3

Settings of the Inventory item classification 1 classification can be used as the default settings of an inventory item in Items → Inventory Management view → Classification 1 field. If the field Setting storage strategies is set as According to classification, an item will inherit the settings of a classification selected in the Classification 1 field.

The toolbar of the line item editor contains the following buttons/fields:

• [Show/hide] – it shows/hides the line item editor
• [Accept] – it accepts changes made in the line item editor and moves the edited item to the classification structure
• [Validate] – it verifies the correctness of the entered data
• Parent – it presents a parent node, if available

Editable fields available in the line item editor include:

• Node – the identification of a classification node. The identification must be unique within the folder; it can be changed at any time. The identification can be composed of up to 5 characters: digits, letters, some special characters (e.g. dots), and their combinations. Node identifications are used to recognize and apply correct nodes in other applications and queries.
• Description – it is an additional description of a classification node. Meaningful descriptions facilitate searching for nodes in other applications.
• Selectable – using this parameter, it can be determined whether the node can be assigned to the user of this classification
• Levels – it is used to set up a node level. The node can be moved to a lower hierarchy level. Using this function, it is possible to flatten the classification structure at lower levels without creating new nodes, e.g. by moving leaves to the lowest level. Values available in this field are retrieved from the Level descriptions view. The field is only active if the Level descriptions view contains some entries. New view entries will be available once they are saved.

General section:

• Picking – in this field, select the picking method for order line items related to the items assigned to a given classification in a warehouse with storage locations. The setting determines whether picking line items will be considered when generating inventory orders. Available options include:
  • Any
  • Only order based – picking line items for items of this classification will only be considered when generating an inventory order if the inventory order is created for one picking only
  • Only for all orders – picking line items for items of this classification will only be considered when generating an inventory order if the inventory order is created for multiple pickings

This classification setting will only be active if the option According to classification has been selected in the master data of a given item in the Picking field.

Storage strategies section:

This section allows defining default settings for units with a selected classification node. Fields available in this section are described in detail in the Storage strategies article.

Storage restriction section:

• Setting storage restrictions – it defines storage restrictions to be used for the classification node. Available options include:
  • According to warehouse – restriction settings defined on the Storage location control tab of the Warehouses application will be used for items to which the classification node is assigned
  • Manual – it allows fields in the Storage restriction section to be filled in manually for the classification node

• Storage restriction – it allows entering the identification of an existing storage restriction or selecting a value from the list under the [Value assistant] button. Storage restrictions can be created in the Storage restrictions application. An entry given in this field sets relevant values of the appropriate storage restrictions in the other fields of this section once the [Accept] button is selected.
• Put-away restriction – using the field’s [Value assistant] button, it is possible to enter a put-away restriction created in the Put-away restrictions application. The value is filled in automatically if the Storage restriction field is completed.
• Withdrawal restriction – using the field’s [Value assistant] button, it is possible to enter a withdrawal restriction created in the Withdrawal restrictions application. The value is filled in automatically if the Storage restriction field is completed.
• Zone type – using the field’s [Value assistant] button, it is possible to enter a warehouse zone type created in the Warehouse zone types application. The value is filled in automatically if the Storage restriction field is completed.

Line item editor 4

The toolbar of the line item editor contains the following buttons/fields:

• [Show/hide] – it shows/hides the line item editor
• [Accept] – it accepts changes made in the line item editor and moves the edited item to the classification structure
• [Validate] – it verifies the correctness of the entered data
• Parent – it presents a parent node, if available

Editable fields available in the line item editor include:

• Node – the identification of a classification node. The identification must be unique within the folder; it can be changed at any time. The identification can be composed of up to 5 characters: digits, letters, some special characters (e.g. dots), and their combinations. Node identifications are used to recognize and apply correct nodes in other applications and queries.
• Description – it is an additional description of a classification node. Meaningful descriptions facilitate searching for nodes in other applications.

General section:

• Inclusion/exclusion – by selecting an appropriate option in this field, it is possible to decide whether facts are to be included in OLTP statistics. Available options include:
  • Inclusion – facts will be included in statistics
  • Exclusion – facts will not be included in statistics
  • Inherited – if the Inclusion or Exclusion options are set for parent nodes, they will be used in statistics accordingly. Otherwise, an appropriate value entered in the Data Warehouse and statistics function of the Customizing application will be applied.

Line item editor 5

Classifications allow classifying revenue accounts for particular items. In the Financials view of the Items application, it is possible to enter classification leaves in the Revenue account classification field. It is not possible to assign nodes.

The toolbar of the line item editor contains the following buttons/fields:

• [Show/hide] – it shows/hides the line item editor
• [Accept] – it accepts changes made in the line item editor and moves the edited item to the classification structure
• [Validate] – it verifies the correctness of the entered data
• Parent – it presents a parent node, if available

Editable fields available in the line item editor include:

• Node – the identification of a classification node. The identification must be unique within the folder; it can be changed at any time. The identification can be composed of up to 5 characters: digits, letters, some special characters (e.g. dots), and their combinations. Node identifications are used to recognize and apply correct nodes in other applications and queries.
• Description – it is an additional description of a classification node. Meaningful descriptions facilitate searching for nodes in other applications.
• Account origin – accounts are determined based on their origin. A default account origin should be set up in the item account classification. This value will be used in vouchers. Available default values include:
  • From account assignment – if this option is selected, it will not be possible to change the value of the Account origin field on the line item editor’s Account assignment tab in individual applications used for voucher creation (e.g. in Sales orders). The Revenue account will then display an account searched automatically based on the account assignment. In an associated voucher, e.g. a supplier invoice, such an account will also be entered automatically based on the account assignment.
  • From voucher – if this option is selected, it will not be possible to change the value of the Account origin field on the line item editor’s Account assignment tab in individual applications used for voucher creation. A relevant account will then need to be entered in the empty Revenue account field. In an associated voucher, e.g. a supplier invoice, the account from the order line item will be applied, with no possibility to change it.
  • According to voucher setting – if this default value is selected, it will be possible to select the value of the Account origin field in individual order applications; available options will include:  From account assignment or From voucher. Depending on the selected value, the field will either present a value or be an editable field. Besides the entries mentioned above, for supplier invoices, it will also be possible to add the value From supplier invoice. In supplementary cost invoices, the following values will be available: From account assignment and From supplementary cost invoice.

Line item editor 6

The toolbar of the line item editor contains the following buttons/fields:

• [Show/hide] – it shows/hides the line item editor
• [Accept] – it accepts changes made in the line item editor and moves the edited item to the classification structure
• [Validate] – it verifies the correctness of the entered data
• Parent – it presents a parent node, if available

Editable fields available in the line item editor include:

• Node – the identification of a classification node. The identification must be unique within the folder; it can be changed at any time. The identification can be composed of up to 5 characters: digits, letters, some special characters (e.g. dots), and their combinations. Node identifications are used to recognize and apply correct nodes in other applications and queries.
• Description – it is an additional description of a classification node. Meaningful descriptions facilitate searching for nodes in other applications.
• Levels – it is used to set up a node level. The node can be moved to a lower hierarchy level. Using this function, it is possible to flatten the classification structure at lower levels without creating new nodes, e.g. by moving leaves to the lowest level. Values available in this field are retrieved from the Level descriptions view. The field is only active if the Level descriptions view contains some entries. New view entries will be available once they are saved.

Line item editor 7

The toolbar of the line item editor contains the following buttons/fields:

• [Show/hide] – it shows/hides the line item editor
• [Accept] – it accepts changes made in the line item editor and moves the edited item to the classification structure
• [Validate] – it verifies the correctness of the entered data
• Parent – it presents a parent node, if available

Editable fields available in the line item editor include:

• Node – the identification of a classification node. The identification must be unique within the folder; it can be changed at any time. The identification can be composed of up to 5 characters: digits, letters, some special characters (e.g. dots), and their combinations. Node identifications are used to recognize and apply correct nodes in other applications and queries.
• Description – it is an additional description of a classification node. Meaningful descriptions facilitate searching for nodes in other applications.

General section:

This section allows entering the settings of a selected classification node.

• Restrict desired measure – selecting this parameter activates the Allowed desired measures field. If the parameter is not selected, all desired measures will be selectable for customers when editing customer return line items.
• Allowed desired measures (activated by selecting Restrict desired measure) – it allows narrowing the list of desired measures that can be selected by customers. Available options include:
  • (All)
  • Free replacement delivery
  • No measure
  • Subsequent delivery
  • Manual measure
  • Credit note
  • Chargeable replacement delivery

• Text required – this parameter allows deciding for a given node whether a return reason’s text should be required from customers editing return line items. This can be, for instance, a description of a defective device. Selecting the parameter activates the Text template field.
• Text template (activated by selecting Text required) – the field allows entering a template helping customers describe a return reason

Line item editor 8

A classification may be used to inherit signature and confirmation settings in the Declarations application; to do so, enter a relevant classification node in the Classification field, select the According to classification option in the Setting signature field on the Signature tab and select the According to classification option in the Setting confirmation field on the Confirmation tab of the Declarations application.

The toolbar of the line item editor contains the following buttons/fields:

• [Show/hide] – it shows/hides the line item editor
• [Accept] – it accepts changes made in the line item editor and moves the edited item to the classification structure
• [Validate] – it verifies the correctness of the entered data
• Parent – it presents a parent node, if available

Editable fields available in the line item editor include:

• Node – the identification of a classification node. The identification must be unique within the folder; it can be changed at any time. The identification can be composed of up to 5 characters: digits, letters, some special characters (e.g. dots), and their combinations. Node identifications are used to recognize and apply correct nodes in other applications and queries.
• Description – it is an additional description of a classification node. Meaningful descriptions facilitate searching for nodes in other applications.

General tab:

• Signature required – if this parameter is selected, the signature status Signed or Signature request manually completed will be required for declarations. If the function is active, signature will not be required for declarations.
• Allow “Complete signature request” – this parameter allows defining whether the [Complete signature request] action should be available in the Declarations application. The function’s setting does not depend on the activation of the Signature required function. If the function is active and the signature status is Signature not required or Not signed and a declaration is not shared yet, the [Complete signature request] action will be available in the Declarations application. Performing the action adds a signature date and changes the signature status to Signature request manually completed. If the function is inactive, the [Complete signature request] action will not be available in the Declarations application.
• Confirmation required – if this parameter is selected, a declaration with a missing confirmation cannot be shared. The confirmation status Confirmed or Confirmation request manually completed will then be required for the declaration. If the function is active, confirmation will not be required for declarations. Users can decide whether confirmation requests can be completed manually using the action.
• Allow “Complete confirmation request” – this parameter allows defining whether the [Complete confirmation request] action should be available in the Declarations application. The function’s setting does not depend on the activation of the Confirmation required function. If the function is active and the confirmation status is Confirmation not required or Not confirmed and a declaration is not shared yet, the [Complete confirmation request] action will be available in the Declarations application. Performing the action adds a confirmation date and changes the confirmation status to Confirmation request manually completed. If the function is inactive, the [Complete confirmation request] action will not be available in the Declarations application.

Line item editor 9

This classification is used to classify packagings. For instance, using this classification, it is possible to estimate the utilization of packagings disposed of in different ways. Based on such an analysis, it is possible to create a notification for a given organization in the country of use and fulfill the statutory obligation for packaging settlements.

In Germany, data must be reported to the Central Agency Packaging Register (ZSVR). According to the packaging law, the authority publishes an official catalogue of reportable packagings, which can be mapped in the system using the classification of packaging items.

To map the ZSVR catalogue, create the following catalogue elements:

The toolbar of the line item editor contains the following buttons/fields:

• [Show/hide] – it shows/hides the line item editor
• [Accept] – it accepts changes made in the line item editor and moves the edited item to the classification structure
• [Validate] – it verifies the correctness of the entered data
• Parent – it presents a parent node, if available

Editable fields available in the line item editor include:

• Node – the identification of a classification node. The identification must be unique within the folder; it can be changed at any time. The identification can be composed of up to 5 characters: digits, letters, some special characters (e.g. dots), and their combinations. Node identifications are used to recognize and apply correct nodes in other applications and queries.
• Description – it is an additional description of a classification node. Meaningful descriptions facilitate searching for nodes in other applications.
• Selectable – using this parameter, it can be determined whether the node can be selected when making assignments to this classification. If the function is active, the node can be assigned. If the function is inactive, it will not be possible to assign this node. In such a case, the node will be used as a structural characteristic whose subordinate data may be available. A subordinate or parent node must be selected when assigning categories.

General tab:

• Product description – it allows entering the description of a packable product
• Product details – it allows entering product description details
• Demarcation criterion – it is a criterion determining whether a given product’s packaging is reportable. For instance, it can be a weight limit.
• Registered trademark – in this field, it is possible to enter one or more registered product trademarks included in the reportable packaging catalogue published for Germany by the Central Agency Packaging Register according to the packaging law

Level descriptions view

The work pane of the Level descriptions view contains a table composed of the following columns:

• Level – a subsequent, automatically assigned number of an opened classification’s level. The field is non-editable.
• Description – an additional level characteristic

Customizing

The Customizing application does not contain settings for the Classifications application.

Business entities

Business entities listed below are relevant to the Classifications application; they are used, for instance, to:

• Assign authorizations
• Create activity definitions
• Import or export data

Authorizations

Comarch ERP Enterprise uses a multi-level authorization concept. Authorizations can be assigned by means of authorization roles as well as by assignment of organizations. The authorization concept has been described in the Authorizations article.

Special capabilities

The Classifications application has the special capability Maintaining organization-dependent classifications. Authorizations related to this capability can be defined in the Authorization roles application.

Maintaining organization-dependent classifications: com.cisag.app.general.ui.UnrestrictedClassificationMaintenance

In a multi-site environment, the special capability Maintaining organization-dependent classifications is relevant to the Classifications application. This capability only refers to organization-dependent classifications. If a given user has no authorizations for this capability, they can change the current classification, provided that the current user organization is the organization that handles this business entity itself.

Organization assignments

If the Content-based authorizations function has been activated in the Customizing application, the Classifications application is visible to the user if the user’s partner data is assigned to an organization associated with at least one of the following organization structures:

• Purchasing
• Inventory Management
• Financials
• Sales

Authorizations for business partners

The Classifications application is not released for business partners.