User Tools

Site Tools


implementation:wms:extensionparameters

2.3. Extension Parameters tab

On the Extension Parameters tab it is possible to define parameters for certain properties. The properties and the applicable extensions are listed in the Property and Extension drop-down menus.

Select a property and the applicable extension parameter and the related parameters are displayed.

With the Search Parameters field it is possible to filter the shown parameters. Only parameters that contain the entered characters are displayed.

Extension Parameters

The following sections describe the available properties and their extensions.

2.3.1. 3PL invoicing controller
2.3.2. Archiving controller
2.3.3. Barcode controller
2.3.4. Batch number 1 on company
2.3.5. Batch number 2 on company
2.3.6. Batch number generator for sales return
2.3.7. Batch number production company
2.3.8. Best before for production generator
2.3.9. Best before for reception generator
2.3.10. Checks controller
2.3.11. Container management controller
2.3.12. Create SAP delivery from PMX delivery controller
2.3.13. Cycle count controller
2.3.14. Document series controller
2.3.15. Freight charges controller
2.3.16. Incoming payment generator
2.3.17. Interface for PMX Advance Shipping Notice importer and exporter
2.3.18. Interface for PMX move im-/export
2.3.19. Interface for PMX move order im-/export
2.3.20. Interface for PMX pick list im-/export
2.3.21. Interface for PMX serial number im-/export
2.3.22. Interface for PMX stock QS change import
2.3.23. Interface for SBO business partner im-/export
2.3.24. Interface for SBO goods issue im-/export
2.3.25. Interface for SBO goods receipt im-/export
2.3.26. Interface for SBO incoming payment im-/export
2.3.27. Interface for sbo item master data im-/export
2.3.28. Interface for SBO production issue im-/export
2.3.29. Interface for SBO production receipt im-/export
2.3.30. Interface for SBO purchase credit note im-/export
2.3.31. Interface for SBO purchase delivery im-/export
2.3.32. Interface for SBO purchase invoice im-/export
2.3.33. Interface for SBO purchase order im-/export
2.3.34. Interface for SBO purchase return im-/export
2.3.35. Interface for SBO sales credit note im-/export
2.3.36. Interface for SBO sales delivery 2 im-/export
2.3.37. Interface for SBO sales delivery im-/export
2.3.38. Interface for SBO sales invoice im-/export
2.3.39. Interface for SBO sales order im-/export
2.3.40. Interface for SBO sales return 2 im-/export
2.3.41. Interface for SBO sales return im-/export
2.3.42. Interface for SBO whs transfer im-/export
2.3.43. Inventory controller
2.3.44. IPmxStockInterface - Pmx stock im-/export
2.3.45. Location controller
2.3.46. Minimum customer stock levels controller
2.3.47. Move controller
2.3.48. On consume for production controller
2.3.47. On release of route controller
2.3.50. On sales delivery creation
2.3.51. Open documents screen controller
2.3.52. Open Sales Orders Controller
2.3.53. Packing controller
2.3.54. Picklist robot
2.3.55. Picking for production controller
2.3.56. Picklist controller
2.3.57. Picklist proposal generator
2.3.58. Picklist proposal manager screen controller
2.3.59. Production controller
2.3.60. Proof of delivery controller
2.3.61. Purchase delivery generator
2.3.62. Put away for order generator
2.3.63. Put away for production generator
2.3.64. QS reception contr. on company
2.3.65. Receive from Whs controller
2.3.66. Replenishment generator
2.3.67. Report mailer
2.3.68. Route controller
2.3.69. Sales delivery note generator
2.3.70. Sales return generator
2.3.71. Sample generator
2.3.72. Serial number controller
2.3.73. Stock allocation controller
2.3.74. Track and trace controller
2.3.75. Warehouse automation controller

2.3.1. 3PL Invoicing Controller

Extension: 3PL Invoicing Controller

3PL Invoicing Controller

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 duration
Defines 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 type
Defines 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 price calculation

2.3.2. Archiving Controller

Extension: Archiving Controller

Archiving tab

Days to keep data line database before moving to archive Y/N
With the process of archiving you will move data to separate, archive tables and with this setting you let the system know which data can be moved. In this example the configuration is 365 days, which means that the system will archive those transactional data/documents which were created/updated more than 365 days ago.

In case data refers to documents, only closed documents can be archived.
For example, if you have a pick list which was created more than 365 days ago, but is still open, it will not be archived.

General data lookup is allowed to use archive Y/N
The archived data is stored in separate, archive tables and they are not available from the SAP B1 client, however, if this setting is enabled, the system will also check the archive tables to find the necessary data.
For example Pick List number 10 is archived. If you look for this pick list in SAP B1 client and this setting is not enabled, they system will not find the pick list. If the setting is enabled, the system will find the pick list and show the details.

Sales Delivery Picklist lookup is allowed to use archive Y/N
This setting refers to archived pick lists from a sales delivery.
Archived pick lists are not available from the SAP B1 client, however, if this setting is enabled, the system will also check the archive tables to find the necessary pick list.
For example Pick List number 10 from a sales delivery is archived. If you look for this pick list in SAP B1 client and this setting is not enabled, the system will not find the pick list. If the setting is enabled, the system will find the pick list and show the details.

Traceability Report is allowed to use archive Y/N
If this setting is enabled, the Traceability Report shows archived data as well.
If this setting is not enabled, the Traceability Report shows data which has not been archived yet.

Use separate database
If the setting is enabled, the archiving process is executed to a separate database. The system automatically displays the name of the separate database on the Archiving tab of the Organizational Structure.

If the setting is disabled, the system uses the company database when the archiving process is executed.

2.3.3. Barcode Controller

(1) Extension: B10 Automotive Barcode

It captures barcodes according to B10 standards.

If the scanned value does not seem to be a B10 barcode, 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 needs to be in Code39 format. This means that the barcode needs to start with ]A0

Note: The location barcodes cannot be in format Code39, otherwise locations that for instance 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 code
S: Serial number - Will be stored as SSCC
V: Supplier code

Barcode Controller

(2) Extension: GS1 Barcode

It captures barcodes according to GS1 standards.

Barcode Controller

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 as the best before date (AI 15).

2.3.4. Batch Number 1 on Company

(1) Extension: Generates Batch Number for Reception Based on Format

Batch Number 1 on Company

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 the reception 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 on the GS1 label (if any) of the received items.

The current sequential number
Field that holds the current sequential number.

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

The format
Defines 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 value that 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 windows allowed 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 processed value should have. The fill character is ‘0’. So if the day of year is 99, and value is 3, the processed value will be 099.

[X:4]
Sequential number: This will be replaced by the sequential number. The value indicates the minimum length 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 number
The last update date in the specified format. This is used to know when the sequential number needs to be reset.

(2) Extension: Generates Prefix-Year-Month-Serial Batch Number for Reception XXXYYYYMMSSSSS

Batch Number 1 on Company

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 the reception 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 on the GS1 label (if any) of the received items.

The current month
Field that holds the current month.

The current serial
Field that holds the current serial number.

The current year
Field that holds the current year.

The length of the serial
Defines the length of the serial number

The prefix
Defines the prefix of the generated batch number.

(3) Extension: Batch Number Generator Reception - Generates Empty Batch Number for Reception

The user must enter the batch number manually.

Batch Number 1 on Company

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 on the GS1 label (if any) of the received items.

(4) Extension: Batch Number Generator Reception - Generates Year-Serial Batch Number for Reception YYYYSSSSS

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

Batch Number 1 on Company

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 the reception 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 on the GS1 label (if any) of the received items.

The current serial
Field that holds the current serial number.

The current year
Field that holds the current year.

The length of the serial
Defines the length of the serial number.

(5) Extension: Prefix-year-month-day-salesordernum batch number for reception PPPYYYYMMDD-SSSSSS

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 generated batch number.

Batch Number 1 on Company

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 the reception process.

Default postfix if no sales order link
Defines the postfix of the generated batch number, if there is no sales order linked to the purchase order.

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 on the GS1 label (if any) of the received items.

Prefix
Defines the prefix of the generated batch number.

2.3.5. Batch Number 2 on Company

2.3.6. Batch Number Generator for Sales Return

Extension: Generates Batch Number for Sales Return Based on Format

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 the production process.

The current sequential number
Field that holds the current serial number.

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

The format
Defines 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 value that 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 windows allowed 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 processed value should have. The fill character is ‘0’. So if the day of year is 99, and value is 3, the processed value will be 099.
  • [X:4]
    Sequential number: This will be replaced by the sequential number. The value indicates the minimum length 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 number
The last update date in the specified format. This is used to know when the sequential number needs to be reset.

2.3.7. Batch Number Production Company

(1) Extension: Generates Batch Number for Production Based on Format

Batch Number Production Company

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 the production 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 number
Field that holds the current sequential number.

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

The format
Defines 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 value that 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 windows allowed 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 processed value should have. The fill character is ‘0’. So if the day of year is 99, and value is 3, the processed value will be 099.

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

[X:4]
Sequential number: This will be replaced by the sequential number. The value indicates the minimum length 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 number
The last update date in the specified format. This is used to know when the sequential number needs to be reset.

(2) Extension: Generates Prefix-Year-Month-Serial Batch Number for Production XXXYYYYMMSSSSS

Batch Number Production Company

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 the production 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 date
Field that holds the current date, based upon the defined date format below. i.e.: date format = yyyy, the current date will be 2013.

The current serial
Field that holds the current serial number.

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

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

The prefix
Field that holds the prefix of the batch number.

(3) Extension: Batch Number Generator Production - Empty Batch Number

The user must enter the batch number manually.

Batch Number Production Company

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 production process.

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.

(4) Extension: Batch Number Generator Production - Generates Batch Number

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

Batch Number Production Company

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 the production 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.

2.3.8. Best Before for Production Generator

Extension: Generates Best Before Date for Production

Best Before Production Generator

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 the production 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.

Generate on every receipt
When 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.

2.3.9. Best Before for Reception Generator

Extension: Default BBD Generator for Reception

Best Before for Reception Generator

Allow to calculate based on manufacturing date
The settings allows for calculating the best before date of the item based on its manufacturing date during the Reception Flow. If the setting is enabled, the system displays the Enter Manufacturing Date button on the Enter Best Before Date screen.

When the manufacturing date is provided on the Enter Manufacturing Date screen, the system calculates the best before date based on the manufacturing date and the expiry date defined on the Item Master Data.

Entering Manufacturing Date

Can the user change the generated best before date? (Y/N)
The setting allows for changing the generated best before date of the item on the Enter Best Before Date screen of the Reception Flow. If the setting is disabled, the Enter Best Before Date screen is not displayed.

Enter Best Before Date

5.3.10. Checks Controller

The Checks Controller holds the configuration for the Checks Flow.

Extension: Checks Controller - Controls the Checks

This is the default controller to store the configuration used in the Checks Flow.

Checks Controller

Check SSCC: Show global SSCC information? (Y/N)
If the setting is enabled, the flow to check an SSCC shows a screen with additional information about the SSCC. This screen is shown after the SSCC is scanned.

2.3.11. Container Management Controller

Extension: Container Management Controller - Controls the Containers

 Container Management Controller

Allow to show purchase reserve invoices
If 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 the Container management screen.

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

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

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

Lead time in days between port and warehouse
The lead time in days between port and warehouse. This is used for the calculation of dates in the container 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.

2.3.12. Create SAP Delivery from PMX Delivery Controller

This controller holds the configuration for the tool to create an SAP delivery from a PMX sales shipping.

Extension: Create SAP Delivery

This is the default controller.

Create SAP Delivery from PMX Delivery Controller

Note: The Create automatically SAP delivery from PMX deliveries? (Y/N) setting is obsolete. It may be displayed as an available parameter, but it has no effect.

2.3.13. Cycle Count Controller

Extension: Controls the Cycle Counting

It controls the Cycle Count Flows and cycle count during other operations. Performing cycle count during other operations means that the system may ask the user to count the items while performing an operation different from cycle count, for example while performing a picking process.

 Cycle Count Controller

Allow to adjust quantity of current stock items?
If this setting and the Show current stock items setting are enabled, the user can select the current stock on the scanner, the available stock quantity is displayed, and the user can adjust the quantity instead of performing a blind count. If the setting is disabled, the displayed value on the scanner is the default value (1).

Allow to select account in case of perpetual inventory?
If the setting is enabled and Perpetual Inventory is used, the account numbers must be selected during the cycle count step Process.

Allow user to skip count
If the setting is enabled, whenever the system prompts the user to perform cycle count during other operations, the user is allowed to skip cycle count.

Auto handle batch?
If the setting is enabled, no batch needs to be entered during the cycle count process. Instead, the system tries to fill in the batch. If there is only one batch on the location, the system takes that batch. If there are multiple batches, the system takes the latest batch. If there is no batch on the location, the system takes the batch defined in setting Default batch on auto handle batch.

Auto move SSCC
The setting is available for type Lost and Found. When an SSCC is counted on a location, it is possible that in the system it is stored on another location. The following options can be set to define what the system needs to do in this case:

  • No move: The SSCC is not moved to this new location and remains recorded in the system in the original location.
  • Ask user: The system asks if the SSCC needs to be moved.
  • Auto move: The system automatically moves the SSCC to this new location.

Auto select batch/BBD when monolot pallet
When cycle counting a mono pallet (a pallet with only one item code and lot number), the system automatically selects the batch and BBD instead of asking the user to select them.

Count after number of days
The number of days after which cycle counting must be performed. A zero means that this location always has to be counted. The setting can be used only if it is not set a location level (Organizational structure elements > Cycle Count tab).

Count after number of operations
The number of operations after which cycle counting must be performed. A zero means that this location always has to be counted. The setting can be used only if it is not set a location level (Organizational structure elements > Cycle Count tab).

Count location when it becomes empty
If the setting is enabled, cycle count must be performed when the used location becomes empty during other operations.

Count type cycle count
The type of cycle count to use when performing cycle count.
Possible options:

  • Lost and Found: A virtual location where differences are recorded. This option corrects the stock on the counted location.
  • Registration: Differences are recorded in a table. With this option the stock on the counted location remains the same until the count is processed.

Note: In case of differences for items with serial number, this setting is ignored and the system uses type Registration.

Count type other operations
The type of cycle count to use when performing cycle count during other operations.
Possible values:

  • Lost and Found: A virtual location where differences are recorded. This option corrects the stock on the counted location.
  • Registration: Differences are recorded in a table. With this option the stock on the counted location remains the same until the count is processed.

Note: In case of differences for items with serial number, this setting is ignored and the system uses type Registration.

Default batch on auto handle batch
The batch number to use when there is no batch on the counted location. To use this setting the Auto handle batch? setting must be enabled.

Dummy serial number format
When using cycle count type Lost and Found and processing the cycle count for lost serial numbers managed with on release only method, dummy serial numbers might need to be generated in order to be issued. With this setting a fix part for all dummy serial numbers can be entered and then the system amends the entered value with incrementing numbers to generate unique dummy serial numbers.

Enter reason on direct cycle count?
If the setting is enabled, during the Direct Cycle Count flow the user must select a reason why there is a difference between the counted items and the items recorded in the system. The reasons can be defined on the Reasons tab of the Organization Structure.

Enter reason when skipping count?
If the setting is enabled, the user must enter a reason when skipping the count during other operations.

Manually set price on processing the count
If this setting is enabled, the user can enter the price that needs to be used when creating goods issue/receipt documents. By default, the new price is the value indicated in the Item Cost column of the Processing Cycle Count screen.
For catch weight items a price per weight can be entered.

Note: If the setting is enabled, settings Price List for Goods Issue and Price List for Goods Receipt are ignored for any price calculation.

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

  • An SBO price list (OPLN.ListNum)
  • 0 or no value: the system uses the default settings of SAP Business One
  • -1 for the last purchase price
  • -2 for the last evaluated price

Note: If setting Manually Set Price on Processing the Count is enabled, setting Price List for Goods Issue is ignored during any price calculation. In this case it is only used by the system to put the price list number on the header of Goods Issue documents.

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

  • An SBO price list (OPLN.ListNum)
  • 0 or no value: the system uses the default settings of SAP Business One
  • -1 for last purchase price
  • -2 for last evaluated price

Note: If setting Manually Set Price on Processing the Count is enabled, setting Price List for Goods Receipt is ignored during any price calculation. In this case it is only used by the system to put the price list number on the header of Goods Issue documents.

Propose default quantity on logistic unit
If the setting is enabled, the system automatically fills in the default quantity on a logistic unit.

Registration: Store lines with no difference
The setting applies to cycle count type Registration. If the setting is enabled, the system also records lines in the registration table where the counted difference is zero.

Show current stock items
If the setting is enabled, the system displays the Items on Location screen and shows the current items in stock for the selected location when the counting starts. If the setting is disabled, the screen is not displayed.

Show differences during cycle count
If the setting is enabled, after counting a location the scanner shows the differences between the counted items and the items recorded in the system.

Show differences during other operations
If the setting is enabled, after counting a location during other operations, the scanner shows the differences between the counted items and the items recorded in the system.

2.3.14. Document Series Controller

Extension: Default SAP Document Series

Note: The controller will be removed from Produmex WMS.

Document Series Controller

2.3.15. Freight Charges Controller

Extension: Controls the Freight Charges

 Freight Charges Controller

Document price reference
The price to take in account for the freight charges

View name
The 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

2.3.16. Incoming Payment Generator

It requires a custom extension that allows for generating incoming payment documents.

2.3.17. Interface for PMX Advance Shipping Notice Importer and Exporter

Extension: Advance Shipping Notice Interface - Default

Interface for PMX Advance Shipping Notice Importer and Exporter

The CSV file
The CSV file is received from a supplier and from the file goods that are received against purchase orders and purchase invoices can be imported to SAP Business One with the Produmex Interfacing Tool.

The CSV file must contain 14 columns with predefined column names that can be present in any order (see the table below).

CSV Custom Header
If the supplier sets different column names in the header of the CSV file (for example Object Type instead of ObjType, Document Number instead of DocNum, etc.), the Interfacing Tool is not able to match the columns to the correct fields. In this case the header of the CSV file is overwritten by the CSV Custom Header.

  • If the supplier lists the columns in an order different from the default order in the CSV Custom Header field, you can change the order of the columns in the field.
  • Note: While customizing the order of the columns in the CSV Custom Header field, make sure that you do not change the column names and do not remove any value from the field.
Column name
(case sensitive)
Description
ObjType The object type of the document, it is either a purchase order or a purchase invoice.
DocNum The document number of the purchase order/purchase invoice
LineNum The correct line of the item in the purchase order
ItemCode The item code of the product
Quantity The quantity of the item to be received
SSCC The SSCC of the logistic unit
MasterSSCC The SSCC number of the master logistic unit
Batch The batch number of the product
Batch2 The second batch number of the product
BBD The best before date of the product
SerialNumber The serial number of the product
UF1 User information
UF2 User information
UF3 User information

2.3.18. Interface for PMX Move Import/Export

Extension: Move Interface – Default

Interface for PMX Move Import/Export

See Produmex Standard EDI Module.

2.3.19. Interface for PMX Move Order Import/Export

Extension: Move Order Interface – Default

Interface for PMX Move Order Import/Export

See Produmex Standard EDI Module.

2.3.20. Interface for PMX Pick list Import/Export

The Produmex picklist document has an interface, but it requires a custom controller.

2.3.21. Interface for PMX Serial Number Import/Export

The Produmex serial number document has an interface, but it requires a custom controller.

2.3.22. Interface for PMX Stock QS Change Import

The Produmex stock QS change document has an interface, but it requires a custom controller.

2.3.23. Interface for SBO Business Partner Import/Export

The SBO business partner document has an interface, but it requires a custom controller.

2.3.24. Interface for SBO Goods Issue Import/Export

The SBO goods issue document has an interface, but it requires a custom controller.

2.3.25. Interface for SBO Goods Receipt Import/Export

The SBO goods receipt document has an interface, but it requires a custom controller.

2.3.26. Interface for SBO Incoming Payment Import/Export

The SBO incoming payment document has an interface, but it requires a custom controller.

2.3.27. Interface for SBO Item Master Data Import/Export

Extension: SBO Item Master Data Interface – Default

Interface for SBO Item Master Data Import/Export

See Produmex Standard EDI Module.

2.3.28. Interface for SBO Production Issue Import/Export

The SBO production issue document has an interface, but it requires a custom controller.

2.3.29. Interface for SBO Production Receipt Import/Export

The SBO production receipt document has an interface, but it requires a custom controller.

2.3.30. Interface for SBO Purchase Credit Note Import/Export

Extension: SBO Purchase Credit Note Interface – Default

Interface for SBO Purchase Credit Note Import/Export

See Produmex Standard EDI Module.

2.3.31. Interface for SBO Purchase Delivery Import/Export

Extension: SBO Purchase Delivery Interface – Default

Interface for SBO Purchase Delivery Import/Export

See Produmex Standard EDI Module.

2.3.32. Interface for SBO Purchase Invoice Import/Export

Extension: SBO Purchase Invoice Interface – Default

Interface for SBO Purchase Invoice Import/Export

See Produmex Standard EDI Module.

2.3.34. Interface for SBO Purchase Return Import/Export

Extension: SBO Purchase Return Interface – Default

Interface for SBO Purchase Return Import/Export

See Produmex Standard EDI Module.

2.3.35. Interface for SBO Sales Cedit Note Import/Export

Extension: SBO Sales Credit Note Interface – Default

Interface for SBO Sales Cedit Note Import/Export

See Produmex Standard EDI Module.

2.3.37. Interface for SBO Sales Delivery Import/Export

Extension: SBO Sales Delivery Interface - Default

Interface for SBO Sales Delivery Import/Export

See Produmex Standard EDI Module.

2.3.36. Interface for SBO Sales Delivery 2 Import/Export

The SBO Sales Delivery 2 document has an interface, but it requires a custom controller.

2.3.38. Interface for SBO Sales Invoice Import/Export

Extension: SBO Sales Invoice Interface – Default

Interface for SBO Sales Invoice Import/Export

See Produmex Standard EDI Module.

2.3.39. Interface for SBO Sales Order Import/Export

Extension: SBO Sales Order Interface – Default

Interface for SBO Sales Order Import/Export

See Produmex Standard EDI Module.

2.3.40. Interface for SBO Sales Return 2 Import/Export

The SBO sales return 2 document has an interface, but it requires a custom controller.

2.3.41. Interface for SBO Sales Return Import/Export

Extension: Sbo Sales Return Interface – Default

Interface for SBO Sales Return Import/Export

See Produmex Standard EDI Module.

2.3.42. Interface for SBO Whs Transfer Import/Export

The SBO warehouse transfer document has an interface, but it requires a custom controller.

2.3.43. Inventory Controller

Extension: Inventory Controller – Controlls the Inventory Report

Inventory Controller

View name - Detail
The 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 - Detail
When 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 - Details
When 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:

  • 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.

2.3.44. IPMX Stock Interface - PMX Stock Import/Export

The Produmex stock document has an interface, but it requires a custom controller.

2.3.45. Location controller

This controller holds the configuration for suggesting locations on moves.

Extension: Location Controller - Handle Location Suggestions

This controller uses put away zones to get a list of possible locations to store the goods.

Location controller

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 fixed pick 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

2.3.46. Minimum Customer Stock Levels Controller

Extension: Default Minimum Customer Stock Levels Controller

It controls the Reserving Minimum Stock for Customers functionality.

Minimum Customer Stock Levels Controller

2.3.47. Move Controller

Extension: Default Move Controller

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 only item 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 to the start of the ad hoc move flow. This allows the user to quickly perform another move of the same type 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 a destination 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

2.3.48. 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.

On Consume for Production Controller

2.3.47. On release of route controller

It requires a custom extension.

2.3.50. On Sales Delivery Creation

None

2.3.51. Open Documents Screen Controller

Extension: Controller for the Open Documents Screen

Open Documents Screen Controller

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 certain values.

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

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.

<PmxLocalizationKey>
    <Canceled>False</Canceled>
   <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>
    </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.

2.3.52. Open Sales Orders Controller

(1) Extension: Open Sales Order Controller - Open Sales Orders Custom

This controller uses a view to show the data on the screen, that is, it is customizable what to show on the screen.

Open Sales Orders Controller

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

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

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

  • ObjType
  • DocEntry
  • DocDueDate
  • PmxWhsCode
  • CardCode

(2) Extension: Open Sales Order Controller - Open Sales Orders that are in Stock

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

Open Sales Orders Controller

Fields to sort by in GUI
Define 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.

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

(3) Extension: Open Sales Order Controller - Open Sales Orders with Stock Status

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

Open Sales Orders Controller

Fields to sort by in GUI
Define 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.

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

2.3.53. Packing Controller

Extension: Packing Controller - Controls the Packaging

Packing Controller

Combine Packed SSCC Flow

Start by scanning SSCC?
If the setting is enabled, the Combine Packed SSCC Flow starts with the step of scanning an SSCC and the Select customer / address screen is skipped. The customer and the address are retrieved from the picklist.

Consolidated Packing flow

Allow partially picked pick lists to be packed (Y/N)
If the setting is enabled, the system allows for packing picklists with partially picked status.

General Settings

Add logistic carriers to all Sub SSCC’s (Y/N)
If the setting is enabled, the selected logistic carrier is linked to the sub SSCC instead of the master SSCC.
If the setting is disabled, the logistic carrier is linked only to the master SSCC.

Note: The combination of adding logistic carriers to master and sub SSCCs is not possible.

The setting applies to the following flows:

Ask logistic carrier when LUID is finished
If the setting is enabled, the Packing Flow does not ask for the logistic carrier when a new LUID is started, but only when the user indicates that the LUID is full.

Allow the input of an external SSCC? (Y/N) and Force user to rescan SSCC? (Y/N)
If both settings are enabled, the system allows for scanning an external SSCC instead of generating a new SSCC automatically. When the first item is added, the system displays the Scan an SSCC extra screen and the user can scan the SSCC.

In addition, each time a new item is added, the user must rescan the SSCC to ensure that the item is added to the appropriate logistic unit. If the wrong SSCC is scanned, the system displays an error message and does not allow the item to be added to the logistic unit. The user must scan the appropriate SSCC (or select a different item and then scan the appropriate SSCC) to proceed with the flow.

Important: Both settings must be enabled to use the functionality. If only one of them is enabled, it will not have any effect.

Finished LUID screen. View name
The name of the view that is used for customizing the Finished LUID screen. Required field: LUID.

Perform automatic shipping per customer/address? (Y/N)
If the setting is enabled, the system tries to perform automatic shipping for each packed picklist for the same customer/address/ship to code instead of checking if all picklists in the wave are packed.

Pick list grouping
When packing items, the user must select the customer/address if there are multiple customer/address on the movable location or SSCC.
There are 2 options:

  • Grouping on CardCode, ShipToCode, ShipToAddress
  • Grouping on CardCode, ShipToAddress

Pick list order by
The sorting of picklists on the Select a Pick List screen of the packing flows. Options:

  • Order by due date, priority, wave key
  • Order by priority, due date, wave key

The setting applies to the following packing flows:

Time to show 'Packing LUID finished' message
The number of seconds during which time the Logistic unit finished message is shown on the scanner: Possible values:

  • Negative values: The message is not shown.
  • Value 0: The message remains visible until the user clicks the OK button.
  • Positive values: The message remains visible for the entered period of time in seconds.

Use pallet packaging type from customer master data?
If the setting is enabled, the packing flows use settings available on the business partner master data to check if multiple identical master and/or sub SSCCs need to be created.
Supported flows:

Item Packing Flow and Cash Register Packing Flow

Force user to only scan items (Y/N)?
If the setting is enabled, the quantity to pack must be added by scanning the barcodes and the quantity cannot be entered manually. The setting applies to the Item Packing Flow and Cash Register Packing Flow.

2.3.54. Picklist Robot

Extension: Default Picklist Robot

Picklist Robot

Picklists

Create picklists? (Y/N)
If set, the system will try to create picklists.

Order by
The ORDER BY clause that is used in combination with the view.

View name
The view name that will be used to create the picklists. Required fields:

  • DocEntry (Of the proposal)
  • CardCode
  • PmxWhsCode

Proposals

Create proposals? (Y/N)
If set, the system will try to create picklist proposals.

Order by
The ORDER BY clause that is used in combination with the view.

View name
The view name that will be used to create the picklist proposals.

Required fields:

  • DocEntry
  • LineNum (NULL if Production)
  • ObjType
  • DocDueDate
  • CardCode
  • ItemCode
  • ItmsGrpCod
  • PmxWhsCode
  • ProductionLineCode (NULL if Sales or Warehouse Transfer)

The default value is PMX_PICK_LIST_ROBOT_CREATE_PROPOSALS that unifies the following views:

  • PMX_PICKLIST_PROPOSAL_MANAGER_SALES
  • PMX_PICKLIST_PROPOSAL_MANAGER_TRANSFER
  • PMX_PICKLIST_PROPOSAL_MANAGER_PRODUCTION

Waves

Group waves? (Y/N)
If set, the system will try to group picklists into waves.

View name
The view name that will be used to group picklists. The logic to group picklists into waves is based on the column 'Grouping'. All rows with the same data in the field 'Grouping' will be grouped into 1 wave. The standard view will group all picklists for the same customer and delivery address into the same wave. Picklists that have been started picking will not be adjusted anymore, so the picklists will not be added to another wave, even if they have the same customer/delivery address. Required fields:

  • DocEntry
  • WaveKey
  • PickListStatus
  • CardCode
  • PmxWhsCode
  • Grouping

2.3.55. Picking for Production Controller

Extension: Picking For Production Controller - Controls the Picking for Production

 Picking for Production Controller

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

Picking order by
Select 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 picking
If 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 same functionality 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 open proposal.
If not, a pick list cannot be created.

2.3.56. Picklist Controller

Extension: Picklist Controller - Controls the Picklist

 Picklist Controller

Ad Hoc Picking

The following settings apply to the three tasks of the Ad Hoc Picking Flow (Customer Collect, Picklist and Route) on the Mobile Client.

If a setting is task specific, the documentation specifies the task(s) that the given setting applies to. If no task is specified, the given setting applies to all the three tasks.

Route picking: picklist order by
The setting applies to Ad Hoc Picking task Route and it defines the sorting of picklists.
From the drop-down menu the following options can be selected:

  • 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 the same item
If the setting is enabled, the system keeps asking the user to pick the item until everything is picked for the given item.
If the setting is disabled, it is not necessary to pick everything for the selected item. When the quantity to pick is defined, the system goes back to the overview screen of all items and the picking process can be started for another item.

Ad hoc: Auto fill pick quantity
If the setting is enabled, the quantity to pick is displayed in the quantity input field of the Enter the Quantity screen. If the setting is disabled, the displayed quantity is 1.

Note: If the quantity to pick is less than 1, the displayed quantity in the quantity input field is the maximum quantity to pick.

Ad hoc: Force to scan SSCC
If the setting is enabled, an SSCC must be scanned when performing the picking.

Allow ad hoc picking from bulk locations
If the setting is enabled, items can be picked from bulk locations (non-pick locations) as well.

Allow confirmation that all goods were picked
The setting applies to Ad Hoc Picking task Customer Collect.
If the setting is enabled and the picklist does not contain any item managed by Produmex serial numbers, the Confirm all picked goods button is displayed on the Mobile Client and the user can confirm that all the items are loaded in one step.

Allow to select a moveable location during ad hoc picking
If the setting is enabled, a movable location can be used during the Ad Hoc Picking flow.

Auto move SSCC on a customer-collected related move
The setting applies to Ad Hoc Picking task Customer Collect.
If the setting is enabled, the SSCC is automatically moved to the dock.
If the setting is disabled, the system asks the user if the SSCC needs to be moved.

Choose dock on ad hoc picking
The setting applies to Ad Hoc Picking tasks Route and Picklist.
If the setting is enabled, the system asks the user to select a dock to pick to. The selected dock is then saved on the route or picklist.

Express Ad Hoc Picking
If the setting is enabled, the Scan SSCC / Location step is skipped. Instead, after selecting a product, the user has the following options:

  • If the item is available on one single location, the system immediately asks the user to enter the quantity to pick.
  • If the item is available on more than one location, the system first asks the user to select a location and then to enter the quantity to pick.

Reason requirements when skipping first location
The Ad Hoc Picking flow suggests a number of locations where the picking can be performed and the locations are sorted in a way that the first location is the best location to pick the items from. (Docks are not considered first locations.) If the user wants to pick from another location, this setting defines if a reason for skipping the first location is needed.

The following options can be selected from the drop-down menu:

  • No reason
  • Requires user-entered reason text: Free text, entered by user, minimum 10 characters
  • Requires a reason to be selected from a list on the scanner

Show stock for location
The setting applies to Ad Hoc Picking task Picklist.
If the setting is enabled, the Select a Pick Location screen shows the free stock quantity of the selected item for each location listed on the screen.

Function/SP name to get the locations
The setting refers to the function/stored procedure that is used to get the locations for Ad Hoc Picking.

Input parameters on SQL:

  • @pmxWhsCode
  • @itemCode
  • @batchToPick
  • @separator
  • @pickListDocEntry

The input parameters can be checked in the PMX_FN_GetAllLocationsForItemForAdHocPicking standard function.

Input parameters on HANA:

  • p_pmxWhsCode
  • p_separator
  • p_pickListDocEntry

The input parameters can be checked in the PMX_SP_GetAllLocationsForItemForAdHocPickingInTmp standard stored procedure.

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

Input parameters on SQL:

  • @pmxWhsCode nvarchar
  • @itemCode nvarchar
  • @batchToPick nvarchar

The input parameters can be checked in the PMX_FN_GetFirstSequenceForLocationsForItemForAdHocPicking standard function.

Input parameters on HANA:

  • p_pmxWhsCode nvarchar
  • p_pickListDocEntry

The input parameters can be checked in the PMX_SP_GetFirstSequenceForLocationsForItemForAdHocPicking standard stored procedure.

View name to get the products
With the setting a separate view can be provided to get the products to be picked. Mandatory columns to be listed for a view:

  • DocEntry
  • PmxWhsCode
  • ProductCode
  • ProductDescription
  • ManBtchNum
  • HasBestBefore
  • GTIN
  • DefaultLocationCode
  • BaseLine
  • BaseEntry
  • LocationCodes
  • Sequence
  • batchToPick
  • StillToPick
  • QuantityPerUom

If no value is entered, the system executes the standard query.

General

Allow multiple customers on SSCC?
If the setting is enabled, the system will allow to put stock for multiple customers/delivery addresses on the same SSCC. This means that when you have a wave for multiple customers, the user is not forced to pick on a 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 contains multiple 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.

Auto selection of moveable location during picking? (Y/N)
If the setting is enabled and there is one available movable location, the system automatically selects the moveable location. In case of full pallets, no moveable location is used.

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

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 a barcode 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 the same or a lower quantity than the quantity that has to be picked for the picklist. Example: if a quantity of 60 has to be picked, and if a full pallet of 40 that answers the best before date and batch number 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 the same 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 picklist.
This setting is only used AFTER the stock is assigned to the pick list, and the user is going to pick the stock 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 list report 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 on the same or lower level as the dock selected on the pick list proposal. The levels are defined by the zones 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 all locations. The default replenishment generator will only try to create replenishment orders for the locations where goods were picked from.

JOIN-sql for custom wave description for scanner
If the ‘Custom wave description fields for scanner’ option contains fields that are not used in the default query, the user needs to define the JOIN query here.
This option cannot be used for pick list for production.

Custom wave description fields for scanner
Here the user has the possibility to enter a custom wave description that will be shown on the scanner. 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 for custom 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 the PMX_PLHE.PickPackRemarks field for example, fill this in the input box : CAST(“PMX_PLHE”.“PickPackRemarks” as nvarchar (2000))
This option cannot be used for pick list for production.

Multi-Picking

Multi picking: Allow to select wave? (Y/N)
When the setting is enabled, during Multi-Picking the user can select the wave instead of scanning a picklist.

Multi picking: Set movable location at start of picking? (Y/N)
When the setting is enabled, during Multi-Picking all the movable locations need to be assigned to a picklist before starting to perform the picking.
If the setting is disabled, the movable location is asked when the first item of a certain picklist is picked.

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 alternate picking, 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 pick location 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 the picked 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 line in 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 item identification 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 to pick.
Note: This setting does not apply to the Multi-Picking flow.

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 flag makes it possible that full monolot pallets at bulk locations (containing items that match the best before 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 pallet from bulk’.
More information at: Pick list.

Consolidate items to pick?
If the setting is enabled, items that have the same batch number/BBD/Quality status/Location/… are picked in one action instead of a pick action by picklist line.
The setting applies to the Picking flow, the Multi-Picking flow and the 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 batch number from the pick list?
Remark: If on the base document line a batch number is set, the batch will always be copied when selecting alternate items.

Force first available batch on selecting alternate item? (Y/N)
This setting refers to the process of selecting alternate stock on the fat client during a picking flow and it is based on FEFO (first expired, first out).
If it is set to true, you can select an item only from the batch with the earliest expiry date that is according to the shelf-life.
This option cannot be used in combination with Ad hoc alternate item? (Y/N). If that setting is enabled, the Force first available batch on selecting alternate item? (Y/N) setting is ignored.

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 an SSCC.
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 entering the 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 flag makes it possible that full monolot pallets at bulk locations (containing items that match the best before 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 from bulk’.
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 by
Custom 'ORDER BY' clause for when the pick list is allocating stock to the pick list line.
This is not applicable for ad hoc picking
It adds the value to the ORDER BY clause of the query to get the stock. The text 'ORDER BY' does not need 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.
When stock is not on an SSCC, the quantity not on an SSCC is still regarded as if it would be on an SSCC, 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 by
Sorting of waves on the picking flows
Options:

  • 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 by
How 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, the system will first pick all quantities of ItemA, regardless of where it is stored. (Full pallets are still picked 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 name
The 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_waveKey
This 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, but in 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:
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.
Picking

Make pick list ready for selected line? (Y/N)
If enabled, the status of the pick list lines remain ‘Not Ready’ and the system does not allocate stock to them up until the user selects the item on the scanner. This setting is used only in the Picking flow.

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 the next item to pick is in the same location.

Picking / Multi-Picking

Select wave – View name
For the picking and multi-picking flows, it is possible to define a customized view which filters the list of waves to be displayed on your scanner when you have the option of selecting a wave.
It is optional to provide a view name to the field . If you do not need a customized view, you can leave the field empty and the system will use its own query.

Mandatory fields:

  • InternalKey
  • InternalKeyAsString
  • DueDate
  • Description
  • Priority
  • SameDelivery
  • PmxWhsCode
  • ItemLabelsPrinted
  • LockedBy
  • USER_CODE
  • U_UseForPicking
  • U_UseForMultiPicking

Example view query:

SELECT "PMX_WAVE"."InternalKey" AS "InternalKey", CAST("PMX_WAVE"."InternalKey" AS NVARCHAR) AS "InternalKeyAsString", "PMX_WAVE"."DueDate" AS "DueDate", 
 "PMX_WAVE"."Description" AS "Description", "PMX_WAVE"."Priority", "PMX_WAVE"."SameDelivery", "PMX_OSEL"."PmxWhsCode", "PMX_WAVE"."ItemLabelsPrinted"
 ,"PMX_WAVE"."LockedBy", "OUSR"."USER_CODE", MAX("U_UseForPicking") AS 'U_UseForPicking', 
MAX("U_UseForMultiPicking") AS 'U_UseForMultiPicking'
 FROM "PMX_WAVE"  WITH (NOLOCK)
 INNER JOIN "PMX_PLHE"  WITH (NOLOCK) ON "PMX_WAVE"."InternalKey" = "PMX_PLHE"."WaveKey"
 INNER JOIN "PMX_OSEL"  WITH (NOLOCK) ON "PMX_OSEL"."Code" = "PMX_PLHE"."DestStorLocCode"
 LEFT JOIN "@PMX_PLTY"  WITH (NOLOCK) ON "PMX_PLHE"."PickListType" = "@PMX_PLTY"."Code"
 LEFT JOIN "OUSR"  WITH (NOLOCK) ON "PMX_WAVE"."LockedBy" = "OUSR"."INTERNAL_K"
 LEFT JOIN (  "PMX_PLLI"  WITH (NOLOCK)
    INNER JOIN "PMX_PLPL" WITH (NOLOCK) ON "PMX_PLPL"."DocEntry" = "PMX_PLLI"."BaseEntry" AND "PMX_PLPL"."LineNum" = "PMX_PLLI"."BaseLine" AND "PMX_PLLI"."BaseType" = N'PMX_PLPH'
    LEFT JOIN "PMX_OSWA" WITH (NOLOCK) ON "PMX_OSWA"."Code" = "PMX_PLLI"."StorLocCode"
 ) ON "PMX_PLLI"."DocEntry" = "PMX_PLHE"."DocEntry" AND "PMX_OSWA"."Code" IS NULL
  AND "PMX_PLLI"."PickListLineStatus" IN ('N','R')
 
 
 WHERE "PMX_WAVE"."InternalKey" 
 IN  ( SELECT DISTINCT "PMX_PLHE"."WaveKey" FROM "PMX_PLHE" WITH (NOLOCK) WHERE "PickListStatus" IN ('N' , 'R' , 'A' , 'I' ))
 AND "IsCustomerCollect" = N'N' AND "PMX_PLLI"."InvLockLevel" <> 'N' 
 AND "PMX_PLHE"."PickObjType" IN (N'Sales', N'WhsTransfer') 
 
 GROUP BY "PMX_WAVE"."LockedBy", "PMX_WAVE"."Priority", "PMX_WAVE"."DueDate", "PMX_WAVE"."InternalKey", "PMX_WAVE"."Description", "PMX_WAVE"."SameDelivery", "PMX_WAVE"."ItemLabelsPrinted", "PMX_OSEL"."PmxWhsCode", "OUSR"."USER_CODE"
Prepare Carts

Wave – View name
This view defines the waves to be displayed on the screen of the fat client.
The default view is PMX_PREPARE_CARTS_WAVE. It lists all the waves which involves a pick list type that can be used for multi-picking and to which no movable location has been assigned yet.

Mandatory fields to be provided:
1.WaveKey
2.Priority
3.WaveDescription

Wave – Order by
This setting defines the order by which the waves are displayed on the screen of the fat client.

Pick list – Order by
This setting defines the order by which the pick lists are displayed on the screen of the fat client.

Zone Picking

Lock wave by zone/user (Zone picking)
If the setting is enabled, the system locks all items to pick on the zone for the current user instead of only 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 the setting is enabled, the user can only see those waves in the Zone Picking flow that have no locking for the user.

2.3.57. Picklist Proposal Generator

(1) Extension: Picklist Proposal Generator - Generates Picklist Proposals

Picklist Proposal Generator

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 the setting is enabled, the system adds components from a BoM when there is one or more component missing. The check is done based on the original BoM.

Base document - order by
When 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

Calculate stock status for expired stock (=slower creation)? (Y/N)
For a new database, the default value is set to No.
For existing databases where Produmex WMS is already installed, the default is set to Yes. It means that the system calculates the stock status for expired stock and will display the data in the Full stock and Stock compliant shelf life on the Pick List Proposal screen.
If it is set to No, the stock status is not calculated. As a result, no data will be displayed in in the Full stock and Stock compliant shelf life on the Pick List Proposal screen.

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 are true, ad hoc picking can only pick from that batch, instead of any batch.

Prioritize pick locations over bulk locations? (Y/N)
If the setting is enabled and the Stock order by setting is set to Order by FEFO (FEFO_PickLocation), Produmex WMS chooses items with batch number first in the pick locations even if the item with batch number in bulk locations expire first. Produmex WMS selects items with batch numbers from bulk locations only if there is no item with batch number in the pick locations.

Note: If the Stock order by setting is set to an option different from Order by FEFO (FEFO_PickLocation), the Prioritize pick locations over bulk locations? setting is not applicable.

Serial numbers stock order by
This option handles what stock should be taken first to put on the proposal, for serial numbered items with 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 number found 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 not all 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 show proposals that have already a pick list.

Stock order by
This option handles what stock should be first put on the proposal. The process makes use of bin locations from the entire warehouse, even if they are not marked as pick locations. For example, FEFO chooses the first expiring batch from the entire warehouse even if the batch is on a bulk location.

Options:

  • Order by FEFO (FEFO_PickLocation)
    The sorting of stock to allocate is: Expiry date, Batch number, batchnumber2. The allocation is done on item-batch level.
  • Order by FEFO Itri (FEFO_ITRI_PickLocation)
    The sorting of stock to allocate is: Expiry date, Batch ID. The allocation is done on item-batch level.
  • Order by LUID (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.
    The allocation is done on item-batch-LUID level.

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

(2) Extension: Picklist Proposal Generator - Generates Picklist Proposals Grouped by Customer-Address

If multiple sales orders are selected for the same customer/address, they are grouped into one proposal.

Picklist Proposal Generator

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 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.

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 component missing.

Base document - order by
When 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

Calculate stock status for expired stock (=slower creation)? (Y/N)
For a new database, the default value is set to No.
For existing databases where Produmex WMS is already installed, the default is set to Yes. It means that the system calculates the stock status for expired stock and will display the data in the columns Full stock and Stock compliant shelf life on the Pick List Proposal screen.
If it is set to No, the stock status is not calculated. As a result, no data will be displayed in columns Full stock and Stock compliant shelf life on the Pick List Proposal screen.

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 are true, ad hoc picking can only pick from that batch, instead of any batch.

Prioritize pick locations over bulk locations? (Y/N)
If the setting is enabled and the Stock order by setting is set to Order by FEFO (FEFO_PickLocation), Produmex WMS chooses items with batch number first in the pick locations even if the item with batch number in bulk locations expire first. Produmex WMS selects items with batch numbers from bulk locations only if there is no item with batch number in the pick locations.

Note: If the Stock order by setting is set to an option different from Order by FEFO (FEFO_PickLocation), the Prioritize pick locations over bulk locations? setting is not applicable.

Serial numbers stock order by
This option handles what stock should be taken first to put on the proposal, for serial numbered items with 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 number found 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 not all 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 show proposals that have already a pick list.

Stock order by
This option handles what stock should be first put on the proposal. The process makes use of bin locations from the entire warehouse, even if they are not marked as pick locations. For example, FEFO chooses the first expiring batch from the entire warehouse even if the batch is on a bulk location.

Options:

  • Order by FEFO (FEFO_PickLocation)
    The sorting of stock to allocate is: Expiry date, Batch number, batchnumber2.
    The allocation is done on item-batch level.
  • Order by FEFO ITRI (FEFO_ITRI_PickLocation)
    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.
    The allocation is done on item-batch-LUID level.

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

2.3.58. Picklist Proposal Manager Screen Controller

Extension: 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.

Picklist Proposal Manager Screen Controller

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 by the 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

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

2.3.59. Production Controller

Extension: Production Controller - Controls Production Orders

 Production Controller

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 production manager. 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 master data the option to auto line up has been set. Otherwise the lined up locations will need to be set on the 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, the user 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 been prepared (Weighed, …) and it is not for the theoretical quantity, but within the tolerance, the system will fill in the prepared quantity, instead of the theoretical quantity.

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 input location to the production line when selecting the production order on the device. This will move all quantities 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 production order 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 deviates from the allowed quantity (See item master data configuration). The system will show the product description + 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 the possibility 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 size
If this is set to true, the system will create a number of logistic units, based on the default quantity defined on the item master data. If the default quantity for production is set, the system will take that quantity, 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 set waste 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 be printed?
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 this option is enabled.
When this option is enabled, the production flow will go to the screen to enter quantity/serial numbers after 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 manager can be limited. When putting a negative number here, the system will show all rows.

2.3.60. Proof of Delivery Controller

This controller holds the configuration for the Proof of Delivery functionality.

Extension: POD Controller - For IM2 ePOD

This is the default controller for the POD.

Proof of Delivery Controller

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 path
The path where the images will be stored.

Route export mode
The 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

2.3.61. Purchase Delivery Generator

Extension: Purchase Delivery Generator

Purchase Delivery Generator

Allow to enter reason on purchase delivery
This option enables you to enter a reason during reception on the handheld device. This option could be used for example to identify that there was no label found on the logistic unit and you want to record 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 the scanner 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 item to 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 the received stock for this sales order. So if a pick list is made for that sales order, the system will use the locked stock to pick. All quantities received will be locked, even if more quantity is received than what was on the purchase order.
When performing cross docking, this option should be checked, so the system will use the received items.

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 the entered/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, Batch number 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 of grouping it on item.

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

Group purchase delivery (Y/N)
During the reception, it is possible to receive stock based on multiple purchase orders for the same vendor.

  • If this setting is enabled, only one Goods Receipt PO document is created for those purchase orders.
  • If this setting is disabled, a separate Goods Receipt PO documents are created for each purchase order.

Purchase line remarks view name
The 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. So at reception the user needs to fill in all the data for each logistic unit. After all data has been entered the system will create the purchase delivery. Because the logistic labels need to be printed after the data has been entered for each logistic unit, the printed label is not based on the actual stock in the system. So if some logistic units have been printed, but for some reason there was an error while creating the purchase delivery, the labels will not correspond to stock in the system. The user will need to enter the data again to create the purchase delivery. But now he can use the already printed labels 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 user identify another location. In this case the items are stored directly on the warehouse location, and no put away is created.

Remarks view name
The 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 on the thin client.

Split received quantity into logistic units of default size (Y/N)
If enabled, the received quantity is automatically split into multiple logistic units based on the ‘Default quantity on logistical unit’ setting of the item.

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 the exchange rate defined on the purchase order instead of the current exchange rate.

2.3.62. Put Away for Order Generator

It determines how received goods (logistic units – SSCC) have to be put away.

Put Away for Order Generator

(1) Extension: Generates Full Pallet Put Away Orders (DFPPAOG)
It generates put away orders that cannot be split up. The user must move the full SSCC to a location.

(2) Extension: Generates No Put Away Orders (EMPAOGEN)
No put away orders are generated during the reception.

(3) Extension: Generates Put Away Orders (DEPAOGEN)
It generates put away orders that can be split up. When processing the order, the user can select if he wants move the full SSCC or not for monolot pallets. Mixed pallets have to be split up.

2.3.63. Put Away for Production Generator

Extension: Generates Put Away for Production

It generates production put away orders when producing onto a logistic unit.

Put Away for Production Generator

2.3.64. QS Reception Contr. on Company

QS Reception Contr. on Company

(1) Extension: Quality Status Reception Controller - Gets the Quality Status for Reception

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

If there is no quality status set for the supplier, the default quality status defined on the Produmex Purchase 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 is used. (Produmex Organizational Structure → Company → Tabpage ‘Defaults’).

(2) Extension: Quality Status Reception Controller - 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 this batch is not present in the system, the default quality status defined on the item is used. If on the item there is no default quality status set, the default quality status on company level (Produmex Organizational Structure → Company → Tabpage ‘Defaults’).

If this batch is present in the system, the system will check if the stock of this batch has the released quality status defined on the item. If on the item there is no released quality status set, the released quality status on company level. If the stock has the released quality status, the stock to receive will also 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 default quality status.

2.3.65. Receive from Whs Controller

Extension: Receive from WHS Controller – Controls the Receive from Whs Flow

 Receive from Whs Controller

General

Line remarks view name
The view that gets the line remarks to show on the scanner after the product is identified. 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.

Move all items in 1 stock transfer? (Y/N)
If enabled, the Inventory Transfer Document is created after every item is transferred, otherwise an Inventory Transfer Document is created after each transferred LUID.

Remarks view name
The view that gets the line remarks to show on the scanner after the Inventory Transfer Document is identified. 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.

2.3.66. Replenishment Generator

(1) Extension: Replenishment Generator - Generates Item Based Replenishment Orders

Replenishment Generator

This replenishment generator starts from the configuration on the item master data. It will try to generate orders where the ‘Replenishment Quantity on pick locations’ (OITM.U_PMX_RQPL found on the 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 pick locations that have this item in the ‘Can be replenished’ list and where the minimum quantity for that item on the location is higher than zero. It will try to create orders on those locations, ordered by the sequence defined on the location.
If no location can be found, or if there is enough stock on the location(s), (taking in account the maximum 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 the replenishment tool.

No destination location on order? (Y/N)
When this is checked, the system will create replenishment orders without setting the destination location.
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 the due 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 is selected, only replenishment orders for locations in the zone can be selected. The zones that are shown 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 asked regardless 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 used when the system is configured that the pick list proposal generator already locks stock based on the LUID and if on the pick list controller the option to pick full pallet from bulk location is allowed.

Stock coverage in days
In combination with the configuration on Item master data it will calculate the needed quantities within 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 by
The 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 subtracted from the current available stock on the location.

CALCULATION:

A replenishment order will be generated when: (Stock on pick location – # on pick list) < = (Est. sales qty * (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 < 50
So we need 50 items to be picked in the 15 days, but there are still 60 available, so no replenishment orders 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 < 50
So we need 50 items to be picked in the 15 days, and there are only 25 available, so replenishment orders 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

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

(2) Extension: Replenishment Generator - Generates Replenishment Orders

Replenishment Generator

This replenishment generator takes in account the items defined on the pick location. When the stock goes 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 after the 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 the replenishment 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 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 is selected, only replenishment orders for locations in the zone can be selected. The zones that are shown 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 when the system is configured that the pick list proposal generator already locks stock based on the LUID and if on the pick list controller the option to pick full pallet from bulk location is allowed.

Stock order by
The 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 be subtracted from the current available stock on the location. This means that only pick list lines without 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) < = Minimum quantity}.

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 range
In this example: 25 < 20
Since the stock on the pick location exceeds the minimum quantity, no replenishment order needs to be generated.

Configuration 2: Pick list taken into account and within the due date range
In this example: 25-12= 13 < 20
If we take into account the pick list, the quantity on the pick location will fall below the minimum quantity, 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 a non-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 be replenished from bulk locations to pick locations.

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

5.1.3.21. Report Mailer

Extension: Report Mailer Interface – Default

The Report Mailer can be used to automatically mail the purchase order report to the vendor after the purchase order is created. For more information see Notification Listener Transactions: Mail Report.

2.3.68. Route Controller

Extension: Route Controller – Controls the Routes

Route Controller

The settings below is to customize the grids on the route planning. 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 certain values.

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.

<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>
      <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 details
The name of the view that will be used.

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

Open routes (Top left grid):

Required fields:

  • DocEntry, PmxWhsCode

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

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

Localization key – Open routes
The 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 header
The name of the route that will be used.

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

Column separator – Route details header
The separator between columns.

Row separator – Route details header
The 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 'Proof of delivery' functionality.

2.3.69. Sales Delivery Note Generator

Extension: Sales Delivery Note Generator - Generates Sales Delivery Notes in Separate Transactions

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

Sales Delivery Note Generator

General

Add quantity to non-inventory sales BOM item? (Y/N)
If enabled, the non-inventory components from a sales BOM are automatically added to the sales delivery when it is created through the Produmex functionality.

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)

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 created through a tool, or manually in SAP.
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 is created.
Also when invoices need to be created immediately after the creation of the delivery, this setting cannot be enabled.

Grouping

Add grouping columns to header level? (Y/N)
Defines how data is queried for grouping. For backward compatibility the default value is ’True’. If you have performance issues during the generation of sales delivery notes, disable this setting.

If this setting is enabled, the ‘Grouping filter columns’ and the ‘Join clause for grouping filter’ fields are added in the main string:

SELECT Table1.*, <Grouping filter columns> 
FROM (
SELECT …  
FROM …
) AS Table 1 
<Join clause for grouping filter> 
WHERE …
ORDER BY … ,<Order by for grouping filter>

If this setting is disabled, the ‘Grouping filter Columns’ and the ‘Join clause for grouping filter’ fields are added in a substring:

SELECT Table1.* 
FROM (
SELECT … , <Grouping filter columns> 
FROM … 
<Join clause for grouping filter>
) AS Table 1 
WHERE …
ORDER BY … ,<Order by for grouping filter>

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 there are 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.

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

Join clause for grouping filter
When the grouping filter columns are in a table that is not available in the standard query, a join clause 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 filter
When 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”

Grouping Order by
Defines the sorting of the sales orders for the grouping. If this field is empty, the value of the 'Grouping filter columns' is used for sorting.

Shipping

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, and already 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. The remainder will still be open on the pick list.

Allow to load all SSCC’s in one time? (Y/N)
If enabled, the user will be able to load all picked SSCC in one step during shipping without scanning the barcodes.

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.

2.3.70. Sales Return Generator

Extension: Default Sales Return Generator

Sales Return Generator

Force mono lot pallet? (Y/N)
If the setting is enabled, the system does not allow to have multiple items/batches on one SSCC and the user is forced to create a new logistic unit for each item.

2.3.71. Sample Generator

Extension: Generates Samples to Supplier

The generator makes the sample orders if this is needed. A sample order is a sales order. This sales order will be created for the customer linked to the business partner on the purchase delivery. The linked business partner can be set on the Business Partner Master Data.

Sample Generator

2.3.72. Serial Number Controller

Extension: Serial Number Controller - Controls the Serial Numbers

 Serial Number Controller

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 the location.
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 a delivery or pick list.
This check happens for the item, and does not take into account the batch.

2.3.73. Stock Allocation Controller

Extension: 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.

Stock Allocation Controller

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 'Sales document'

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

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
  • OpenQtyNotAllocated
  • 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
  • OpenQtyNotAllocated
  • ObjType
  • DocEntry
  • LineNum
  • ErrorMessage

2.3.74. Track and Trace Contoller

It determines how to use the track and trace product.

Extension: Movilitas Cloud Track and Trace

It uses the Movilitas Cloud interface.

Track and Trace Contoller

API URL
The URL to the API of Movilitas Cloud

5.1.3.57. Warehouse automation controller

It requires a custom controller.

implementation/wms/extensionparameters.txt · Last modified: 2020/09/27 09:04 by vise