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

Note: The setting does not apply to the Bulk Reception Flow.

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 the setting is enabled, the system checks data entered on the purchase order and checks if the correct data has been entered on the Mobile Client.

• 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 is done based on PO line, instead of grouping it on item.
• Example: Best Before Date is entered on the purchase order. After selecting a product on the Mobile Client, the system checks the best before date on the purchase order. If you enter a different best before date on the Mobile Client, the Failed Data Check screen is displayed with the following message: Best before date entered does not match the one on the purchase order. Enter again?

Note: The setting does not apply to the Bulk Reception Flow.

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.

Note: The setting does not apply to the Bulk Reception Flow.

Example: A new view can be added with the listed query examples.
This example is displaying the shipdate and open quantity for each purchase order line.

SQL:

CREATE VIEW [dbo].[PMX_PO_LINE_REMARKS_CUSTOM] AS
 
SELECT
T1.[ObjType] 
, T1.[DocEntry] 
, T1.[LineNum] 
, T1.[ItemCode] 
, CAST(T1.[ShipDate] AS VARCHAR(20)) AS "ShipDate" 
,CAST(T1.[OpenQty] AS VARCHAR(20)) AS "OpenQty" 
FROM POR1 T1 
 
WHERE T1.LineStatus = 'O'

SAP HANA:

CREATE VIEW "PMX_PO_LINE_REMARKS_CUSTOM" AS
 
SELECT
T1."ObjType"
, T1."DocEntry"
, T1."LineNum"
, T1."ItemCode"
--, T1."FreeTxt" ++ '  Shipdate:' ++ cast(T1."ShipDate" as varchar(20)) ++ '  OpeQty:' ++ cast(T1."OpenQty" as varchar(20)) as "Remark" 
, CAST(T1."ShipDate" AS VARCHAR(20)) AS "ShipDate" 
--,T1."OpenQty" as "OpenQty" 
,CAST(T1."OpenQty" AS VARCHAR(20)) AS "OpenQty" 
FROM POR1 T1
 
WHERE T1."LineStatus" = 'O'

The result screen:

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.

Note: The setting does not apply to the Bulk Reception Flow.

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.

When we use the suggested location functionality in the reception flow (receiving items to a location instead of a dock) and the system cannot find a suitable location for the item, it automatically receives the item to the dock.

Note: The setting does not apply to the Bulk Reception Flow.

Remaining quantity by default? (Y/N)
When enabled, the open quantity on base document for the selected product is displayed on the mobile client.

Note: the displayed quantity also depends on the Default Quantity set for the Logistic unit in the Inventory Tab in the Item Master Data.

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.

Note: The setting does not apply to the Bulk Reception Flow.

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.

Note: The setting does not apply to the Bulk Reception Flow.

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.

Note: The setting does not apply to the Bulk Reception Flow.

Take the rate of the base document?
By default, SAP Business One uses the current exchange rate. If this setting is enabled, Produmex WMS uses the exchange rate defined on the purchase order header instead of the current exchange rate.