1. produmex wms for sap business onewiki.produmex.name/lib/exe/fetch.php?media=... · 3. extensions...

2018/06/19 21:42 1/255 1. Produmex WMS for SAP Business One

- http://wiki.produmex.name/

1. Produmex WMS for SAP Business One

Introduction

Produmex WMS for SAP Business One extends the standard functionality of SAP Business One withfunctions to support shopfloor operations in the area of production, packaging, inventorymanagement and logistics (inbound, picking, shipping). Produmex WMS consists of 3 parts:

1. Extensions of existing SAP Business One functions (e.g. article, users, …)

2. An administrative Produmex module offering new office functions for defining e.g. theorganizational structure of a company, the creation of inventory reports, definition and planning ofdelivery routes, the creation of step lists for production and packaging, the creation of picklists, etc.

3. Finally Produmex WMS offers functions to support the shopfloor operations. These functions aremade available on the shopfloor through “thin clients”. This includes touchscreens, handheldterminals, … through which the operators can execute the production, packaging and logisticsoperations and transfer the required information transparently to SAP Business One. Produmex WMSalso provides connections to data capture (barcode) and print devices (label and document printers).

http://wiki.produmex.name/lib/exe/detail.php?id=implementation%3Awms%3Aconfguide_complete&media=implementation:confguide:introduction:pdmx_salesflow.png



http://wiki.produmex.name/lib/exe/detail.php?id=implementation%3Awms%3Aconfguide_complete&media=implementation:confguide:introduction:devicechain.png





Last update:2018/03/1212:56

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

http://wiki.produmex.name/ Printed on 2018/06/19 21:42

2. Terminology

LUID = Logistic Unit IDBBD = Best Before DateITRI = Item Transactional Information Key. This is a key used to identify a batch, batchnumber 2, BBDOSE = Organizational structure element. Element used to define the structure in the company.(Example: Bin, Warehouse, Printer, …)UDT = User defined tableUDF = User defined fieldATP = Available to promisePocketSize = The small screen layout, used on a scanner.TouchScreen = The large screen layout, used on touch screens.PRD = Production OrderDB = DatabaseBOM = Bill of materialWAS = Warehouse automation systemWA = Warehouse automationClient = A device (Scanner or touchscreen)Device = A scanner or touchscreenAI = GS1 Application Identifier

3. Extensions of SAP Business One

Produmex WMS extends SAP Business One’s standard functions with a number of concepts that areimportant for the operational management of items, including Best Before Date, location code, ….



Apart from this Produmex WMS also adds a number of specific parameters to standard SAP BusinessOne functions, which have to be set to ensure the proper functioning of Produmex WMS.

It is recommended to avoid the asterisk (*), pipe (|) and apostrophe (’) characters in Produmex orSBO master data because these characters have a special role in Produmex products.

3.1. Item Master Data

3.1.1. Item Master Data Main Screen

Bar CodeBar code is an existing field in SAP Business One. Produmex instead of Produmex offers users thepossibility to choose the type of barcode:

GTIN-14 (GS1 Global Trade Item number)●

The system verifies whether this is a correct bar code (according to the GS1 rules).❍

GTIN-Variable●

This is also a GTIN-14 barcode, but with a part of the barcode that holds information about a❍

certain value (Weight, price, …)This kind of barcode is used nationally and not internationally. This means some additional❍

configuration needs to be added so it is possible to know what part of the barcode is variable,and what that values represents. This configuration is done in a UDT called PMX_VGTC.

Last update:2018/03/1212:56



The barcode that needs to be stored should only be the fixed part of the variable barcode,❍

without the checkdigit.Free barcode.●

No restrictions on format❍

On the scanner it will be possible to scan an EAN 13. The system will convert it to a GTIN, and checkthat GTIN against the barcode on the item master data. So if you have valid EAN 13 barcodes, itshould be stored in the system as a GTIN, with a leading 0 in front of the EAN 13.

Has PMX serial numberIn SAP Business One an item can be managed by batches OR serial numbers. Produmex also allows tomanage an item both by batches AND serial numbers.

Track location of serial numbersIf this is checked Produmex will keep track of the location of items with serial numbers (both SAPserial numbers as well as Produmex serial numbers). The system does this, by forcing the stock to beon an SSCC. The serial number is linked to that SSCC.

Serial number formatSpecifies the serial number format as a regular expression. The available formats will have to bespecified in the User Defined Table (default form) “PMX_ISFT” (Produmex Item Serial Number Format).

3.1.2 Item Master Data – Inventory tab

There are some columns added on this inventory grid:

PMX Free stockThis is the free stock that is available for Produmex. This is the sum of the quantity in inventory minusthe sum of the quantity that is locked.(SUM(PMX_INVT.Quantity) – SUM(PMX_INLD.Quantity))

The UOM2 columns will only be filled in when there is a UOM2 defined.

Uom2 qty warehouseThis is the quantity for the second UOM that is in stock. In case it is a catch weight item, this will bethe actual weight. If it is an item with a UOM2, but no catch weight, this will be the calculation ofUOM2 based on the default ratio between both UOM.

Uom2 qty confirmedThis is the quantity for the second UOM that is commited. The calculation of UOM2 based on thedefault ratio between both UOM.

Uom2 qty Ordered



This is the quantity for the second UOM that is ordered. The calculation of UOM2 based on the defaultratio between both UOM.

Uom2 qty availableThis is the quantity for the second UOM that is available. The calculation is: (In stock + Ordered) -Confirmed

3.1.3. Produmex Item Master Data Tabs

Under the Inventory function → Item Master Data, a special Produmex tab has been added whichcontains a number of fields that are not available in standard SAP Business One.

3.1.3.1. Inventory

Inventory UOMInventory UoM is an existing SAP Business One field, with a formatted search on the SAP OUOM table.This table contains all the defined UoM’s.

Number of Decimals for uom1This field indicates the number of decimals for the first UoM. This is used in flows when entering aquantity.

Uom 2Uom2 identifies the second UoM for the item.

Last update:2018/03/1212:56



1 uom 2 =If a second UoM is defined, the conversion rate between the two UoM’s is entered in this field.

Has best before dateIf the item has a best before date, this field has to be ticked.

Has second batch numberDefines whether the item has a second batch number.

Default quantity on logistic unitDefines whether the item has a default quantity on a logistic unit.Is used for:

Splitting a proposal in full pallets/item picking●

Cycle count flows: When configured to propose default quantity, this field is used●

Bulk receiving●

Bulk shipping●

Production: Splitting produced quantity●

Reception: Default quantity when entering quantity●

Reception: When configured to split quantity into multiple logistic units, this is the quantity of a●

logistic unit

Item storage location typeDefines the item storage location type.The list is retrieved from the UDT PMX_ISLT?This is used in the Location suggestions functionality.

Is logistic carrierThis field has to be ticked if the item in question is a logistic carrier (pallet, europallet, container, …).An item can be a logistic carrier as well as a returnable item, e.g a europallet.

Is logistic unit (GS1)A logistic unit is an individual unit that has been composed for transport and/or storage and have tobe manageable throughout the supply chain. These items are identified by means of the ApplicationIdentifier 01 in the GS1 standard.

Has no valueOnly applies to logistic carriers. If this is checked, the system will allow to deliver the logistic carrierfree of charge to the customer during ad hoc picking – customer collect.

Standard location/zoneHere a default location or zone can be specified for an item. This will be shown as information on thehandheld.

Report label keyThe identification of the label that belongs to a specific item.

Report label number of copiesThe number of labels that have to be printed for a specific item.

Ask for quantity on item label printingIf checked the system will ask to enter a quantity. This entered quantity is passed to the label. This



can be used for instance to put the weight on the label.

Item label printing by packaging typeIf checked the system will print item labels based on packaging types. When item labels need to beprinted, the user can enter the number of labels by each packaging type + inventory uom. On theProdumex Attributes tab it is possible to set a specific report for each packaging type. Also thenumber of copies can be set there.If the global option on Company for automatic printing of item labels during goods receipt is set totrue, and the option for printing item labels by packaging type is set to true, the system will print thelabel for the packaging type linked to the purchase order, of purchase uom in case of receivingwithout PO.

Seveso class (Hazmat in North America)Defines the seveso class the item belongs to. Based on the Seveso class, Produmex will check thequantity of the item that can be ordered (maximum inventory). An order for a quantity that willexceed the maximum allowed inventory will show a warning. Receiving the goods will be prevented.Configuration is done in user defined table: PMX_SEVE

Use in WA functionalityEnable this option to use this item for the WA functionality.

Is returnable itemThis field is checked if the item in question is a “returnable item” (“empties”).

Non-inventory returnable item codeThis field contains the item code of the non-inventory returnable item. This code is used for thedelivery and receipt of returnable items (“empties”) and is one-to-one coupled with the inventory itemcode of the same returnable item. (This is configurable on the organizational structure on the‘General’ tab of the company)

Force serial numbers during cycle count?When this option enabled for an item with PMX serial numbers and track location enabled, then serialnumbers must be entered during cycle counting operations. Otherwise, it's also possible to just enterthe counted quantity.Note: This option has no effect on SAP serial numbered items.

Zone type codeApart from indicating a standard location or zone, the user can also specify the zone type code. Ifsuch a code is entered, the system verifies upon storing an item whether it can be stored in this zoneand prevents the item from being stored in a different zone. This can be used for instance if a productneeds to be ‘cooled’. If the product has this zone type, it can only be stored on location within a zonethat is also ‘cooled’

3.1.3.2. Sales

Last update:2018/03/1212:56



Shelf life deliveryThis field specifies the minimum remaining shelf life in days of an item (article) from the moment it isoutside the responsibility of the manufacturer/distributor (external shelf life), i.e. the actual periodthat the product is physically present at the customer and can be sold to the end customer. Theexternal shelf life is defined by the Best Before Date and means that the product will need to staygood at the retailer for at least a specified number of days before the “Best Before Date”. Toguarantee that a product can be sold long enough, the retailer usually requires a minimal externalshelf life from the manufacturer/distributor of the product.

Pick typeWill define how an item will be handled during pick list generation and picking. The list of item picktypes is defined on the User Defined table “PMX_IPIT”. If an item is a of a certain pick type (e.g.’Handle with care’) and it is indicated on the Produmex Pick List Type (User Defined Table“PMX_PITY”) that a pick list should be split based on the item pick type, this item will not be added topick list with items of another pick type (e.g. slow mover). In this case two pick lists will be generated.On the UDT “PMX_UIPT” users can be linked to certain item pick types. If such a configuration exists,the system will only allow the user to pick items that he is allowed to pick. This option is used in the‘Zone picking’ option on the scanner.

Pick type 2Apart from the primary pick type, an item can also have a second pick type. The list of item pick typesis defined on the User Defined table “PMX_IPIT”. If it is indicated on the Produmex Pick List Type (UserDefined Table “PMX_PITY”) that a pick list should be split based on item “pick type 2” the system willgenerate separate pick lists based on this criterion, if applicable in combination with the first picktype. The configuration for linking it to a user is also available for item pick type 2.

Bulk pick quantity



The quantity (lower or equal than a full logistic unit) for which the system will also allow to pick from abulk location. This is used on stock allocation to a pick list, when it is selected on the scanner.Configuration on the PickListController needs to allow picking from bulk. Example: If bulk quantity =10 and on the sales order you need 24 items, 20 pieces can be picked from bulk, and 4 from picklocation.

Enter reason for sales returnIndicates whether a reason has to be specified when a sold item is returned.

Print label during pickingSet whether item labels need to be printed during picking for this item.

Replenishment: quantity on pick locationsThe quantity of that item that should be available on pick locations. Based on the parameters that areset in the “Item-based replenishment generator” the system will check whether there are picklocations with this item where there is a lower quantity than the needed quantity and will replenishthese. In the “item-based replenishment generator” it can be specified whether or not the system hasto take into account open pick lists, pick lists for a specific due date range, or required quantities for aspecific stock coverage period (based on the estimated sales quantity by month)

Estimated sales quantity by monthEstimated sales quantity to be sold by month (1 month = 30 days), to be used for stock coveragecalculations. Used by the “Item-based replenishment generator”.

Default quality status for sales returnIndicates the default quality status of a sold item that is returned. The standard possibilities are:blocked, quarantine, released, rejected, returned. This overrides the general definition of the qualitystatus for sales return.

Allow multiple batches on sales doc.Indicates whether it is allowed on a sales document to have multiple batches of an item in one line(e.g. ordered quantity cannot be fulfilled by a single batch of a product). This is for information only.

Allow stock to be locked in advanceWhen this option is set to true, this item can be used for locking in advance. This means it will bepossible to lock the stock for certain customer(s) at the moment the stock is received.(Purchase/production/inventory receipt, warehouse transfer)

Smallest sellable packaging typeIndicates the smallest packaging type of the item that can be sold. This is for information only.

Default log. car. pickingThe default logistic carrier that is used for the product (e.g. a CHEP or a EURO pallet, …) on thepicking process. This is for information only.

Scan base componentIn case items are shipped in a special container (e.g. a crate), it can be indicated that the basecomponent needs to be scanned, instead of scanning the container with the items (the crate as awhole). So a single item in the crate has to be scanned to make sure that the crate is sent containingthe right items.This is used in the Picking flow on the scanner. It uses a BOM to check the base component.

Packing remarks

Last update:2018/03/1212:56



Specific remarks for packing the item in question which is shown on the RF terminal or touchscreenwhen handling the item.

Packing imageImage of the specific packing of the item in question (e.g. picture of the kit). This image is shownduring Packing and Consolidated packing flow.

Sales remarks pop-upIf checked, the system will show the sales remarks that are specified for the product when selectingthe product on a sales document.

Sales remarksSpecific remarks that are shown in SAP Business One when creating a sales order for this item.

Add non-inventory item to pick listIf some non-inventory items need to be on the pick list, this option can be checked. When creating apick list/proposal, the system will add this item to the pick list/proposal.This option can only be set for items that are configured to be non-inventory items.This item can be picked/packed on the scanner/touchscreen. Only the quantity will be asked as this isa non-inventory item.When the pick list has 10 pieces to pick, and the user only enters 8, the system will register this 8pieces, but the 2 additional pieces will automatically be skipped, so they will not be picked.

Grid: Shelf life by customer and countryProdumex also offers the possibility to define a shelf life per individual customer and/or countries,apart from the general shelf life. This is then taken into account when picking goods (i.e. some goodsmay still be picked for certain customers or countries, but not for others).You can enter a shelf life for either just a customer, or just a country, or a combination of both acustomer and a country.

3.1.3.3. Purchase



Shelf life receptionThe minimum number of days a product will have to remain sellable from the moment the systemreceives the product into inventory (prior to the product’s expiry date).

Enter reason for purchase returnIndicates whether a reason has to be specified when returning a purchased item.

Default quality status for receptionThis is the default quality status when receiving the item in question.

Released quality status for receptionThe released quality status for reception. This is only used for the ‘Quality status for reception bybatch’ controller. When the system receives a quantity of this item of a certain batch, the system willcheck whether there is already a specific quantity of the same batch available with the “releasedquality status”. If there is such a quantity available, the system will overrule the default quality statusand assign the released quality status to the received item.

Expiry def. for receptionAllows to specify the expiry definition for reception as defined in the User Defined Table “PMX_EXDE”– Expiry Definitions

Purchase barcode typeIf the purchase barcode differs from the main barcode, the type of this barcode can be filled in. Thepossible values are: GTIN-14 (GS1 Global Trade Item Number) or a free code. If the user enters aGTIN-14 code, the system verifies whether this is a correct barcode (according to the GS1 rules).

Purchase barcodeContains the purchase barcode if it is different from the main barcode.

Last update:2018/03/1212:56



Create SSCC on receptionIf checked the system will automatically generate an SSCC on reception if no SSCC was scanned. Ifunchecked, no SSCC will be created and stock can be manipulated without reference to the SSCC.If multiple items are received, and at least one of them requires an SSCC, the system will create one.If no SSCC is created at reception, no put away order will be generated. Items need to be movedthrough ad hoc movement.If the items is configured as a serial number, with track location on, this setting needs to be ticked.

Print label at receptionSet whether item labels need to be printed at reception for this item.

Sample quantityDefines the quantity (in inventory uom) of the sample that should be sent back for inspection. Thesample generator will use this quantity to generate the sample order (Sales order). The generation ofthe actual sample order is done through the SboNotificationListener.

Weight capture from scale neededSet whether the item must be weighed during the reception or not.

Purchase remarks pop-upIs set to true, the text in the purchase remarks is shown as a pop-up when using this item in apurchase document in SAP.

Purchase remarksThe purchase remarks to be shown when selecting the item in a purchase document in SAP.

Grid: Released quality status reception by supplierProdumex offers the possibility to define a default quality status on reception per supplier. Enter thesupplier card code and select the quality status from the dropdown list.

This option is used in the ‘Reception’ and the ‘Receive from WHS’ flows if the QS reception controlleron company is set to the ‘Gets the quality status for reception’ extension.

3.1.3.4. Production



Default quality status for productionThis is the quality status the stock will get when producing new stock. This overrules the generalsetting.

Default log. car. ProductionThis is the default logistic carrier for production. If this is set, the system will automatically use thatlogistic carrier to put the stock on.

Expiry def for productionAllows to specify the expiry definition for production as defined in the UDT “PMX_EXDE” – ExpiryDefinitions

Auto line up selectionDoes this item need to be automatically lined up? If set to true, the system will automatically line upthe location, instead of letting the user select it. This option is used in combination with theproduction manager.

Lined up locations are sorted by location name.

Additional pick for production (%)When picking for production without a pick list, the system will propose to pick more thantheoretically needed for the production order.

Allowed production deviation (%)The allowed deviation of the produced quantity. This is used in combination with the setting ‘Confirmproduced quantity after production’ on the production controller. It will check if the deviation isallowed, based on the default quantity to produce. If it is not allowed, a warning is shown on the flow.

Default production quantity

Last update:2018/03/1212:56



This is the default quantity on a produced logistic unit. This setting is used in combination with the‘Split produced quantity into logistic units of default size’ setting on the ProductionController.

Use for time registrationIndicates if the item is used as a time registration type that can be added to a Bill of Material and aproduction order. The quantity is in hours.

Production remarksHere production remarks for the item. This is for information only.

3.1.3.5. Catch weight

Catch weight item?Indicates if the item is a catch weight item.

GS1 AI for uomThe GS1 application identifier to capture the quantity for pieces. Possible values:

37 (Count)●

31 (Net weight Kilo)●

32 (Net weight Pound)●

GS1 AI for uom2The GS1 application identifier to capture the quantity for the weight. Possible values:

37 (Count)●

31 (Net weight Kilo)●

32 (Net weight Pound)●

1 uom = xxx uom 2The weight of 1 piece.

Weight tolerance (%)The weight tolerance in percentage. Here it can be defined what the allowed tolerance for the weightis. If the tolerance >= 100, no tolerance check will be done. This check will be used for all documentsexcept: goods issue and goods receipts. Calculation:( Pieces * Default weight of 1 piece ) -( Pieces * Default weight of 1 piece ) * Weight tolerance/100< Allowed weight <( Pieces * Default weight of 1 piece ) +( Pieces * Default weight of 1 piece ) * Weight tolerance/100

Uom to use for purchaseThe uom that should be asked when receiving items.Possible values:

Pieces (UOM1): The weight is calculated based on the weight of 1 piece.●

Weight (UOM2): The number of pieces are calculated based on the weight of 1 piece.●

Pieces and weight●



Uom to use for inventoryThe uom that should be asked when moving items.Possible values:




Uom to use for sales The uom that should be asked when delivering items.Possible values:




Price calculation for salesThe calculation of the price for creating a sales delivery.Possible values:

Price by piece: This option is the default option. In this case no price calculation is done because the●

price from SAP is already by piecePrice by weight: The calculation of the price is done by weight.●

Price by weightWhen a sales delivery/reserve invoice is generated, the price will need to be set when:

The item is a catch weight item●

The option for price calculation is set to 'Price by weight'●

The base document is NOT an invoice●

Delivery is made through Produmex functionality●

The unit price before discount will be adjusted. The default unit price is based on the default weight ofa catch weight item. So a recalculation based on the actual delivered weight needs to be done.

The calculation formula is: Unit price before discount = (Unit price before discount sales order /Default weight by piece) * Actual weight) / Quantity

Database columns: DLN1.PriceBefDi = ( RDR1.PriceBefDi / OITM.U_PMX_DQUM) * DLN1.U_PMX_QTY2 )+ DLN1.Quantity

Example:

ItemA* Inventory uom = Case* Weight uom = Pounds* 1 Case = 24 pounds (U_PMX_DQUM = 24)* Price per case = 48$ (= 2$ / pound)

Sales order* 20 cases* Unit price = 48$* Total price = 960$

Last update:2018/03/1212:56



When we deliver the 20 cases the actual weight = 500 pound (Nominal weight was 480 pound)The calculation is as follows:

(Unit price sales order / Default weight by piece) * Actual weight) / Quantity = Unit price (48$/24pounds) * 500 pounds) / 20 cases = 50$Total price of the delivery line will be 1000$This means if you deliver 500 pounds, this is 2$ by pound.

Scan weight for each caseWhen this is enabled, when scanning/entering the weight in the device, the system will notautomatically calculate the number of pieces that would be associated with the weight, but it will usethe # pieces in a case.So on the first entry of the weight, the user can either enter the total weight for all pieces.Flow:

Check if scanned weight is within tolerance of the # pieces in case●

Yes: Use the pieces and weight, and ask for next weight●

No:●

Check if the scanned weight is within tolerance of the needed number of pieces❍

Yes: Use the needed number of pieces, and total weight❍

No: Error is shown that weight is not within tolerance❍

# pieces in caseThis is used in combination with the setting 'Scan weight for each case'. It stored the number ofpieces in a case.

Record weight details during pickingWhen this is enabled, the entered weight during picking on a device will be stored in a separate table:PMX_WDET.It stores the pick list doc entry, item and batch details.This allows to retrieve the detailed weight entry for an item on a pick list.

3.1.3.6. Attributes

Packaging typeShows the packaging type of the item. If the UoM Group of the item is set to manual, the user candefine here a specific packaging type based on the SAP OUOM Table. If the item is linked to a definedUoM Group, the system will apply the packaging type specified therein.

Packaging type codeThe packaging type code.

Number of UOM 1The quantity in the packaging, in inventory uom.

Has variable quantity (Goods entry)?If the quantity for the packaging type can change on each goods entry, this option can be set to true.If the item is batch controlled, the system will ask during goods entry what the quantity in the currentpackaging type is. This information will be stored, linked to the batch information.



Hide during entering quantityWhen this option is set, that packaging type is not shown to the user when he needs to enter thequantity.

Item label reportThe specific report that needs to be printed when the option ‘Item label printing by packaging type’ isset to true. When a report is selected, the number of copies need to be more than 0.

# Copies item labelThe number of copies that need to be printed in case of option ‘Item label printing by packaging type’is set to true. If this is set to 0, no item labels will be printed for that packaging type.

Batch attributesIf an item has a batch, batch2 or BBD, the system can ask for batch attributes during reception andproduction.When a new combination of batch, batch2 or BBD is entered, the system will ask for the batchattributes linked to the item.

The data will be stored into the table PMX_ITBA.There are some predefined batch attribute types. Those batch attributes will be stored also on thetable PMX_ITRI.

Batch attribute codeThis is a list of batch attribute types defined in the UDT @PMX_BATT

Value entry option at receptionThis will set whether he 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.●

Is linked to batch?When this option is set to true, this batch attribute will be linked to the batch number.This means when a new combination of batch/batch2/BBD is created, and the batch number alreadyexists in the system for this item, the batch attribute is not asked to the user, but the value is copied.

AllergensThis grid stores all the allergens the item can have.

Allergen codeThis is a list of allergens defined in the UDT @PMX_ALLE

Can contain allergen?If this product does not contain the allergen by default, but it is possible that some trace of thisallergen could be present, this option can be checked.

3.1.3.7. 3PL

3PL inbound price

Last update:2018/03/1212:56



Defines the price to invoice 3PL partners for each received unit (in inventory UoM) of that item.

3PL outbound priceDefines the price to invoice 3PL partners for each delivered unit (in inventory UoM) of that item.

3.2. Administration

The Administration module of SAP Business one allows to define important general settings to ensurethe proper functioning of the system. Produmex WMS adds specific settings to these in the field ofauthorizations and users.

3.2.1. Authorizations

General authorizations for Produmex WMS

At the user level it is possible to define the authorizations for the various functions of Produmex WMS.An authorized user can define the rights of the individual users. In order to do this selectAdministration → System Initialization → Authorizations → General Authorizations.



An authorized user can then set the user authorization for Produmex WMS as a whole or for thevarious parts of it. The authorization levels are:

Full Authorization●

Read Authorization●

No Authorization●

The various aspects to which the authorization levels apply are:

Organization structure●

Print reception logistic unit reports●

Inventory reports selection criteria●

Inventory report detail●

Change quality status●

Route templates●

Route generation●

Route detail●

Picklist proposal generation●

Generated Picklist proposal detail●

Picklist proposal detail●

Picklist detail●

Open documents●

Move●

Production order step list●

Last update:2018/03/1212:56



Tracking Tracing Search●

Route planning customer details●

Production step list●

Open Sales Orders●

Audit trail search●

Audit trail●

Interface monitor●

Production manager●

Cycle count select location●

Cycle count processing●

Adjust packaging quantity●

Adjust manual locking●

Move order●

Manual interfacing●

Container●

Advance inventory locking●

Print SSCC●

Change BBD on batch●

Change Batch2 on batch●

3.2.2. Users

Additional setting for users

It is possible to set the language in which the “thin client” application runs for each individual users.●

To do this select Administration → Setup → General → Users. A user-defined field “Language” hasbeen added there to allow you to set the language code for the user in question. This language isused on the scanner/touchscreen when the user has logged on.It is also possible to assign a user to a PMX User Group. The available authorizations are defined in●

the UDT “PMX_UAUT” (User Authorizations Definitions Table) and can be linked to the PMX UserGroups (UDT “PMX_USGR”) through the UDT “PMX_UGAU” (Link Usergroup To Authorizations Table).



3.2.3. User defined tables

User defined tables data can be entered through: SAP Tools → Default forms

3.2.3.1. Shipping quality option (PMX_SQOP)

This lists the options for shipping quality.

The values are:

CAN_USE_SUQ: All quality statuses that ‘Can be shipped’ and ‘Can be shipped under quarantine’ are●

allowed.MUST_USE_SUQ: Only quality statuses that ‘Can be shipped under quarantine’ are allowed.●

RELEASED: Only quality statuses that ‘Can be shipped’ are allowed.●

It is allowed to delete an option if this is not needed. But changes to the code are not allowed.This is used on an SAP document line UDF (Shipping quality option) in combination with the pick list

Last update:2018/03/1212:56



proposal creation.

3.2.3.2. Produmex pick list types (PMX_PLTY)

Pick list types are used on proposals and pick lists.On a business partner there is also a default pick list type.On a sales order/sales reserve invoice/warehouse transfer request a pick list type can be defined.

When creating a proposal, the system will set the pick list type in this order:

Pick list type on document●

Pick list type on business partner (Only for sales proposals)●

Default pick list type●

Configuration:

CodeThe code.

NameThe name.

Split PL on item pick type?When this is true, several pick list proposals can be created, grouping items with the same item picktype.

Split PL on item pick type 2?When this is true, several pick list proposals can be created, grouping items with the same item picktype 2.

Ask weight?When this is true, the weight of the (master) logistic unit will be asked when the logistic unit isfinished. The data will be stored on the PMX_LUID table. The unit of measure is the Default WeightUoM set on the Display tab of General Settings.

Ask length?When this is true, the length of the (master) logistic unit will be asked when the logistic unit isfinished. The data will be stored on the PMX_LUID table. The unit of measure is the Default LengthUoM set on the Display tab of General Settings.

Ask width?When this is true, the width of the (master) logistic unit will be asked when the logistic unit is finished.The data will be stored on the PMX_LUID table. The unit of measure is the Default Length UoM set onthe Display tab of General Settings.

Ask height?When this is true, the height of the (master) logistic unit will be asked when the logistic unit isfinished. The data will be stored on the PMX_LUID table. The unit of measure is the Default LengthUoM set on the Display tab of General Settings.



Full pallet pick list typeWhen this is set, the proposal that is created will be split up between full quantity (This is a multiple ofthe default quantity defined on the item master data) and partial quantity (Item pick). The proposalcreated for the full pallet will have this pick list type.

Item pick pick list typeWhen this is set, the proposal that is created will be split up between full quantity (This is a multiple ofthe default quantity defined on the item master data) and partial quantity (Item pick). The proposalcreated for the item pick will have this pick list type.

Always status picked?When this is true, the pick list line status after picking will always be ‘Picked’. This means that whenyou pick without a moveable location, the status will not be ‘Packed’. Pick lists with a type that havethis setting, need to go through the ‘Consolidated packing flow’. If any pick list within the same wavehas this option, all pickings will follow this setting.

Use for production?When this is true, the pick list can be used for pick lists of type ‘Production’. When this is false, thepick list type can be used for shipping and warehouse transfer.

Use for picking?When this is true, the pick list can be used in the picking flow.At least 1 of the pick lists in the flow needs to have a pick list type with this flag enabled.

Use for ad hoc picking?When this is true, the pick list can be used in the ad hoc picking flow.

Use for zone picking?When this is true, the pick list can be used in the zone picking flow.At least 1 of the pick lists in the flow needs to have a pick list type with this flag enabled.

Use for multi picking?When this is true, the pick list can be used in the multi picking flow.

Number of palletsThis defines the number of pallets that can be added to a pick list proposal.When the value is higher than 0, the proposals will be split during creation.The splitting will be done based on the setting on the item master data for the default quantity on alogistic unit. (OITM.U_PMX_DQLU)The system will calculate a fill rate of the proposal line, based on this setting. The fill rate of theproposal lines can go up to the defined number of pallets.In case the default quantity on a logistic unit on the item master data is not set (=0), the fill rate ofthat proposal line will be 0.

Ask weight Sub SSCC?When this is true, the weight of the logistic unit will be asked when the sub logistic unit is finished.The data will be stored on the PMX_LUID table. The unit of measure is the Default Weight UoM set onthe Display tab of General Settings.

Ask length Sub SSCC?When this is true, the length of the logistic unit will be asked when the sub logistic unit is finished. Thedata will be stored on the PMX_LUID table. The unit of measure is the Default Length UoM set on the

Last update:2018/03/1212:56



Display tab of General Settings.

Ask width Sub SSCC?When this is true, the width of the logistic unit will be asked when the sub logistic unit is finished. Thedata will be stored on the PMX_LUID table. The unit of measure is the Default Length UoM set on theDisplay tab of General Settings.

Ask height Sub SSCC?When this is true, the height of the logistic unit will be asked when the sub logistic unit is finished. Thedata will be stored on the PMX_LUID table. The unit of measure is the Default Length UoM set on theDisplay tab of General Settings.

3.2.3.3. Produmex item pick types (PMX_IPIT)

This lists the possible item pick types. This is used on the item master data on fields ‘Item pick type’and ‘Item pick type 2’.This is only used in the ‘Zone Picking’ flow.

Configuration:

CodeThe code.

NameThe name.

3.2.3.4. Produmex user item pick types (PMX_UIPT)

This table is to configure the item pick types a user can pick. If the user is not present in the list, he isallowed to pick all items. If the user is present in the list, he can only pick items with item pick typesdefined in the table.This is only used in the ‘Zone Picking’ flow.

Configuration:

CodeThe code.

User codeThe code of the user.

Item pick typeThe item pick type. The item pick type can be selected from a list. The list comes from the ‘ProdumexItem pick types’ UDT.

Item pick type property



The property on the item master data the current line refers to. Possible values:

ItemPickType1: The item pick type on item master data.●

ItemPickType2: The item pick type 2 on item master data.●

3.2.3.5. Produmex user pick list types (PMX_UPLT)

This table is to configure the pick list types a user can pick. If the user is not present in the list, he isallowed to pick all pick lists. If the user is present in the list, he can only pick from pick lists with picklist types defined in the table.

Configuration:

CodeThe code.


Pick list typeThe pick list type. The pick list type can be selected from a list. The list comes from the ‘Produmexpick list types’ UDT.

3.2.3.6. User group for PMX (PMX_USGR)

Definition of Produmex user groups. The user group can be linked to a user.

There are already 2 predefined user groups.

01_ADMIN: Administration●

02_SHPFLR: Shopfloor●

3.2.3.7. User authorization definition (PMX_UAUT)

Definition of possible authorizations that can be set. This is system information. Do not adjust/deletethe code.

Last update:2018/03/1212:56



Possible values:

PRD_FLOW_ON_HOLD: The ‘on hold’ button on the Production flow●

PRD_FLOW_STOP_BTN: The ‘stop’ button on the Production flow●

PROPOSAL_CLOSE_BUTTON: The close button to close pick list proposals (Open documents report,●

pick list proposal form, …)PICK_LIST_CLOSE_BUTTON: The close button to close pick lists (Open documents report, pick list●

proposal form, …)

3.2.3.8. Link usergroup to authorization(PMX_UGAU)

Define the authorization a user group can have.

Configuration:

CodeThe code.


User group codeThe user group code. The user group code can be selected from a list. The list comes from the ‘Usergroup for PMX’ UDT.

User authorization codeThe user authorization code. The user authorization code can be selected from a list. The list comesfrom the ‘User authorization definition’ UDT.

ValueThe actual authorization. Possible values:

Disabled●

Enabled●

Hidden●

3.2.3.9. Link pack line to zone (PMX_LPLZ)

Defines the zone linked to pack lines. This is use on the ‘Consolidated packing’ flow.The pick list destination location should be on that zone. Also the available stock to pack needs to be



stored on that zone.The level of the zone is 1. This means that the zone you define here needs to be the direct zone of thelocation.

Configuration:

CodeThe code.


Code of the pack lineThe code of the pack line, as define in the organizational structure.

Code of the zoneThe code of the zone, as define in the organizational structure.

3.2.3.10. Box type for WAS (PMX_BTWA)

Definition of box types that can be used in the warehouse automation system (WAS).

Configuration:

CodeThe code.

NameThe name.

# CompartmentsThe number of compartments a box has.

3.2.3.11. Box for WAS (PMX_BFWA)

Definition of all boxes that can be used in the warehouse automation system (WAS).

Configuration:

CodeThe code.

NameThe name.

Box typeThe box type. The box type can be selected from a list. The list comes from the ‘Box type for WAS’UDT.

Last update:2018/03/1212:56



3.2.3.12. Box type for item for WAS (PMX_BTIT)

If needed, it can be specified how much items in a certain box type can be stored.

Configuration:

CodeThe code.

NameThe name.

Box typeThe box type. The box type can be selected from a list. The list comes from the ‘Box type for WAS’UDT.

Item codeThe item code.

QuantityThe quantity of the item that can be stored in the given box type.

3.2.3.13. Down time types (PMX_DTTY)

List of down time types. This is used in the time registration module when entering a down time.

Configuration:

CodeThe code.

NameThe name.

3.2.3.14. Pmx priority (PMX_PRIO)

The Produmex priorities. This is used on pick list (proposals) and move orders. The system hasalready 3 predefined priorities:

High (100)●

Normal (200)●

Low (300)●

Configuration:



CodeThe code.

NameThe name.

SequenceA number defining the order of the priority. The value needs to be unique.Order is done ascending. This means that 1 has a higher priority than 99.

Is default?For the default priority this option should be set to true.

3.2.3.15. Produmex user warehouses (PMX_UWHS)

Here it can be defined what warehouses can be visible for a certain user.This is used on the RF terminals and Produmex screens in the administrative module (SAP).If the user is not present in the table, he can view data for all warehouses.

Configuration:

CodeThe code.


SBO WarehouseThe SBO warehouse a user is allowed to view.

3.2.3.16. Produmex user item group (PMX_UITB)

Here it can be defined what item groups can be visible for a certain user.This is used on the RF terminals and Produmex screens in the administrative module (SAP).If the user is not present in the table, he can view data for all item groups.

Configuration:

CodeThe code.


Item groupThe item group a user is allowed to view.

Last update:2018/03/1212:56



3.2.3.17. Produmex cycle count – Other operations filter (PMX_COOF)

Cycle counting can be done during other operations. To have a more flexible way of configuring whensuch a cycle count can be performed, configuration settings can be defined in this table.

Configuration:

CodeThe code.

[Days of the week]Define whether the cycle count during other operations can occur or not on a certain day of the week.

Other operation type for cycle countThe type of operation where the cycle count can be performed. Possible values:

Ad hoc picking – Transport (Pick list or route)●

Ad hoc picking – Customer collect.●

Picking●

3.2.3.18. Freight charges definitions (PMX_FCDE)

Configuration of freight charges that will be added to a sales document.

Configuration:

CodeThe code.

NameThe name.

Freight codeThe line number of the freight to be added. The freight charges are added on a sales order when it isadded. The line number must correspond to a line in the freight charges screen on sales order header:

Shipping type codeThe shipping type code where this freight charge needs to be added.

CostThe price to be added.



Min. document priceThe minimum document price that is required to add the cost.

Example:

Freight code Shipping type code Cost Min document price1 1 30 01 1 20 1001 1 0 200

If the price is between 0 and 99,999999, a cost of 30 will be added to Freight for shipping type 1If the price is between 100 and 199,999999, a cost of 20 will be added to Freight for shipping type 1If the price is above or equal to 200, no cost will be added to Freight for shipping type 1

3.2.3.19. Scale definition (PMX_SCLD)

Configuration of scales that can be used in Produmex RF terminals.

Configuration:

CodeThe code.

NameThe name.

Linked object typeData needed by the system for the current weighing object. Do NOT adjust values in this column.

Linked doc entryData needed by the system for the current weighing object. Do NOT adjust values in this column.

Linked line numberData needed by the system for the current weighing object. Do NOT adjust values in this column.

Scale settingSettings for the scale. What needs to be entered here is depending on the scale.

Scale provider typeProvider type for the scale. What needs to be entered here is depending on the scale.

Scale settingSettings for the scale.

Instance IDThe instance ID

Max. WeightThe maximum weight the scale can handle.

Last update:2018/03/1212:56



Nr. of decimalsThe number of decimals the weight is captured in.

3.2.3.20. Defines the weighing scales available to a specific thin-client (PMX_TCSC)

Links a scale to a thin client.

Configuration:

CodeThe code.

NameThe name.

Thin client codeThe code of the thin client, as defined in the organizational structure.

Scale def. codeThe scale definition code. This can be selected from a list. The list comes from the ‘Defines theweighing scales available to a specific thin-client’ UDT.

3.2.3.21. Seveso (PMX_SEVE)

Defines a seveso class, to hold the maximum quantity allowed on a warehouse.This class can be linked to an item.

Configuration:

CodeThe code.

NameThe name.

Max. QuantityThe maximum quantity.

3.2.3.22. Produmex item serial number format (PMX_ISFT)

A list of possible serial number formats. This can be linked to item master data.

Configuration:



CodeThe code.

NameThe name.

Serial formatThe format a serial number must have. This is a regular expression (regex).

3.2.3.23. List of warehouse to warehouse where serial numbers need to be entered (PMX_WSMM)

Defines whether a PMX serial number needs to be asked when performing a move betweenwarehouses.

Configuration:

CodeThe code.

NameThe name.

From warehouse (PMX)The source warehouse. This is the code of the warehouse as defined in the organizational structure.

To warehouse (PMX)The source warehouse. This is the code of the warehouse as defined in the organizational structure.

Ask serial number?Do serial numbers need to be asked?

Print documents?Do warehouse documents need to be printed?

3.2.3.24. List of selectable trailer numbers (PMX_TRNR)

A list of known trailer numbers that can be selected during shipping process.

Configuration:

CodeThe code.

NameThe name.

Is the record canceled?If set to ’Yes’, the record is cancelled. The user cannot select cancelled records when the data is

Last update:2018/03/1212:56



asked on the scanner or the touchscreen.

3.2.3.25. License plate (PMX_LIPL)

A list of known license plates that can be selected during shipping process.

Configuration:

CodeThe code.

NameThe name.

Is the record canceled?If set to ’Yes’, the record is cancelled. The user cannot select cancelled records when the data isasked on the scanner or the touchscreen.

3.2.3.26. Drivers (PMX_DRIV)

A list of known drivers that can be selected during shipping process.

Configuration:

CodeThe code.

NameThe name.

Is the record canceled?If set to ’Yes’, the record is cancelled. The user cannot select cancelled records when the data isasked on the scanner or the touchscreen.

3.2.3.27. Links between ‘GS1 units of measurement’ (PMX_LUMT)

This is not used.

3.2.3.28. Location types (PMX_LOTY)

A list of location types. These types can be selected on the organizational structure – location.



Configuration:

CodeThe code.

NameThe name.

3PL item codeFor 3PL invoicing only. The code of the item that will be used on the A/R invoices sent to the 3PLcustomers. The price of one day of storage in each location of that location type is represented by the3PL item’s price.The item must be non-inventory.

3PL active?For 3PL invoicing only. If disabled, the price for this location type will not be included in the A/Rinvoices sent to the 3PL customers.

3.2.3.29. Expiry definition (PMX_EXDE)

A list of possible expiry definitions. This is used to calculate best before dates.

Configuration:

CodeThe code.

NameThe name.

DaysThe number of days to add.

MonthsThe number of months to add.

YearsThe number of years to add.

3.2.3.30. List of actions for certain events (PMX_EVAC)

Defines actions that can be performed for certain events.

Possible events:

Open extra documents when another print job within SAP is performed.●

This print job needs to be for Sales quotation/order/invoice.

Last update:2018/03/1212:56



It will get documents defined on the item master data in the column defined.

Configuration:

Table name = OITM●

Colum name = [a column name within OITM where the path to the document that needs to be●

opened is stored]Object type = The object type for Sales quotation/order/invoice●

Action type = Does not need to be filled●

For event = Does not need to be filled●

Configuration:

CodeThe code.

NameThe name.

Table nameThe name of the table.

Column nameThe column name.

For eventDefines the event this action is for.

Action typeThe type of action that needs to be performed.

Object typeThe object type.

3.2.3.31. Batch attribute types (PMX_BATT)

Configuration:

CodeThe code.

NameThe name.

ConvertorThe data is stored in the database as text. The system needs to know what type to convert it to.This can be set with the convertor.Possible values:

Int●



String●

Date●

Double●

List●

SequenceThe sequence the batch attributes should be shown when entering the data. This is used to sort thebatch attributes. This can be any numeric value.

The key for translationThe key that will be used for the translation of the title. When this is not set, the system will useMSG_TITLE_BATCH_ATTRIBUTE.<Code of the batch attribute>. In case there is only 1 language in thecompany, a title can be entered here directly.

A list of possible batch attributes that can be linked to an item.Some predefined codes have been added:

COUNTRY_OF_ORIGIN: Country of origin●

MANUFACTURING_DATE: Manufacturing date●

When custom batch attribute types are added, a translation should be added to the system. Thistranslation is used on a device when entering the batch attributes.The translation node for COUNTRY_OF_ORIGIN looks like:

<PmxLocalizationKey> <Canceled>False</Canceled>

<LocalizationKey>MSG_TITLE_BATCH_ATTRIBUTE.COUNTRY_OF_ORIGIN</LocalizationKey> <ApplicationTypeCode>SLIM_SCR</ApplicationTypeCode> <LocalizationProperties> <PmxLocalizationProperty> <Canceled>False</Canceled> <LocalizationProperty /> <ExtensionCode>CONVSTR</ExtensionCode> <LocalizationValues> <PmxLocalizationValue> <Canceled>False</Canceled> <LocalizationValue>Enter the country oforigin</LocalizationValue> <LanguageCode>3</LanguageCode> </PmxLocalizationValue> <PmxLocalizationValue> <Canceled>False</Canceled> <LocalizationValue>Vul het land van herkomstin</LocalizationValue> <LanguageCode>16</LanguageCode> </PmxLocalizationValue> </LocalizationValues> </PmxLocalizationProperty> </LocalizationProperties>

Last update:2018/03/1212:56



</PmxLocalizationKey>

The LocalizationKey starts with ‘MSG_TITLE_BATCH_ATTRIBUTE.’Add the code of the attribute type at the end.

When making a complete valid translation file to import, make sure the root tags are also added:

<?xml version="1.0" encoding="utf-8"?><TestRoot></TestRoot>

AIThe application identifier. It allows a scanned value from a barcode to be automatically stored in thebatch attributes.

3.2.3.32. Batch attribute valid values (PMX_BAVV)

A list of possible values a batch attributes type can have.

Configuration:

CodeThe code.

NameThe name.

Batch attribute typeThe batch attribute type. This is a link to the table PMX_BATT

ValueThe possible value for the batch attribute type

3.2.3.33. Quality types (PMX_QUTY)

This is the configuration of quality types that can be asked during certain processes. The recordedvalues are stored in the table PMX_QUVA.Supported flows:

Reception●

Bulk reception●

Production●

Production receipt●

Disassembly●

Configuration:



CodeThe code.

NameThe name.

ConvertorThe data is stored in the database as text. The system needs to know what type to convert it to.This can be set with the convertor.Possible values:

Int●

String●

Date●

Double●

List●

Document typeThe document object type for this quality type. This is the ObjType from SAP.For the moment only Purchase delivery (=20) and production order (202) are supported.

RemarksAdditional remarks. This is just informational.

SequenceThe sequence the quality type should be shown when entering the data. This is used to sort thequality types. This can be any numeric value.

Moment of captureThe moment of capture: When does this quality type need to be asked?Possible values:

Start●

End●

The key for translationThe key that will be used for the translation of the title. When this is not set, the system will useMSG_TITLE_QUALITY_TYPE.<Code of the quality type>.In case there is only 1 language in the company, a title can be entered here directly.

When custom quality types are added, a translation should be added to the system. This translation isused on a device when entering the quality values.The translation node for TEMP_TRUCK looks like:

<PmxLocalizationKey> <Canceled>False</Canceled> <LocalizationKey>MSG_TITLE_QUALITY_TYPE.TEMP_TRUCK</LocalizationKey> <ApplicationTypeCode>SLIM_SCR</ApplicationTypeCode> <LocalizationProperties> <PmxLocalizationProperty> <Canceled>False</Canceled> <LocalizationProperty />

Last update:2018/03/1212:56



<ExtensionCode>CONVSTR</ExtensionCode> <LocalizationValues> <PmxLocalizationValue> <Canceled>False</Canceled> <LocalizationValue>Enter the temperature of thetruck</LocalizationValue> <LanguageCode>3</LanguageCode> </PmxLocalizationValue> <PmxLocalizationValue> <Canceled>False</Canceled> <LocalizationValue>Vul de temperatuur in van devrachtwagen</LocalizationValue> <LanguageCode>16</LanguageCode> </PmxLocalizationValue> </LocalizationValues> </PmxLocalizationProperty> </LocalizationProperties> </PmxLocalizationKey>

The LocalizationKey starts with ‘MSG_TITLE_QUALITY_TYPE.’Add the code of the attribute type at the end.

When making a complete valid translation file to import, make sure the root tags are also added:

<?xml version="1.0" encoding="utf-8"?><TestRoot></TestRoot>

AIThe GS1 application identifier (AI) linked to this batch attribute. On the flows batch attributes can beentered, based on the batch attributes linked to an item. When a GS1 barcode has been scanned, anda batch attribute needs to be entered with an AI, the system will check if this AI is available in thescanned barcode. If so, this value will be used and the user will not have to manually enter a value forthis batch attribute.

3.2.3.34. Quality type valid values (PMX_QUVV)

A list of possible values a batch attributes type can have.

Configuration:

CodeThe code.

NameThe name.

Sequence



The sequence of the valid value in the list. This is used to sort the values to select from.

Quality typeThe quality type. This is a link to the table PMX_QUTY

ValueThe possible value for the quality type

3.2.3.35. Allergen types (PMX_ALLE)

A list of possible values an allergen can have.This is used on the item master data to select an allergen.

Configuration:

CodeThe code.

NameThe name.

3.2.3.36. Shelf life per country and business partner (PMX_CSSL)

A list of default shelf lives per business partner and country.These shelf lives are taken into account for items where no shelf life per business partner and countryis defined on the item master data. They have however precedence over the general shelf livesdefined on the item master data.You can enter a shelf life for either just a customer, or just a country, or a combination of both acustomer and a country.

Configuration:

CodeThe code.

NameThe name.

Country codeThe country code (from table OCRY).

Card CodeThe card code of the business partner.

Shelf lifeThe shelf life in days.

Last update:2018/03/1212:56



3.2.3.37. Variable GTIN configuration (PMX_VGTC)

This table holds a list of configurations of variable GTIN barcodes. The user can store a prefix, definethe variable part of the barcode, and what the purpose is of the quantity retrieved from the barcode.

Configuration:

CodeThe code.

NameThe name.

PrefixThe prefix of a barcode that needs to be regarded as a variable GTIN. This does not need to be the fullfixed part of the barcode.

Start index variable partThe barcode has variable part. This field stores the index where the variable part starts. This index iszeor-based.

Length variable partThe barcode has variable part. This field stores the length of the variable part.

# DecimalsThe number of decimals of the variable value.

Value purpose (AI)This defines on what Application Identifier the value needs to be stored, after the value has beencaptured.

3.2.3.38. Put away zones (PMX_PAZO)

This table holds a list of put away zones.It is used in the functionality for 'Location suggestions'

Configuration:

CodeThe code.

Name



The name.

3.2.3.39. Item storage location type (PMX_ISLT)

This table holds a list of item storage location types.An item and/or location can have this property.It is used in the functionality for 'Location suggestions'

Configuration:

CodeThe code.

NameThe name.

3.2.3.40. Sequence configuration (PMX_SECO)

This table holds the configuration of sequence numbers.It is used when Produmex creates a document.It sets the sequence on a document for the Brazilian localization.(Like ODLN.SeqCode)

So when a document is created by Produmex, the sequence code for the type of document, andbranch is retrieved from this configuration table.When no configuration is found, no sequence code is set.

Configuration:

CodeThe code.

NameThe name.

Document typeThe type of the document.Like '17' = Sales order, '15' = Sales delivery, …

Branch IDThe branch ID.

Sequence codeThe sequence code. This is a numeric value.

Last update:2018/03/1212:56



3.2.3.41. Ports (PMX_PORT)

This table holds the ports.It is used for the container management: Port of origin, port of destination.

Configuration:

CodeThe code.

NameThe name.

Normal lead time (in days)The lead time in days for normal delivery at this port.This is used for calculation of dates in the container management.

Express lead time (in days)The lead time in days for express delivery at this port.This is used for calculation of dates in the container management.

3.2.3.42. Container shipping status (PMX_CSST)

This table holds the shipping statuses a container can have.

Configuration:

CodeThe code.

NameThe name.

SequenceThe sequence is used for the sorting on the combobox on the container management screen.

3.2.3.43. Hidden Fat Client Buttons (PMX_HBCB)

This table holds configuration to hide buttons on flows used in the Fat Client.This configuration table is intended to be used by consultants who are familiar with the workflows andknow how to retrieve the needed information to complete the configuration.

Configuration:

CodeThe code.



NameThe name.

Calling workflowThe work flow that is used.

Title keyThe title key of the screen where the button needs to be hidden.

Button keyThe button key of the button that needs to be hidden.

DisabledCheck this checkbox to disable the configuration to hide the button.

Pmx User GroupThe user group this configuration applies to.If no user group is set, it applies to all users.

Examples:

How to hide button 'No PO' on the reception flow●

How to hide button 'Change lined up location' on the production flow●

3.2.3.44. Scale weight result user table (PMX_SCWR)

Last update:2018/03/1212:56



CodeThe code of the scale. Add the Organizational Structure scale code here.

NameThe name of the scale.

WeighThe measured weigh. This field will be filled by the ScaleComm Service if the ‘Skip Polling’ option isset to ‘False’ in the configuration file of the ScaleComm Service.

UomThe Uom of the scale. This field is for information only.

3.2.4. Business partner master data



S/P remarks pop-upIf checked, the text in the Sales/Purchase remarks is shown as a pop-up when using this businesspartner in a sales/purchase document in SAP.

Sales/Purchase remarksThe Sales/Purchase remarks to be shown when selecting the business partner in a sales/purchasedocument in SAP.

Group sales deliveryIf various orders for a customer have been entered and picked, it is possible to group the variousorders in one sales delivery (Y) or to have a sales delivery per individual order (N). It is also possibleto base this setting on the extension parameter “Sales delivery note generator” at the company levelin the organization structure.

Linked Business PartnerIn a third party logistics context, a supplier can be linked to a customer so that a purchase order tothe supplier can be linked to a sales order to the customer.

Pick list typeIn case a default pick list type applies to a business partner, this can be indicated here. When aproposal is created, it will set a pick list type in this order:

On document●

On business partner (Only for sales proposals)●

Default pick list type●

Pallet packing typeThis is used during packing, consolidated packing,item packing, in combination with allowing to usethe pallet packing type on customer (Setting on PackingController).Possible values:

Last update:2018/03/1212:56



Pallet (Default)●

In case master is allowed, then user is asked whether to create master SSCC or normal SSCC❍

Multiple identical pallets●

Creates identical normal pallets❍

Pallet - Multiple identical sub packages●

Creates 1 master SSCC, but identical sub SSCC's❍

Always ask user●

Ask the user how to create the pallets❍

Identical master and/or identical sub SSCC's are allowed.■

Enter specific pallet number?If checked, a supplier pallet number needs to be entered during reception. This is stored on the table(PMX_LUID) where the SSCC is stored.

If for certain business partners you use that business partner’s own pallets (meaning that these haveto be traceable within your company), you can indicate that upon receipt of such a pallet, the palletnumber has to be registered.

Has no logistic carriersIf checked, the screen to select a logistic carrier will be skipped during the reception process

Has no logistic labelsIf checked, the screen to scan the logistic label will be skipped during the reception process

Has no identical logistic unitsIf checked, the screen to choose between identical and non identical logistic units will be skippedduring the reception process

Never delivers mixed logistic units?If checked, the screen to add more items to the logistic unit will be skipped during the receptionprocess

3.2.5. Shipping types

Produmex has extended the shipping types.Configuration for pick list/proposals, creation of delivery documents, … can be done here.

When creating proposals, the goods on the sales document can be split up in several proposals,according to settings defined on the shipping type on document line level

Automatic shipping?If checked, the system will try to automatically create a delivery when the pick list is packed. Thissetting is taken in account for splitting document lines into several proposals.

Automatic invoicing?If checked, the system will try to automatically create an invoice when the delivery is made. Thissetting is taken in account for splitting document lines into several proposals.The automatic invoicing is only supported for deliveries made by an RF terminal.



Mail report on document addIf checked, a report will be mailed when the document is added. This requires the SBO Notificationlistener to be installed, and configured to perform the mailing.

Is customer coming to collect?If checked, the proposal/pick list that is generated will have the setting that it is for a customer collectto true. This setting is taken in account for splitting document lines into several proposals.

Ask license plate during shipping?If checked, system will ask for a license plate when performing the shipping. This overrules the settingon global level.

Ask driver name during shipping?If checked, system will ask for a driver name when performing the shipping. This overrules the settingon global level.

Ask trailer number during shipping?If checked, system will ask for a trailer number when performing the shipping. This overrules thesetting on global level.

Ask tracking number during shipping?If checked, system will ask for a tracking number when performing the shipping. If it is configured tohave multiple deliveries created when shipping (multiple) pick lists, only 1 tracking number is asked,and stored on all deliveries.

The shipping type setting in SBO 9.2.

Disclaimer: This documentation describes the standard SAP Business One shippingtype function.

The shipping type can be set in three level:

Business Partner (On the General tab of the Business Partner Master Data)1.Sales order (On the Logistics tab of the order)2.Item (On the General tab of the Item Master Data)3.

The default shipping type of a sales order is the shipping type of the customer, but it can beadjusted on the Logistics tab of the order. When changing the sales order shipping type, thesystem will ask whether to modify the shipping type of the sales order lines as well.

The default shipping type of the sales order lines is the shipping type of the sales order. Whenadding an item that has a shipping type defined, the shipping type will be automatically set tothe item’s default. Changes of the sales order line shipping type will not affect the sales ordershipping type.

Last update:2018/03/1212:56



3.3. Production

3.3.1. BOM

Is base componentIs the current ingredient the base component of the product to produce? (Informational)This is also used in combination with the ‘Scan base component’ option on item master data.During picking the user will be asked to scan the barcode of this base component when picking themaster item.

Has to be lined upDoes this component need to be consumed from a lined up location?

Qty tolerance %The tolerance (percentage) of the quantity of components to consume. This will allow the systemdeviate from the theoretical quantity needed for the production.

Is the item optionalSet wether the component is optional. If set to true, this component is not required to produce.

Prod. Order start condition

N = No condition●

Q = Component part. weighed●

W = Component weighed●

These are the start conditions of a production order. The requirements need to be met, before theproduction order can be started.

Best before date optionThis is used when picking for production. It configures the way the system should calculate a validbest before date for the ingredient. Possible values:

BBD of finished product and shelf life: Take the BBD defined on the production order + shelf life of●

the ingredient.Due date and shelf life: Take the due date of the production order + shelf life of the ingredient●

Pick date: Take the date when the picking occurs or in case of pick lists for production the creation●

date of the proposal.

Allow to pick for line up? (True/False)If enabled for a component that has to be lined up, the component can be consumed from every linedup location assigned for the production line, otherwise it can be consumed only from the assignedlined up locations with stock for the item.

Such a component will be added to the pick list (proposal) for production or can be picked forproduction. When moving the components to the production line, it will be moved to the lined uplocation selected for the component.

When the ‘Direct consumption of goods’ option is enabled for the lined up location the component is



consumed, the component will be automatically issued when the product is received, therefore it willnot be listed among the other components on the Production Manager – Stop screen. However, it the‘Allow to pick for line up setting’ is enabled for the component, it is possible to issue more than theplanned quantity, therefore the component will be listed on the Stop screen of the ProductionManager.

Weighing needed? (True/False)Set whether the component must be weighed or not. When creating a weighing order, onlycomponents, that have the ‘Weighing needed?’ setting enabled, are added to the weighing order.

Weigh order batch quantityAdd number of batches for the weighing order. If the quantity is greater than 1, the planned quantityof the item to be weighed will be split into multiple weigh order lines. The number of lines is definedby the Weigh order batch quantity value.

Batch attribute & Batch attribute valueThis is used when picking for production.

If certain batch attributes need to be picked for production, select the batch attribute type from thedropdown menu in the Batch attribute field. Every batch attribute defined on the Batch attribute typesuser table can be selected. Then enter the given value to the Batch attribute value field. You can addup to three batch attribute per line.

On the production order, you can also add batch attributes by selecting the ‘Batch attributes’ optionfrom the right-click menu of the line. On the opening Batch attributes control screen you can selectthe batch attribute type and add/select the batch attribute value.

If a batch attribute is defined for a production line, the stock that can be picked is filtered based onthe batch attribute.

3.3.2. Production order header

Produmex production status

http://wiki.produmex.name/doku.php?id=implementation:wms:productionmanager#stop_production

http://wiki.produmex.name/doku.php?id=implementation:wms:productionmanager#stop_production

Last update:2018/03/1212:56



Next to the status of SAP, there is the Produmex production status.Possible values: Planned, On hold, Started, Closed

Production step listNext to the item to produce, the user can select a steplist.The requirements to select a steplist:

One or more steplists for the item to produce needs to be configured●

The production type needs to be ‘Special’●

When a step list is selected, a list of components is created according to the selected steplist.

Production lineNext to the warehouse, the user can select the production line where this production order needs tobe produced. Only the production lines in the warehouse are shown.

3.3.3. Production order lines

The extra fields added to the BOM, are also added to the production order. When creating a newproduction order, the Produmex add-on will copy the data from the BOM to the production order incase the UDF’s are named the same.

The following fields are used for picking for production: (And not for Pick List for production)

Quantity pickedThe quantity that already has been picked for this component.

Batch(es) to pickIf a certain batch needs to be picked for this production order, this column needs to be filled with thebatch to pick.When multiple batches are required, those batches can be entered with a pipe as separator: '|'

3.3.4. Production issue lines

Is waste?Is this line registered as waste?

The production batchThis stores the production batch this line was issued for.



4. Produmex WMS Office Module

Apart from the extension of existing SAP Business One functions, Produmex WMS offers specificadministrative functions for streamlining the operational processes of goods receipt, put away,production, packaging, picking and shipping. These functions are grouped under the Produmex tab inthe main menu of SAP Business One. You can also access these functions by way of the menu optionModule where you can then select the option Produmex at the bottom.

Last update:2018/03/1212:56



5. Organizational Structure

Before you can start using Produmex you have to define the structure of your company. Here youdefine how your company is organized in practice.In the main screen of the organization structure you can start by adding and arranging the variousstructure elements in your company.

These OSE’s (Organization Structure Elements) are (in hierarchic order):

Company: this OSE can only be created once per company database●

Warehouse: this is the highest level below a company. Warehouse not only refers to the place where●

goods are received, stored and from which they are shipped. The warehouse can also be thelocation where goods are transformed (manufactured or packaged). A warehouse in Produmex mustalways be linked to a warehouse in SAP Business One.Zone: a specific area in the warehouse where certain functions are grouped (e.g. goods receipt,●

shipping, packaging, …)Production line: a line where goods are produced and packaged (as part of a warehouse)●

Packing line: a line where goods that were picked on a movable location can be packed onto a●

logistic carrier to be shipped as a logistic unitDock: a location where goods are received and/or shipped (as part of a warehouse)●

Warehouse Automation Location – an automated warehouse (mini load) that manages input and●

output of items automatically. Produmex does not manage the individual locations (boxes) in the



automated warehouse but keeps track of the inventory in on a global level.Bin: an individual storage location managed by Produmex.●

Silo Tank: a fixed bulk storage location●

Movable Location: a movable storage location (e.g. a picking cart) on which goods are temporarily●

stored after picking before they are packed on a logistics carrier or used in production (e.g. aforklift).Thin Client: a fixed or mobile operator station (touch screen, handheld terminal, …), by which the●

operator interacts with ProdumexPrinter: a printer at a specific location or connected to a specific thin client●

5.1. Organizational Structure Settings at Company Level

All the data on several tab pages can be changed within the tab page itself. When a change has beenmade, the OK button (Number 4) will be enabled.It is only when clicking the OK button (4) the changes are committed to the database.

An example to add a report:

Last update:2018/03/1212:56



Enter the configuration of the report.1.Click the Add button to add the new report to the list.2.The report is added, but has as key = 0, because it is not committed to the database yet.3.Click OK button to add the changes to the database.4.

5.1.1. General settings

At the company level a number of general settings can be specified that apply to the entire ProdumexWMS Add-On.



LanguageThis includes the standard language (the language that is used by default on the thin clients, unlessspecified otherwise at the individual user level (cfr. Administration → Users).

LogoFurthermore a reference to the company logo can be added: this path points to a shared folder whichcontains the company logo that is used on the login page of the thin clients.

DB credentialsThe standard connection to the SAP Business One database (username / password ). Needs to be setfor reporting purposes.

Logistic carriersNext it is also possible to define whether logistic carriers (pallets, containers, …) are stored at onelocation per warehouse (where they are stored after emptying) and what the standard quality statusfor logistic carriers is.

Store logistic carriers on 1 storage location by warehouse \\When this option is enabled,●

logistic carriers are stored at one location per warehouse. Set the default storage location for logisticcarriers on the Warehouse level.This setting should be enabled in order to use logistic carriers properly.Move all logistic carriers on reception●

When this option is enabled, logistic carriers are automatically moved to the default storage locationof the logistic carriers after the reception.This setting is only active if the ‘Store logistic carriers on 1 storage location by warehouse’ option is

Last update:2018/03/1212:56



enabled.Quality status for logistic carriers●

Select the standard quality status for logistic carriers from the dropdown menu.

Transport servicesIn case the company uses transport services, it is also possible to indicate whether the name of thedriver has to be specified or selected when loading and/or whether the license plate and/or the trailernumber of the transport vehicle should be recorded.These global settings can be overruled on the SAP Shipping types.

Goods receipt requires suppl. refIf this parameter is checked, the operator will be asked to enter a supplier reference number duringthe goods reception process.

Goods receipt automatically prints item labelsWhen this is ticked, the goods receipt on scanner will automatically print item labels. The number oflabels printed, is the received number of items. Otherwise the user will be asked if he wants to print.

Use inventory returnable items on documentsIf this is ticked, the returnable item added to the document will be the inventory item.

Set vat group returnable items on documentsIf this is ticked, the VAT group of the returnable item will be set when added to the document. Forpurchase this will be OITM.VatGroupPu and for sales this will be OITM.VatGourpSa.

Check to add returnable itemsWhen this is ticked, the system will try to add returnable items when booking a document. To avoidthis check this can be unticked.

Disable item selection in flowsIf this is ticked, it will not be possible to select an item on scanner/touchscreen. The user will alwayshave to scan a barcode to identify the item.

Use Produmex QualityThis setting must be enabled in order to use the Produmex Quality module.

Pick list proposal allowed to exceed orderIf ticked, it is possible to adjust the quantity of the proposal, so it exceeds the ordered quantity.

Do not lock stock on picking (pick lists can be created even if no stock is available)When proposals are made, stock is locked. If this is ticked, the system will not lock stock whencreating the proposal. This means that there is no more check of available quantity, so proposals canbe made, even if there is not enough quantity.Picking can only happen through the ‘Ad hoc picking’ flow.This option does not apply to pick lists for production. Those pick lists will have locking.

Allow over pickingIf “Allow over picking” is checked, the operator will be able to pick more items than specified in thesales order/picklist. This can be done for convenience purposes, e.g. if an order for 14 items isreceived and the packaging unit for that item is a box of 15 items. In such a case, picking a whole boxmay be more convenient than opening the box and taking one item out.

http://wiki.produmex.name/doku.php?id=implementation:quality:main



This option is only available for Picking, Zone picking and Multi picking, Ad hoc picking - route, Ad hocpicking - pick list.

Allow over picking on (Customer collect)If this setting is enabled, the operator will be able to pick more items than specified in the salesorder/pick list in the Ad hoc picking – Customer collect flow.

Count colli after pickingAs a further check to ensure the correctness of deliveries, it can be specified that the operator has tocount and enter the number of colli that were picked and put onto a logistic unit (SSCC), which theoperator wishes to finish. The system will then verify whether this number is the same as the numberof colli it has recorded during the picking process onto this logistic unit (SSCC). The count is done inthe inventory UoM.When this is ticked, it can be configured how many times the user can enter an incorrect count.When this maximum is reached, the picked SSCC is considered unpicked, and a new pick list iscreated for these items, forcing the user to pick again.

Embed .NET forms in SBO formsWhen this option is set, all forms run within SAP.But in some cases it is useful if some screens are not embedded in SAP. In that case it is possiblewhen you have 2 monitors to move certain screens outside of SAP on another monitor.This can be done by unchecking this checkbox.Some screens will be shown in the Windows taskbar, and will be outside of SAP.Supported screens:

Organizational structure●

Route planning●

Production manager●

Cycle count – Select location●

Cycle count – Process●

5.1.2. Defaults

Last update:2018/03/1212:56



LabelsIn the default settings you can specify the standard labels for goods receipt, shipping and thestandard item label.

Put away generatorHow received goods (logistic units – SSCC) have to be put away. The options are:

Generates full pallet put away orders●

For these put away orders, the user will always have to move the full SSCC to a location. The SSCCcannot be split up.

Generates NO put away orders●

If no put away orders are needed, this option can be selected.

Generates put away orders●

This is the default put away generator. This will generate the order. When processing the order, theuser can select if he wants move the full SSCC or not for monolot pallets. Mixed pallets will have to besplit up.

Additional expenses generator:This setting is used to copy additional expenses like for example freight costs from a sales order/lineto a sales delivery. The way the costs get divided on the base documents depend on the configuration



within SAP. Produmex does not handle this.

Default quality status receptionThe default quality status for goods receipt.This option can be overruled by settings on the item master data.

Released quality status receptionThis setting is related to the setting “default quality status reception”. The setting defines the qualitystatus of a lot number that is released in inventory. For example an item with a lot number is receivedin inventory with a quality status of quarantine (default quality status reception), if the item and lotnumber changed of quality status to released and the item with the same lot number is againreceived into inventory it will retrieve the quality status defined in the setting “Released quality statusreception”.This option can be overruled by settings on the item master data.

Quality status sales returnThe default quality status for sales return.This option can be overruled by settings on the item master data.

Quality status cycle countingDefines the default status of items that are added to the inventory (Inventory Transaction → GoodsReceipt) as a result of Cycle Counting (when a positive difference has been established between theactual physical stock in the warehouse and the administrative stock that was registered in SAPBusiness One). This quality status only applies to additional items that are NOT on an existing logisticunit (SSCC) in the system. Additional items that are counted on an existing logistic unit get the qualitystatus of that logistic unit.

Quality status returnable itemsThe default quality status for returnable items.This is used when inventory returnable items need to be added to the system.

5.1.3. Extension Parameters

General

In the “Extension Parameters” tab, it is possible to define a number of parameters for certainproperties. This is how you configure the system to behave in certain processes.These properties and the applicable extension parameters are:

Last update:2018/03/1212:56



After a property and extension is selected, the related parameters are displayed.

It is possible to filter the shown parameters. Start typing to the ‘Search parameters’ field. Onlyparameters that contain the entered characters will be displayed.

5.1.3.1. 3PL invoicing controller

3PL Invoicing Controller (3PLINV)



Add zero-price lines to 3PL invoices? (Y/N)Option to whether or not include price with a calculated price or zero to the 3PL invoices.

Shortest invoiceable storage durationDefines the minimum duration to be invoiced when a bin location is used by an item.Possible values:

‘Day’: if a bin location is used by an item on one day, invoice the daily storage price or that bin●

location one time‘Week’: if a bin location is used by an item on any day of a week, invoice the daily storage price of●

that bin location for the whole week‘Month’: if a bin location is used by an item on any day of a month, invoice the daily storage price of●

that bin location for every day of the month

Storage price calculation typeDefines the way to calculate the storage price for bin locations.Possible values:

‘Daily used number of locations’: every bin location that has contained a supplier item will be●

considered as having been used for storage, and will be included in the storage price calculation‘Daily final stock’: only the bin locations that contain an item of the supplier at the end of each day●

will be considered as having been used for storage, and will be included in the storage pricecalculation

Last update:2018/03/1212:56



5.1.3.2. Batchnumber 1 on company

Generates batch number for reception based on format (BGRF)

Can the user change the generated batch number? (Y/N)Option to whether or not the user will be able to change the generated batch number during thereception process.

Must batch number be overwritten by scanned batch number of GS1 label? (Y/N)Can the entered batch number be overwritten by the batch number that is present in the barcode onthe GS1 label (if any) of the received items.

The current sequential numberField that holds the current sequential number.

The date format to reset sequential numberDefines the date format on what the sequential number will be reset. In the example above thesequential number fill be reset when the year changes.

The formatDefines the format of the generated batch numbers.A tag starts with ‘[‘ and ends with ‘]’. Inside a tag the first part is the identifier of the type of valuethat needs to be entered. Next is a ‘:’ to split the identifier and the value of the identifier.

Possible tags in the format:

[Date:yyMMdd] or [D:yyMMdd]Date: This will be replaced by the date format provided in the value of the identifier. All windowsallowed formats are allowed. It will perform the method DateTime.ToString(string value) of Windows.

[DayOfYear:3] or [DY:3]Date: This will be replaced by the day of year. The value indicates the minimum length the processedvalue should have. The fill character is ‘0’. So if the day of year is 99, and value is 3, the processedvalue will be 099.

[X:4]Sequential number: This will be replaced by the sequential number. The value indicates the minimumlength the processed value should have. The fill character is ‘0’. So if the sequential number is 99,and value is 4, the processed value will be 0099.

The update date for sequential numberThe last update date in the specified format. This is used to know when the sequential number needsto be reset.

Generates prefix-year-month-serial batch number for reception XXXYYYYMMSSSSS


Must batch number be overwritten by scanned batch number of GS1 label? (Y/N)



Can the entered batch number be overwritten by the batch number that is present in the barcode onthe GS1 label (if any) of the received items.

The current monthField that holds the current month.

The current serialField that holds the current serial number.

The current yearField that holds the current year.

The length of the serialDefines the length of the serial number

The prefixDefines the prefix of the generated batch number.

BatchNumberGeneratorReception - Generates empty batch number for reception

The user will have to enter the batchnumber manually.

Must batch number be overwritten by scanned batch number of GS1 label? (Y/N)Must the entered batch number be overwritten by the batch number that is present in the barcode onthe GS1 label (if any) of the received items.

BatchNumberGeneratorReception - Generates year-serial batch number for reception YYYYSSSSS

Generates an automatic batch number based on the specified criteria: i.e. year + serial number of aspecific length. It can furthermore be defined whether or not the user will be able to change thegenerated batch number.




The current yearField that holds the current year.

The length of the serialDefines the length of the serial number.

Prefix-year-month-day-salesordernum batch number for reception PPPYYYYMMDD-SSSSSS (BGR-YMDS)

Generates an automatic batch number based on the specified criteria: prefix + year + month + date+ linked sales order. It can furthermore be defined whether or not the user will be able to change the

Last update:2018/03/1212:56



generated batch number.


Default postfix if no sales order linkDefines the postfix of the generated batch number, if there is no sales order linked to the purchaseorder.


PrefixDefines the prefix of the generated batch number.

5.1.3.3. Batchnumber 2 on company

Identical to batch number 1

5.1.3.4. Batchnumber production company

Generates batch number for production based on format

Can the user change the batch number during production? (Y/N)Option to whether or not the user will be able to change the generated batch number during theproduction process.



Can the user change the generated batch number? (Y/N)Option to whether or not the user will be able to change the generated batch number.

Save changed batch on production order? (Y/N)This option defines if the changed batch number needs to be saved on the production order or not.

The current sequential numberField that holds the current sequential number.

The date format to reset sequential numberDefines the date format on what the sequential number will be reset. In the example above thesequential number fill be reset when the month changes.

The formatDefines the format of the generated batch numbers.

A tag starts with ‘[‘ and ends with ‘]’. Inside a tag the first part is the identifier of the type of valuethat needs to be entered. Next is a ‘:’ to split the identifier and the value of the identifier.



[DayOfYear:3] or [DY:3]Date: This will be replaced by the day of year. The value indicates the minimum length the processedvalue should have. The fill character is ‘0’. So if the day of year is 99, and value is 3, the processedvalue will be 099.

[L:2] or [Line:2]Production line: This will be replaced by the name of the production line linked to the productionorder. The value indicates the length of the processed value. The system will take the first part of theproduction line name, until the required length.



Generates prefix-year-month-serial batch number for production XXXYYYYMMSSSSS

Last update:2018/03/1212:56






The current dateField that holds the current date, based upon the defined date format below. i.e.: date format = yyyy,the current date will be 2013.


The date formatField that holds the date format, based upon this the current date is stored and calculated.

The length of the serialField that holds the length of the serial number.

The prefixField that holds the prefix of the batch number.

BatchNumberGeneratorProduction - Empty batch number

The user will have to enter the batch number manually.



Can the user change the batch number during production? (Y/N)Option to whether or not the user will be able to change the batch number during the productionprocess.


BatchNumberGeneratorProduction - Generates batch number

The format is: yy-[DayOfYear]-[ProductionOrderNumber]




5.1.3.5. Batchnumber generator for sales return

Generates batch number for sales return based on format

Last update:2018/03/1212:56



Can the user change the generated batch number? (Y/N)Option to whether or not the user will be able to change the generated batch number during theproduction process.

The current sequential numberField that holds the current serial number.

The date format to reset sequential numberDefines the date format on what the sequential number will be reset. In the example above thesequential number fill be reset when the month changes.

The formatDefines the format of the generated batch numbers.

A tag starts with ‘[‘ and ends with ‘]’. Inside a tag the first part is the identifier of the type of valuethat needs to be entered. Next is a ‘:’ to split the identifier and the value of the identifier.



[DayOfYear:3] or [DY:3]Date: This will be replaced by the day of year. The value indicates the minimum length the processed



value should have. The fill character is ‘0’. So if the day of year is 99, and value is 3, the processedvalue will be 099.



5.1.3.6. Best before for production generator

Generates best before date for production

Can the user change the bbd number during production? (Y/N)Option to whether or not the user will be able to change the generated best before date during theproduction process.

Can user change the date (Y,N)Option to whether or not the user will be able to change the generated best before date.

Last update:2018/03/1212:56



Generate on every receiptWhen enabled, the BBD will be calculated each time a production receipt is being added.

Save changed bbd on production order? (Y/N)This option defines if the changed best before date needs to be saved on the production order or not.

5.1.3.7. Best before for reception generator

Default BBD generator for reception

Can the user change the generated best before date? (Y/N)Option to whether or not the user will be able to change the generated best before date.

5.1.3.8. Barcode controller



GS1 Barcode

Captures barcodes according to GS1 standards.

Set AI(17) as AI(15) (Y/N)If enabled, then when scanning a barcode containing an AI17 value, the AI17 value will be added asthe best before date (AI 15).

B10 Automotive Barcode

Captures barcodes according to B10 standards. If the scanned value does not seem to be a B10barcode, the scanned value is parsed through the GS1 barcode controller.To be able to know the difference between a scanned barcode and manual entry, the barcode needsto be in Code39 format.This means that the barcode needs to start with ]A0Remark: The location barcodes cannot be in format Code39, otherwise locations that forinstance start with Q, P, … would be considered a value for the B10

Q: Quantity - Stored in field for AI(37) Count (=int)P: Part number - This is the item codeS: Serial number - Will be stored as SSCCV: Supplier code

5.1.3.9. Cycle count controller

Controls the cycle counting

Last update:2018/03/1212:56



Allow to adjust quantity of current stock items?If this option is enabled, and the option 'Show current stock items' is enabled, ths cycle count flow willallow to select currect stock and adjust the quantity instead of performing a 'blind' count.

Allow to select account in case of perpetual inventory?If this option is enabled, the accounts numbers need to be selected during the cycle count processingprocess if the option ‘Perpetual inventory’ is set.

Allow user to skip countWhen performing cycle count during other operations, the user is allowed to skip the count.

Auto handle batch?When this option is set, no batch needs to be entered in the cycle count process. The system will tryto fill in the batch. If there is only 1 batch on the location, the system will take that batch. If there aremultiple batches, the system will take the youngest batch. If no batch is on the location, the systemwill take the batch defined in the ‘Default batch on auto handle batch’.

Auto move SSCC



When an SSCC is counted on a location, it is possible that for the system it is stored on anotherlocation. These options set what actions should happen when this occurs:

No move●

Ask user●

Auto move●

Option is available for type 'Lost and Found'

Auto select batch/BBD when monolot palletWhen cycle counting a monolot pallet (a pallet with only 1 item and lot number), the system will autoselect the batch and BBD instead of the user that needs to fill it in.

Count after number of daysWhen a location has not been counted for the number of days defined here, the location needs to becounted. This setting is only used if on location level this setting is not set.A zero means that this location will always have to be counted.

Count after number of operationsIf the number of operations since the last count exceeds the defined number of operations, thelocation needs to be counted. This setting is only used if the setting is not set on location level.A zero means that this location will always have to be counted.

Count location when it becomes emptyCount the location if the used location becomes empty (count during other process)

Count type cycle countThe type of cycle count to use when doing cycle count.Possible values:

‘Lost and Found’: An actual theoretical location where differences are stored. This option will correct●

the stock on the counted location.‘Registration’: Differences are stored in a table. With this option the stock on the counted location●

remains the same until the count is processed.

Please note that differences for serial numbers will always use type 'Registration', regardless of theselected type.

Count type other operationsThe type of cycle count to use when doing cycle count during other operations.Possible values:

‘Lost and Found’: An actual theoretical location where differences are stored. This option will correct●

the stock on the counted location.‘Registration’: Differences are stored in a table. With this option the stock on the counted location●

remains the same until the count is processed.

Please note that differences for serial numbers will always use type 'Registration', regardless of theselected type.

Default batch on auto handle batchThe batch number to use when there is no batch on the counted location, and if the ‘auto handlebatch’ option is set to true.

Last update:2018/03/1212:56



Dummy serial number formatWhen using the lost & found method for cycle count, and processing the cycle count for lost serialnumbers on release only, dummy serial numbers might need to be generated in order to be issued.In this setting you can enter a fix part for all dummy serial numbers. Incrementing numbers will beappended to this value to generate unique dummy serial numbers.

Enter reason on direct cycle count?Does the user need to enter a reason during direct cycle counting?

Enter reason when skipping count?Does the user need to enter a reason when skipping a count? A count can only be skipped duringother operations.

Manually set price on processing the countThis allows the user to enter the price that needs to be used when making the goods issue/receipt.By default the new price will be the value from the column 'item cost'.For catch weight items a price per weight can be entered.

Price list for goods issueThe price list to use when the cycle count needs to perform a goods issue. Possible values:

An SBO price list (OPLN.ListNum)●

-1 for last purchase price●

-2 for last evaluated price●

Price list for goods receiptThe price list to use when the cycle count needs to perform a goods receipt. Possible values:

An SBO price list (OPLN.ListNum)●

-1 for last purchase price●

-2 for last evaluated price●

Propose default quantity on logistic unitIf set, the system will automatically fill in the default quantity on a logistic unit.

Registration: Store lines with no differenceIf set, the system will also store lines in the registration table where the counted difference is zero.This option is only taken in account when the 'Count type' = Registration.

Show current stock itemsIf set, the system will show the current items in stock for the selected location when the countingstarts.

Show differences during cycle countAfter counting a location it is possible to show the differences between the counted items and theitems in the system. This is shown on the device during cycle count.

Show differences during other operationsAfter counting a location during other operations, it is possible to show the differences between thecounted items and the items in the system. This is shown on the device during cycle count.



5.1.3.10. Container management controller

Container management controller - Controls the containers

Allow to show purchase reserve invoicesIf enabled, purchase invoices can be selected on the container management form.

Auto close container when delivered? (Y/N)If enabled, the container will be closed when it is delivered.If disabled, the container will be in status 'Delivered'.This means that some fields can still be adjusted. Closing the container needs to be done through theContainer management screen.

Color if values are in rangeDefines the color the controls should get if the values are in range. If no maximum value is set, thiscolor will also be used. This name needs to be a valid Windows color name.

Color if values are too highDefines the color the controls should get if the values are higher than the ‘in range’ values. This nameneeds to be a valid Windows color name.

Color if values are too lowDefines the color the controls should get if the values are lower than the ‘in range’ values. This nameneeds to be a valid Windows color name.

Last update:2018/03/1212:56



Lead time in days between port and warehouseThe lead time in days between port and warehouse. This is used for the calculation of dates in thecontainer management screen.

Lower threshold: price (%)The lower threshold (in percentage) for the ‘in range’ values for the price.

Lower threshold: volume (%)The lower threshold (in percentage) for the ‘in range’ values for the volume.

Lower threshold: weight (%)The lower threshold (in percentage) for the ‘in range’ values for the weight.

Upper threshold: price (%)The upper threshold (in percentage) for the ‘in range’ values for the price.

Upper threshold: volume (%)The upper threshold (in percentage) for the ‘in range’ values for the volume.

Upper threshold: weight (%)The upper threshold (in percentage) for the ‘in range’ values for the weight.

5.1.3.11. Document series controller

Default SAP Document series

5.1.3.12. Freight charges controller



Document price referenceThe price to take in account for the freight charges

View nameThe name of the view to use for calculation of the freight charges. The default value is:‘PMX_FREIGHT_CHARGES’

Configuration of the freight charges is done on the UDT PMX_FCDE

5.1.3.13. Incoming payment generator

None

5.1.3.14. Inventory Controller

Inventory Controller – Controller for the inventory

View name - DetailThe view name that is used to show the inventory report for ‘Group by’ = Detail.This means that the inventory report can be customized.It is possible to ADD additional columns to this view.

Localization key - DetailWhen the inventory report is called for ‘Group by’ = Detail, this translation key will be used.There is the possibility to select one of the existing sortings.

Order by - DetailsWhen the inventory report is called for ‘Group by’ = Detail, this sorting will be used on the query.There is the possibility to select one of the existing sortings.But it is also possible to just type text for the order by statement.

The text in the field will be added to the ORDER BY clause of the query.There is no need to start the text with ORDER BY.

Possible values:

Last update:2018/03/1212:56



ItemCode ASC, InternalKey ASC: This will sort it on the item code, and next the row key of the●

inventory.InternalKey ASC: This will sort based on the row key of the inventory.●

StorLocCode ASC, ItemCode: This will sort on the storage location code and next on the item code.●

5.1.3.15. Interface for PMX Advance Shipping Notice im-/export

None

5.1.3.16. Interface for PMX move order im-/export

IPmxMoveOrderInterface – Default

5.1.3.17. Interface for PMX move im-/export

IPmxMoveInterface – Default

5.1.3.18. Interface for PMX serial number im-/export

IPmxStockInterface - Pmx stock im-/exporter

5.1.3.19. Interface for stock QS change import

None

5.1.3.20. Interface for stock im-/export

None

5.1.3.21. Report mailer

IReportMailerInterface – Default



Default e-mail body fileLocation of the email body

Default e-mail recipientDefault email recipient

Default e-mail send passwordDefault e-mail send password

Default e-mail send serverDefault e-mail send server

Default e-mail send user nameDefault e-mail send user name

Default e-mail senderDefault e-mail sender

5.1.3.22. Interface for SBO business partner im-/export

None

5.1.3.23. Interface for SBO goods issue im-/export

None

Last update:2018/03/1212:56



5.1.3.24. Interface for SBO goods receipt im-/export

None

5.1.3.25. Interface for sbo item master data im-/export

ISboItemMasterDataInterface – Default

5.1.3.26. Interface for SBO incoming payment im-/export

None

5.1.3.27. Interface for SBO purchase credit note im-/export

ISboPurchaseCreditNoteInterface – Default

5.1.3.28. Interface for SBO purchase delivery im-/export

ISboPurchaseDeliveryInterface – Default

5.1.3.29. Interface for SBO purchase invoice im-/export

ISboPurchaseInvoiceInterface – Default



5.1.3.30. Interface for SBO production issue im-/export

None

5.1.3.31. Interface for SBO production receipt im-/export

None

5.1.3.32. Interface for SBO purchase return im-/export

ISboPurchaseReturnInterface – Default

5.1.3.33. Interface for SBO purchase order im-/export

ISboPurchaseOrderInterface – Default

5.1.3.34. Interface for SBO sales credit note im-/export

ISboSalesCreditNoteInterface – Default

5.1.3.35. Interface for SBO sales delivery 2 im-/export

None

5.1.3.36. Interface for SBO sales delivery im-/export

ISboSalesDeliveryInterface – Default

5.1.3.37. Interface for SBO sales invoice im-/export

ISboSalesInvoiceInterface – Default

Last update:2018/03/1212:56



5.1.3.38. Interface for SBO sales return im-/export

ISboSalesReturnInterface – Default

5.1.3.39. Interface for SBO sales return 2 im-/export

None

5.1.3.40. Interface for SBO sales order im-/export

ISboSalesOrderInterface – Default

5.1.3.41. Interface for SBO warehouse transfer im-/export

None

5.1.3.42. Open Sales Orders Controller

OpenSalesOrderController - Controls the open sales orders

This shows all approved sales orders with active business partners and with open lines.

Fields to sort by in GUIDefine the field(s) the screen should be sorted on. The value to enter is adjustable.



However 2 predefined options can be chosen:

CardCode in Ascending order●

DocDueDate, Cardcode both in Ascending order.●

OpenSalesOrderController - Open sales orders that are in stock

Shows all approved sales orders with active business partners and with items that are in stock.

Fields to sort by in GUIDefine the field(s) the screen should be sorted on. The value to enter is adjustable.However 2 predefined options can be chosen:



*This option will become obsolete. Please use the option Open sales orders with stock status*

OpenSalesOrderController - Open sales orders with stock status

Show all approved sales orders with active business partners and with items that are in stock. This willalso check if partial deliveries are allowed.

Last update:2018/03/1212:56



Fields to sort by in GUIDefine the field(s) the screen should be sorted on. The value to enter is adjustable.However 2 predefined options can be chosen:



Show undeliverable ordersWhen checked, the system will also show sales orders that cannot create a proposal, meaning allopen orders are shown.

OpenSalesOrderController - Open sales orders controller custom

This contoller uses a view to show the data on the screen.This means it is customizable what to show on the screen.

Localization keyThis is the key that is used for the translation of the grid.

Order byDefine the field(s) the screen should be sorted on.

View nameThe view can be customized, but the following fields are required:

ObjType●

DocEntry●

DocDueDate●

PmxWhsCode●

CardCode●



5.1.3.43. Purchase delivery generator

Purchase delivery generator

Allow to enter reason on purchase deliveryThis option enables you to enter a reason during reception on the handheld device. This option couldbe used for example to identify that there was no label found on the logistic unit and you want torecord why the label was not scanned.

Allow to exceed ordered quantity?If set to false, it will not be possible to receive more than what was ordered. This check is done on thescanner application.

Allow to select batch?If this is set to true, the system will propose all batch numbers that are currently in stock for the itemto receive. The user can still enter another batch number if he wants.

Ask user to print labels? (Y/N)If this is set to true, during the reception flow the user will be asked if he wants to print labels or not.When disabled, the system will not ask, and perform the printing as normal.

Auto reserve stock when purchase order is linked to sales order?A purchase order can be linked to a sales order. If this setting is set to true, the system will lock thereceived stock for this sales order. So if a pick list is made for that sales order, the system will use thelocked stock to pick. All quantities received will be locked, even if more quantity is received than what

Last update:2018/03/1212:56



was on the purchase order.When performing cross docking, this option should be checked, so the system will use the receiveditems.

Auto select internal batch based on batch number?If this is ticked, the system will not ask for an internal batch number if there is one found for theentered/scanned batch number.

Check data in UDF’s from PO line?If this is ticked, the system will check if the correct data has been entered on the scanner.If the data is incorrect, a warning will be shown. The possible data to check: Batch number, Batchnumber 2, Best before date, Serial number.On the scanner the selection of the item to receive will now be done based on PO line, instead ofgrouping it on item.

Cross-docking pick list typeFor cross docking, the received goods will be delivered immediately based on the linked sales order ofthe purchase order. To do this, a pick list will be generated. To have a distinction between pick liststhat are created for cross-docking, you can provide a pick list type.

Purchase line remarks view nameThe view to be used to get the line remarks that need to be shown on the scanner.This view needs at least these columns:

ObjType●

DocEntry●

LineNum●

ItemCode●

The view can return multiple rows/columns for the same document.The screen to show the remarks will then show the data in multiple rows/columns.

Receive all items in one purchase delivery?If set to true, the system will try to make 1 purchase delivery for all the entered data on reception. Soat reception the user needs to fill in all the data for each logistic unit. After all data has been enteredthe system will create the purchase delivery. Because the logistic labels need to be printed after thedata has been entered for each logistic unit, the printed label is not based on the actual stock in thesystem. So if some logistic units have been printed, but for some reason there was an error whilecreating the purchase delivery, the labels will not correspond to stock in the system. The user willneed to enter the data again to create the purchase delivery. But now he can use the already printedlabels to enter the data.If set to false, a purchase delivery is made for each logistic unit.

Receive on location instead of dock?By default Produmex will receive the goods on the selected dock. But it is possible to let the useridentify another location. In this case the items are stored directly on the warehouse location, and noput away is created.

Remarks view nameThe view to be used to get the remarks that need to be shown on the scanner.This view needs at least these columns:



ObjType●

DocEntry●

The view can return multiple rows/columns for the same document.The screen to show the remarks will then show the data in multiple rows/columns.

Show reserve invoices for purchase order selection?When set to true, purchase reserve invoices are also shown in the selection of the purchase orders onthe thin client.

Take the rate of the base document?By default SAP uses the current exchange rate. If this setting is set to true, Produmex will use theexchange rate defined on the purchase order instead of the current exchange rate.

5.1.3.44. Picklist controller

Pick list controller - Controls the pick list

Ad hoc picking

Last update:2018/03/1212:56



Route picking picklist order byThe sorting of picklist when picking for a route during ad hoc pickingOptions:

Order by priority, due date and doc entry●

Order by sequence on route: forward●

Order by sequence on route: reverse.●

Ad hoc picking: Keep picking same item? (Y/N)If this is set to true, the system will keep asking to pick the chosen item until everything is picked forthat item.If set to false, after picking an item, the system will go to the overview screen of all items to pick, sothe user can select the next item to pick.

Ad hoc: Auto fill pick quantity? (Y/N)When this is set to true, the quantity to pick will be entered in the screen to enter the quantity.Else the quantity will be 1, or when the maximum quantity is less than 1, the maximum quantity isshown.

Ad hoc: Force to scan SSCC? (Y/N)If this option is enabled, the user needs to scan the SSCC when performing item picking.

Allow ad hoc picking from bulk locations?This option enables the confirmation message at the end of the picking that all the items are picked.

Allow confirmation that ALL goods were pickedThis option enables the confirmation message at the end of the picking that all the items are picked.

Auto move SSCC on a customer-collected related moveWhen scanning an SSCC during ad hoc picking – customer collect, the SSCC is automatically moved tothe dock instead of asking the user if he wants to move the complete SSCC.

Choose dock on ad hoc picking?When this option is checked, the system will ask the user to select a dock where he is going to pick to.This is used in the ad hoc picking flow for the options Route and Pick list. The selected dock is storedon the route/pick list.

Reason requirements when skipping first location (Ad hoc picking)The ad hoc picking flow will suggest a number of locations. Those locations are sorted, so to firstlocation is the best location to take it from. If the user wishes to pick from another location, it ispossible to let the user enter a reason if it does not match the first location (Docks are not consideredas a first location).Options:

No reason●

Requires user-entered reasontext: Free text, entered by user, minimum 10 characters●

Requires selected reason from list●

Function/SP name to get the locationsThe function/stored procedure that is used to get the locations for ad hoc picking.

Input parameters on SQL:



@pmxWhsCode●

@itemCode●

@batchToPick●

@separator●

@pickListDocEntry●

You can check the input parameters in the standard function:PMX_FN_GetAllLocationsForItemForAdHocPicking

Input parameters on HANA:

p_pmxWhsCode●

p_separator●

p_pickListDocEntry●

You can check the input parameters in the standard SP:PMX_SP_GetAllLocationsForItemForAdHocPickingInTmp

Function/SP name to get the location sequenceThe function/stored procedure that is used to get the sequence of the locations.

Input parameters on SQL:

@pmxWhsCode nvarchar●

@itemCode nvarchar●

@batchToPick nvarchar●

You can check the input parameters in the standard function:PMX_FN_GetFirstSequenceForLocationsForItemForAdHocPicking

Input parameters on HANA:

p_pmxWhsCode nvarchar●

p_pickListDocEntry●

You can check the input parameters in the standard SP:PMX_SP_GetFirstSequenceForLocationsForItemForAdHocPicking

View name to get the productsThe view that is used to get the products to be picked. If no value is entered, the standard query isexecuted. This view needs at least these columns:

DocEntry●

PmxWhsCode●

ProductCode●

ProductDescription●

ManBtchNum●

HasBestBefore●

GTIN●

DefaultLocationCode●

BaseLine●

BaseEntry●

LocationCodes●

Last update:2018/03/1212:56



Sequence●

batchToPick●

StillToPick●

QuantityPerUom●

General

Allow multiple customers on SSCC?If set to true, the system will allow to put stock for multiple customers/delivery addresses on the sameSSCC. This means that when you have a wave for multiple customers, the user is not forced to pick ona moveable location and going through the pack station.

Allow to create master SSCC (Y/N)If enabled, a master SSCC can be created. A master SSCC is a single logistic unit that containsmultiple sub-logistic units.

Auto fill quantity for packaging types?If set to true, the quantity to pick will be automatically entered instead of a zero.

Copy non-inventory items to reserve invoice?If set to true, the system will copy non-inventory items to the reserve invoice when creating reserveinvoices from pick lists.

Disable selection of items? (Y/N)If set to true, it will not be possible to select items on flows. The user will always have to scan abarcode for the item selection.

Force the user to pick full pallet? (Y/N)Allows to define whether or not the user will be forced to pick a full pallet of items that contains thesame or a lower quantity than the quantity that has to be picked for the pick list. Example: if aquantity of 60 has to be picked, and if a full pallet of 40 that answers the best before date and batchnumber criteria is available, this full pallet will be selected by the system for picking.Picking will occur by scanning the SSCC. The quantity will not be asked. The SSCC will remain thesame as the original SSCC.If this is set to false, the user will need to pick it as ‘item picking’.

Please note that this setting does not apply when assigning stock to the pick list!This setting is only used AFTER the stock is assigned to the pick list, and the user is going to pick thestock on the scanner.

Make picklist ready before print? (Y/N)The ‘Make pick list ready’ functionality allocates stock on location level to the pick list. So if a pick listreport needs to have the locations filled in, this option should be enabled.

Only pick items on location on same or lower level as dock? (Y/N)If set to true, the system will only create a pick list for items it can find on storage location defined onthe same or lower level as the dock selected on the pick list proposal. The levels are defined by thezones those locations are in.

Time to show ‘item is picked’ message?



The number of seconds the ‘item is picked’ message is shown on the scanner:Possible values:

Negative values: The message is not shown.●

Value 0: The message will remain visible until the user clicks the ‘OK’ button●

Positive values: The message will remain visible for the entered number of seconds.●

Create replenishment orders after picking? (Y/N)If enabled, a replenishment order is generated after the picking is completed for the source location,if the following conditions are met:

The location can be replenished●

There is a minimum quantity set for a picked item●

The stock for item on the location reaches the minimum quantity●

The replenishment after picking is supported in the following flows:

Picking●

Zone picking●

Multi picking●

Ad hoc picking●

For the item based replenishment generator, system will try to create replenishment orders for alllocations. The default replenishment generator will only try to create replenishment orders for thelocations where goods were picked from.

JOIN-sql for custom wave description for scannerIf the ‘Custom wave description fields for scanner’ option contains fields that are not used in thedefault query, the user needs to define the JOIN query here.

Custom wave description fields for scannerHere the user has the possibility to enter a custom wave description that will be shown on thescanner. This text will be added to the select statement to select the waves on the Picking flow.If the fields in the description are not on tables used by the default query, the option ‘JOIN-sql forcustom wave description for scanner’ need to have the correct join to the table.The standard available tables are:

ORDR●

OUSR●

PMX_OSEL●

PMX_OSWA●

PMX_PLHE●

PMX_PLLI●

PMX_PLPL●

PMX_WAVE●

PMX_WALO (Zone picking only)●

Make sure the selected fields are casted to nvarchar if required. To add thePMX_PLHE.PickPackRemarks field for example, fill this in the input box :CAST(“PMX_PLHE”.“PickPackRemarks” as nvarchar (2000))

MultiPicking

Last update:2018/03/1212:56



Multi picking: Set movable location at start of picking? (Y/N)When this is enabled, then during multi picking all the movable locations need to be assigned to apick list before staring to perform the picking.If disabled the movable location is asked when the first item of a certain pick list is picked.

Multi picking: Allow to select wave? (Y/N)When this is enabled, then during multi picking the user can select the wave instead of scanning apick list.

All, except Ad hoc picking

Ad hoc alternate item? (Y/N)If this is set to false, the system will show a list of alternate items to choose from.If this is set to true, the system will allow the user to enter any data when performing alternatepicking, and the system will check if the entered data is allowed.

Allow cycle count on alternate picking? (Y/N)If this option is enabled, the user has the possibility to perform a cycle count on the original picklocation in case of alternate picking form a different location.

Allow to identify the SSCC to pick on?If set to true, the system will allow the user to scan an SSCC number he wants to use to put thepicked stock on.

Allow to select the item to pick?Enables the option to select an item to pick instead of letting the system choose the first item.

Alternate: Show locked quantity for current line? (Y/N)When this is checked, the system will also show the item that was locked for the current pick list linein the list of alternate items.

Auto fill quantity (No packaging types)? (Y/N)If set to true, the quantity to pick will be automatically entered.If set to false, the quantity to pick will be zero. And in case a barcode was scanned in the itemidentification screen, the quantity will be 1, because there was already an item scanned.This is for items without packaging types.

Auto select batch/BBD on picking?Enables the option to automatically select a Batch/BBD.

Auto select the wave?If set to true, the system will select the wave. If set to false, the user can select the wave he wants topick.

Auto selection of moveable location during picking? (Y/N)If set to true, the system will automatically select the moveable location. But this is only when there is1 available moveable location. In case of full pallets, no moveable location will be used.

Can the user pick bulk quantity from bulk location? (Y/N)If ticked the user can pick bulk quantities defined on the item master data from bulk locations.



Can the user pick full pallet from bulk location? (Y/N)Normally bulk locations are not considered when allocating stock to a pick list. However this flagmakes it possible that full monolot pallets at bulk locations (containing items that match the bestbefore date and batch number criteria) can be picked by the operator.The sorting of the stock to use depends on this setting and the option ‘Must user first pick full palletfrom bulk’.More information at: Pick list.

Consolidate items to pick?If set to true, items that have the same Batchnumber/BBD/Quality status/Location/… will be picked inone action, instead of a pick action by pick list line.This option is used in ‘Picking’ and ‘Zone picking’ flow.

Copy batch number when selecting alternate item? (Y/N)When the user wants to select an alternate batch, does the system need to copy the original batchnumber from the pick list?Remark: If on the base document line a batch number is set, the batch will always be copied whenselecting alternate items.

Item picking: Force user to scan SSCC when stock is on SSCC? (Y/N)When this setting is enabled, the user will have to scan the SSCC if the stock he is picking is on anSSCC.This setting refers to 'Item picking' and not full pallet picking.It will show an additional screen to scan the SSCC before proceeding to selection of batch, or enteringthe quantity.

Must the user first pick full pallet from bulk location? (Y/N)Normally bulk locations are not considered when allocating stock to a pick list. However this flagmakes it possible that full monolot pallets at bulk locations (containing items that match the bestbefore date and batch number criteria) can be picked by the operator.This option forces to first take full pallets from a bulk location before using pick locations.The sorting of the stock to use depends on this setting and the option ‘Can user pick full pallet frombulk’.More information at: Pick list.

Skip screen to identify the pick location? (Y/N)When this is enabled, the user does not need to identify the pick location.Users can immediately identify the item to pick. (The pick location is visible in that screen)

Stock order byCustom 'ORDER BY' clause for when the pick list is allocating stock to the pick list line.This is not applicable for ad hoc pickingIt adds the value to the ORDER BY clause of the query to get the stock. The text 'ORDER BY' does notneed to be added to the value.Any text can be entered here, however there are 2 predefined options:

*DEFAULT*●

This option will use the sorting as it is currently in the system❍

*BIGGEST PALLET FIRST*●

The pallet with the biggest quantity will be assigned first.❍

If there are 2 pallets with the same quantity, the oldest LUID will be taken first.

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

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

Last update:2018/03/1212:56



When stock is not on an SSCC, the quantity not on an SSCC is still regarded as if it would be on anSSCC, and it will be used first in case of equal quantity.

“Quantity”, “IsPickLoc” DESC, “LogUnitIdentKey_IsNull” DESC, “LogUnitIdentKey”, “InternalKey”●

This option will take lowest quantity, pick location, no LUID, LUID❍

For more information please see: 1.2. Stock order by.

Wave order bySorting of waves on the picking flowsOptions:

Order by Priority, due date, wave key●

Order by due date, priority, wave key●

Only pick on 1 SSCC? (Y/N)If enabled, the system will auto select an SSCC when there was already an SSCC created for the wave.This is useful for when users need to go out of the picking flow, and continue at a later time.

Pick items order byHow are the items to pick sorted on the scanner?Options:

Order by Full LUID, sequence, no location: First full pallet, then the sequence of the location, then all●

lines without a location.Order by Full LUID, picked item, location code: First full pallets, then picked items, then location●

code. This means that when ItemA and ItemB needs to be item-picked on several locations, thesystem will first pick all quantities of ItemA, regardless of where it is stored. (Full pallets are stillpicked first)Order by Sequence, Location code, Full LUID, : First Sequence of the location, then the code of the●

location, then full pallets.Order by Custom stored procedure: The sorting is based on a custom SP.●

It uses the SP defined in the setting below.

Pick items order by - Stored procedure nameThe name of the stored procedure that is used for the custom order by.Used for the picking and zone picking flow.The input of this stored procedure is the wave key. SQL: @waveKey, HANA: p_waveKeyThis SP needs to be in the extra DB.If this SP does not return all line numbers to pick, the system will still add those lines to be picked, butin the order:

Order by Full LUID, sequence, no location.●

Packing

Time to show pick/pack remarks on packing?The number of seconds the pick/pack remarks are shown in a popup window in the packaging client:

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



Possible values:




Picking

Picking: Keep picking same location (Y/N)When this is set to true, the system will not ask the user to identify the pick location again when thenext item to pick is in the same location.

Zone picking

Lock wave by zone/user (Zone picking)If this is set to true, the system will lock all items to pick on the zone for the current user instead ofonly locking the item/zone he is picking from.This is used in the ‘Zone picking’ flow.

Only show completely unlocked waves in case of zone picking?If set to true, the user can only see wave that have no locking for a user on it. This is used in the‘Zone picking’ flow.

5.1.3.45. Pick List Proposal generator

PickListProposalGenerator - Generates picklist proposals

Last update:2018/03/1212:56



Add empty rows for items with insufficient stock? (Y/N)If set, the system will add rows with quantity = 0 to the proposal when there is no stock available.This can be used to quickly see if all stock is available.

Add empty rows for items with quantity to reserve zero? (Y/N)If set, the system will add rows with quantity = 0 to the proposal when there is nothing to reserve.This can be used to quickly see if all stock is available. Useful in custom proposal generator.

Allow broken-up (incomplete) sales-item BOM's? (Y/N)If set, the system will not add components from a BOM when there is one or more componentmissing. The check is done based on the original BOM.

Base document - order byWhen proposals are made, it is possible to do this for several orders in one time.The system will group them by customer, ship to, and pick list type and item pick list types.This option is to sort those orders within the same group.Options:

Order by doc due date,●

Order by line delivery date, doc entry,●

Order by doc entry●

Force the proposed batch? (Y/N)When this option is set to true, the batch the system proposes will be forced. This is used on ad hoc



picking, in combination with the option ‘Allow multiple batches’ on a document line. When both aretrue, ad hoc picking can only pick from that batch, instead of any batch.

Serial numbers stock order byThis option handles what stock should be taken first to put on the proposal, for serial numbered itemswith track location.Options:

Use default order by●

The sorting of stock to allocate for serial numbered items with track location is the one defined in the“Stock order by” option.

Order by serial numbers (alphanumerical)●

The sorting of stock to allocate for serial numbered items with track location is: Oldest serial numberfound on LUID (serial numbers are sorted alphanumerically). The allocation is done on item-batch-LUID level.

Show pick list proposal info screen on incomplete proposal? (Y/N)When this option is set to true, an additional screen will be shown after creating a proposal, and notall stock is on the pick list proposal.The screen will show the information why not all stock was on a proposal.

Show proposals with pick lists on open doc. report? (Y/N)When this option is set to false, the open documents report for pick list proposals will not showproposals that have already a pick list.

Stock order byThis option handles what stock should be taken first to put on the proposal.Options:

Order by FEFO on a pick location●

The sorting of stock to allocate is: Expiry date, Batch number, batchnumber2. The allocation is doneon item-batch level.

Order by FEFO ITRI on a pick location●

The sorting of stock to allocate is: Expiry date, Batch ID. The allocation is done on item-batch level.

Order by LUID●

The sorting of stock to allocate is: Has LUID, LUID, Expiry date, Batch number, batchnumber2.The allocation is done on item-batch-LUID level.

Order by Bulk, Full LUID, LUID, BBD, Itri●

The sorting of stock to allocate is: Non Pick location, Is full pallet, Has LUID, LUID, Expiry date, Itri.The allocation is done on item-batch-LUID level.

Order by Bulk, Full LUID, BBD, Itri, LUID●

The sorting of stock to allocate is: Non Pick location, Is full pallet, Expiry date, Itri, Has LUID, LUID.

Last update:2018/03/1212:56



The allocation is done on item-batch-LUID level.

Try to group items on 1 proposalWhen this is checked the system will try to group the items on 1 proposal. This means that each timea proposal is being made, it will try to close the existing one (If no pick list has been created yet), andcreate a new one for all remaining items.When this is not checked, the system will always try to create a new proposal.

PickListProposalGenerator - Generates picklist proposals grouped by customer-address If multiplesales orders are selected for the same customer/address, they will be grouped into 1 proposal.

Add empty rows for items with insufficient stock? (Y/N) If set, the system will add rows with quantity = 0 to the proposal when there is not enough stockavailable. This can be used to quickly see if all stock is available.

Add empty rows for items with quantity to reserve zero? (Y/N)If set, the system will add rows with quantity = 0 to the proposal when there is nothing to reserve.This can be used to quickly see if all stock is available.

Allow broken-up (incomplete) sales-item BOM's? (Y/N)If set, the system will not add components from a BOM when there is one or more componentmissing.

Base document - order byWhen proposals are made, it is possible to do this for several orders in one time.This option is to sort those orders.



Options:

Order by doc due date,●

Order by line delivery date, doc entry,●

Order by doc entry●

Force the proposed batch? (Y/N)When this option is set to true, the batch the system proposes will be forced. This is used on ad hocpicking, in combination with the option ‘Allow multiple batches’ on a document line. When both aretrue, ad hoc picking can only pick from that batch, instead of any batch.

Serial numbers stock order byThis option handles what stock should be taken first to put on the proposal, for serial numbered itemswith track location.Options:

Use default order by●

The sorting of stock to allocate for serial numbered items with track location is the one defined in the“Stock order by” option.

Order by serial numbers (alphanumerical)●

The sorting of stock to allocate for serial numbered items with track location is: Oldest serial numberfound on LUID (serial numbers are sorted alphanumerically). The allocation is done on item-batch-LUID level.

Show pick list proposal info screen on incomplete proposal? (Y/N)When this option is set to true, an additional screen will be shown after creating a proposal, and notall stock is on the pick list proposal.The screen will show the information why not all stock was on a proposal.

Show proposals with pick lists on open doc. report? (Y/N)When this option is set to false, the open documents report for pick list proposals will not showproposals that have already a pick list.

Stock order byThis option handles what stock should be taken first to put on the proposal.Options:

Order by FEFO on a pick location●

The sorting of stock to allocate is: Expiry date, Batch number, batchnumber2.The allocation is done on item-batch level.

Order by FEFO ITRI on a pick location●

The sorting of stock to allocate is: Expiry date, Batch ID. The allocation is done on item-batch level.

Order by LUID●

The sorting of stock to allocate is: Has LUID, LUID, Expiry date, Batch number, batchnumber2.The allocation is done on item-batch-LUID level.

Last update:2018/03/1212:56



Order by Bulk, Full LUID, LUID, BBD, Itri●

The sorting of stock to allocate is: Non Pick location, Is full pallet, Has LUID, LUID, Expiry date, Itri.The allocation is done on item-batch-LUID level.

Order by Bulk, Full LUID, BBD, Itri, LUID●

The sorting of stock to allocate is: Non Pick location, Is full pallet, Expiry date, Itri, Has LUID, LUID.The allocation is done on item-batch-LUID level.

Try to group items on 1 proposalWhen this is checked the system will try to group the items on 1 proposal. This means that each timea proposal is being made, it will try to close the existing one (If no pick list has been created yet), andcreate a new one for all remaining items.When this is not checked, the system will always try to create a new proposal.

5.1.3.46. Pick list robot

None

5.1.3.47. Picking for production controller

IPickingForProductionController - Controles the picking for production

Allow continuous picking for productionIf set, the system will allow to pick production order lines, even if full quantity has been picked.

Picking order bySelect the sorting of the items to propose when performing picking for production.This option is used when no proposals are created for production (FEFO = BBD, BatchNumber,BatchNumber2)Options:

FEFO_LUID_PickProduction: Order by FEFO, Non pick location, LUID, no LUID●

LUID_PickProduction: Order by LUID, No LUID, Non pick location, FEFO●

FEFO_FullPallet_PickProduction: Order by FEFO, Non pick location, Full LUID, LUID, no LUID●

FEFO_PickProduction: Order by FEFO, Non pick location, no LUID, LUID●

Create proposal for pickingIf set, the system will create pick lists for the production orders. This will lock stock for this pick list(proposal). If ticked you can create proposals and pick lists for production orders with the samefunctionality as the pick lists for sales.

Force all ingredients to be on a proposal before creating a pick list?If set, the system will check that all ingredients on of the production orders are available on an openproposal.



If not, a pick list cannot be created.

5.1.3.48. Production controller

IProductionController - Controls production orders

Allow starting production order on production receipt flow? (Y/N)The normal process using the production manager, is to start the production order on the productionmanager. On the production receipt flow, only started production orders are shown.If this is set to true, the user will be able to start the production order on the production receipt flow.If there are locations that need to be lined up, the system will only line them up if on the item masterdata the option to auto line up has been set. Otherwise the lined up locations will need to be set onthe production manager.

Allow to move stock to prod. line from rest location? (Y/N)By default the stock is moved from the input to the production line. By setting this option to true, theuser can also move stock from the rest location to the production line.

Auto fill consumed qty from prepared qty on stop production? (Y/N)This option is used in the production flow with immediate consumption. If components have beenprepared (Weighed, …) and it is not for the theoretical quantity, but within the tolerance, the systemwill fill in the prepared quantity, instead of the theoretical quantity.

Last update:2018/03/1212:56



Auto move all linked items to BOM? (Y/N)If this is set to true, all items that are on the production order line will be moved from the inputlocation to the production line when selecting the production order on the device. This will move allquantities for those items.

Automatically close production orders on completion? (Y/N)If this is set to true, the production order will be closed when all planned quantity for the productionorder has been reached.This is used in the ProductionFlow and ProductionReceiptFlow.

Confirm produced quantity after production? (Y/N)If this is set to true, the user will need to confirm the quantity he has entered to produce if it deviatesfrom the allowed quantity (See item master data configuration). The system will show the productdescription + quantity on the screen to confirm.

Hide move all item buttons? (Y/N)If this option is enabled, when adding the items to use in the production client, there is only thepossibility of ‘Move an item’ instead of ‘move an item’, move all items linked to the production order’and ‘move all items’.

Skip consumption screen on flow for linked components?If this is set to true, all screens for consumption on the production flow for items that are prepared(Weighed, …) will be skipped.

Split produced quantity into logistic units of default sizeIf this is set to true, the system will create a number of logistic units, based on the default quantitydefined on the item master data. If the default quantity for production is set, the system will take thatquantity, otherwise the default quantity is used.

Use waste? (Y/N)When producing, it is possible to enter waste quantities. When set to true, the user will be able to setwaste quantities when producing according to ‘Production with immediate consumption’.

Allow waste to be editable when finishing production on production manager?If this is set to true, the user will be able to also edit the columns for the waste quantity.This option is used on the production manager.

Print labels for open partial weighing when doing ‘Complete weighing’When there is still open quantity and the user presses ‘Complete weighing’, do labels need to beprinted?Options:

Yes●

No●

Ask●

Proceed with current production order after entering quantity on prod. receipt flow?The user can proceed with the current production order on the production receipt flow when thisoption is enabled.When this option is enabled, the production flow will go to the screen to enter quantity/serial numbersafter a logistic unit has been created instead of going to the selection of production order screen.



Stock row limitation on stop PRD (PRD manager)The number of rows shown for used stock when stopping the production on the production managercan be limited. When putting a negative number here, the system will show all rows.

5.1.3.49. QS reception contr. on company

IQualityStatusReceptionController - Gets the quality status for reception

When receiving, the default quality status defined for the supplier on the Produmex Purchase tab ofthe Item Master Data is used.

If there is no quality status set for the supplier, the default quality status defined on the ProdumexPurchase tab of the Item Master Data is used.

If on the item there is no default quality status set, the default quality status on company level isused. (Produmex Organizational Structure → Company → Tabpage ‘Defaults’).

IQualityStatusReceptionController - Gets the quality status for reception by batch

This controller is more complex. The system will first check the batch that is being received. If thisbatch is not present in the system, the default quality status defined on the item is used. If on theitem there is no default quality status set, the default quality status on company level (ProdumexOrganizational Structure → Company → Tabpage ‘Defaults’).

Last update:2018/03/1212:56



If this batch is present in the system, the system will check if the stock of this batch has the releasedquality status defined on the item. If on the item there is no released quality status set, the releasedquality status on company level. If the stock has the released quality status, the stock to receive willalso get this quality status, because this batch has already been approved.If the released quality status is not found in the system, the stock to receive will get the defaultquality status.

5.1.3.50. Replenishment generator

IReplenishmentGenerator - Generates item based replenishment orders

This replenishment generator starts from the configuration on the item master data. It will try togenerate orders where the ‘Replenishment Quantity on pick locations’ (OITM.U_PMX_RQPL found onthe item master data produmex sales tab) is greater than 0.If there is enough stock on pick locations, no order will be generated.

In case of setting a destination location for the replenishment order:When the generator has calculated the quantity that should be replenished, it will try to find all picklocations that have this item in the ‘Can be replenished’ list and where the minimum quantity for thatitem on the location is higher than zero. It will try to create orders on those locations, ordered by thesequence defined on the location.



If no location can be found, or if there is enough stock on the location(s), (taking in account themaximum quantity on the location), it will not create a replenishment order.

Close open orders first? (Y/N)When this is checked, the system will first close all open replenishment orders when running thereplenishment tool.

No destination location on order? (Y/N)When this is checked, the system will create replenishment orders without setting the destinationlocation.The user who executes the replenishment will be able to select a pick location.

Pick list due date range (in days)The pick list due date range in days. If ‘Take in account pick lists’ is checked, this setting defines thedue date range of all the pick lists that should be taken in account.

Remove SSCC on execution? (Y/N)When this setting is enabled, the executed move will remove the SSCC of the stock.This means that the stock that will be stored on the pick location will not contain an SSCC anymore.This removal of the SSCC can only happen if there is no locking for this SSCC.

Select zone on replenishment flow? (Y/N)If enabled, the user has to select the zone before selecting the replenishment order. After a zone isselected, only replenishment orders for locations in the zone can be selected. The zones that areshown are the parent zones of the locations that need replenishment.Please note: If the ‘No destination location on order’ option is enabled, the zone will not be askedregardless of the ‘Select zone on replenishment flow’ setting.

Skip stock when LUID is blocked? (Y/N)When this option is checked, the blocked LUID will not be moved to the pick location. This can be usedwhen the system is configured that the pick list proposal generator already locks stock based on theLUID and if on the pick list controller the option to pick full pallet from bulk location is allowed.

Stock coverage in daysIn combination with the configuration on Item master data it will calculate the needed quantitieswithin the days defined in the stock coverage. If for example you have a stock coverage of 15 days,the generator will calculate the needed quantities for those 15 days, and create replenishment orders(if needed) so there will be enough stock on the locations for at least 15 days.

Stock order byThe order of the stock to be used:

Order by BBD, Batch1, Batch2 (FEFO)●

Order by ItriKey, No LUID, LUID (FIFO)●

Order by BBD, ItriKey (FEFO_ITRI)●

Take in account pick lists? (Y/N)When this option is checked, items that are on pick lists (with a due date in range) will be subtractedfrom the current available stock on the location.

CALCULATION:

Last update:2018/03/1212:56



A replenishment order will be generated when: (Stock on pick location – # on pick list) < = (Est. salesqty * (Stock coverage/#days in month))

Configuration 1:

ItemA: Quantity on pick locations = 120 (OITM.U_PMX_RQPL)●

ItemA: Estimated sales quantity by month = 100 (OITM.U_PMX_ESQM)●

ItemA: Sum of Stock On Hand on pick locations = 70●

ItemA: Sum of Items on a pick list (in range) = 10●

Generator: Stock coverage = 15●

In this example:(70 – 10) < (100 * (15/30)) → 60 < 50So we need 50 items to be picked in the 15 days, but there are still 60 available, so no replenishmentorders need to be generated.

Configuration 2:

ItemA: Quantity on pick locations = 120 (OITM.U_PMX_RQPL)●

ItemA: Estimated sales quantity by month = 100 (OITM.U_PMX_ESQM)●

ItemA: Sum of Stock On Hand on pick locations = 40●

ItemA: Sum of Items on a pick list (in range) = 15●

Generator: Stock coverage = 15●

In this example:(40 – 15) < (100 * (15/30)) → 25 < 50So we need 50 items to be picked in the 15 days, and there are only 25 available, so replenishmentorders need to be generated.

The number of items to be replenished is calculated:(Qty on pick locations – (Stock on pick locations - # on pick list))

In this example:(120 – (40 – 15)) = 95

So 95 items need to be replenished from bulk locations to pick locations.

IReplenishmentGenerator - Generates replenishment orders



This replenishment generator takes in account the items defined on the pick location. When the stockgoes below the minimum quantity, it will generate a replenishment order.The system will create an order so the minimum quantity (Defined on the location) is exceeded afterthe execution of the replenish order. The quantity will be a multiple of the Replenish Qty.

Close open orders first? (Y/N)When this is checked, the system will first close all open replenishment orders when running thereplenishment tool.

Pick list due date range (in days)If ‘Take in account pick lists’ is checked, this setting defines the due date range of all the pick liststhat should be taken in account.

Remove SSCC on execution? (Y/N)When this setting is enabled, the executed move will remove the SSCC of the stock.This means that the stock that will be stored on the pick location will not contain an SSCC anymore.This removal of the SSCC can only happen if there is no locking for this SSCC.

Select zone on replenishment flow? (Y/N)If enabled, the user has to select the zone before selecting the replenishment order. After a zone isselected, only replenishment orders for locations in the zone can be selected. The zones that areshown are the parent zones of the locations that need replenishment.

Skip stock when LUID is blocked? (Y/N)When this option is checked, the blocked LUID will not be moved to the pick location. This can be used

Last update:2018/03/1212:56



when the system is configured that the pick list proposal generator already locks stock based on theLUID and if on the pick list controller the option to pick full pallet from bulk location is allowed.

Stock order byThe order of the stock to be used:

Order by BBD, Batch1, Batch2 (FEFO)●

Order by ItriKey, No LUID, LUID (FIFO)●

Order by BBD, ItriKey (FEFO_ITRI)●

Take in account pick lists? (Y/N)When this option is checked, pick list lines in status 'Not ready' with a due date in range will besubtracted from the current available stock on the location. This means that only pick list lineswithout an allocation on location level will be taken into account.

CALCULATION:

A replenishment order will be generated when: {(Stock on pick location - # on pick list) < = Minimumquantity}.

Example:

Stock on pick location= 25●

Minimum quantity = 20●

Maximum quantity = 60●

Replenish quantity = 10●

# on pick list = 12●

Configuration 1: Pick list not taken into account/ not within the due date rangeIn this example: 25 < 20Since the stock on the pick location exceeds the minimum quantity, no replenishment order needs tobe generated.

Configuration 2: Pick list taken into account and within the due date range In this example: 25-12= 13 < 20If we take into account the pick list, the quantity on the pick location will fall below the minimumquantity, therefore a replenishment order needs to be generated.

The quantity to replenish in the order will be a multiple of the Replenish Qty. It will be calculated by:{n*(Replenish Quantity) > = Minimum Quantity - Stock on pick location + # on pick list} where n is anon-negative integer.

Example:

Stock on pick location= 5●

Minimum quantity = 20●

Maximum quantity = 60●

Replenish quantity = 10●

# on pick list = 12●

Pick list not taken into account: n*10 >= 20-5 → n*10 >=15



Because the quantity to replenish must be the multiple of the Replenish quantity, 20 items need to bereplenished from bulk locations to pick locations.

Pick list taken into account: n*10 >= 20-5+12 → n*10>=27Because the quantity to replenish must be the multiple of the Replenish quantity, 30 items need to bereplenished from bulk locations to pick locations.

5.1.3.51. On release of route controller

None

5.1.3.52. Route controller

RouteController – Controls the routes

The settings below is to customize the grids on the route planning. There is a view to get the data toshow on the grid. The order in which the columns are on the view, will also be the order in which theywill appear in the grid.Per view there are some mandatory fields, so the system knows what column to use for certainvalues.

Pick list (proposals) without route (Bottom-left grid):

Required fields:

DocType, DocEntry, PickListStatus, PmxWhsCode●

View name – Open pick list (proposals)The name of the view that will be used.

Order by – Open pick list (proposals)The order by for the view. The text ‘ORDER BY’ does not need to be entered here.

Localization key – Open pick list (proposals)The localization key to use. This is used to translate the grid.Below is a reduced translation tag for the standard grid.It shows how to translate, or if needed how to hide a columns.


<LocalizationKey>Logex.AddOn.RoutePlanningControl.GrdPicklistsWithoutRoute</LocalizationKey> <ApplicationTypeCode>SBOGUIAP</ApplicationTypeCode> <LocalizationProperties> <PmxLocalizationProperty>

Last update:2018/03/1212:56



<Canceled>False</Canceled> <LocalizationProperty>Columns[1].HeaderText</LocalizationProperty> <ExtensionCode>CONVSTR</ExtensionCode> <LocalizationValues> <PmxLocalizationValue> <Canceled>False</Canceled> <LocalizationValue>Type</LocalizationValue> <LanguageCode>3</LanguageCode> </PmxLocalizationValue> <PmxLocalizationValue> <Canceled>False</Canceled> <LocalizationValue>Type</LocalizationValue> <LanguageCode>16</LanguageCode> </PmxLocalizationValue> </LocalizationValues> </PmxLocalizationProperty> <PmxLocalizationProperty> <Canceled>False</Canceled> <LocalizationProperty>Columns[13].Visible</LocalizationProperty> <ExtensionCode>CONVBOOL</ExtensionCode> <LocalizationValues> <PmxLocalizationValue> <Canceled>False</Canceled> <LocalizationValue>False</LocalizationValue> <LanguageCode>3</LanguageCode> </PmxLocalizationValue> <PmxLocalizationValue> <Canceled>False</Canceled> <LocalizationValue>False</LocalizationValue> <LanguageCode>16</LanguageCode> </PmxLocalizationValue> </LocalizationValues> </PmxLocalizationProperty> </LocalizationProperties> </PmxLocalizationKey>

Route details (Right grids):

Required fields:

RouteDocEntry, RouteLineNum, Sequence, DocType, DocEntry, PickListStatus●

View name – Route detailsThe name of the view that will be used.

Localization key – Route detailsThe localization key to use. This is used to translate the grid.

Open routes (Top left grid):

Required fields:



DocEntry, PmxWhsCode●

View name – Open routesThe name of the view that will be used.

Order by – Open routesThe order by clause for the view. The text ‘ORDER BY’ does not need to be entered here.

Localization key – Open routesThe localization key to use. This is used to translate the grid.

Route header extra information:

This will show additional information for the route in the route planning screen.This view can contain multiple rows/columns for the route.All that data will be combined into 1 line of text.Values of rows/columns will be separated by the separators defined below.

Required fields:

DocEntry●

View name – Route details headerThe name of the route that will be used.

Order by – Route details headerThe order by clause for the view. The text ‘ORDER BY’ does not need to be entered here.

Column separator – Route details headerThe separator between columns.

Row separator – Route details headerThe separator between rows.

Routes are by default POD? (Y/N)When creating a new route, this setting will automatically set whether the route is used for the 'Proofof delivery' functionality.

5.1.3.53. Sales delivery note generator

SalesDeliveryNote Generator - Generates PMX sales shipping delivery

This functionality will book the delivery into a temporary table. The SAP sales delivery can be createdthrough a tool, or manually in SAP.

This generator will become obsolete

Last update:2018/03/1212:56



Allow loading of ready logistic units on not fully packed picklists? (Y/N)If set to true, the users will be able to already select an unfinished picklist on the shipping client, andalready start loading finished SSCC’s.

Allow shipping of partial LUID? (Y/N)If set to true, on the shipping flow, a button will be available to only ship a part of a picked SSCC. Theremainder will still be open on the pick list.

Group sales orders for the same customer to 1 delivery? (Y/N)When the delivery is made, it is possible according to the type of shipping: wave/route/… that thereare goods that come from different sales orders, for the same customer.If the option is set to true, only 1 delivery will be made for those sales orders.If set to false, a delivery by sales order will be made.

Group similar picklists? (Y/N)If set to true, during shipping the system will get all picklists that are available for the same customer,delivery address, dock, due date, … for the selected pick list.All SSCC’s for those pick lists can be loaded.

Grouping filter columnsEnter columns on which deliveries need to be grouped.When columns are added, the deliveries that will be created will be split when values in thesecolumns are different.Multiple columns can be split by ','



Join clause for grouping filterWhen the grouping filter columns are in a table that is not available in the standard query, a joinclause can be added to join to the missing table(s).This join clause will be fully added to the query, which means that the 'INNER JOIN', 'LEFT JOIN', …keywords need to be added to this value.

Example grouping filterWhen splitting on discount percentage of the sales order:Value for filter:

"ORDR"."DiscPrcnt"

Value for join clause:

INNER JOIN "ORDR" ON "ORDR"."DocEntry" = "GROUPED_TABLE"."SalesDocEntry"

SalesDeliveryNote Generator - Generates sales delivery notes

This generator will become obsolete

Allow loading of ready logistic units on not fully packed picklists? (Y/N)

Last update:2018/03/1212:56



If set to true, the users will be able to already select an unfinished picklist on the shipping client, andalready start loading finished SSCC’s.


Copy text lines from order to delivery? (Y/N)If set to true, text lines from the base document will be copied to the delivery.

Fill packing info in delivery? (Y/N)If set to true, the packing info will be entered in the delivery.This will be based on the SSCC/Master SSCC.(DLN7 & DLN8)


Group similar picklists? (Y/N)If set to true, during shipping the system will get all picklists that are available for the same customer,delivery address, … for the selected pick list.All SSCC’s for those pick lists can to be loaded.



Example grouping filterWhen splitting on discount percentage of the sales order:Value for filter: “DiscPrcnt”Value for join clause: INNER JOIN “ORDR” ON “ORDR”.“DocEntry” =“GROUPED_TABLE”.“SalesDocEntry”

SalesDeliveryNote Generator - Generates sales delivery notes in separate transactions



This means that for instance when delivering a route, all deliveries are created in a separatetransaction, instead of 1 transaction.This will lead to less long lasting blocks when creating deliveries.

Allow loading of ready logistic units on not fully packed picklists? (Y/N)If set to true, the users will be able to already select an unfinished picklist on the shipping client, andalready start loading finished SSCC’s.


Copy text lines from order to delivery? (Y/N)If set to true, text lines from the base document will be copied to the delivery.

Fill packing info in delivery? (Y/N)If set to true, the packing info will be entered in the delivery.This will be based on the SSCC/Master SSCC.(DLN7 & DLN8)


Group similar picklists? (Y/N)If set to true, during shipping the system will get all picklists that are available for the same customer,delivery address, … for the selected pick list.All SSCC’s for those pick lists can to be loaded.



Example grouping filterWhen splitting on discount percentage of the sales order:Value for filter: “DiscPrcnt”Value for join clause: INNER JOIN “ORDR” ON “ORDR”.“DocEntry” =“GROUPED_TABLE”.“SalesDocEntry”

Use Pmx sales shipping? (Y/N)If set to true, it will book the delivery into a temporary table. The SAP sales delivery can be createdthrough a tool, or manually in SAP.

Last update:2018/03/1212:56



The advantage of this setting is that the creation of the delivery is much faster.The disadvantage is that the stock remains on the dock, pick list is still open until the SAP delivery iscreated.Also when invoices need to be created immediately after the creation of the delivery, this settingcannot be enabled.

5.1.3.54. Sales return generator

Default sales return generator

Force mono lot pallet? (Y/N)If set to true, the system will not allow to have multiple items/batches on one SSCC. SO the user isforced to create a new logistic unit for each item.

5.1.3.55. Sample generator

Generates samples to supplier



This generator makes the sample orders if this is needed. A sample order is a sales order. This salesorder will be created for the customer linked to the business partner on the purchase delivery. Thelinked business partner can be set on the business partner master data.

5.1.3.56. Serial number controller

SerialNumberController - Control the serial numbers

Last update:2018/03/1212:56



Always entering serial numbers in uppercase? (Y/N)If set to true, the system will always put the entered serial numbers in upper case.

Ask for dest. loc. before entering serial numbers? (Y/N)When moving stock, the system normally first asks to scan the serial numbers before asking for thelocation.If the user wants to first ask for the destination location, this option can be set.

Picking: Warn when serial number has been sent in the past? (Y/N)When this is enabled, the user will see a warning when this serial number has already been used in adelivery or pick list.This check happens for the item, and does not take into account the batch.

5.1.3.57. Warehouse automation controller

None

5.1.3.58. Move controller



Default move controller

Ad hoc move

Always scan product? (Y/N)If enabled, the item must be scanned during an ad hoc move on the scanner, even if it is the onlyitem on the SSCC/location.

General

Return to next move when performing ad hoc move? (Y/N)If set to true, the system will go back to a screen to perform the next move instead of going back tothe start of the ad hoc move flow. This allows the user to quickly perform another move of the sametype without entering again if it is a local move, select destination whs, …

Translation key for 'Select empty location'?This can be used to customize the text on the button to select an empty location when choosing adestination location.This is used in combination with the SelectLocationForAdHocMovesHookScript.That hook script can return a customized query to list locations.Used in the flows:

Ad hoc moves●

Partial move❍

Full LUID move❍

Multiple LUID move❍

Undo picking●

5.1.3.59. Stock allocation controller

Controller for the stock allocation screen

This controller holds the configuration for the Stock Allocation Screen.The screen supports custom views that are used to show data on the screen.This can be used when customers want additional info on the screen.But that custom view will have some fields that are required.

Grid localization key (Customer info)The translation key that is used to translate the grid on the screen for grouping option 'Customer'

Grid localization key (Sales order info)The translation key that is used to translate the grid on the screen for grouping option 'Salesdocument'

Order by (Customer info)The order by clause for the query for grouping option 'Customer'

Last update:2018/03/1212:56



Order by (Sales order info)The order by clause for the query for grouping option 'Sales document'

View name (Customer info)The view used for grouping option 'Customer'.The view can be customized, but the following fields are required:

ItemCode●

SboWhsCode●

GroupCode●

CardCode●

CardName●

AllocatedQuantity●

AllocatedQuantityOriginal●

FreeQuantity●

FreeQuantityOriginal●

InventoryQuantity●

OpenQuantity●

OpenQuantityNotAllocated●

ErrorMessage●

View name (Sales order info)The view used for grouping option 'Sales document'.The view can be customized, but the following fields are required:

ItemCode●

SboWhsCode●

GroupCode●

CardCode●

CardName●

AllocatedQuantity●

AllocatedQuantityOriginal●

FreeQuantity●

FreeQuantityOriginal●

InventoryQuantity●

OpenQuantity●

OpenQuantityNotAllocated●

ObjType●

DocEntry●

LineNum●

ErrorMessage●

5.1.3.60. Picklist proposal manager screen controller

Controller for the picklist proposal manager screen

This controller holds the configuration for the Picklist Proposal Manager Screen.The screen supports custom views that are used to show data on the screen.



This can be used when customers want additional info on the screen.But that custom view will have some fields that are required.

Production

Grid localization key (Production info)The translation key that is used to translate the grid on the screen for document type 'Production'

Order by (Production info)The order by clause for the query for document type 'Production' This option is not supported yet bythe Pick list proposal manager.

View name (Production info)The view used for document type 'Production'.The view can be customized, but the following fields are required:

ObjType●

DocEntry●

WhsCode●

ItemCode●

ItmsGrpCod●

CardCode●

DocDueDate●

Sales order

Grid localization key (Sales order info)The translation key that is used to translate the grid on the screen for document type 'Sales'

Order by (Sales order info)The order by clause for the query for document type 'Sales order'

View name (Sales order info)The view used for document type 'Sales order'.The view can be customized, but the following fields are required:

ObjType●

ObjTypeString●

DocEntry●

LineNum●

WhsCode●

ItemCode●

ItmsGrpCod●

CardCode●

DocDueDate●

Whs transfer

Last update:2018/03/1212:56



Grid localization key (Transfer info)The translation key that is used to translate the grid on the screen for document type 'Transfer'

Order by (Inv. transfer info)The order by clause for the query for document type 'Transfer'

View name (Inv. transfer info)The view used for document type 'Transfer'.The view can be customized, but the following fields are required:

ObjType●

ObjTypeString●

DocEntry●

LineNum●

ToWhsCode●

WhsCode●

ItemCode●

ItmsGrpCod●

CardCode●

DocDueDate●

5.1.3.61. Location controller

This controller holds the configuration for suggesting locations on moves.

Location controller - Handle location suggestions

This controller uses put away zones to get a list of possible locations to store the goods.

Use suggested locations?Enables the location suggestion functionality.

Allow to suggest an empty fixed pick location?When getting the list of locations, can an empty fixed pick location be suggested? If an empty fixedpick location is found, this will be the first suggested location.

Allow to suggest pick locations during moves?Are pick locations allowed to be suggested?This is used on the ad hoc move flows.

Allow to suggest pick locations during put away?Are pick locations allowed to be suggested?This is used on the put away or reception flow.

Force to use first suggested location during moves?Is the user forced to use the first suggested location?If he is forced to do this, but he enters another location, he will need to enter a reason.This is used on the ad hoc move flows.



Force to use first suggested location during put away?Is the user forced to use the first suggested location?If he is forced to do this, but he enters another location, he will need to enter a reason.This is used on the put away or reception flow.

Order by (Moves)The order by clause for the locations that need to be retrieved.A predefined value can be selected:

CASE COUNT( “PMX_INVT”.“InternalKey” ) WHEN 0 THEN 0 ELSE 1 END, ISNULL(“PAZ”.“Sequence”,●

999999999),CASE WHEN “PAZ”.“SortPickSequenceDescending” = 'Y' THEN “PMX_OSSL”.“Sequence”*-1 ELSE “PMX_OSSL”.“Sequence” END,“PMX_OSSL”.“Code”

It sorts the location on:

Empty locations●

Put away zone sequence (Defined on the location)●

Pick sequence of locations that belong to the put away zone●

Location code●

The value can be adjusted freely.This is used on the ad hoc move flows.

Order by (Put away)The order by clause for the locations that need to be retrieved.A predefined value can be selected:

CASE COUNT( “PMX_INVT”.“InternalKey” ) WHEN 0 THEN 0 ELSE 1 END, ISNULL(“PAZ”.“Sequence”,●

999999999),CASE WHEN “PAZ”.“SortPickSequenceDescending” = 'Y' THEN “PMX_OSSL”.“Sequence”*-1 ELSE “PMX_OSSL”.“Sequence” END,“PMX_OSSL”.“Code”

It sorts the location on:

Empty locations●

Put away zone sequence (Defined on the location)●

Pick sequence of locations that belong to the put away zone●

Location code●

The value can be adjusted freely.This is used on the put away or reception flow.

For more information about the usage see: Location suggestions

5.1.3.62. Checks controller

This controller holds the configuration for the Checks flow.

ChecksController - Controls the checks

This is the default controller to store the configuration used in the checks flow.

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

Last update:2018/03/1212:56



Check SSCC: Show global SSCC information? (Y/N)When enabled, the flow to check an SSCC will show a screen with additional information about theSSCC.This screen is shown after the SSCC was scanned.

5.1.3.63. Proof of delivery controller

This controller holds the configuration for the Proof of Delivery functionality.

POD Controller - For IM2 ePOD

This is the default controller for the POD.

Allow only full quantity to be delivered? (Y/N)When this is enabled, the delivery of the item is a 'All or nothing' delivery.The user can either deliver nothing, or deliver the full quantity.

Image pathThe path where the images will be stored.

Route export modeThe level of details the export needs to contain.

Possible values:

SSCC: Lists every SSCC. Confirmation is on SSCC level●

Item: Lists every item on an SSCC. Confirmation is on item level●

Batch: Lists every batch for every item on an SSCC. Confirmation is on batch level●

5.1.3.64. Create SAP delivery from PMX delivery controller

This controller holds the configuration for the tool to create an SAP delivery from a PMX salesshipping.

Create SAP delivery

This is the default controller.

Create automatically SAP delivery from PMX deliveries? (Y/N)When enabled the tool will create SAP deliveries.

5.1.3.65. On consume for production controller

This is a controller that gets executed when ingredients are being consumed for production.



This can be used for adding additional items to the issue for production.

There is no default implementation of this controller.It needs to be created on a customer base.

5.1.3.66. Open documents screen controller

Controller for the open documents screen (DEDOCCTR)

The settings below are to customize the grids shown on the open documents report.There is a view to get the data to show on the grid. The order in which the columns are on the view,will also be the order in which they will appear in the grid.Per view there are some mandatory fields, so the system knows what column to use for certainvalues.

Container

Order by – (Container)The order by for the view. The text ‘ORDER BY’ does not need to be entered here.

View name – (Container)The name of the view that will be used. Required fields:

DocEntry●

Grid localization key – (Container)The localization key to use. This is used to translate the grid.

Move orders

Order by – (Move order)The order by for the view. The text ‘ORDER BY’ does not need to be entered here.

View name – (Move order)The name of the view that will be used. Required fields:

DocEntry, FromPmxWhsCode, ToPmxWhsCode●

Grid localization key – (Move order)The localization key to use. This is used to translate the grid.

Pick lists

Last update:2018/03/1212:56



Order by – (Pick list)The order by for the view. The text ‘ORDER BY’ does not need to be entered here.

View name – (Pick list)The name of the view that will be used. Required fields:

DocEntry, DestStorLocCode, WaveKey●

Grid localization key – (Pick list)The localization key to use. This is used to translate the grid.

Pick list proposals

Order by – (Pick list proposal)The order by for the view. The text ‘ORDER BY’ does not need to be entered here.

View name – (Pick list proposal)The name of the view that will be used. Required fields:

DocEntry, DestStorLocCode, HasPickList●

Grid localization key – (Pick list proposal)The localization key to use. This is used to translate the grid.

Pmx Sales shipping

Order by – (Pmx sales shipping)The order by for the view. The text ‘ORDER BY’ does not need to be entered here.

View name – (Pmx sales shipping)The name of the view that will be used. Required fields:

DocEntry●

Grid localization key – (Pmx sales shipping)The localization key to use. This is used to translate the grid.

Routes

Order by – (Route)The order by for the view. The text ‘ORDER BY’ does not need to be entered here.



View name – (Route)The name of the view that will be used. Required fields:

DocEntry, LoadingDock●

Grid localization key – (Route)The localization key to use. This is used to translate the grid.Below is a reduced translation tag for the standard grid is.It shows how to translate, or if needed how to hide a columns.


<LocalizationKey>Logex.AddOn.OpenDocumentsReportForm.Grid.Route</LocalizationKey> <ApplicationTypeCode>SBOGUIAP</ApplicationTypeCode> <LocalizationProperties> <PmxLocalizationProperty> <Canceled>False</Canceled> <LocalizationProperty>Columns[1].HeaderText</LocalizationProperty> <ExtensionCode>CONVSTR</ExtensionCode> <LocalizationValues> <PmxLocalizationValue> <Canceled>False</Canceled> <LocalizationValue>Document number</LocalizationValue> <LanguageCode>3</LanguageCode> </PmxLocalizationValue> <PmxLocalizationValue> <Canceled>False</Canceled> <LocalizationValue>Type</LocalizationValue> <LanguageCode>16</LanguageCode> </PmxLocalizationValue> </LocalizationValues> </PmxLocalizationProperty> <PmxLocalizationProperty> <Canceled>False</Canceled> <LocalizationProperty>Columns[13].Visible</LocalizationProperty> <ExtensionCode>CONVBOOL</ExtensionCode> <LocalizationValues> <PmxLocalizationValue> <Canceled>False</Canceled> <LocalizationValue>False</LocalizationValue> <LanguageCode>3</LanguageCode> </PmxLocalizationValue> <PmxLocalizationValue> <Canceled>False</Canceled> <LocalizationValue>False</LocalizationValue> <LanguageCode>16</LanguageCode> </PmxLocalizationValue> </LocalizationValues> </PmxLocalizationProperty>

Last update:2018/03/1212:56



</LocalizationProperties> </PmxLocalizationKey>

Weigh orders

Order by – (Weigh orders)The order by for the view. The text ‘ORDER BY’ does not need to be entered here.

View name – (Weigh orders)The name of the view that will be used. Required fields:

DocEntry●

Grid localization key – (Weigh orders)The localization key to use. This is used to translate the grid.

5.1.3.67. Packing controller

Controller for packing (DEPC)

Combine packed SSCC

Start by scanning SSCC?If enabled, the system will start by scanning an SSCC instead of selecting the customer/ship toaddress. Available on the Combine packed SSCC flow.

Consolidated packing

Allow partially picked pick lists to be packed (Y/N)If set to true, the system will allow to pack ‘Partially Picked’ pick lists with the Consolidated packingflow.

General

Add logistic carriers to all Sub SSCC’s (Y/N)If enabled, the selected logistic carrier is linked to the sub SSCC instead of the master SSCC.Otherwise the logistic carrier is linked to the master SSCC only. Combination of adding logistic carriersto master and sub is not possible.This setting only effects the Packing, Consolidated packing and Item packing flows.

Ask logistic carrier when LUID is finished



When enabled, the packing flow will not ask the logistic carrier when users starts a new LUID, butwhen the users indicates that the LUID is full.

Finished LUID screen. View nameThe name of the view that is used for customizing the Finished LUID screen. The following field isrequired:

LUID●

Perform automatic shipping per customer/address? (Y/N)When enabled, the process to try to automatically ship will occur for each packed pick list for thesame 'customer/address/ship to code' instead of checking if all pick lists in the wave are packed.

Pick list groupingWhen packing items users need to select the customer/address if there are multiple customer/addresson the movable location or SSCC.There are 2 options:

Grouping on CardCode, ShipToCode, ShipToAddress●

Grouping on CardCode, ShipToAddress●

Time to show 'Packing LUID finished' messageThe number of seconds the ‘Logistic unit finished’ message is shown on the scanner: Possible values:




Use pallet packaging type from customer master data?When enabled the packing flows will use settings available on the business partner master data toknow if multiple identical master and/or sub SSCCs need to be made.Supported flows:

Packing flow●

Consolidated packing flow●

Item packing flow●

5.1.3.68. Receive from WHS controller

Receive from WHS controller – Controls the Receive from WHS flow

General

Line remarks view nameThe view that gets the line remarks to show on the scanner after the product is identified. This viewneeds at least these columns:

ObjType●

DocEntry●

Last update:2018/03/1212:56



LineNum●

ItemCode●

The view can return multiple rows/columns for the same document. The screen to show the remarkswill then show the data in multiple rows/columns.

Move all items in 1 stock transfer? (Y/N)If enabled, the Inventory Transfer Document is created after every item is transferred, otherwise anInventory Transfer Document is created after each transferred LUID.

Remarks view nameThe view that gets the line remarks to show on the scanner after the Inventory Transfer Document isidentified. This view needs at least these columns:

ObjType●

DocEntry●

The view can return multiple rows/columns for the same document. The screen to show the remarkswill then show the data in multiple rows/columns.

5.1.4. SSCC

In the SSCC (Serial Shipping Container Code) settings screen, the system shows the actual SSCCnumber, as well as the start and end number of the range.



5.1.5. Reports

The reports tab offers an overview of the standard reports that have been defined in Produmex.

This also includes a reference to the shared folder (report path) where the reports are stored as well●

as the report parameters (name, path from the entered report path, page size, orientation, type ofreport and the format in which the report is created (Crystal Reports, CoreSuite))“Uses the external database”: as it is not allowed to store “Stored Procedures” in the SAP●

Business One databases, an external Produmex database has been created which contains thestored procedures that are required to generate the reports.

Last update:2018/03/1212:56



5.1.5.1. Crystal Report

This functionality uses reports located at the ‘Report path’.

5.1.5.2. Crystal report by SAP

This functionality uses the default reports that are stored within SAP.

To configure this, you first need to know the ID of the report.

Next this ID needs to be stored in the field Path.

When the system will need to print, it will get the report with that ID from the database.

5.1.5.3. Coresuite

This will use the reports available in Coresuite.

When printing the system will create a file to a certain folder.The field Coresuite report path need to be filled in with a folder where the file needs to be stored.



The Coresuite add-on will pick up the file and print the report.

5.1.5.4. Unknown

Used for custom reports types.

5.1.6. Print events

In the “Print events” you can indicate which report has to be generated on which event. These eventsare defined upon configuration of Produmex WMS. At that moment the report that has to be printedupon the occurrence of an event can be defined, as well as the number of copies and the condition(filter) that has to be met for the report to be generated.

You can find the list of the events here: List of print events.

Predefined filters:The filter “PRFLUIDG” determines that when a logistic unit is received with a valid logistic labelcontaining an SSCC, the system will NOT generate a new reception label with a new system-generated SSCC. The filter can be used for the following print events:

101 Reception new LU identified●

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

Last update:2018/03/1212:56



200 Picking: new LU full●

400 Production: LU produced●

500 Packing: finished LU●

700 WHS: created LU●

702 WHS: created master LU●

The filter “PRFWMM” can be used for warehouse move documents. It will use the settings on theWarehouse move Matrix UDT to check whether a document should be printed.

The filter “PRFCUCO” determines that the document will not be printed for customer collects. On theother hand, the filter “PRFNCUCO” determines that the document will only be printed for customercollects. These filters can be used for the following print events:

200 Picking: new LU full●

300 Shipping: sales delivery note created●

302 Shipping: picklist shipped●

500 Packing: finished LU●

The filter “PRFSCRIP” offers users the possibility to develop own criteria for determining when andhow a label should be printed.

5.1.6.1. Scripted print filters

It is possible to define a custom print filter. It will allow to block printing for certain parameters.

A typical print filter consists of 3 main sections

Running of SELECT QUERY to get needed info for document●

Determination of TRUE or FALSE value according to needed info●

Return RESULT●

Creation of a new print filterIn the Produmex Organizational Structure, go to the Print Events tab:



Here you can add a filter to the desired print event.Select Filter → IPrintReportFilter – Script (PRFSCRIPT)Then select the ‘Edit’ button.

The following script editor opens, here we will paste our script.

Last update:2018/03/1212:56



Press the ‘Empty script’ button to open a script template designed for the selected print event.We recommend to use this template instead of starting from an empty script.

The template contains two print report methods.

Use the first method if the report has only one parameter.●

Use the second method if the report has more than one parameters.●

Here you can find a demonstration script that explains what is needed.

using System;using System.Reflection;using Produmex.Foundation.Data.Sbo;using Produmex.Foundation.Diagnostics;using Produmex.Sbo.Logex.Data.BusinessObjects;using Produmex.Sbo.Logex.Data.Providers;using Produmex.Foundation.Data.Sbo.BusinessObjects;using Produmex.Foundation.Data.Sbo.Utilities;using Produmex.Foundation.Data.SqlClient;

public class Script{ private static readonly ILog s_log =

LogProvider.GetLogger(MethodInfo.GetCurrentMethod().DeclaringType);



public static bool PrintReport(PmxPrintReportEventType eventType, intkey, PmxDbConnection dbConn) { //Create the query you want to use string query = "SELECT [COLUMNAME1], [COLUMNAME2] FROM [TABLENAME]WHERE [Key] = "+ key.ToString();

//Run the query using (ISboRecordset rs = SboRecordsetHelper.RunQuery(s_log, query,dbConn)) { if (!rs.EoF)//Check if you get result from the query { string var1 = rs.GetTypedValue<string>("COLUMNAME");//Get astring value int var2 = rs.GetTypedValue<int>("COLUMNAME2");//Get an intvalue

//Possibility to add a check on the result //In this case if the value of column with name 'COLUMNAME2'equals to 99, //a label should be printed if (var2 == 99) { return true; //Label will be printed } else { return false; //Label will not be printed } } } return false; //Label will not be printed }}

So you can modify this script to fit your needs:

Modify the query to lookup the needed info●

Get the needed values from the query result●

Modify the check on the result and return the correct TRUE or FALSE●

Validate and test

Last update:2018/03/1212:56



You can also use this screen to:

Validate the Script●

Do a test run with a KEY from the database :●

The key is what is passed to the report. So for the print event ProductionLogisticUnitProduced this isthe LUID of the produced pallet.

In order to avoid performance issues, do not use ‘SELECT *’ syntax in the select query. Select



only the required columns or the primary key.Example:

What should be avoided: SELECT * FROM "OITM" WHERE "ItemCode" = 'ITEM01' 1. What to use instead:2.

SELECT "InvntItem", "MinLevel" FROM "OITM" WHERE "ItemCode" = 'ITEM01' ❍

SELECT "ItemCode" FROM "OITM" WHERE "ItemCode" = 'ITEM01' ❍

It’s also recommended to add the WITH (NOLOCK) hint to all tables used in these queries.For example:

SELECT "ItemCode" FROM "OITM" WITH (NOLOCK) WHERE "ItemCode" = 'ITEM01' ●

Or with a join (NOLOCK on all tables): SELECT "OITM"."InvntItem" FROM "DLN1" WITH●

(NOLOCK) JOIN "OITM" WITH (NOLOCK) ON "DLN1"."ItemCode" = "OITM"."ItemCode" WHERE"DLN1"."ItemCode" = 'ITEM01'

5.1.7. Zone types

The “Zone types” tab allows you to define the various zones types in your company that can beassigned afterwards to specific items, depending on their storage conditions.

Once a zone type is created it remains possible to change and update its name (description) but notits code.

Last update:2018/03/1212:56



Needs reasonIf ticked you will have to enter a reason when receiving this item.This can be used to confirm that specific conditions were met when receiving the item.For example the item needs to be stored below 5° Celsius and it arrives at 10 °You would enter that conditions were not ok.

Show zonetype?If ticked the zone type will show at reception of an item.

5.1.8. Page sizes

The “Page sizes” tab allows you to define the used page sizes for reports and printers.



Once created it is possible to change the name (description) of a page size but not its code.

5.1.9. Quality status

The “Quality status” allows you to define the applicable quality statuses for your company.For each quality status it is possible to define whether or not an item with that specific quality statuscan be shipped and/or picked for production and/or picked for a replenishment order.Furthermore you can specify to which quality status a specific status can be changed: e.g. “blocked”can be changed to “released”.

Ask for reasonOn the transition between quality statuses the user can set whether a reason needs to be entered forthe change.

Last update:2018/03/1212:56



Can be shippedThe quality status is allowed to be picked and shipped.

Can be picked for replenishmentIndicates if the stock can be used to replenish pick locations.

Can be picked for productionIndicates if the stock can be used pick for production.

Can be used for productionIndicates if the stock can be used for production. Stock that does not have this option, are not allowedto be stored on production lines.

Can be put on a pick locationIndicates if the stock can be stored on pick locations.

Can be shipped under quarantineIndicates that the stock is in quarantine, but still allowed to ship. Setting ‘Shipping quality option’ onthe sales order line can be changed to allow shipment of these goods.

Quality status transitions

This lists the quality statusses to where the current quality status can be changed to.

It is possible to flag the setting Ask for reason. By doing this, when the user changes the qualitystatus through the inventory report, he will have to select a reason for this quality status change.

It is also possible to limit users from making certain quality status transitions.This is done by selecting a user group for the transaction.If a user wants to perform a quality status transition, he is only allowed to change it to a quality statusthat has no user group, or a quality status that has the user group he is assigned to.

Please note that reasons or user group limitations do not apply when moving stock to a location witha predefined quality status.



5.1.10. Reasons

The “Reasons” tab offers the possibility to define the reasons that can be selected for picking and/orshipping and/or sales/purchase return when a specific action cannot be completed or a specific itemcannot be used.

The sequence number is the order the reason is shown on the terminals.

5.1.11. 3PL invoicing

Last update:2018/03/1212:56



The “3PL invoicing” tab offers the possibility to define which items will be used on the A/R invoicessent to the 3PL customers. 6 items can be defined, each corresponding to one kind of 3PL pricecalculation:

‘Inbound document count’: price depending on the number of Goods Receipt PO’s●

‘Inbound line count’: price depending on the number of lines in Goods Receipt PO’s●

‘Inbound item quantity’: price depending on the item quantities received●

‘Outbound document count’: price depending on the number of sales deliveries●

‘Outbound line count’: price depending on the number of lines in sales deliveries●

‘Outbound item quantity’: price depending on the item quantities delivered●

Only non-inventory items can be selected. Each item can be enabled or disabled; pricescorresponding to disabled items will not be added to the 3PL invoices.

In addition to these 6 kinds of 3PL price calculations, it’s also possible to define 3PL price calculationsbased on the storage per location type. See Location Types section for more details.



5.1.12. History configuration

The “History config.” tab offers the possibility to define for which elements or aspects (which arestored in individual database tables) the changes have to be tracked in the context of Audit Trail. Thiscan be changes to characteristics of specific Organizational Structure Elements (e.g. a bin, a zone, aproduction line, … ) which need to be tracked, such as their name, zone type code, … It may also benecessary to track changes to specific characteristics of items, such as e.g. the shelf life of an item forthe various business partners of a company. This is shown in the example below, where it has beenconfigured that for the table “Item shelf life for partner” it has to be recorded when the shelf life for aspecific item for a specific business partner is added, updated or deleted.These changes will then be tracked by the Produmex Office function “Audit Trail”.

Last update:2018/03/1212:56



5.1.13. Workflows

Overview of the used workflows

5.1.13.1. Edit workflowscripts

It is possible to adjust for instance main menu flows to remove buttons. Do not adjust the flowsprovided by Produmex, because they will be overwritten when an update of the database is done.

Instead a copy should be made:



Open the Produmex Organizational Structure (1) → Select the company (2) → go to ‘Workflows’ tab(3) → Select the flow you want to edit (4) en click ‘Edit Script’ (5)

This opens the following screen:Press CTRL + C to copy all the content to your clipboard

http://wiki.produmex.name/lib/exe/fetch.php?media=implementation:wf_1.png

Last update:2018/03/1212:56



Then you can close this screen again.

Next, we will need to add a new script for the customer that we will edit later on.

On the Workflows tab → Select the script you want to edit again and modify the name below (6) →Then click on ‘Add’ (7)




This has added a line to you workflows (see (8)), now we must paste the content in this script.Select this newly added line and click on ‘Edit script’ (9) → Then paste (CTRL + V) the copied contentin this new script:



Last update:2018/03/1212:56



In this Workflow script editor, scroll to the top of this new script. There, edit the following line in thecode to match the name you gave your script (MainWarehouseMenuFlowScrip becomesMainWarehouseMenuFlowScript_CustomerName in this example)

If you do not do this, the flow will not run on the client! This has to be done on 2 places in thescript, see red underline in the image below.

Now we can really edit the available button in this script.Therefore we have to scroll to the section with the button list.Here we can disable or enable button by placing them in or out comment.




( / / in front of the code means it is in comment and will not be taken into account)

So I will delete the Production button from the main flow in this example.

I look for the code m_MenuOptions.Add(new MenuOption(“MSG_BUTTON_PRODUCTION”,Create(“ProductionMainFlowScript”)));

Then I can disable this button by adding / / in front of it:

Then we can ‘Validate’ this script with the foreseen button.

Finally, we need to make sure this code is launched, so we will possibly need to modify the script thatis used on the fat client: Select client in Org. Struc. (1) → Select new Workflow (2) → OK (3)


Last update:2018/03/1212:56



If we then startup this client, we can see that he production button is no longer present:(Only Purchase, Sales and Logistics)

http://wiki.produmex.name/lib/exe/fetch.php?media=implementation:5.1.13.1h.png



5.1.13.2. Call modified workflowscripts

When we have created a modified workflowscript that is a sub-script of the main script, we need tocall this modified script.

An example could be that with the explanation from point 5.1.13.1 you have created a modifiedSalesMainFlowScript_CustomerName. After it has been created, we have to make sure it is called inour MainWarehouseMenuFlowScript_CustomerName.

So we open the MainWarehouseMenuFlowsScript_CustomerName to edit, and call the modifiedSalesMainFlowScript_CustomerName like this:

http://wiki.produmex.name/lib/exe/fetch.php?media=implementation:5.1.13.1i.png

Last update:2018/03/1212:56



5.1.14. Config

The config tab list some configuration that can be done for several processes.Also customer specific configuration can be stored here.

It will have settings for:

Interfacinig●

WA interfacing●

Configuration for SBO notification listener actions●

…●



5.2. Other Organization Structure Settings

All OSE objects have a code and a description field.

CodeThe code of the OSE object. This field cannot be updated.

DescriptionThe description of the OSE object.

5.2.1. Warehouse settings

At the warehouse level the following settings can be defined:

Last update:2018/03/1212:56



WarehouseThis is the link between the warehouse defined in Produmex and the warehouse in SAP Business One(Cfr. Administration → Setup → Inventory → Warehouses.)Each SAP warehouse can only be linked once in Produmex warehouses.

Stor. Loc. logistic carriersThe location in the warehouse where the logistic carriers are located (in case you have indicated atthe company level that logistic carriers have to be stored at one location per warehouse).This location needs to be a pick location!

Stor. Loc. returnable itemsThe storage location for the returnable items. This is used when inventory returnable items are used.

Location ‘Lost and Found’The ‘Lost and Found’ location for that warehouse. All item differences counted during cycle counting(indirect cycle counting) will be moved to the Lost and found location in case this is set up on theCycleCountController.



Stock on storage locations set for Lost and found, logistic carriers, … are not taken in account tocreate pick list (proposals).

Use location suggestions?Set whether location suggestions will be used for move in or to this warehouse. This is used in theLocation Suggestions functionality.

5.2.2. Zone settings

At the level of a zone, the following settings can be defined:


Last update:2018/03/1212:56



Use for zone pickingCan this zone be selected on the flow ‘Zone picking’?

Zone typeSelection from a drop-down list. A zone can belong to one or more zone types: e.g. temperature-related and/or humidity-related. If the zone in question is a main zone (highest level) consisting of oneor more sub-zones, the zone type that applies to the highest level zone also applies to the lower levelones too. In that case the “Locked” field is ticked.

5.2.3. Production line settings

A production line in Produmex WMS is always subordinate to a warehouse.

There are multiple ways of doing production:

Production flow: This flow handles the receipt AND issue for production in the client●

Production manager + Production receipt: On the scanner/touchscreen the receipt for production is●

booked. The production manager handles the starting + stopping of the production order.

Do not use the same production line for both flows

The following settings can be defined for a production line:

5.2.3.1. General

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

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

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



ActiveSet whether or not the production line is active. A production line can only be active when an Input,Output and Rest location is filled in.

Only 1 started production order allowedIf set, only 1 started production order is allowed for this production line. This can only be used incombination with the production manager and ‘Production receipt’ flow.The ‘Production’ flow always forces to only have 1 production order started on the production line.

Pick to locationThe location where the needed ingredients are picked to. When this is not filled in, the system will usethe ‘Input’ location. The ComponentWeighingFlow will use the ‘Pick to’ location as input for the itemsto be weighed. The weighed items will be stored on the ‘Input’ location. Stock on a ‘Pick to’ location isnot taken in account to create pick list (proposals).

Lock items picked to this locationWhen this is enabled, picking for production will lock the items that are picked to this location.Pick lists for production do not support this.

Last update:2018/03/1212:56



On the Component weight flow the locked stock will be removed when it is weighed.

Input locationThe location where the needed ingredients are picked to. Production flows will move stock from theinput location to the production line. Stock on an input location is not taken in account to create picklist (proposals).

Output locationThe location where the finished products will be stored.

Rest locationLocation to which the rest of used materials and ingredients are moved. It is possible to use the inputlocation as rest location. In this case the remaining items will be ready to use for the next productionorder.

Parent production lineThe parent production line is used if for instance the production is done in several steps. In this casethe user can define the sequence of the production lines.

Production manager typeThis is used when the processing of the production issues is done administratively. This can have 2possible values.

SPL_CONS_LOCK: When producing on the shop floor, the items to consume are not directly●

consumed, but they are locked. When processing the production order administratively, the systemwill use the locked stock as base for the consumption. MPL_CONS_INPUT: When the users do not want to perform the tasks to move the correct stock to●

the production line when producing, this option is used. When processing the production orderadministratively, all stock on the input location is used as base for the consumption. Furthermore, allproduction orders on production lines with the same input location will be processed in 1 time.

Current production orderThe current production order for this production line (read-only)

Can be lined upSome locations can be lined up. If a location is added here, it means the stock in this location is useddirectly, and does not need to be picked. This is usually used for tanks and/or silo’s.However an output location of another production line can also be set as ‘lined up’. Now the produced



items on the ‘previous’ (linked) production order can directly be used instead of picking the items.Stock on possible lined up location is not taken in account to create pick list (proposals).

Produce ingredientsThis option is used if a linked production order needs to automatically produce stock.The prerequisites for this to work correctly, is that the lined up location is used as an output locationon another production line. At the time of production on the shopfloor, a started production orderneeds to be found on the production line with as output location the lined up location.

Lined up locationsThe current lined up locations

5.2.3.2. Cycle count

Last update:2018/03/1212:56



Allow location to be counted during cycle countIs the location allowed to be counted?

Allow location to be counted during other operationsIs the location allowed to be counted during other operations? This means that when this location isused on certain flows, the system will check if a count is needed. If so, the system will ask the user toperform a count.

Locations needs to be counted nowWhen this option is enabled, the location will be counted, regardless of the other settings (Number ofdays, number of operations, …)

Count after X daysWhen a location has not been counted for the number of days defined here, the location needs to becounted. If the number is 0, this setting is not taken in account, and the setting on company level istaken.

Count after X operationsIf the number of operations since the last count exceeds the defined number of operations, thelocation needs to be counted. If the number is 0, this setting is not taken in account and the settingon company level is taken.

Locked by (read-only field)This field shows the key of the user that is locking the location, because he needs to count thelocation or is currently in process to count the location.When a location is locked, it cannot be used in other processes.The location is released by clicking the ‘unlock’ button.Stock on locked locations is not taken in account to create pick list (proposals).

5.2.4. Packing line settings

On a packing line, items that have been picked on a movable location (picking cart) can be packed



onto a logistic carrier to be shipped as a logistic unit with an SSCC.For a packing line the following settings can be made:

5.2.4.1. General

ActiveSet whether or not the packing line is active.

Can be destination for pickingSet whether the packing line can be a destination for picking.

Block stock from being used for the picking processIf this setting is enabled, the stock on this location cannot be used to put on a proposal. Also when apick list gets the allocation on location level, these locations are not taken in account.

Last update:2018/03/1212:56



The locations with this flag to true are added to the view PMX_DISALLOWED_LOCATIONS_FOR_PICKING










5.2.5. Dock settings

At the dock level the following settings can be made:

5.2.5.1. General

Last update:2018/03/1212:56



ActiveSet whether or not the dock is active.

Loading & unloadingWhether the dock can be used for loading, unloading or both.

Pick locationSet whether a dock can also be a pick location (e.g. whether or not newly received goods that are stillon the receiving dock can already be considered for picking)

Block stock from being used for the picking processIf this setting is enabled, the stock on this location cannot be used to put on a proposal. Also when apick list gets the allocation on location level, these locations are not taken in account.The locations with this flag to true are added to the view PMX_DISALLOWED_LOCATIONS_FOR_PICKING



SequenceThe order in which the products at this location will be used to compose a picking order. The picklocations with the lowest sequence number will be used first to complete the pick order.




Last update:2018/03/1212:56







5.2.6. Bin settings

At the bin level (storage location) the general and cycle count settings can be defined:

5.2.6.1 General



ActiveSet whether or not the bin is active.

Location typeThe user can define a location type (UDT) and link it with a bin location. This information has furtherno technical use. It’s for information purposes only.

Pick locationSet whether or not the bin is a pick location: if this is not the case the items that are stored at thislocation cannot be used for composing a shipment (order picking). A bin that is not used for picking(=bulk location) can be used to store safety stock that is used to replenish various pick locations.

Priority pickingIf the bin location is a pick location, an additional ’Priority picking’ checkbox is displayed. When thischeckbox is checked, the bin location has higher priority during stock allocation for pick lists thanother bin locations.

Last update:2018/03/1212:56



Can be destination for pickingSet whether the bin can be a destination for picking. This means on the pick list it will be possible toselect this location as ‘dock’.


Block stock from being used for the picking processIf this setting is enabled, the stock on this location cannot be used to put on a proposal. Also when apick list gets the allocation on location level, these locations are not taken in account.Replenishment orders will not take stock from locations with this flag enabled.The locations with this flag to true are added to the viewPMX_DISALLOWED_LOCATIONS_FOR_PICKING.

Can be lined upSet whether or not the bin can be lined up.

Direct consumption of goods (Production manager):If the option ‘Can be lined up’ is set to true, this option is visible. By default the lined up locations arenot directly consumed when using the production manager (ProductionReceipt flow). The stock islocked for the production order, and it is consumed when stopping the production order using theproduction manager. If this option is set to true, the goods that are lined up on this location, will beautomatically consumed on the receipt from production.

Block move when location is not empty.If set, a move to this location when is not empty is not allowed.

Block on different item or batch

None: Nothing will happen●

Warn: Display a warning message when a different item or a different lot number will be added to●

that location. This warning is only when using the RF terminals. Block: Block the move when a different item or a different lot number will be added to that location.●

Max logistic unitsThe maximum number of allowed logistic units (SSCC’s).If stock is not on an SSCC, the system will regard all this stock as 1 logistic unit.



This will not block a move, but is used when proposing locations on the devices.

Quality statusThis option will force a certain quality status on the location.When adding/moving stock to the location, the system will check whether the quality status of thestock matches with the quality status of the location. If the quality status does not match, thefollowing can happen:

When booking a move through the handheld device or the Produmex inventory report, the system●

will automatically set the quality status of the stock to the quality status of the location and then itwill perform the move. When booking a move with other processes, the system will not change the quality status of the●

stock and the move will be blocked.

When performing a direct cycle count on a location with a quality status, newly created stock will getthis quality status.

How to set up location where only ‘released’ stock can be stored, but avoid the quality statuschange when non-released stock is moved on the location

On the Quality status tab disable the ‘Can be put on a pick location’ setting for every qualitystatus that is not allowed on the given location. Then enable the pick location setting for thegiven bin location. Set the reception/quality control area as a non-pick location.This way only the allowed quality statuses can be stored on pick locations.

FixedIndicates that the storage location is used for specific products. In this case a minimum, maximumquantity is defined for the item on that location.When a location is fixed, the system will block local moves for other products into that location.

Can be replenishedEnables this option if the bin location can be taken in account for replenishment orders.A minimum, maximum and replenish quantity needs to be set.This can only be set when the location is a pick location.

Last update:2018/03/1212:56



5.2.6.2 Cycle count









5.2.6.3 Put away

This is used in the functionality 'Location suggestions'

Item location typeThis can be used to link a location to an item.An item can also have an item storage location type.When locations need to be suggested, and an item has a location item type selected, only locationswith the same item location type are allowed. The list of item storage location types is stored in theUDT PMX_ISLT.

Put away zonesThis stores for a certain storage location:

What the zones are where the items can be placed ●

Or to what put away zone a location belongs to●

Put away zoneThe put away zone

Last update:2018/03/1212:56



Sort the pick sequence descending?Locations belong to a put away zone. How are locations within this zone sorted? Pick sequencedescending or ascending?

Location belongs to put away zone?Does this location belong to a put away zone?If it is not checked, it means that when goods need to be put away for the current location, thesystem should look for locations that belong to this zone.If it is checked, the location belongs to this put away zone.

Sequence numberThis is the sequence number for the put away zones. It defines the order in which locations in a putaway zone needs to be retrieved.

For more information about the usage see: Location suggestions

5.2.7. Cycle count settings


Last update:2018/03/1212:56





5.2.8. Moveable location settings

A moveable location is an intermediate storage location: this can be a cart, a movable rack, etc. Amoveable location allows the operator to pick one or more orders and pack them onto a logisticcarrier at another location (packing station).

5.2.8.1. General



In the organization structure it is possible to set the code and name of a moveable location anddefine whether or not it is active.

Stock on movable locations is not taken in account to create pick list (proposals).


A moveable location can also be used in the cycle counting and has the same settings as a binlocation.

Last update:2018/03/1212:56











5.2.9. Silo/Tank settings

At the level of silo or tank the following settings can be defined:

5.2.9.1. General

ActiveSet whether or not it is active.

Can be lined upSet whether or not it can be lined up for production.

Direct consumption of goods (Production manager):If the option ‘Can be lined up’ is set to true, this option is visible. By default the lined up locations arenot directly consumed when using the production manager (ProductionReceipt flow). The stock islocked for the production order, and it is consumed when stopping the production order using theproduction manager. If this option is set to true, the goods that are lined up on this location, will beautomatically consumed on the receipt from production.

Last update:2018/03/1212:56




Max quantityThe maximum quantity. His is for informational purposes.This will not block a move when quantity will be exceeded.

Pick locationSet whether or not it can be used as a pick location

Block stock from being used for the picking processIf this setting is enabled, the stock on this location cannot be used to put on a proposal. Also when apick list gets the allocation on location level, these locations are not taken in account.The locations with this flag to true are added to the view PMX_DISALLOWED_LOCATIONS_FOR_PICKING

FixedSet whether the silo/tank is reserved for a specific product and if so which are the minimum andmaximum quantities.

5.2.9.2. Consumption algorithm

The consumption algorithm by which the contents of the silo/tank is consumed: differs for fluids orsolids (second tab)

FEFO: First to expire, first out●

Silo: Bottom layer (FIFO)●

Tank: Multi-layer (Consume a part from each batch)●


Last update:2018/03/1212:56





5.2.10. Thin client settings

A thin client is a fixed or mobile operator station (touchscreen, handheld terminal, …), by which theoperator can interact and communicate with Produmex.At the thin client level the following settings can be made:



Workflow tabWorkflowNext you can also assign a thin client to a “workflow”. A workflow is a sequence of actions to executea certain operation, e.g. Reception, Picking, Production, Shipping, …

Parameter setFor certain flows extra parameters can be set. When selecting a parameter set, the options to enterare available below.

‘Showroom ThinClient – ParameterSet’

Last update:2018/03/1212:56



Number of items in sales unit column nameDefine here the column name of the column that stores the number of items in the sales unit, definedon the item master data. By default ‘NumInSale’ is used. If you have a UDF to store this value, youcan provide the name of the UDF.

Admin passwordProvide here the password that will be used to unlock the administrator functionality in the showroomapplication. By default the password is ‘produmex’

Warehouse tabThin clients created under a warehouse will see the warehouse locations and orders for thewarehouse by default. On the ’Warehouse’ tab additional warehouses can be assigned for the thinclient. If a warehouse is assigned for the thin client, its locations and orders can be seen on the client.It is not possible to disable the parent warehouse for the thin client by unticking the checkbox to theparent warehouse.

Users tabBy default every SBO user can use the thin client if there is a free license that can be allocated for thethin client. However it is possible to assign only certain users for a thin client.

If there is at least one assigned user, only assigned users can login on the thin client. In case nousers are assigned, ALL users are allowed to access the flow.

On the Users tab every SAP Business One user is listed. Check the ’Assigned’ checkbox in to assignan user.



5.2.11. Printer settings

For printers the following settings can be made:

Windows printer nameThe printer name by which the printer is referred to in Windows

Page sizeThe default page size for the printer

ActiveSet whether or not the printer is active.

Last update:2018/03/1212:56



DefaultSet whether it is the default printer

5.2.11.1. Printer search path

These printers are used in flows on the devices.The system will get the printer with the same page size as the report that needs to be printed.

First the system looks for printers below the device (In the organizational structure). Next the systemwill look if it can find a printer in higher levels, starting from the device.

If the system still does not find a printer, the system will check for printers starting from a location.Which location is taken will depend on the flow where the report will be printed.Example: For a reception, the location will be the receiving dock.

The same search pattern as for the device is used. So first look for a printer below the location, nexton higher levels.

When the system finds several printers on the same level, and there is 1 printer defined as default, itwill take that printer. Otherwise the system will take the first printer it finds on that level.

Remark: When the system searches for printers on higher levels, it will not go back to a lower level tosearch for a printer.

5.2.12. Weighing room settings

At the level of a weighing room, the following settings can be defined:



5.2.12.1. General

ActiveSet whether the weighing room is active or not.

Input locationThe location where the ingredients that needed to be weighed are picked. During the weighingprocess, stock will be moved to the weighing room from the input location.

Output locationThe location where the weighed goods will be moved.

A typical setup is when the input location of the weighing room is the pick to location or the inputlocation of the linked production line and the output location of the weighing room is the inputlocation of the linked production line.

Weigh strategy

Last update:2018/03/1212:56



The weigh strategy defines whether the stock to weigh can be selected based on the weigh order orthe item code.










5.2.13. Scale settings

Define the scale under a weighing room or a reception dock. One scale can only belong to a singleweighing room/reception dock.

At the scale level the following settings can be defined:

Last update:2018/03/1212:56



ActiveSet whether the weighing room is active or not.

Scale definitionsDefine the scale on the Scale definitions field.

If the scale is connected without the ScaleComm service, define it with the one of the followingformulas:

Direct connection: com:/ /Port?Baudrate,Databits,Parity,Stopbits●

Example: com://COM3?9600,8,N,1 Local network: tcp:/ /IP address●

Example: tcp://192.168.1.5:4001

If the scale is connected by using the ScaleComm service, tick the Use as a service checkbox anddefine the scale with the following formula:

http:/ /URL of the server where the service runs/scale code (OSE)/communication parameters●

Example: http://192.168.1.2:9991/SCL01/com://COM3?9600,8,N,1



UomSelect the unit of measurement of the scale from the Uom dropdown list.

Minimum weightEnter the minimum weigh of the scale in the Minimum weigh field.

Maximum weightEnter the maximum weigh of the scale in the Maximum weigh field.

AccuracyEnter the accuracy of the scale to the Accuracy field.Example: If the number of decimals is 2 – Accuracy: 0.01

Scale commandsDefine the scale commands. Select the command type. The following command types are supported:

Set tare●

Set zero●

Get weight ●

Weight return●

The ‘Zero return’ and the ‘Tare return’ commands are not supported yet but are reserved for futureuse.

Add the description to the Description field and the command to the Command format field.

Command formatPlease refer to the user manual of the scale to see the command.

The syntax of the Weight return result string should be a regular expression.

Example:

Last update:2018/03/1212:56



Weight return string from the scale manual:

<LF><p>w1w2w3w4w5w6<dp>w7w8u1u2<CR><LF>H1H2H3<CR><ETX>

Weight return string defined for the scale on the Organizational Structure:

\x0a *(?'weight'.+)(?'uom'..)\x0d\x0a.+\x0d\x03

5.2.13.1. How to define multiple scales through one port

Produmex WMS Organizational StructureFirst create a ‘scale’ type element in the Organizational Structure of Produmex WMS for the port.Add a unique code and name. Example:

PORT, Port for scale

Define the port on the Scale definitions field with one of the following formulas:

Direct connection: com:/ /Port?Baudrate,Databits,Parity,Stopbits●

Example: com://COM3?9600,8,N,1 Local network: tcp:/ /IP address●

Example: tcp://192.168.1.5:4001

Do not check the ‘Use as service’ checkbox.The ScaleComm service will establish the connection to the port based on the configuration file of theScaleComm service.

The scales connected through the port will be identified based on the sent command.

Select the command type and add the scale codes and the scale command to the Command formatfield using the following formula: scale code;command;scale code;command

Example:Get weight command:

scale01;S6R$;scale02;S7R$



Where:

‘scale01’ = scale code of the first scale●

‘S6R$‘= get weight command of the first scale●

‘scale02’ = scale code of the second scale●

‘S7R$’ = get weight command of the second scale●

Weight Return command:

(?'weight'.+)\x0d\x0a;(?'weight'.+)\x0d\x0a

The order and the number of the scale commands must be the same as in the 'Get weight command'.

ScaleComm serviceOpen the configuration file of the ScaleComm Service.

Add the code of the port defined in the Organizational Structure as the value for ScalesCodes.Example:

<add key="ScalesCodes" value="PORT" />

Make sure that the ‘Skip Polling’ option is set to ‘False’ and adjust the ‘Polling Interval’ if needed.

Scale weigh resultOpen the Scale weigh result user table via the following path: Tools> Default forms. Add the scale

Last update:2018/03/1212:56



codes defined on the Command format field as the ‘Code’.

When the ScaleComm Service runs, it will add the weight to the ‘Weigh’ field of the matching scale.

6. Designing Pervasive Dashboards usingPMX predefined views

6.1.Design a Pervasive Dashboard

First add the PMX query to the list of the user defined queries. Create a custom query: Tools >Queries > Query Generator.

http://wiki.produmex.name/lib/exe/detail.php?id=implementation%3Awms%3Aconfguide_complete&media=implementation:confguide:dashboard:querygenerator.png

http://wiki.produmex.name/lib/exe/detail.php?id=implementation%3Awms%3Aconfguide_complete&media=implementation:confguide:dashboard:querygenerator.png



Add the view name to the ‘From’ clause in the ‘Query generator’ window. Produmex providespredefined views (e.g. PMX_KPI_PACKING, PMX_KPI_PICKING), but it is possible to add custom madeviews as well. To expand a predefined view, create a custom view which refers to the PMX view inquestion.

Execute, then save the query.

http://wiki.produmex.name/lib/exe/detail.php?id=implementation%3Awms%3Aconfguide_complete&media=implementation:confguide:dashboard:querypreview.png




http://wiki.produmex.name/lib/exe/detail.php?id=implementation%3Awms%3Aconfguide_complete&media=implementation:confguide:dashboard:savequery.png

Last update:2018/03/1212:56



Then create a new dashboard. Click on the ‘Pervasive Analytics’ button in the toolbar.

Click on the ‘New Dashboard’ button.

http://wiki.produmex.name/lib/exe/detail.php?id=implementation%3Awms%3Aconfguide_complete&media=implementation:confguide:dashboard:toolbar.png

http://wiki.produmex.name/lib/exe/detail.php?id=implementation%3Awms%3Aconfguide_complete&media=implementation:confguide:dashboard:designer.png



Click on the ‘Select Base Data Source’ button to select the data source of the report. Predefinedqueries and user-defined queries will be listed after clicking. Select the previously created query andclick on the ‘Ok’ button.

http://wiki.produmex.name/lib/exe/detail.php?id=implementation%3Awms%3Aconfguide_complete&media=implementation:confguide:dashboard:data_source.png



Last update:2018/03/1212:56



Adjust the settings and parameters of the dashboard then save.

http://wiki.produmex.name/lib/exe/detail.php?id=implementation%3Awms%3Aconfguide_complete&media=implementation:confguide:dashboard:adjust_settings.png



To pin the dashboard to the welcome screen, click on the ‘Settings’ button and select the ‘Settings’option from the dropdown menu. In the ‘Select Dashboard’ window, select the dashboard and set the‘Display’ option to true.

http://wiki.produmex.name/lib/exe/detail.php?id=implementation%3Awms%3Aconfguide_complete&media=implementation:confguide:dashboard:pin.png



Last update:2018/03/1212:56



6.2. Predefined Produmex views

KPI picking

The view provides a list of all item quantities picked per user and per pick list. It contains the followingcolumns:

Internal numberThe internal number of the user.


PickListNumberThe pick list number.

WaveKeyThe wave key of the pick list.

CreateDateThe date when the picking was performed.

CreateTimeThe time (hour, minute) when the picking was performed.

Item codeThe item code of the picked item. Different batches are displayed in separate lines.

ItemDescriptionThe description of the picked item.

QuantityThe picked quantity from the batch in the uom applied in the sales order that was the base of the picklist.

Quantity per uomThe conversion rate between the base uom of the item and the uom applied in the sales order.

Inventory quantityThe picked quantity in the base uom.

Quantity uom2The quantity for the second uom.



KPI packing

The view provides a list of all item quantities packed per user and per pick list. It contains thefollowing columns:

Internal numberThe internal number of the user.


PickListNumberThe pick list number.

WaveKeyThe wave key of the pick list.

CreateDateThe date when the picking was performed.

CreateTimeThe time (hour, minute) when the picking was performed.

Item codeThe item code of the picked item. Different batches are displayed in separate lines.

ItemDescriptionThe description of the picked item.

QuantityThe picked quantity from the batch in the uom applied in the sales order that was the base of the picklist.

Quantity per uomThe conversion rate between the base uom of the item and the uom applied in the sales order.

Inventory quantityThe picked quantity in the base uom.

Last update:2018/03/1212:56



Quantity uom2The quantity for the second uom.

7. How to customize Produmex WMS views

It is possible to customize some of the Produmex WMS queries through the use of the views.

7.1. List of customizable queries

Picklist proposal manager screenController: 5.1.3.60. Picklist proposal manager screen controllerStandard view name

Production: PMX_PICKLIST_PROPOSAL_MANAGER_PRODUCTION●

Sales: PMX_PICKLIST_PROPOSAL_MANAGER_SALES●

Transfer: PMX_PICKLIST_PROPOSAL_MANAGER_TRANSFER●

Stock allocation screenController: 5.1.3.59. Stock allocation controllerStandard view name

Customer info: PMX_STOCK_ALLOCATION_SCREEN_CUSTOMER●

Sales order info: PMX_STOCK_ALLOCATION_SCREEN_SALES_DOCUMENT●

Route planningController: 5.1.3.52. Route controllerStandard view name

Route details: PMX_ROUTE_PLANNING_DETAILS Special remarks: Because the order of the rows is●

defined in the ‘Route planning’ window, there is no ‘Order by’ field on the controller.



Open picklists: PMX_ROUTE_PLANNING_OPEN_PICK_LIST_PROPOSALS●

Open documents reportController: 5.1.3.66. Open documents screen controllerStandard view name

Route: PMX_OPEN_DOCUMENT_REPORT_ROUTE●

Pick list: PMX_OPEN_DOCUMENT_REPORT_PICKLIST●

Proposal: PMX_OPEN_DOCUMENT_REPORT_PICKLIST_PROPOSAL●

Move order: PMX_OPEN_DOCUMENT_REPORT_MOVE_ORDER●

PMX Sales Shipping: PMX_OPEN_DOCUMENT_REPORT_PMX_SALES_SHIPPING●

Container: PMX_OPEN_DOCUMENT_REPORT_CONTAINER●

Open sales order formController: 5.1.3.42. Open Sales Orders ControllerStandard view name

PMX_OPEN_SALES_ORDERS_WITH_STOCK_STATUS●

7.2. Customization process

Note: It is recommended to use the Form Setting tool for disabling a column or for changing the orderof columns because making these changes in the view might cause issues with the query.

Example: stock allocation screen- customer

Open the controller of the view.

http://wiki.produmex.name/lib/exe/detail.php?id=implementation%3Awms%3Aconfguide_complete&media=implementation:confguide:view:view_ose.png

Last update:2018/03/1212:56



7.2.1. View name

The ‘View name’ field is filled with the standard view by default.To customize the grid, make a copy of the standard view and adjust it. Do not adjust the standardview, because it will be overwritten during a version update.Note: When adding columns always paste the new columns after the default columns. The order ofthe columns can be changed later on with the Form Setting tool.

In the example we added a new column with the source table.



Copy the new view name and paste it to the ‘View name’ field, then save it. Always restart the add-onafter a parameter change.

7.2.2. Order by

To customize the sorting of the grid, change the clause in the ‘Order by’ field.The order by clause will be included at the end of the query using the view. It can contain any columnreferenced by the view.

Note: When using SAP HANA, column names are case sensitive. Don’t forget the quotation markswhen they are needed.

After adding the clause save it. Always restart the add-on after a parameter change.

Last update:2018/03/1212:56



7.2.3. Form setting tool

Open the ‘Form Setting’ window and go to the ‘Table Format’ tab.To change the order of the grid, click on and hold a ‘Column’ field then drag and place it to thedesired position. After saving it, the grid will be displayed with the newly set order.



To disable a column, disable the ‘Visible’ box next to the ‘Column’ field. After saving it, the disabledcolumn will not be visible in the grid.

Last update:2018/03/1212:56



Please note: The customizations made by the Form Settings tool will affect only the user. To hide acolumn from every user, use the localization file. Please see: 7.3.3. Hide column

7.3. Localization

When adding a custom view without a translation file, the system will take the column name from theview.

To change the column name or to support more than one language, create a new custom translationfile from the standard ‘ImportLocalizationKeys.xml’ translation file. The standard translation file canbe found under the ‘Localization’ folder in the install zip.

Open the file with a text editor and find the Localization Key of the view. The Localization Key can beseen on the controller of the view.



Copy the node within <PmxLocalizationKey> and paste it to a new file. Make sure that you added theroot tags.

<?xml version="1.0" encoding="UTF-8"?><TestRoot></TestRoot>

7.3.1. Add the translation of a custom column

The node within <PmxLocalizationProperty> contains the translation of one column. Copy the node ofany column and paste it right after the <LocalizationProperties> tag or after any</PmxLocalizationProperty> tag.

Change the column number in Columns[number of the column].Title/Header Text after<LocalizationProperty>. The new column number must be one more than the existing highest columnnumber.

The node within <PmxLocalizationValue> contains the localization value of a language.

The <LanguageCode> defines the language. You can find the languages and language codes on theOLNG table. Add the column title as the <LocalizationValue> to the node containing thecorresponding <LanguageCode>. It is not mandatory to keep the localization values of everylanguage. You can delete the <PmxLocalizationValue> nodes containing the code of languages notrequired.Save the file in xml format.

Last update:2018/03/1212:56



Example:

<?xml version="1.0" encoding="UTF-8"?><TestRoot><PmxLocalizationKey> <Canceled>False</Canceled>

<LocalizationKey>Logex.AddOn.RoutePlanningControl.GrdPicklistsWithoutRoute</LocalizationKey> <ApplicationTypeCode>SBOGUIAP</ApplicationTypeCode> <LocalizationProperties>

<PmxLocalizationProperty> <Canceled>False</Canceled> <LocalizationProperty>Columns[1].HeaderText</LocalizationProperty> <ExtensionCode>CONVSTR</ExtensionCode> <LocalizationValues> <PmxLocalizationValue> <Canceled>False</Canceled> <LocalizationValue>Type</LocalizationValue> <LanguageCode>3</LanguageCode> </PmxLocalizationValue> <PmxLocalizationValue> <Canceled>False</Canceled> <LocalizationValue>Type</LocalizationValue> <LanguageCode>16</LanguageCode> </PmxLocalizationValue> </LocalizationValues> </PmxLocalizationProperty>

</LocalizationProperties> </PmxLocalizationKey></TestRoot>

7.3.2. Edit the title of a standard column

It is also possible to change the title of a standard column. Find the column based on the columnnumber then simply rewrite the text after the <LocalizationValue> tag in the node with thecorresponding <LanguageCode>.

7.3.3. Hide column

To hide a column from every user, add a new <PmxLocalizationProperty> node in the same way asdescribed above. Change the <ExtensionCode> to ‘CONVBOOL’.



As the <LocalizationProperty> add Columns[number of the column].Visible. Add ‘False’ as the<LocalizationValue> to the node with the respective <LanguageCode>.

When using multiple languages, create a <PmxLocalizationValue> node for every used language.

Example:

<?xml version="1.0" encoding="UTF-8"?><TestRoot><PmxLocalizationKey> <Canceled>False</Canceled>

<LocalizationKey>Logex.AddOn.RoutePlanningControl.GrdPicklistsWithoutRoute</LocalizationKey> <ApplicationTypeCode>SBOGUIAP</ApplicationTypeCode> <LocalizationProperties>

<PmxLocalizationProperty> <Canceled>False</Canceled> <LocalizationProperty>Columns[13].Visible</LocalizationProperty> <ExtensionCode>CONVBOOL</ExtensionCode> <LocalizationValues> <PmxLocalizationValue> <Canceled>False</Canceled> <LocalizationValue>False</LocalizationValue> <LanguageCode>3</LanguageCode> </PmxLocalizationValue> <PmxLocalizationValue> <Canceled>False</Canceled> <LocalizationValue>False</LocalizationValue> <LanguageCode>16</LanguageCode> </PmxLocalizationValue> </LocalizationValues> </PmxLocalizationProperty>

</LocalizationProperties> </PmxLocalizationKey></TestRoot>

7.3.4. Import the translation file

Use the Produmex Import Tool to import the translation file.

Select the database with the connection string then add the file path to the field next the ‘ImportLocalization’ button or click on the ‘Browse’ button and browse the file. Click on the ‘ImportLocalization’ button to import the file. Restart the add-on.

Last update:2018/03/1212:56



The translation file will be overwritten during a Produmex database upgrade therefore you haveto repeat the import after every Produmex database upgrade.

How to setup a scale

1. Prepare setup

1.1. Install Serial Grabber

As the first step, install the Serial Grabber. The Serial Grabber is an application that tests the



connection and the configuration of the scale.

You can download the application from here: FTP

1.2. Check scale connection

Make sure the scale is connected and visible in the device manager. Only continue if the scale isvisible.

ftp://public:[email protected]/Tools/SerialGrabber.7z

Last update:2018/03/1212:56



2. Configure scale

The configuration steps might differ based on the used device. In this documentation we describe theconfiguration steps of a Mettler Toledo PS60 scale.

2.1. Verify the settings of the scale

Check the following setup parameters of the scale:

Baudrate●

Number of Databits per ASCII Characters●

Parity Bit●

Number of Stopbits●

Protocol●

Mettler Toledo PS60 exampleIn order to check the scale settings, follow these steps:

Press the ’Units’ key and hold it until the „SETuP?” message is displayed. (This takes1.approximately 10 seconds.)Press the Units key repeatedly until a required parameter is shown on the display. The2.required parameters are shown with the following codes:

Baudrate: BAud❍

Number of Databits per ASCII Characters: ASCii❍

Parity Bit: PAr❍

Number of Stopbits: StoP❍

Protocol: Proto❍

Press the Zero key to read the parameter value.3.Write down the parameter vale.4.Repeat steps 2. 3. and 4. until you have checked every required parameter.5.

Parameter Scale display Example ValueBaudrate BAud 9600Number of Databits per ASCII Characters ASCii 7Parity Bit PAr EvenNumber of Stopbits StoP 1Protocol Proto toLEdo

2.2. Test connection

Test the scale connection with the help of the SerialGrabber application.

Run the application and fill in the values:1. Port: The port number. You can check the port number on the Device Manager.

http://wiki.produmex.name/lib/exe/detail.php?id=implementation%3Awms%3Aconfguide_complete&media=implementation:wms:scale:port.png



2. Baudrate: The Baudrate value.3. Databits: The number of Databits per ASCII characters.4. Parity: The Parity value.5. Stopbits: The number of Stopbits.

Add any scale command to the field next to the ‘Send’ button (6) then press the button. You can lookup the scale command in the documentation of the scale. Make sure that you use a valid commandused by the given scale. The response of the scale is displayed on the field below the command in thefollowing format:7. TX: entered command8. time9. returned command in HEX10. returned command in ASCII

Last update:2018/03/1212:56



Example:In the example we used the get weight command for the Mettler Toledo PS60 scale which is ‘W’.In return, the Serial Grabber displays the return weight command displayed in hexadecimal andin ASCII characters.

Serial Grabber does not support special characters except for the line feed (\n) and carriagereturn (\r) characters.If you have to include another special character(s) in the entered command, you can useDocklight instead of SerialGrabber. You can download the evaluation version of Docklight fromhere: https://docklight.de/downloads/

2.3. Configure the scale

Create a scale in the Organizational Structure. For more information about the scale settings pleasesee: Scale settings.

First define the scale connection. Make sure that you use the correct scale parameters when youdefine the communication parameters. In some cases it is possible that the connection can beestablished with incorrect parameters but the scale returns the result in incorrect characters if theconnection is not set properly.

Example: Scale definition for the Mettler Toledo PS60

https://docklight.de/downloads/



The following parameters are required in order to define the scale connection:

Port number: We can check the port number on Computer Management. In this example the●

port number is COM3.Scale parameters:●

Baudrate: In this example the Baudrate value is 9600.❍

Databits: In this example the Databits value is 7.❍

Parity: In this example the Parity value is Even (E).❍

Stopbits: In this example the Stopbits value is 1.❍

If the scale is connected through direct connection, the scale definition is:com://COM3?9600,7,E,1

If the scale is connected through the ScaleComm service, the scale definition is:com://COM3?9600,7,E,1

Then set up the scale commands based on the manual of the given scale. The weight returncommand is used to return the captured weight into the Produmex application. The weight returncommand must be defined as a regular expression.

You can use the RegExTester tool to test your regular expression for the weight return command.Download the tool from here: FTP

Example: Weight return command for the Mettler Toledo PS60On the SerialGrabber we can see that the scale returns the following HEX command:02 30 30 31 2E 39 30 0D

The HEX command starts and ends with a control character, in this example the start controlcharacter is ‘02’ and the end control character is ‘0D’.

HEX code Regexp code02 \x020d \x0d

The string between the control characters is the weight. The weight in the expression shouldalways be surrounded by (?’weight’). Because the weight string can contain any character andhas no defined length, we also add the ‘.’ (match any character operator) and the ‘+’ (match oneor more operator) to the expression.

Therefore the regular expression for the weight return command is: \x02(?'weight'.+)\x0d

ftp://public:[email protected]/Install/RegExTester/RegExTester.zip

Last update:2018/03/1212:56



2.3.1. Legacy configuration for the Component weighing flow

Set up the scale on the Scale definition user table:

Define the code and the name.●

Define the scale provider type.●

Define scale settings●



Link a scale to a thin client on the Defines the weighing scales available to a specific thin-client usertable.Please note: Only one scale can be hooked up to a thin client.

2.4. Enable ports in remote desktop connection

Enable the ports, otherwise the scale will not communicate through the RDP session.

Open the Remote Desktop and click on ‘Show options’. Go to the Local Resources tab and click on the‘More…’ button under Local devices and resources. On the opening window check the ‘Ports’checkbox.

http://wiki.produmex.name/lib/exe/detail.php?id=implementation%3Awms%3Aconfguide_complete&media=implementation:confguide:scale_setup:scale_setting2.png

Last update:2018/03/1212:56



9. Best practices

9.1. Custom reports

When creating custom reports, based on a default report, it is best to rename the reports, to avoid itto be overwritten after an upgrade.

When the default stored procedure provided by Produmex needs to be extended, it is also best torename the stored procedure. Otherwise the changes will be overwritten after upgrading, or runningthe update database tool.

9.2. Cached data

Some master data is cached by Produmex. This is done to avoid to query this information each timethis is needed, thus improving the performance.



So when making changes to item master data, organizational structure, … the add-on and deviceapplications should be restarted.

10. Application configurations

10.1. General parameters

Logging levelThe logging level defines the amount of logging done by the application. Each event that can belogged has a priority. The logging level defines which events will be added to the log file.

Logging levels listed in order of increasing amount of information logged:

OFF●

FATAL●

ERROR●

WARN●

INFO●

DEBUG●

ALL●

Add-On Loader

Fat Client

http://wiki.produmex.name/lib/exe/detail.php?id=implementation%3Awms%3Aconfguide_complete&media=implementation:wms:config:appconfig:addonloader_log.png

http://wiki.produmex.name/lib/exe/detail.php?id=implementation%3Awms%3Aconfguide_complete&media=implementation:wms:config:appconfig:fatclient_log.png

Last update:2018/03/1212:56



ScaleCommService

Notification Listener

http://wiki.produmex.name/lib/exe/detail.php?id=implementation%3Awms%3Aconfguide_complete&media=implementation:wms:config:appconfig:scalecomm_log.png

http://wiki.produmex.name/lib/exe/detail.php?id=implementation%3Awms%3Aconfguide_complete&media=implementation:wms:config:appconfig:nl_log.png



10.2. Add-On

The configuration file of the add-on loader will be used. The configuration file for the add-on loaderapplication is located in the folder of the Add-On Loader, for examlpe: C:\Program Files(x86)\SAP\SAPBusiness One\AddOns\PMX\Produmex AddOnLoader 7The file name is Produmex.Foundation.Sbo.AddOnLoader.exe.config

TransactionIsolationDefines the isolation level. For more information please see: IsolationLevelEnumerationDefault value: ReadCommitted

TransactionTimeoutSets the wait time before terminating the attempt to commit the transaction. The value is inhour:minute:second format.Default value: 00:10:00

CommandTimeout

https://msdn.microsoft.com/en-us/library/system.data.isolationlevel(v=vs.110).aspx

Last update:2018/03/1212:56



Sets the wait time before terminating the attempt to execute an SQL command and generating anerror. The value is in seconds.Default value: 30

NumberOfRetriesDeadlockSpecifies the amount of times the application will try to book the same transaction again, when it failsdue to specific error types like deadlock, timeout, uncommittable transaction or -2038 SBO errorcode.Default value: 3

LogDocumentAsXMLIf set to true, data sent to the SAP DI API to generate documents will be exported to the log file in xmlformat.Default value: false

In order to export documents to the log file, the ’INFO’ level logging is required. Change all ’WARN’levels to ’INFO’ in the configuration file.

10.3. Fat Client

The configuration file for the fat client application is located in the installation folder of the fat client,for example: C:\Program Files (x86)\Produmex\Produmex Fat ClientThe file name is Produmex.Sbo.Logex.Execute.FatClient.exe.config


TransactionTimeoutSets the wait time before terminating the attempt to commit the transaction. The value is in




hour:minute:second format.Default value: 00:10:00

CommandTimeoutSets the wait time before terminating the attempt to execute an SQL command and generating anerror. The value is in seconds.Default value: 30

NumberOfRetriesDeadlockSpecifies the amount of times the application will try to book the same transaction again, when it failsdue to specific error types like deadlock, timeout, uncommittable transaction or -2038 SBO errorcode.Default value: 3

LogDocumentAsXMLIf set to true, data sent to the SAP DI API to generate documents will be exported to the log file in xmlformat.Default value: false

In order to export documents to the log file, the ’INFO’ level logging is required. Change all ’WARN’levels to ’INFO’ in the configuration file.

Produmex.ScriptAssembliesPathSpecifies the path to the script assemblies.Default path: C:\Produmex\ScriptAssemblies\

Produmex.TempSAPReportPathSpecifies the path to the folder where reports that are retrieved from SAP Business One directly, arestored temporary during the printing.Default path: C:\Produmex\Reports\TempSAPReports\

Produmex.Error.BackColorDetermines the background color of the error messages. For the supported values please see:Color.FromName Method (String)Default value: DarkOrange

Produmex.Message.BackColorDetermines the background color of the information messages. For the supported values please see:Color.FromName Method (String)Default value: WhiteSmoke

Produmex.Screen.Menu.BackColorDetermines the menu background color. For the supported values please see: Color.FromNameMethod (String)Default value: LightSteelBlue

Produmex.DI_API.LanguageDefines the DI API language.Supported values: language codes (You can find the language codes in the OLNG table).Default value: EN

Produmex.Barcode.UseAltModeForBarcodeDefines whether Produmex reads scanned barcode digits as they were keyed in ALT mode or not. Set

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

https://msdn.microsoft.com/en-us/library/system.drawing.color.fromname(v=vs.110).aspx?cs-save-lang=1&cs-lang=csharp#code-snippet-1

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




Last update:2018/03/1212:56



this option to true if the ALT mode is enabled on the scanning device.Default value: false

Produmex.Barcode.ParseCode128AsGS1If set to ‘True’, every Code 128 barcode will be parsed as a GS1-128 barcode.Default value: false

Produmex.Grid.NavigationByPageDefines the grid navigation type.If set to True, the list/grid will navigate by page.If set to False, the list/grid will navigate by element.

Produmex.Screen.IEnterItemQuantityCombinedScreen.MaxNumberOfButtonsSpecifies the maximum number of the component buttons on the ‘Enter the quantity disassembled’screen in the Disassembly-weight flow. If there are more components than the value set, componentbuttons will be displayed on multiple screens. Left and right buttons will be added for navigation.

Supported values: n*n, n*(n+1), n*(n+2) where n=positive integerDefault value: 49 (7*7)

10.4. ScaleComm Service

The configuration file for the ScaleComm service is located in the installation folder of the ScaleCommservice, for example: C:\Program Files (x86)\Produmex\ProdumexScaneCommThe file name is Produmex.Sbo.Logex.ScaleComm.Service.exe.config



http://wiki.produmex.name/doku.php?id=implementation:wms:disassemblyweigh#disassemble




ModeSpecifies the communication mode of the ScaleComm Service. Possible values:

SBO: Obsolete communication mode. Scales will be identified based on the InstanceID.●

WSBO: New communication mode. Scales will be identified based on the ScalesCodes. In order to●

use Produmex Weigh, the mode must be WSBO.

Default value = WSBO

Instance IDThe instance ID of the scale defined in the Scale definition (PMX_SCLD) table. Please note: TheInstance ID will only be taken into account if the Mode is ‘SBO’.Default value = Instance 1

ScalesCodesThe scale code defined in the Produmex Organizational Structure. To add multiple scales, separatethe scale codes by comma.

Skip PollingSpecifies whether to automatically fill the Scale weight result UDT with the measured weight.

If set to ’False’ the Scale weight result UDT will be automatically filled with the weight.●

If set to ’True’ the Scale weight result UDT will not be filled automatically.●

Default value = False

Please note: When using the SBO mode, the Scale weight result UDT will not be filled regardless ofthis setting.The values saved in the Scale weight result UDT are not used in the standard Produmex WMSprocesses. However these values can be used to easily integrate the Produmex WMS scale integrationto other systems. (You can find an integration example with PDC here.)

Polling IntervalDefines the polling frequency. The value is in milliseconds.Default value = 1500

10.5. Notification Listener Tool

The configuration file for the Notification Listener tool is located in the installation folder of theNotification Listener, for example: C:\Program Files (x86)\Produmex\Produmex SB1 NotificationListener (SboConnectionString)The file name is Produmex.Foundation.SboNotification.ServiceHost.exe.config

http://wiki.produmex.name/doku.php?id=implementation:manufacturing:pdc_connect_scale

Last update:2018/03/1212:56





FrequencyMilisecondsDefines the run frequency of the Notification Listener tool. The value is in milliseconds.Default value: 5000

10.6. How to configure logging into database in the configfile

This document describes how to set additional logging into a database/schema by modifying theconfiguration file.

It is possible to insert the logs into an UDT in the given database or into a manually created table in aseparate database.

10.6.1. Logging into an UDT

10.6.1.1. Create UDT

First create the user defined table in SAP Business One.

In this example we added a PMX_LOG user table.

Then add the following fields to the user table:

field name field type field structure lengthDate Date/Time Date -

Thread Alphanumeric Text -




field name field type field structure lengthLevel Alphanumeric Regular 50

Logger Alphanumeric Text -Message Alphanumeric Text -Exception Alphanumeric Text -

DomainName Alphanumeric Regular 50UserName Alphanumeric Regular 50

SessionName Alphanumeric Regular 50

10.6.1.2. Modify config file

Download an example for the fat client config file from here:

MSSQL: Produmex.Sbo.Logex.Execute.FatClient.exe_WITH SQL Log_1.config●

HANA: Produmex.Sbo.Logex.Execute.FatClient.exe_WITH HANA Log_1.config●

10.6.1.2.1. Trigger Ado Net Appender

In order to trigger the Ado Net Appender, add the following to the root tag:

<appender-ref ref="AdoNetAppender" />

If there is no logging level defined in the root tag, then the logging level is the minimum logging levelset for the AdoNetAppender.

If there is a logging level defined in the root tag, then that logging level is used regardless of theminimum logging level set for the AdoNetAppender.

http://wiki.produmex.name/lib/exe/fetch.php?media=implementation:wms:config:appconfig:produmex.sbo.logex.execute.fatclient.exe_with_sql_log_1.zip

http://wiki.produmex.name/lib/exe/fetch.php?media=implementation:wms:config:appconfig:produmex.sbo.logex.execute.fatclient.exe_with_hana_log_1.zip

Last update:2018/03/1212:56



10.6.1.2.2. Edit appender tag

Then insert the following before the <root> tag:

MSSQL

<appender name="AdoNetAppender" type="log4net.Appender.AdoNetAppender"> <filter type="log4net.Filter.LevelRangeFilter"> <levelMin value="DEBUG" /> <levelMax value="FATAL" /> </filter> <bufferSize value="100" /> <connectionType value="System.Data.SqlClient.SqlConnection, System.Data,Version=1.0.3300.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" /> <connectionString value="data source=server;initialcatalog=database;integrated security=false; persist security info=True;UserID=user;Password=password" /> <commandText value="NSERT INTO "@PMX_LOG"("Code","Name","U_Date","U_Thread","U_Level","U_Logger","U_Message","U_Exception","U_DomainName","U_UserName","U_SessionName") SELECT NEWID(), NEWID(), @log_date, @thread, @log_level, @logger,@message, @exception,@DomainName,@UserName,@SessionName" /> <parameter> <parameterName value="@log_date" /> <dbType value="DateTime" /> <layout type="log4net.Layout.RawTimeStampLayout" /> </parameter> <parameter> <parameterName value="@thread" /> <dbType value="String" /> <size value="4000" /> <layout type="log4net.Layout.PatternLayout"> <conversionPattern value="%thread" /> </layout> </parameter> <parameter> <parameterName value="@log_level" /> <dbType value="String" /> <size value="50" />

Last update:2018/03/1212:56



</appender>

HANA

<appender name="AdoNetAppender" type="log4net.Appender.AdoNetAppender"><bufferSize value="100" /><connectionType value="System.Data.Odbc.OdbcConnection, System.Data,Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" /><connectionString value="Driver=driver;SERVERNODE=server address:portnumber;CURRENTSCHEMA=schema;UID=user;PWD=password;" /><commandText value="INSERT INTO "@PMX_LOG" SELECT SYSUUID,SYSUUID, ?, ?, ?, ?, ?, ?, ?, ?, ? FROM DUMMY" /> <parameter> <parameterName value="@log_date" /> <dbType value="DateTime" /> <layout type="log4net.Layout.RawTimeStampLayout" /> </parameter> <parameter> <parameterName value="@thread" /> <dbType value="String" /> <size value="4000" /> <layout type="log4net.Layout.PatternLayout"> <conversionPattern value="%thread" /> </layout> </parameter> <parameter> <parameterName value="@log_level" /> <dbType value="String" /> <size value="50" /> <layout type="log4net.Layout.PatternLayout"> <conversionPattern value="%level" /> </layout> </parameter> <parameter> <parameterName value="@logger" /> <dbType value="String" /> <size value="4000" /> <layout type="log4net.Layout.PatternLayout"> <conversionPattern value="%logger" /> </layout> </parameter> <parameter> <parameterName value="@message" /> <dbType value="String" /> <size value="64000" /> <layout type="log4net.Layout.PatternLayout"> <conversionPattern value="%message" /> </layout> </parameter> <parameter>



<parameterName value="@exception" /> <dbType value="String" /> <size value="64000" /> <layout type="log4net.Layout.ExceptionLayout" /> </parameter> <parameter> <parameterName value="@DomainName" /> <dbType value="String" /> <size value="50" /> <layout type="log4net.Layout.PatternLayout"> <conversionPattern value="${USERDOMAIN}" /> </layout> </parameter> <parameter> <parameterName value="@UserName" /> <dbType value="String" /> <size value="50" /> <layout type="log4net.Layout.PatternLayout"> <conversionPattern value="${USERNAME}" /> </layout> </parameter> <parameter> <parameterName value="@SessionName" /> <dbType value="String" /> <size value="50" /> <layout type="log4net.Layout.PatternLayout"> <conversionPattern value="${SESSIONNAME}" /> </layout> </parameter></appender>

10.6.1.2.3. Adjust the log4net connection string

Adjust the dummy connection string in the log4net part to point to your database/schema.

SQL

<connectionString value="data source=server;initialcatalog=database;integrated security=false; persist security info=True;UserID=user;Password=password" />

The DATA SOURCE is the server name.The INITIAL CATALOG is the database where the logging table has been created.The USER ID is the database user and the PASSWORD is the password of the user.

Last update:2018/03/1212:56



HANA

<connectionString value="Driver=driver;SERVERNODE=server address:portnumber;CURRENTSCHEMA=schema;UID=user;PWD=password;" />

The DRIVER is {HDBODBC32} on 32 bit environments and {HDBODBC} on 64 bit environments.The SERVERNODE is the server address and the port number, for example 10.45.74.42:30015.The CURRENTSCHEMA is the schema where the logging table has been created.The UID is the database user ID and the PWD is the password of the user.

10.6.2. Logging into a separate database

10.6.2.1. Create the log table

First create a new database/schema for the log table. Then run the following query on thedatabase/schema:

MSSQL

CREATE TABLE [dbo].[PMX_log] ([Id] [int] IDENTITY (1, 1) NOT NULL,[Date] [datetime] NOT NULL,[Thread] [varchar] (4000) NOT NULL,[Level] [varchar] (50) NOT NULL,[Logger] [varchar] (4000) NOT NULL,[Message] [varchar] (64000) NOT NULL,[Exception] [varchar] (64000) NULL,[DomainName] [varchar] (50) NULL,[UserName] [varchar] (50) NULL,[SessionName] [varchar] (50) NULL)

Where the PMX_log is the name of the table where the log entries will be inserted.

HANA

CREATE TABLE "schema"."PMX_log " ( "Date" datetime NOT NULL, "Thread" varchar (4000) NOT NULL, "Level" varchar (50) NOT NULL, "Logger" varchar (4000) NOT NULL, "Message" varchar (64000) NOT NULL, "Exception" varchar (64000) NULL, "DomainName" varchar (50) NULL,



"UserName" varchar (50) NULL, "SessionName" varchar (50) NULL)

Where the schema is the new schema and the PMX_log is the name of the table where the log entrieswill be inserted.

10.6.2.2. Modify config file

Download an example for the fat client config file from here:

MSSQL: Produmex.Sbo.Logex.Execute.FatClient.exe_WITH SQL Log_2.config●

HANA: Produmex.Sbo.Logex.Execute.FatClient.exe_WITH HANA Log_2.config●

10.6.2.2.1. Edit appender tag

Insert the following before the <root> tag:

<appender name="AdoNetAppender" type="log4net.Appender.AdoNetAppender"> <filter type="log4net.Filter.LevelRangeFilter"> <levelMin value="DEBUG" /> <levelMax value="FATAL" /> </filter> <bufferSize value="100" /> <connectionType value="System.Data.SqlClient.SqlConnection, System.Data,Version=1.0.3300.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" /> <connectionString value="data source=server;initialcatalog=extra_database;integrated security=false; persist securityinfo=True;User ID=user;Password=password" /> <commandText value="INSERT INTO "PMX_Log"("Date","Thread","Level","Logger","Message","Exception","DomainName","UserName","SessionName") VALUES (@log_date, @thread, @log_level,@logger, @message, @exception,@DomainName,@UserName,@SessionName)" /> <parameter> <parameterName value="@log_date" /> <dbType value="DateTime" /> <layout type="log4net.Layout.RawTimeStampLayout" /> </parameter> <parameter> <parameterName value="@thread" /> <dbType value="String" /> <size value="4000" /> <layout type="log4net.Layout.PatternLayout"> <conversionPattern value="%thread" /> </layout> </parameter> <parameter>

http://wiki.produmex.name/lib/exe/fetch.php?media=implementation:wms:config:appconfig:produmex.sbo.logex.execute.fatclient.exe_with_sql_log_2.zip

http://wiki.produmex.name/lib/exe/fetch.php?media=implementation:wms:config:appconfig:produmex.sbo.logex.execute.fatclient.exe_with_hana_log_2.zip

Last update:2018/03/1212:56



<parameterName value="@log_level" /> <dbType value="String" /> <size value="50" /> <layout type="log4net.Layout.PatternLayout"> <conversionPattern value="%level" /> </layout> </parameter> <parameter> <parameterName value="@logger" /> <dbType value="String" /> <size value="4000" /> <layout type="log4net.Layout.PatternLayout"> <conversionPattern value="%logger" /> </layout> </parameter> <parameter> <parameterName value="@message" /> <dbType value="String" /> <size value="64000" /> <layout type="log4net.Layout.PatternLayout"> <conversionPattern value="%message" /> </layout> </parameter> <parameter> <parameterName value="@exception" /> <dbType value="String" /> <size value="64000" /> <layout type="log4net.Layout.ExceptionLayout" /> </parameter> <parameter> <parameterName value="@DomainName" /> <dbType value="String" /> <size value="50" /> <layout type="log4net.Layout.PatternLayout"> <conversionPattern value="${USERDOMAIN}" /> </layout> </parameter> <parameter> <parameterName value="@UserName" /> <dbType value="String" /> <size value="50" /> <layout type="log4net.Layout.PatternLayout"> <conversionPattern value="${USERNAME}" /> </layout> </parameter> <parameter> <parameterName value="@SessionName" /> <dbType value="String" /> <size value="50" /> <layout type="log4net.Layout.PatternLayout">

Last update:2018/03/1212:56



</parameter> <parameter> <parameterName value="@exception" /> <dbType value="String" /> <size value="64000" /> <layout type="log4net.Layout.ExceptionLayout" /> </parameter> <parameter> <parameterName value="@DomainName" /> <dbType value="String" /> <size value="50" /> <layout type="log4net.Layout.PatternLayout"> <conversionPattern value="${USERDOMAIN}" /> </layout> </parameter> <parameter> <parameterName value="@UserName" /> <dbType value="String" /> <size value="50" /> <layout type="log4net.Layout.PatternLayout"> <conversionPattern value="${USERNAME}" /> </layout> </parameter> <parameter> <parameterName value="@SessionName" /> <dbType value="String" /> <size value="50" /> <layout type="log4net.Layout.PatternLayout"> <conversionPattern value="${SESSIONNAME}" /> </layout> </parameter></appender>

10.6.2.2.2. Trigger Ado Net Appender

Please see: 10.6.1.2.1. Trigger Ado Net Appender

10.6.2.2.3. Adjust the log4net connection string

Adjust the dummy connection string in the log4net part to point to the extra database/schema wherethe created log table is located.

SQL

<connectionString value="data source=server;initialcatalog=extra_database;integrated security=false; persist securityinfo=True;User ID=user;Password=password" />



The DATA SOURCE is the server name.The INITIAL CATALOG is the new database where the log table is located.The USER ID is the database user and the PASSWORD is the password of the user.

HANA

<connectionString value="Driver=driver;SERVERNODE=server address:portnumber;CURRENTSCHEMA=extra_schema;UID=user;PWD=password;" />

The DRIVER is {HDBODBC32} on 32 bit environments and {HDBODBC} on 64 bit environments.The SERVERNODE is the server address and the port number, for example 10.45.74.42:30015.The CURRENTSCHEMA is the new schema where the log table is located.The UID is the databse user ID and the PWD is the password of the user.

11. 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.

Last update:2018/03/1212:56



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

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.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:

Last update:2018/03/1212:56



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).❍

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_CompartmentNrC1;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.

Last update:2018/03/1212:56



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

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


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 ImportAllergens and save the worksheet as a CSV file. The CSVfile should look like this:

ItemCode;AllergenCode;CanContainAllergenA006;GLUTEN;YA006;EGGS;N

1.1.14. Item – Card Code/Quality status


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. Organizational Structure settings

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

Last update:2018/03/1212:56



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\SAPBusiness 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. The selectedconnection 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 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●

Last update:2018/03/1212:56



Item – Zone types●

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.

Last update:2018/03/1212:56



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.

Last update:2018/03/1212:56



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 destinationdatabase:

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●

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

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

Last update: 2018/03/12 12:56

http://wiki.produmex.name/

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