Import warehouse areas

Topic overview

This article describes the procedures for using the Import data application in relation to warehouse areas. These procedures contain general instructions on how to import warehouse areas. You will also be informed about the supported attributes.

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

Procedures

This section describes the procedures for importing warehouse areas.

Attributes required for the import

Enter at least the following attributes for each warehouse area:

  • Identification attributes (business key)
  • Mandatory fields

No warehouse area can be imported without the identification attributes. If a mandatory field is missing, post-processing is started in the relevant application if the With correction application has been selected in the Correct field in the Import data dialog window. The mandatory fields of the individual business entities can sometimes be recognized in the respective applications by a grey corner in the input field of the corresponding attribute. The mandatory fields are not marked as such in the field descriptions of the application documentation, as they can vary with regard to this property in the individual Comarch ERP Enterprise installations.

In addition, there are relationships to other business entities that do not belong directly to the imported business entity. These relationships are established via foreign keys. Relationships via foreign keys are indicated by italics in the filter. In order to be able to resolve such foreign key relationships, the identification attributes of the referenced business entities must be selected in the filter. Data referenced via foreign keys cannot be imported together with the referencing data. They must already exist in the system. If attributes other than their identification attributes are specified via the foreign key relationship, these are ignored.

If the primary key of a business object consists entirely or partially of foreign keys, the business object to which this foreign key refers must be resolved in the import file using its identification attributes.

Importing warehouse areas

  1. Open the Import data application.
  2. Display the or a filter for the business object com.cisag.app. inventory.obj.WarehouseArea
  3. The filter for importing the is displayed.
    If required, you can also enter a new filter for this business object.
  1. The selected attributes of the filter are already marked. If necessary, you can still adjust the attributes.
  2. Select the [Import data] button in the standard toolbar.
  • The Import data dialog box opens.
  1. You can make settings for the import file in this dialog window. A detailed description of the fields can be found in the Import data article.
  2. You can carry out the import by selecting the [In background] or [Immediately] button.

Overview: Supported attributes

This section lists all the attributes supported when importing warehouse areas. For foreign key attributes, the corresponding relationship name is also included. The attributes can be subject to changes and can also be extended by adjustments.

The identification attributes (key attributes) are also marked with a (K), the functional identification attributes with a (BK).

Basic data

Attribute

Relationship

Meaning

guid(K)Technical identification
code(BK)Warehouse area identification
descriptionWarehouse area description
responsibleResponsibleEmployee responsible for the warehouse area
You can also import the key attribute via the relationship Responsible and its key attribute number.
warehouse(BK)WarehouseWarehouse of the warehouse area
You can also import the key attribute via the relationship Warehouse and its key attribute code.

Warehouse area components

Attribute

Relationship

Meaning

guid(K)Technical identification
warehouseArea(K)Warehouse area
This attribute is filled automatically and should therefore not be set.
zoneWarehouse zone
rowFromFrom row
rowTo(BK)To row
levelFrom(BK)From level
levelTo(BK)To level
binFrom(BK)From location
binTo(BK)To location

Output settings for document templates

Attribute

Relationship

Meaning

guidTechnical identification
organizationalUnit(BK)Organization
This attribute is filled automatically and should therefore not be set.
warehouseAreaWarehouse area
This attribute is filled automatically and should therefore not be set.
document(BK)Voucher document type
medium(BK)Output medium
documentDefinitionDocumentDefinitionVoucher document template
communicationTypeCommunicationTypeCommunication type for fax and e-mail
preferredPreferred output setting
partnerPartner
This attribute is filled automatically and should therefore not be set.
warehouse(BK)Warehouse
This attribute is filled automatically and should therefore not be set.

Example import file

An XML import file for entering or updating a warehouse area including warehouse area components and output settings for voucher document templates has the following content, for example:

<?xml version="1.0" encoding="UTF-8"?><semiramis xmlns="com.cisag.app.inventory.obj.WarehouseArea" xsi:schemaLocation="com.cisag.app.inventory.obj.WarehouseArea WarehouseArea. xsd" created="2012-10-31T12:35:28.229Z" locale="en-US-XMLSchemaCompliant" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" nlsMode="MULTI_LANGUAGE" dateTimeMode="COMPACT">
 <WarehouseArea xmlns="com.cisag.app.inventory.obj.WarehouseArea">
  <code>AREA_1</code>
  <description>
   <text lang="en">TEST</text>
   <text lang="it">TEST</text>
   <text lang="en">TEST</text>
  </description>
  <Responsible>
   <number>70010</number>
  </Responsible>
  <Warehouse>
   <warehouse>300</warehouse>
  </Warehouse>
  <Definitions>
   <zone>RES</zone>
   <rowFrom>001</rowFrom>
   <rowTo>010</rowTo>
   <levelFrom/>
   <levelTo/>
   <binFrom/>
   <binTo/>
  </Definitions>
  <Definitions>
   <zone>ZONE</zone>
   <rowFrom/>
   <rowTo/>
   <levelFrom/>
   <levelTo/>
   <binFrom/>
   <binTo/>
  </Definitions>
  <InventoryOutputSettings>
   <document>TRANSPORT_ORDER</document>
   <medium>EMAIL</medium>
   <preferred>true</preferred>
   <CommunicationType>
    <name>300</name>
    <description>
     <text lang="en">Email, business</text>
     <text lang="it">Email, lavoro</text>
     <text lang="en">Email, work</text>
    </description>
   </CommunicationType>
   <DocumentDefinition>
    <code>311</code>
    <description>
     <text lang="en">Storage order (e-mail)</text>
     <text lang="it">Ordine Magazzino/Prelevato (e-mail)</text>
     <text lang="en">Inventory Order/Pick Order (e-mail)</text>
    </description>
   </DocumentDefinition>
  </InventoryOutputSettings>
 </WarehouseArea>
</semiramis>

 

Czy ten artykuł był pomocny?