Topic overview

This article describes the procedures and actions for the Import data application in relation to warehouses. It will also inform you about the expected preconditions, effects and restrictions.

The description of the application Import data application, which includes field and button descriptions, can be found in the article Importing data.

General

Both simple warehouses and structured warehouses that are divided into warehouse zones can be imported. The import is essentially based on the current data model of the warehouse, which is stored in the repository database.

Both importing and exporting warehouses support the same attributes. You therefore only need to define a single filter for both importing and exporting.

1:1 relationships are usually based on a technical GUID attribute in the data model. Depending on the use case, either the technical GUID attribute or the functional key from the target object (usually code or number) can be used during import. If the GUIDs of the warehouse or the GUIDs of the warehouse zones are also specified in the import file, then these GUIDs are used. Otherwise, new GUIDs are assigned for both the warehouse and the warehouse zones.

The same rules apply when importing as when processing via the application. For example, the warehouse in a saved item can no longer be subsequently changed. Attribute values are ignored if they cannot be adopted in the current context. The same logic is applied when determining the default value, so that import and application behave identically. The same applies to the checks.

Procedures: Importing warehouses

1. Open the Import data application
2. Display a particular warehouse or a filter for this business object: cisag.app.inventory.obj.StorageArea

• The filter for importing warehouses is opened.

3. Duplicate or create a new filter for this business object
4. If necessary, change the attributes of the filter that have already been selected
5. Select the [Import data] button in the standard toolbar

• The Import data dialog box opens.

6. You can make settings for the import file in the Import data dialog box. You can find a description of the fields in the Import data article
7. Select one of the buttons: [In background] or [Immediately]

• The import is executed.

Details

In this chapter you will find information on the following topics:

• Import of a simple warehouse
• Import of a structured warehouse

Import of a simple warehouse

A simple warehouse is not structured in warehouse zones. The system recognizes a simple warehouse based on the Warehouse organization (locationOrganisation) if this is marked with Simple warehouse (NONE) or 0 or if the value is not specified in the import file. If warehouse zones are contained in the import file and one of the listed values is specified for the warehouse organization, the warehouse zones are not taken into account.

When importing a simple warehouse, it is necessary to enter the warehouse data.

Warehouse data

The warehouse data includes the following attributes. Attributes marked with an asterisk (*) must be specified when importing. The specification of the other attributes is optional.

Example of an import file for a simple warehouse

An XML file that can be used to import a simple warehouse has the following content, for example:

<?xml version="1.0" encoding="UTF-8"?>
<semiramis xmlns="com.cisag.app.inventory.obj.StorageArea" xsi:schemaLocation="com.cisag.app.inventory.obj.StorageArea StorageArea.xsd" created="2005-12-14T08:40:48.140Z" locale="en-US-XMLSchemaCompliant" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
 <StorageArea xmlns="com.cisag.app.inventory.obj.StorageArea">
  <code>100</code>
  <description>Standard bearing</description>
  <OrganizationalUnit>00000</OrganizationalUnit>
  <WarehouseManagementServer>100</WarehouseManagementServer>
 </StorageArea>
</semiramis>

Import of a structured warehouse

A structured warehouse has warehouse zones, which in turn can be subdivided into storage locations. The system recognizes a structured warehouse based on the warehouse organization. The warehouse organization indicates that the warehouse is further divided into warehouse zones.

When importing a structured warehouse, the following elements must be specified:

• Warehouse data
• Storage location control data
• Warehouse zones
  • Exactly one warehouse zone with the usage Receipt of goods zone
  • Exactly one warehouse zone with the usage Issue of goods zone
  • Exactly one warehouse zone of the usage Inventory count differences
  • At least one warehouse zone with the use Reserve or Not specified

Warehouse data

In the warehouse data, a warehouse organization must be specified that does not have the value NONE so that warehouse zones can be taken into account at all during import. The warehouse data of a structured warehouse includes the same attributes as for a simple warehouse (see this chapter: Warehouse data).

Storage location control data

The storage control data includes the following information:

• Put-away according to storage location priorities
• Report using check digit
• Storage strategies
• Storage restrictions
• Voucher document templates

Put-away according to storage location priorities

Put-away according to storage location priorities includes the following optional attributes. If Used is activated, put-away is carried out according to storage location priorities. To do this, the A, B and C item priorities must be specified.

Report using check digit

The reporting via a check digit includes the following optional attribute.

Storage strategies

When specifying the storage strategies, you must either specify the identification (attribute: code) of an existing storage strategy or you can define the storage strategy yourself via the import. If you specify an existing storage strategy, the remaining attributes are determined by this storage strategy and do not need to be explicitly specified in the import file. If you do not specify an existing storage strategy, you must specify the attributes marked with an asterisk (*). The specification of the other attributes is optional.

Further information on storage strategies can be found in this article: Introduction: Storage strategies.

Storage restrictions

The storage restrictions include the following optional attributes.

Voucher document templates

Optionally, you can import any number of voucher document templates. A voucher document template includes the following attributes. Attributes marked with an asterisk (*) must be specified. The specification of the other attributes is optional.

Warehouse zones

The storgate location control data includes the following information:

• Warehouse zone data
• Storage strategies

Warehouse zone data

A warehouse zone includes the following attributes. Attributes marked with an asterisk (*) must be specified when importing. The specification of the other attributes is optional.

Storage strategies

If no storage strategy is defined for the warehouse zone in the import file, the storage strategy specified in the warehouse data applies. The warehouse data for a warehouse zone includes the same attributes as for a simple warehouse.

Example of an import file for a structured warehouse

An XML file that can be used to import a structured warehouse with the necessary warehouse zones has the following content, for example:

<?xml version="1.0" encoding="UTF-8"?>
<semiramis xmlns="com.cisag.app.inventory.obj.StorageArea" xsi:schemaLocation="com.cisag.app.inventory.obj.StorageArea StorageArea.xsd" created="2005-12-15T11:14:17.428Z" locale="en-US-XMLSchemaCompliant" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
 <StorageArea xmlns="com.cisag.app.inventory.obj.StorageArea">
  <code>0006</code>
  <description>Structured warehouse</description>
  <locationOrganization>BLOCK_STORAGE</locationOrganization>
  <OrganizationalUnit>99000</OrganizationalUnit>
  <WarehouseManagementServer>Warehouse logistics server</WarehouseManagementServer>
  <StrategyData>
   <putStrategy>EMPTY_BIN</putStrategy>
   <pickStrategy>FIFO</pickStrategy>
   <putSortOrder index="0">0</putSortOrder>
   <putSortOrder index="1">1</putSortOrder>
   <putSortOrder index="2">2</putSortOrder>
   <putSortOrder index="3">0</putSortOrder>
   <pickSortOrder index="0">0</pickSortOrder>
   <pickSortOrder index="1">1</pickSortOrder>
   <pickSortOrder index="2">2</pickSortOrder>
   <pickSortOrder index="3">0</pickSortOrder>
   <fixPutStrategy>NOT_PREFERRED</fixPutStrategy>
   <fixPickStrategy>NOT_PREFERRED</fixPickStrategy>
   <fillUpStrategy>FIXED_BIN</fillUpStrategy>
   <pickingStrategy>ANY_BIN</pickingStrategy>
  </StrategyData>
  <Zones>
   <code>INV</code>
   <description>Inventory difference zone</description>
   <locationOrganization>NONE</locationOrganization>
   <use>INVENTORY_DIFFERENCES</use>
  </zones>
  <Zones>
   <code>WA</code>
   <description>Goods issue zone</description>
   <locationOrganization>NONE</locationOrganization>
   <use>SHIPPING</use>
  </zones>
  <Zones>
   <code>WE</code>
   <description>Incoming goods zone</description>
   <locationOrganization>NONE</locationOrganization>
   <use>RECEIVING</use>
  </zones>
  <Zones>
   <code>Z1</code>
   <description>Storage zone 1</description>
   <locationOrganization>BLOCK_STORAGE</locationOrganization>
   <use>NOT_SPECIFIED</use>
   <qcStatus>RELEASED</qcStatus>
   <Owner>00000</Owner>
  </zones>
 </StorageArea>
</semiramis>

Overview: Attributes

The attributes of the individual business objects that are available for import are listed below. The corresponding relationship name is also included for foreign key attributes. The identification and mandatory fields are subject to change and can be extended by making adjustments.

The identification attributes (key attributes) are identified by a (K).

Header data

Storage location (StorageArea)

The identification of a warehouse consists of the warehouse and ZEROGUID in the parent attribute. The parent attribute cannot be imported; it is generated automatically.

Address data (AddressData)

The address data is stored in the database as a hash code business object and is displayed as a part for export/import.

Part Put away according to storage location priorities (locationPriority)

Inventory order grouping (TransportOrderGroupingInfos)

Logical data types of the grouping and sorting criteria

The entries for the adjustable grouping and sorting criteria are individual logical data types.

Inventory order sorting (TransportOrderSortingInfos)

Inventory owner sequence (OwnerSequence)

Output settings (InventoryOutputSettings)

Put-away strategy (StrategyData)

When importing a warehouse, you can either use an existing put-away strategy or define a new put-away strategy.

Withdrawal strategy (StrategyData)

When importing a warehouse, you can either use an existing withdrawal strategy or define a new withdrawal strategy.

Warehouse zones

Warehouse (StorageArea)

The identification of a warehouse zone consists of the warehouse zone and the GUID of the associated warehouse in the parent attribute. The parent attribute cannot be imported, it is generated automatically.