User Tools

Site Tools


implementation:wms:importtool

Importing data using the Produmex import tool

The import tool can be used to import elements through files to the Produmex system or to copy them directly from one database to another.

1. Import via files

Before starting the import, create the Produmex managed warehouse.

First create the SAP warehouse. Then create the company and the Produmex warehouse under the company in the Organizational Structure and link the SAP warehouse to it.

Zones and bin locations can only be imported into existing warehouses managed by Produmex.

1.1. Preparation

The CSV templates for the Produmex import tool can be found in the installation zip folder, in the Templates > Import Templates subfolder.

If the data to be imported contains special characters (eg. °), save the CSV file with UTF-8 encoding.

1.1.1. Zone

  • Code: The code of the zone.
  • Name: The name of the zone.
  • Parentcode: Code of the warehouse/zone the zone belongs to. The parent element must exist in the organizational structure of Produmex or must be defined in the same import file in a preceding line.
  • UseForZonePicking (Y/N): Can this zone be selected on the flow ‘Zone picking’?

Fill in relevant data in the worksheet Zone and save the worksheet as a CSV file. The CSV file should look like this:

Code;Name;ParentCode;UseForZonePicking
Z1;Zone1;02;N
Z2;Zone2;Z1;Y

1.1.2. Bin

  • Code: The scancode of the bin.
  • Name: The name of the bin.
  • Parentcode: The code of the structure element where the bin belongs to. The parent element must exist in the organizational structure of Produmex.
  • Is Active (Y/N): Is the location active?
  • IsDestinationForPicking (Y/N): Can the location be selected to put products on after a picking? Is the location a ‘pick and hold’ – location?
  • CanBeLinedUp (Y/N): Can the location be lined up during a production process. (Mostly used for Tanks/ Silo’s)
  • IsPickLocation: Can the location be used to perform item picking?
  • IsFixedItem (Y/N): Is the location a fixed pick location?
  • CanBeReplenished (Y/N): Can the location be replenished?
  • AllowCountDuringCycleCount (Y/N): Is the location allowed to be counted?
  • CountAfterNumberOfDays: The number of days after the location needs to be counted again.
  • MaximumLogisticUnits: The maximum number of allowed logistic units.
  • ItemStorageLocationType: Defines the item storage location type. Must be an existing Item Storage Location type stored in the PMX_ISLT user table.

Fill in relevant data in the worksheet Bin and save the worksheet as a CSV file. The CSV file should look like this:

Code;Name;ParentCode;IsActive;IsDestinationForPicking;CanBeLinedUp;Sequence;IsPickLocation;IsFixedItem;CanBeReplenished;AllowCountDuringCycleCount;CountAfterNumberOfDays;MaximumLogisticUnits;ItemStorageLocationType
E01A001;E01A001;Zone1;Y;N;N;100;Y;N;N;Y;0;;
A05A05;A05A05;Zone2;Y;N;N;120;Y;N;N;Y;0;;

1.1.3. BinItem

  • ParentCode: The code of the Bin location. The bin location must exist in the organizational structure of Produmex.
  • ItemCode: The item code. Must be an item defined in SAP Business One.
  • MinimumNumberOfItems: The minimum quantity of the item on the location. If the quantity falls below the minimum the system will generate a replenishment order.
  • MaximumNumberOfItems: The maximum quantity the location can contain of the specified item on the specified location.
  • NumberOfItemsToReplenish: Quantity that should be used to replenish a fixed pick location.

Fill in relevant data in the worksheet Bin Item and save the worksheet as a CSV file. The CSV file should look like this:

ParentCode;ItemCode;MinimumNumberOfItems;MaximumNumberOfItems;NumberOfItemsToReplenish
E01A001;A0001;10;999;10

1.1.4. Customer Shelf life

  • ItemCode: The item code. Must be an item defined in SAP Business One.
  • CardCode: The cardcode of the customer. Must be a customer defined in SAP Business One.
  • CountryCode: The country code for this shelf life. (optional)
  • ShelfLifeInDays: Shelf life for the customer for the item.

Fill in relevant data in the worksheet Customer Shelf life and save the worksheet as a CSV file. The CSV file should look like this:

ItemCode;CardCode;ShelfLifeInDays
A006;K00001;94

1.1.5. Item zonetypes

  • ItemCode: Item of the zone type. Must be an item defined in SAP Business One.
  • ZoneTypeCode: The code of the Zone Type. The Zone Type must exist in the organizational structure of Produmex.

Fill in relevant data in the worksheet Zone Types and save the worksheet as a CSV file. The CSV file should look like this:

ItemCode;ZoneTypeCode
A006;C

1.1.6. Packaging types

  • ItemCode: The item code. This item code must be known in SAP Business One.
  • PackagingTypeCode: The SAP UoM code.
  • Quantity: The quantity of the inventory unit of measure.
  • BarcodeType: Fixed value. Possible values:
    • G: Use this value for a GTIN14 barcode type (System will do a check if it is a valid GTIN-14 barcode).
    • F: Use this value for a Free Barcode type (System will perform no check).
  • Barcode: The Barcode of the Packaging Type.
  • AskDuringReception:
    • N: The system will not ask the quantity in the packaging type during the reception process.
    • Y: The system will ask the quantity in the packaging type during the reception process.
    • Remark: if the item is not managed in batches, the system will not allow a ‘Y’ value in this field.
  • HideDuringEnteringQuantity
    • N: The user cannot enter how much packaging types he is receiving.
    • Y: The user can enter how many packaging types he is receiving.

Fill in relevant data in the worksheet Packaging Types and save the worksheet as a CSV file. The CSV file should look like this:

ItemCode;PackagingTypeCode;Quantity;BarcodeType;Barcode;AskDuringReception;HideDuringEnteringQuantity
ITEM02;BOX;12;G;12345678901231;Y;N

1.1.7. Item Batch Attributes

  • Item code: The item code. Must be an item defined in SAP Business One.
  • BatchAttributeCode: The batch attribute code. This code should exist in the PMX_BATT user table.
  • ValueEntryOption: This will set whether the value should be asked during reception. Possible values:
    • Required: User will have to fill in the data.
    • Optional: User can skip entry of the data.
    • Hidden: This batch attribute will not be asked during reception.
  • IsLinkedToBatch (Y/N): Is the batch attribute linked to a batch number?

Fill in relevant data in the worksheet Item Batch Attributes and save the worksheet as a CSV file. The CSV file should look like this:

ItemCode;BatchAttributeCode;ValueEntryOption;IsLinkedToBatch
02004;COUNTRY_OF_ORIGIN;OPTIONAL;N
02004;MANUFACTURING_DATE;HIDDEN;N
02005;COUNTRY_OF_ORIGIN;REQUIRED;N

1.1.8. Box Type For WAS

  • Code: The code.
  • Name: The name.
  • U_BoxType: The box type.
  • U_ItemCode: The item code.
  • U_Quantity: The quantity of the item that can be stored in the given box type.
  • U_DividerType: The divider type.
  • U_CompartmentNr: The number of compartments a box has.

Fill in relevant data in the worksheet Box Type For WAS and save the worksheet as a CSV file. The CSV file should look like this:

Code;Name;U_BoxType;U_ItemCode;U_Quantity;U_DividerType;U_CompartmentNr
C1;C1;BT1;ITEM02;25;DIV1;3

1.1.9. Box For WAS

  • Code: The box code.
  • Name: The box name.
  • U_BoxType: The box type. The box type should exist in the Box type for WAS user table.

Fill in relevant data in the worksheet Box For WAS and save the worksheet as a CSV file. The CSV file should look like this:

Code,Name,U_BoxType
C1;C1;BT1
C2;C2;BT2

1.1.10. Route Header

  • Code: The code of the route template.
  • Name: The name of the route template.
  • Weekday: The code of the weekday.
  • StandardLoadingDock: The loading dock assigned to the route template. Must be a loading dock that exists in the organizational structure of Produmex.

Fill in relevant data in the worksheet Route Header and save the worksheet as a CSV file. The CSV file should look like this:

Code;Name;Weekday;StandardLoadingDock
Test;Test route header;2;D2.1
Test2;Test2 route header;3;D2.1

1.1.11. Route Line

  • ParentCode: The route template code.
  • CardCode: The cardcode of the customer.
  • Sequence: Defines the shipping order of the route.
  • ShipToCode: The ship to code of the customer. Must be an existing Ship To code.

Fill in relevant data in the worksheet Route Line and save the worksheet as a CSV file. The CSV file should look like this:

ParentCode;CardCode;Sequence;ShipToCode
Test;C00002;1;Customer 2 B
Test2;C00001;2;Customer 1
Test2;C00002;1;Customer 2 B

1.1.12. Location PutAwayZones

  • ParentCode: The code of the parent structure element. The bin location must exist in the organizational structure of Produmex.
  • PutAwayZone: The code of the put away zone.
  • SortPickSequenceDescending (Y/N): Are the locations belonging to the put away zone sorted by the pick sequence descending?
  • Sequence: The sequence number for the put away zone.
  • BelongsTo (Y/N): Does the location belong to the put away zone?

Fill in relevant data in the worksheet Location Put Away Zones and save the worksheet as a CSV file. The CSV file should look like this:

ParentCode;PutAwayZone;SortPickSequenceDescending;Sequence;BelongsTo
A11;Z1;Y;1;N
AA10;Z1;Y;2;N
AA10;Z4.1;Y;3;N
AA10;Z4;Y;4;N

1.1.13. Item allergen

  • ItemCode: The item code. Must be an item defined in SAP Business One.
  • AllergenCode: The allergen code. Must be an allergen code defined on the Allergen types user table.
  • Can contain allergen (Y/N): If set to ’Yes’, the item does not contains the allergen by default, but it is possible that there are some traces of this allergen present.

Fill in relevant data in the worksheet ImportItemAllergens and save the worksheet as a CSV file. The CSV file should look like this:

ItemCode;AllergenCode;CanContainAllergen
A006;GLUTEN;Y
A006;EGGS;N

1.1.14. Item – Card Code/Quality status

  • ItemCode: The item code. Must be an item defined in SAP Business One.
  • CardCode: The card code of the supplier. Must be a customer defined in SAP Business One.
  • QualityStatusCode: The code of the quality status. Must be a quality status defined on the Quality status tab of the Organizational Structure

Fill in relevant data in the worksheet ImportItemSupplierQualityStatus.csv and save the worksheet as a CSV file. The CSV file should look like this:

ItemCode;CardCode;QualityStatusCode
A006;V00002;BLOCKED

1.1.15. Item-Warehouse-Location or Zone

  • ItemCode: The item code. Must be an item defined in SAP Business One.
  • PmxWhsCode: The Produmex code of the warehouse. The warehouse must exist in the organizational structure of Produmex.
  • DefaultLocationZone: The code of the location or zone that is default location/zone in the warehouse for the item. The location/zone must exist in the organizational structure of Produmex.

Fill in relevant data in the worksheet ImportItemWarehouseLocationOrZone and save the worksheet as a CSV file. The CSV file should look like this:

ItemCode;PmxWhsCode;DefaultLocationZone
ITEM01;WH01;A0001
ITEM01;WH02;ZONE2.2

1.1.16. Organizational Structure settings

Export the configurations of the source database. Click on the ‘Export’ button on the General tab of the Organizational Structure.

The configurations will be exported to an .xml file.

Select the destination folder for the export. The default folder is C:\Program Files (x86)\SAP\SAP Business One\AddOns\PMX\Produmex AddOnLoader 7

„The export is finished” message indicates that the export is finished.

The following configurations will be exported:

  1. General settings (Except the Language, the Logo and the DB Credentials.)
  2. Default tab settings: default quality statuses (Default quality status reception, Released quality status reception, Quality status sales return, Quality status cycle counting, Quality status returnable items)
  3. Production tab settings: Quality status production

This export file can be used by our support team to match the settings in their environment.

1.2. Import tool

The import tool can be found in the installation folder of the Produmex tools:

Launch the import tool by executing Produmex.Sbo.Logex.Tools.ImportTool.exe. To define the destination database, select a connection string from the ‘Connection’ dropdown list. Every connection string defined in the configuration file of the import tool (Produmex.Sbo.Logex.Tools.ImportTool.exe.config) can be selected.

The selected connection string will connect the database to the tool. After the connection string has been selected, the system displays the connected database.

Restart the add-on after the import is finished.

1.2.1. General import

In the General import section, select the import type in the ’Import type’ dropdown list. The following import types can be selected:

  • Box Type by Item for WAS
  • Box for WAS
  • Item – Allergens
  • Item – Batch Attributes
  • Item – Card Code/Shelf Life
  • Item – Card Code/Quality status
  • Item – Packaging types
  • Item – Zone types
  • Item – Warehouse – Location or Zone
  • Localization
  • OSE objects (.xml)
  • OSE settings

Browse the file then click on the Import button. The application will show you that the import is finished at the bottom of the screen.

1.2.2. Import OSE objects (.csv)

Browse the CSV file and select the type in the ’Type’ dropdown list. The following types can be selected:

  • Bin
  • BinItem
  • Zone
  • Bin Item WAS

Click on the ’Import OSE objects (.csv)’ button. The application will show you that the import is finished at the bottom of the screen.

1.2.3. Import Route Templates

Browse the Route Header .csv file in the ‘Route Template Header’ field and browse the Route Line .csv file in the 'Route Template Line’ field. Click on the ‘Import Route Templates (.csv)’ button. The application will show you that the import is finished at the bottom of the screen.

1.2.4. Import Put away zones

Browse to the CSV file next to the button ‘Import Put away zones’. Select the type from the ’Type’ dropdown list. Click on the button ’Import Put away zones’. The application will show you that the import is finished at the bottom of the screen.

2. Copy data

2.1. Select the source and destination database

Launch the import tool by executing Produmex.Sbo.Logex.Tools.ImportTool.exe. To define the source database, select a connection string from the ‘Source database’ dropdown list. To define the destination database, select a connection string from the ‘Destination database’ dropdown list.

The database version of the destination database must be the same as the database version of the source database.

The selected connection strings will connect the databases to the tool. After the connection string have been selected, the system displays the connected databases.

2.2. Copy OSE

Press the ‘Copy OSE’ button to copy PMX created structure elements from the Organizational Structure of the source database and import them to the destination database.

Please note: If there are fixed bin locations or bin locations that can be replenished in the source database, the fixed items/items to be replenished must be exist in the destination database.

2.3. Copy Stock

Click on the ‘Get data’ button to get the list of quality statuses from the source database and the price lists from the destination database.

Then select the quality status from the ‘Quality status’ dropdown list. Every quality status defined in the source database are listed.
Next select the price list from the ‘Pricelist’ dropdown list. Every price list existing in the destination database will be listed.

The selected quality status and price list will be applied to the stocks imported in the destination database. Press the ‘Copy Stock’ button to import the stock with the previously defined parameters from the source database to the destination database.

Please note: Before starting the import, make sure that the following exists in the destination database:

  • Every item that are on stock in the source database is defined in the destination database
  • The storage locations where the stock is stored is defined in the destination database too
implementation/wms/importtool.txt · Last modified: 2019/03/13 10:37 by vise