implementation:scan:supportguide:functional_issues
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
implementation:scan:supportguide:functional_issues [2019/08/13 13:44] vise [7.1. No blank serial number found] proofreading |
implementation:scan:supportguide:functional_issues [2019/12/05 09:48] (current) vise |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ======7. Issues while working with Produmex Scan====== | + | ======7. Issues while Working with Produmex Scan====== |
| =====7.1. No blank serial number found===== | =====7.1. No blank serial number found===== | ||
| When scanning a serial number on the client, Produmex Scan displays an error message despite the fact that there is stock for the item in the inventory: | When scanning a serial number on the client, Produmex Scan displays an error message despite the fact that there is stock for the item in the inventory: | ||
| Line 14: | Line 14: | ||
| =====7.2. Mobile picking data of pick lists cannot be synchronized===== | =====7.2. Mobile picking data of pick lists cannot be synchronized===== | ||
| When synchronizing mobile picking data on the //Pick List// screen, SAP B1 may experience a discrepancy between the picked quantity and the open quantity on the base document and it displays an error message. | When synchronizing mobile picking data on the //Pick List// screen, SAP B1 may experience a discrepancy between the picked quantity and the open quantity on the base document and it displays an error message. | ||
| - | |||
| - | {{ :implementation:scan:support:synchronize_mobile_picking_data.png |Synchronizing mobile picking data}} | ||
| - | |||
| - | {{ :implementation:scan:support:synchronize_mobile_picking_data_error2.png |Error message}} | ||
| The cause of the discrepancy is that the SAP stock has been modified during the picking process. | The cause of the discrepancy is that the SAP stock has been modified during the picking process. | ||
| Line 24: | Line 20: | ||
| * //Cannot add row without complete selection of batch/serial numbers.// \\ | * //Cannot add row without complete selection of batch/serial numbers.// \\ | ||
| * //1470000341 - Fully allocate item <itemcode> to bin locations in warehouse <whcode>. Fix stock allocations in SAP based on available quantities for all the lines of this Pick List.// | * //1470000341 - Fully allocate item <itemcode> to bin locations in warehouse <whcode>. Fix stock allocations in SAP based on available quantities for all the lines of this Pick List.// | ||
| + | |||
| + | {{ :implementation:scan:support:synchronize_mobile_picking_data.png |Synchronizing mobile picking data}} | ||
| + | |||
| + | {{ :implementation:scan:support:synchronize_mobile_picking_data_error2.png |Error message}} | ||
| __Best practice__\\ | __Best practice__\\ | ||
| - | Review the picked items (picked quantity, bin location and batch quantity) and compare them to the open quantity of the base document. Adjust the quantities manually to resolve the discrepancy or if it is not possible, create new pick lists and start the picking process again. | + | Review the picked items (picked quantity, bin location and batch quantity) and compare them to the open quantity of the base document. Adjust the quantities manually to resolve the discrepancy or if it is not possible, close the original pick list, create a new one and start the picking process again. |
| <WRAP center round tip 100%> | <WRAP center round tip 100%> | ||
| Line 33: | Line 33: | ||
| After running the query, open the Mobile Picking Data UDT (BXPLMSMOBPICK) via //Tools// > //User Defined Windows// and on the basis of the query results modify the picked quantity of the given pick list manually.</WRAP> | After running the query, open the Mobile Picking Data UDT (BXPLMSMOBPICK) via //Tools// > //User Defined Windows// and on the basis of the query results modify the picked quantity of the given pick list manually.</WRAP> | ||
| + | |||
| + | =====7.3. The stock cannot be allocated in Produmex Scan===== | ||
| + | |||
| + | Example: Error message while performing a stock transfer | ||
| + | |||
| + | {{ :implementation:scan:support:error_message.png |Error message}} | ||
| + | |||
| + | __Possible causes:__ | ||
| + | |||
| + | a) The stock is allocated for another transaction which has not been finished. | ||
| + | |||
| + | Solution: Finish the blocking transaction. | ||
| + | |||
| + | b) A transaction started in Produmex Scan must be finished in Produmex Scan. If it is finished in SAP B1, next time when you use the same stock in another transaction in Produmex Scan, the system displays the error message. The stock is allocated for the previous transaction and cannot be used for another transaction. | ||
| + | |||
| + | Solution: Cancel the blocking transaction in SAP B1. \\ | ||
| + | * Navigate to //Inventory// > //Inventory Transactions// > //Mobile Transactions// > //Search Mobile Transactions//. Here you can find the pending transactions. | ||
| + | * Double-click on the transaction and the system opens the //Mobile Transactions// screen. | ||
| + | * Right-click on the //Mobile Transactions// screen and select //Cancel//. | ||
| + | |||
| + | {{ :implementation:scan:support:mobile_transactions.png |Cancelling a transaction}} | ||
| + | |||
implementation/scan/supportguide/functional_issues.1565703849.txt.gz ยท Last modified: 2019/08/13 13:44 by vise
