Topic overview

The Import data application is used to perform the import transfer of selected data in such formats as an .xlsx file, which can be used, for instance, for material requirements planning.

The following article describes how to work with the Import data application
with regard to:

• Customer item data
• Supplier item data
• Customer item classification data
• Customer item planning data

The following describes the steps that must be completed when importing data. Also, the article documents expected preconditions and results.

More information may be found in the Import data article.

Data import procedures

1. Open the Import data application

2. Display the filter for an appropriate business unit using the [Value assistant] button

3. Selected attributes of the business unit filter are already activated in the work pane. At this stage, if necessary, it is possible to adjust required import attributes.

4. Select the [Import data] button available in the standard toolbar. The Import data dialog window will open.

5. In the opened Import data dialog window, select an import file. More information about the window’s fields may be found in the Import data article.

6. Select the button [In background] in the opened dialog window to initiate the import process.

Sequence

When importing data items that are dependent on one another, it is necessary to follow a defined sequence. A given item must already exist.

Recommended sequence:

1. Item base data
2. Purchasing data should be imported before importing supplier data
3. Sales data should be imported before importing customer data, customer classification data, or customer planning data

Sequence and additional conditions for multi-site environments:

When importing supplier item data at a specific organization level, the item must already have data entered in the Purchasing view at that level.

When importing customer item, customer classification, or customer planning data at a specific organization level, the item must already have data entered in the Sales view at that level.

1. Purchasing data should be imported before importing supplier item data

2. Sales data should be imported before importing customer data, customer classification data, or customer planning data

Import of supplier items

Preconditions

• Purchasing data has already been defined for the item at a specific organization level
• A filter is available for the business entity cisag.app.purchasing.obj.SupplierPurchaseItem which contains attributes to be imported

Instructions

1. Make sure that the import file to be generated contains at least one reference to the item, organization, and supplier

2. Make sure that all the required fields related to the supplier item data (see the chapter Identification fields and required fields) are filled in

3. Perform the steps as described in the chapter Data import procedures

Import of customer items

Preconditions

• Sales data has already been defined for the item at a specific organization level
• A filter is available for the business entity cisag.app.sales.obj.CustomerSalesItem which contains attributes to be imported

Instructions

1. Make sure that the import file to be generated contains at least the identification of the item, organization, and customer

2. Make sure that all the required fields related to the customer item data (see the chapter Identification fields and required fields) are filled in

3. Perform the steps as described in the chapter Data import procedures

Import of customer classification item data

Preconditions

• Sales data has already been defined for the item at a specific organization level
• A filter is available for the business entity cisag.app.sales.obj.CustomerClassificationItem which contains attributes to be imported

Instructions

1. Make sure that the import file to be generated contains at least the identification of the item, organization, and customer classification

2. Make sure that all the required fields related to the customer classification item data (see the chapter Identification fields and required fields) are filled in

3. Perform the steps as described in the chapter Data import procedures

Import of customer planning item data

Preconditions

• Sales data has already been defined for the item at a specific organization level
• A filter is available for the business entity cisag.app.sales.obj.CustomerPlanningData which contains attributes to be imported

Instructions

1. Make sure that the import file to be generated contains at least the identification of the item, organization, and customer

2. Make sure that all the required fields related to the customer planning item data are filled in

3. Perform the steps as described in the chapter Data import procedures

Special features for reference items

A reference item is directly associated with variant items, but is not subject to purchasing and sales processes. It serves as an information carrier for the associated variant items and as their template.  A change in existing or new data in the Items application causes a corresponding change in the associated variant items. In the case of reference items, it also refers to supplier item data, customer item data, customer classification data, and customer planning data.

Special features for variant items

A variant item always refers to a reference item. In the case of variant items, it is only possible to import data that can be entered manually in the Items application. The import operation cannot be used to change attributes that cannot be edited in a selected application view.

Changes made via import

The import functionality can also be used to make changes to existing data.

For instance, if the user wants to activate the availability check for all customer items, this can also be done via import.

Instructions

1. Generate a filter that contains the identification of a relevant item, the key attribute of the utilization, and the fields to be changed

2. Then export the corresponding items, for instance in the CSV format

3. In the file created, change the corresponding field to the desired value

4. Then import the file again with the generated filter

The following example will activate the availability check of customer items.

Identification fields and required fields

Below are listed the required fields and key attributes (K) of individual business objects. The identification fields and required fields are subject to changes.

The following information may also be referred to by opening the Items application, switching to the relevant view, and validating it by clicking the [Validate] button. All fields marked with a red corner are required.

Supplier item data

Specifying an organization is mandatory only in a multi-site environment. If an organization is not specified in a single-site environment, the default organization of the active OLTP client will be set.

The following units are required fields; by default, their values are retrieved from item units:

Customer item data

Specifying an organization is mandatory only in a multi-site environment. If an organization is not specified in a single-site environment, the default organization of the active OLTP client will be set.

The following units are required fields; by default, they are assigned the primary unit of an item:

Customer classification item data

Specifying an organization is mandatory only in a multi-site environment. If an organization is not specified in a single-site environment, the default organization of the active OLTP client will be set.

The following units are required fields; by default, they are assigned the primary unit of an item:

Customer planning item data

Specifying an organization is mandatory only in a multi-site environment. If an organization is not specified in a single-site environment, the default organization of the active OLTP client will be set.