produmex wms - complete tools guidewiki.produmex.name/lib/exe/fetch.php?media=... · 2020. 12....

2020/01/20 14:36 1/33 Produmex WMS - Complete Tools Guide

- http://wiki.produmex.name/

Produmex WMS - Complete Tools Guide

1. Import Tool

The import tool can be used to import elements through files to the Produmex system or to copy themdirectly 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 thecompany 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 theTemplates > Import Templates subfolder.

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

http://wiki.produmex.name/doku.php?id=implementation:wms:companylevelhttp://wiki.produmex.name/doku.php?id=implementation:wms:warehousesettings

Last update: 2019/12/1113:03 implementation:wms:tools_complete http://wiki.produmex.name/doku.php?id=implementation:wms:tools_complete

http://wiki.produmex.name/ Printed on 2020/01/20 14:36

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 shouldlook like this:

Code;Name;ParentCode;UseForZonePickingZ1;Zone1;02;NZ2;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 shouldlook like this:

Code;Name;ParentCode;IsActive;IsDestinationForPicking;CanBeLinedUp;Sequence;IsPickLocation;IsFixedItem;CanBeReplenished;AllowCountDuringCycleCount;CountAfterNumberOfDays;MaximumLogisticUnits;ItemStorageLocationTypeE01A001;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.

http://wiki.produmex.name/doku.php?id=implementation:wms:islt



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 fileshould look like this:

ParentCode;ItemCode;MinimumNumberOfItems;MaximumNumberOfItems;NumberOfItemsToReplenishE01A001;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. TheCSV file should look like this:

ItemCode;CardCode;ShelfLifeInDaysA006;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 fileshould look like this:

ItemCode;ZoneTypeCodeA006;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).❍

http://wiki.produmex.name/doku.php?id=implementation:wms:zonetypes



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 CSVfile should look like this:

ItemCode;PackagingTypeCode;Quantity;BarcodeType;Barcode;AskDuringReception;HideDuringEnteringQuantityITEM02;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. TheCSV file should look like this:

ItemCode;BatchAttributeCode;ValueEntryOption;IsLinkedToBatch02004;COUNTRY_OF_ORIGIN;OPTIONAL;N02004;MANUFACTURING_DATE;HIDDEN;N02005;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. TheCSV file should look like this:

Code;Name;U_BoxType;U_ItemCode;U_Quantity;U_DividerType;U_CompartmentNr

http://wiki.produmex.name/doku.php?id=implementation:wms:batt



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 fileshould look like this:

Code,Name,U_BoxTypeC1;C1;BT1C2;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 fileshould look like this:

Code;Name;Weekday;StandardLoadingDockTest;Test route header;2;D2.1Test2;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 fileshould look like this:

ParentCode;CardCode;Sequence;ShipToCodeTest;C00002;1;Customer 2 BTest2;C00001;2;Customer 1Test2;C00002;1;Customer 2 B

http://wiki.produmex.name/doku.php?id=implementation:wms:btit



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;BelongsToA11;Z1;Y;1;NAA10;Z1;Y;2;NAA10;Z4.1;Y;3;NAA10;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. TheCSV file should look like this:

ItemCode;AllergenCode;CanContainAllergenA006;GLUTEN;YA006;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 asa CSV file. The CSV file should look like this:

ItemCode;CardCode;QualityStatusCodeA006;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 worksheetas a CSV file. The CSV file should look like this:

ItemCode;PmxWhsCode;DefaultLocationZoneITEM01;WH01;A0001ITEM01;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 ofthe 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:

General settings (Except the Language, the Logo and the DB Credentials.)1.Default tab settings: default quality statuses (Default quality status reception, Released quality2.status reception, Quality status sales return, Quality status cycle counting, Quality statusreturnable items)Production tab settings: Quality status production3.3PL Invoicing settings4.Extension Parameters5.

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 thedestination database, select a connection string from the ‘Connection’ dropdown list. Every

http://wiki.produmex.name/doku.php?id=implementation:wms:generalsettingshttp://wiki.produmex.name/doku.php?id=implementation:wms:defaultshttp://wiki.produmex.name/doku.php?id=implementation:wms:3plhttp://wiki.produmex.name/doku.php?id=implementation:wms:extensionparameters



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 hasbeen 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 followingimport 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 isfinished 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 beselected:

Bin●BinItem●Zone●Bin Item WAS●

Click on the ’Import OSE objects (.csv)’ button. The application will show you that the import isfinished 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. Theapplication 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 theimport 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 sourcedatabase, select a connection string from the ‘Source database’ dropdown list. To define thedestination 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 ofthe source database.

The selected connection strings will connect the databases to the tool. After the connection stringhave 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 OrganizationalStructure 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 sourcedatabase, 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 theprice lists from the destination database.

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

The selected quality status and price list will be applied to the stocks imported in the destinationdatabase. Press the ‘Copy Stock’ button to import the stock with the previously defined parametersfrom 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●

2. Import Initial Stock Tool

On a database where Produmex WMS is installed for the first time, use the Import Initial Stock tool tocreate Produmex stocks for all SAP stocks in selected warehouses.

Make sure you do not run this tool in a warehouse if there are Produmex stocks already. It canresult inconsistencies between stock in SBO and stock in Produmex.

Run the Produmex.Sbo.Logex.Tools.ImportInitialSAPStockTool.exe. The file is located in C:\ProgramFiles (x86)\Produmex \Produmex Tools.

On the opening ‘Import initial stock from SAP into PMX’ form every warehouse that is managed byProdumex and has inventory in SAP is listed.

Enter the location code to the PmxLocationCode field on the line of the warehouse. Only activelocations that belong to the warehouse can be added. If you leave the location code empty, theimport is not performed for the given warehouse.

Before starting the import, check whether there is stock registered in Produmex for the givenwarehouse. Make sure you do not run this tool if there is stock registered in Produmex for thewarehouse.

Press the Import button to start the import.

After the import is finished, the system displays a message containing the number of the updated



stock lines. Please note: If a batch managed item is on stock with multiple batches, each batch countsas a stock line.

The initial inventory from SAP Business One is booked for the selected location. The quality status ofthe stock is ’Released’. The stock has no linked LUID.

The import is not registered in the Traceability report.

Once the stock is booked in Produmex, you can distribute it to their location with the Move functionon the scanner. During the move it is possible to create new SSCC’s or to scan existing SSCC’s.

Items managed by serial numbers are not supported.

3. Interfacing Tool

18.1. Configuration

18.1.1. Define the path

Define the input and the output path for the EDI module on the Config tab of the OrganizationStructure.

In the Interface Monitor Input Archive Path field define the path where the system moves the file1.after processing it.In the Interface Monitor Input Error Path field define the path where the file is moved if there is an2.error during the processing.In the Interface Monitor Input Path field define the path to a folder from where the system imports3.the file.In the Interface Monitor Output Archive Path field define the path where the third party software4.puts the file after processing it.Note: This path is not used by the Produmex Interfacing tool.In the Interface Monitor Output Error Path field define the path where the third party software puts5.the file if there is an error while processing it.Note: This path is not used by the Produmex Interfacing tool.In the Interface Monitor Output Path field define the path to the folder where the system exports6.the file. Set this folder as an input for the third party software.

http://wiki.produmex.name/doku.php?id=implementation:wms:traceability



18.1.2. Set up the interfacing controller

Produmex offers standard controllers for the following documents:

Document Property ExtensionPMX advance shippingnotice

Interface for PMX Advance Shipping Notice(Im-Exporter)

IPmx Advance Shipping NoticeInterface

PMX move order Interface for PMX Move Order Im-/Export IPmx Move Order InterfacePMX move Interface for PMX Move Im-/Export IPmx Move Interface

SBO item master data Interface for SBO Item Master Data Im-/ExportISBO Item Master DataInterface

SBO purchase creditnote

Interface for SBO Purchase Credit Note Im-/Export

ISBO Purchase Credit NoteInterface

SBO purchase delivery Interface for SBO Purchase Delivery Im-/ExportISBO Purchase DeliveryInterface

SBO purchase invoice Interface for SBO Purchase Invoice Im-/ExportISBO Purchase InvoiceInterface

SBO purchase order Interface for SBO Purchase Order Im-/Export ISBO Purchase Order Interface

SBO purchase return Interface for SBO Purchase Return Im-/Export ISBO Purchase Return Interface

SBO sales credit note Interface for SBO Sales Credit Note Im-/ExportISBO Sales Credit NoteInterface

SBO sales delivery Interface for SBO Sales Delivery Note Im-/Export ISBO Sales Delivery Interface



Document Property ExtensionSBO sales invoice Interface for SBO Sales Invoice Im-/Export ISBO Sales Invoice InterfaceSBO sales return Interface for SBO Sales Return Im-/Export ISBO Sales Return InterfaceSBO sales order Interface for SBO Sales Order Im-/Export ISBO Sales Order Interface

The following documents have an interface, but they require custom controllers:

Document PropertyPMX picklist Interface for PMX Pick List Im-/ExportPMX serial number Interface for PMX Serial Number Im-/ExportPMX stock QS change Interface for PMX Stock QS Change ImportPMX stock IPmx Stock Interface – Pmx Stock Im-/ExporterSBO business partner Interface for SBO Business Partner Im-/ExporterSBO goods issue Interface for SBO Goods Issue Im-/ExporterSBO goods receipt Interface for SBO Goods Receipt Im-/ExportSBO incoming payment Interface for SBO Incoming Payment Im-/ExportSBO production issue Interface for SBO Production Issue Im-/ExportSBO production receipt Interface for SBO Production Receipt Im-/ExportSBO sales delivery 2 Interface for SBO Sales Delivery 2 Im-/ExportSBO sales return 2 Interface for SBO Sales Return 2 Im-/ExportSBO whs transfer Interface for SBO Sales Order Im-/Export

Configuration steps:1. Select the controller for the necessary document type on the Extension Parameters tab of theOrganization Structure.2. Select the Property and the Extension.3. Click OK.

http://wiki.produmex.name/doku.php?id=implementation:wms:extensionparameters



With the Interfacing tool certain documents can be imported to and exported from the system. Thisapplication is installed during the Produmex Tools installation (see 3.2. Install components).

18.3.1. Preparing documents for import

The following table shows the prefixes, the extensions and the object types to be used whilepreparing documents for import. The table lists documents with standard controllers.

Document Type Prefix Extension Object typePurchase order OPOR_ xml 22Purchase delivery OPDN_ xml 20Purchase invoice OPCH_ xml 18Purchase credit note ORPC_ xml 19Purchase return ORPD_ xml 21Sales order ORDR_ xml 17Sales delivery ODLN_ xml 15Sales invoice OINV_ xml 13Sales credit note ORIN_ xml 14Sales return ORDN_ xml 16Proof of delivery EPOD_ csv POD_RTHEAdvance shipping notice* N/A csv 18 or 22Move* PMX_MV_ csv N/AMove order* PMX_MO_ csv N/A

http://wiki.produmex.name/doku.php?id=implementation:wms:install_pdmx_suite#install_components



*See section 18.3.3.Templates for importing.

18.3.2. Running the Interfacing tool

The tool is located in the installation folder of the Produmex Tools, for example: C:\ProgramFiles\Produmex \Produmex Tools\ and the file name is Produmex.Sbo.Logex.Tools.InterfacingTool.exe.

Start the interfacing tool with startup parameters. The following command line parameters aresupported:

/cs: Contains the connection string that should be used. Default value: 'SboConnectionString'●/t: Defines the type of the interface. Possible values:●

salesorder❍salesdelivery❍salesinvoice❍salescreditnote❍salesreturn❍purchaseorder❍purchasedelivery❍purchaseinvoice❍purchasecreditnote❍purchasereturn❍productionissue❍productionreceipt❍advanceshippingnotice❍itemmasterdata❍incomingpayment❍move❍moveorder❍stock❍stockqschange❍businesspartnermasterdata❍warehouseautomation❍POD❍Default value: ‘stock’

/d: Defines the direction of the interface. Possible values:●import❍export❍Default value: ‘export’.

/rf: If added, the system reprocesses failed actions.●

Example: Produmex.Sbo.Logex.Tools.InterfacingTool.exe /cs:SboConnectionString /t:move /d:import

Note: It is recommended to run the interfacing tool as a scheduled task.

18.3.3. Templates for importing

http://wiki.produmex.name/doku.php?id=implementation:wms:edi_module#templates_for_importing



18.3.3.1. Move and move order template for importing

1. For moves/move orders create a csv. file with the following fields:

FromPmxWhsCode: the code of the source warehouse●ToPmxWhsCode: the code of the destination warehouse●ItemCode: the item code of the product●Quantity: quantity to move or to make a move order from●Serialnumber: If the item is managed by serial numbers, add the serial number here.●SrcQualityStatusCode: the quality status of the stock that should be moved●DestQualityStatusCode: the quality status that the stock should get after the move●Batchnumber: If the item is managed by batches, add the batch number here.●InternalBatchnumber: If the item has a second batch number, add it here.●BestBeforeDate: If the item has a best before date, add it here.●SrcStorLocCode: the code of the source storage location●DestStorLocCode: the code of the destination storage location●SrcLogUnitIdentKey: the source LUID●DestLogUnitIdentKey: the destination LUID●

Note: The field names are case sensitive.

2. Save the file as a .csv file.

Naming convention: Use the PMX_MO_ prefix for move order templates and the PMX_MV_ prefix formove templates. The system checks the file name to determine whether a move order or a moveshould be created.

Example:

Move order: PMX_MO_07032012.csv●Move: PMX_MV_07032012.csv●

18.3.3.2. ASN template for importing

With the Interfacing Tool goods that are received against purchase orders or purchase invoices can beimported from CSV files to SAP B1. As a result of the import, the system generates open ASN lines,which you can use to create goods receipt PO documents.

To implement the import process, proceed as follows.

1. Prepare the CSV file with the 14 columns listed in the table below and provide the necessary data.Make sure that you list all the 14 columns, keep the column names and the order of the columns asindicated in the table.

Alternatively, the ASN template can be used, which is available in your installation folder (Templates●> Import Templates folder).

If you receive CSV files from your supplier and you define a CSV Custom Header, the order of the●columns in the CSV file depends on the order you define in the CSV Customer Header field (seeInterface for PMX advance shipping notice importer and exporter).

http://wiki.produmex.name/doku.php?id=implementation:wms:interfaceasn



Field name (casesensitive) Description/Activity

ObjTypeIn case of a purchase order the value of the field should be 22 while in caseof a purchase invoice it should be 18.Note: If no value is added to the field, the system automatically considers theobject type a purchase order.

DocNum Add the document number of the purchase order/purchase invoice.

LineNum andItemCode

It is not mandatory to provide a value for both fields. You can provide only theline number, which you can check in SAP B1. If you provide only the item code,the system uses this value to find the line number.Note: If the purchase order contains two or more lines with the same itemcode, the system cannot find the correct line number. In this case you need toprovide a value for the line number as well.

Quantity Add the inventory quantity of the item to be received. If you provide value tothe SerialNumber column, the value of the Quantity should be 1.SSCC Add the SSCC of the logistic unit if there is any.MasterSSCC Add the SSCC number of the master logistic unit if there is any.Batch If the item is managed by batches, add the batch number in this column.Batch2 Add the second batch number of the product if there is any.BBD Add the best before date of the product if there is any.SerialNumber Add the serial number of the product if there is any.UF1 User information - optionalUF2 User information - optionalUF3 User information - optional

Example of a CSV file:

ObjType;DocNum;LineNum;ItemCode;Quantity;SSCC;MasterSSCC;Batch;Batch2;BBD;SerialNumber;UF1;UF2;UF3;22;123;0;ITEM01;10;123456789012345678;;BATCHA;;20200131;;User info 1;;;22;123;1;SERIAL01;1;123456789012345678;;BATCHA;;20200131;SER01;User info1;;;22;123;1;SERIAL01;1;123456789012345678;;BATCHA;;20200131;SER02;User info1;;;

2. Save your CSV file to the folder defined in the Interface Monitor Input Path.

3. Run the Interfacing Tool.

4. You can check the imported data in SAP B1 by navigating to Produmex > Purchasing > ASN. Thesystem displays the Open ASN Lines screen (see 6.3.2. Open ASN lines).

5. Now you can create goods receipt PO documents from the open ASN Lines (see 28.6. ASNReception).

4. HANA Report Setting Tool

On MSSQL, the connection data is replaced dynamically when printing and there is no need to save

http://wiki.produmex.name/doku.php?id=implementation:wms:open_asn_lineshttp://wiki.produmex.name/doku.php?id=implementation:wms:asn_receptionhttp://wiki.produmex.name/doku.php?id=implementation:wms:asn_reception



the report with the actual connection data. In contrast, the connection data is not replaceddynamically on HANA and it is necessary to save the selected reports with the actual connection tothe right database and schema.

With the HANA Report Setting tool it is possible to modify the connection data for multiple reports byproceeding as follows.

1. Configuration

1.1. Run the Produmex.Sbo.Logex.Tools.HanaReportSettingTool.exe.

The file can be found in the Produmex Tools folder, for example: C:\ProgramFiles\Produmex\Produmex Tools.

Please note that the file is only installed during a HANA installation.

When the tool opens, the following fields are prefilled based on the configuration file of the tool(Produmex.Sbo.Logex.Tools.HanaReportSettingTool.exe.config):

Database sectionDB Server: the name of the database serverCompany DB: the name of the database used by SAP B1



1.2. Configure the 32 Bit section

32 bit OBCD Driver:When you open the tool, it automatically displays your 32-bit OBCD Driver set as default.

Folder of 32 bit RPT files:This is the source folder of the reports you want to modify and this is where the modified reports aresaved.The default setting for the source folder is C:\Produmex or C:\Produmex\Reports and if the defaultfolder contains RPT files, they are displayed in the Report Files grid.

If the source folder does not contain any RPT file, the grid is empty.

In case you want to change the setting, browse another folder.



1.3. Configure the 64 Bit section

64 Bit ODBC Driver:When you open the tool, it automatically displays your 64-bit OBCD Driver set as default.

Folder of 64 bit RPT files:This is where the modified, 64-bit reports are saved. By default, no folder is set.

In case you have a 64-bit HANA environment, create your new folder for the 64-bit reports, forexample C:\Produmex\Reports\Reports64bit, and browse it for the Folder of 64 bit RPT files field.

Make sure that you have two different folders for the 32-bit and for the 64-bit RPT files.



2. Saving reports with 32 bit and 64 bit

2.1. Saving reports with 32 bit

1. Copy the necessary reports from your installation folder (for example:C:\Install\Produmex_WMS_19_1.x64\Reports\HANA) into your 32-bit RPT file source folder.Now all the reports from your source folder are listed in the grid.

2. Select the necessary report files in the grid. \\You can select all of them by clicking the SelectAll button or select the necessary ones one by one.

3. Click Update Selected Reports to the New Connection Settings..

4. Now the tool starts modifying the reports into 32 bit versions. In the log window the process isdisplayed step by step:

The tool creates a new folder named OLD within your 32-bit RPT file source folder and saves a copy ofthe selected report files into the OLD folder.Then it overwrites the report files by modifying them into 32 bit versions. Once the process isfinished, you can find the 32 bit versions in your source folder.



5. The tool displays the successful actions per report on the Last Action column of the grid.

2.2. Saving reports with 64 bit

With this function the tool modifies the 32-bit RPT files into 64-bit versions.

In case you have a 64-bit HANA environment and you need 64-bit RPT files, proceed as follows.

1. Select the necessary 32-bit report files in the grid.

2. Click Copy and Update All reports with 64 bit ODBC.



The steps of the process is displayed in the grid.The tool starts to modify the 32-bit RPT files into 64-bit versions and saves them to your 64-bit RPTfiles folder.

3. Setting the report path in SAP B1

After modifying the reports, set the appropriate report path in SAP B1. In this way the system knowswhere to find the reports whenever you want to generate a new report in SAP B1.

1. Open your organization structure and select the Reports tab.

2. Provide the path of your 32-bit RPT files folder or your 64-bit RPT files folder in the Report path



field.

3. Click OK.

5. Generate Documentation Tool

Use the ’Generate documentation’ tool to export the structure of Produmex related database tables,indexes and user defined fields into a html file.

Go to the installation folder: Produmex > Produmex Tools and run theProdumex.Sbo.Logex.Tools.GenerateDocs.exe file. Make sure that you run it in Administrator mode.

Check the connection string on the screen and adjust it if necessary in the configuration file of thetool: Produmex.Sbo.Logex.Tools.GenerateDocs.exe.config.



Click on the ’SAP tables doc’ button to start the export.

The tool exports the following:

If a table name contains the ’PMX_’ or the ’@PMX_’ prefix, but does not contain the ’PMX_ADDON’1.alias, then the tool exports the following for that table:

table name❍column name❍data type❍character maximum length❍numeric precision❍numeric scale❍is nullable value (Y/N)❍column default value❍primary key❍

If the name of a database index contains the ’PMX_’ prefix, the tool exports the following for that2.index:

table name❍index name❍type description❍is primary key value (Y/N)❍is unique value (Y/N)❍is unique constraint (Y/N)❍key ordinal❍column name❍is included column (Y/N)❍

If the name of a user defined field contains the ’PMX_’ prefix, the tool exports the following for that3.user defined field:

table name❍column name❍data type❍is nullable value (Y/N)❍character maximum length❍numeric precision❍numeric scale❍description❍



type ID❍edit type❍edit size❍default value❍index ID❍field value❍field value description❍

The html file is exported to the folder of the Generate Doc tool.

6. Sales Delivery Tool

The Sales Delivery Tool creates SBO Sales Deliveries from PMX Sales Shipping documents. When thetool is started, it processes all deliveries that needs to be processed when it was started, then exists.The Sales delivery tool only runs once.Please note: The SBO Sales Delivery is only created if the items on the PMX Sales Shipping documentcan be shipped.

It is recommended to run the tool as a scheduled task.

The tool is located in the Produmex Tools folder. Before running the tool, make sure that an extensionis set for Create SAP delivery from PMX delivery controller.

With default settings, the tool only processes PMX Sales Shipping documents that were created within7 days from the company that has the „SboConnectionString” connection string in the app config fileof the sales delivery tool.

The name of the config file is Produmex.Sbo.Logex.Tools.SalesDeliveryTool.exe.config.

In order to run the sales delivery tool with different conditions, run it from a batch file. The followingparameters are supported:

/NumberOfDays: or /d: A number of days to go back in time to get possible items to deliver.●/ConnectionStringName: or /cs: A string that identifies the name of the connecting string in●app.config file to use.

Example batch fileIn order to process the PMX Sales Shipping documents from the last two weeks, run the Sales deliverytool with the following parameters:

Produmex.Sbo.Logex.Tools.SalesDeliveryTool.exe /d:14 /cs:SboConnectionString

7. Robot Tool

The Robot Tool is an executable tool that is started with command line parameters.

The command line parameters indicate the specific functionality that needs to be executed. If the/RobotType or /t parameter is not passed, the system defaults to PickListRobot.

http://wiki.produmex.name/doku.php?id=implementation:wms:createsapdeliveryfrompmxcontroller



Example 1If you pass command line /? all possible command line parameters will be displayed togetherwith a description.

Produmex.Sbo.Logex.Tools.Robot.exe /?

Example 2To run the Minimim Stock Level tool you need to execute:

Produmex.Sbo.Logex.Tools.Robot.exe /t:customerminimumstock

To run the Minimim Stock Level tool for a specific database you need to execute:

Produmex.Sbo.Logex.Tools.Robot.exe /t:customerminimumstock /cs:SboConnectionStringTest

http://wiki.produmex.name/lib/exe/detail.php?id=implementation%3Awms%3Atools_complete&media=implementation:wms:tools:robot_tool.pnghttp://wiki.produmex.name/doku.php?id=implementation:wms:reserve_stockhttp://wiki.produmex.name/doku.php?id=implementation:wms:reserve_stock



From:http://wiki.produmex.name/ -

Permanent link:http://wiki.produmex.name/doku.php?id=implementation:wms:tools_complete

Last update: 2019/12/11 13:03

http://wiki.produmex.name/http://wiki.produmex.name/doku.php?id=implementation:wms:tools_complete

Produmex WMS - Complete Tools Guide1. Import Tool1. Import via files1.1. Preparation1.1.1. Zone1.1.2. Bin1.1.3. BinItem1.1.4. Customer Shelf life1.1.5. Item zonetypes1.1.6. Packaging types1.1.7. Item Batch Attributes1.1.8. Box Type For WAS1.1.9. Box For WAS1.1.10. Route Header1.1.11. Route Line1.1.12. Location PutAwayZones1.1.13. Item allergen1.1.14. Item – Card Code/Quality status1.1.15. Item-Warehouse-Location or Zone1.1.16. Organizational Structure settings

1.2. Import tool1.2.1. General import1.2.2. Import OSE objects (.csv)1.2.3. Import Route Templates1.2.4. Import Put away zones

2. Copy data2.1. Select the source and destination database2.2. Copy OSE2.3. Copy Stock

2. Import Initial Stock Tool3. Interfacing Tool18.1. Configuration18.1.1. Define the path18.1.2. Set up the interfacing controller

18.3.1. Preparing documents for import18.3.2. Running the Interfacing tool18.3.3. Templates for importing18.3.3.1. Move and move order template for importing18.3.3.2. ASN template for importing

4. HANA Report Setting Tool1. Configuration2. Saving reports with 32 bit and 64 bit2.1. Saving reports with 32 bit2.2. Saving reports with 64 bit

3. Setting the report path in SAP B1

5. Generate Documentation Tool6. Sales Delivery Tool7. Robot Tool

produmex wms - complete tools guidewiki.produmex.name/lib/exe/fetch.php?media=... · 2020. 12....

Documents