Picklist profiles can't be adapted
Under certain circumstances, it is possible that the picklist profiles can be adapted, however you can't save the changes. That is because after the change has been carried out the query is displayed by name and description of the profile and a new profile is created.
In this case, please follow these instructions to delete the local application data. You should then be able again to edit the picklist profiles and save the changes.
Items can't be processed at Scan-In
If you can't scan an item during Scan-In, or if the message "PUT INTO STOCK" appears, the cause more often than not will be that after the time the order was placed onto the picklist and before the Scan-In of the individuals items on the picklist, the order has been changed in a way that pixi* can no longer assign the scanned item to the order.
In this case, you should process all items in the picklist that can be scanned and create the picklist for the affected item(s) or the order again. In the picklist history, you can see which orders the picklist was created for. This allows you to find out more quickly which order the problematic item belongs to.
Polling/Tracking-Paths are automatically reset
Under certain circumstances, the polling / tracking paths that you specify in pixi* Shipping can be reset to the default value at the next start of the application (often you see C:\ displayed here). The reason for this is, in many cases, the (missing) user rights of the Windows user on the path in the Windows registry editor, where the polling paths from the application are stored.
Make sure that as a logged-on Windows user, you start the pixi* Shipping application with rights that allow you to make changes in the intended path in the Windows Registry.
Often it is sufficient to use the option "Run as administrator" to open the pixi* Shipping application. To do this, click on the application with the right mouse button and select the above option .
If this does not get you the desired result, and you know where in the registry you must store the path, you can also enter the path directly in the registry.
Note: Please note that incorrect changes to the Windows Registry can also cause damage to Windows itself. In any case, communicate any planned changes to your administrator!
Orders appear on the picklist despite customer lock
Orders will appear on the picklist despite the customer lock. This option is disabled in the default settings.
Open the settings for creating a picklist
Disable the setting: "Include customer and orders with shipping lock"
Items from particular bins don't appear on the picklist
Items from specific storage bins do not appear on the picklist, although you have stocked items for orders there that are ready for shipment. This can occur in the following circumstances:
You are using a bin for your goods receipt and have created this afterwards.
You have not created any picklist profiles yet. When you create a picklist, you can define the storage bins which are to be taken into account and save these in a picklist profile.
You have subsequently created new storage bins with a higher sorting number than the goods receipt storage location.
In such cases, please amend the sorting numbers of the respective bin.
Amend the bin sorting number
Open the pixi* Control Center > Tables tab > Table Bins.
Check the length of the sorting number of the storage bin.
Change the number (in our example from 100,000,000 to 100,000) by 2 zeros.
The storage bin is now taken into account during the picklist creation.
Notes:
- Make sure that you do not change the order of the bins (keyword here: efficient picking).
- A high sorting number is usually selected when the storage bin has been created subsequently.
- The goods receipt bin(s) receive(s) either the lowest or the highest sorting number. This means that the bin(s) in the list is (are) at the very beginning or the end and can be excluded from the picklist creation when generating a picklist.
The sorting number of a storage bin can have a maximum of 9 digits, which means the highest sorting number is 999999999. Otherwise, the bins and their contents are not taken into account during the picklist production.
Invoice can't be printed because the subject line of the corresponding payment is too long
When attempting to print an invoice for an order, the following error message appears:
ASTA SERVER ERROR String or binary data would be truncated
This usually indicates that a subject line of a payment that is part of this order is too long.
You can edit the subject line of the payment. To do this, follow these steps:
Open the pixi* Payments application and look for the appropriate payment in the Payment matching tab.
By right-clicking on the desired payment and selecting the Properties item, you can now edit the properties of the payment.
A new window with the payment details will be opened.
In the General tab of this window, you can now edit the corresponding subject texts (01 to 03) and confirm the changes by pressing the OK button. No changes can be made in the tab Text data - all.
Afterwards it should be possible to print the invoice for the corresponding box in pixi* Invoices.
Ship-Out results in an Error Message
Initial situation: An error message is displayed on Ship-Out of an invoice/box:
cdsScanOutBox: Exception "[ASTA SERVER ERROR]ScanOUT Error --- String or binary data would be truncated"
This message can have various causes. In most cases the root cause is a field in the customers shipping address which contains too many characters. Check one of these fields:
Care of / company
Street / house number
Address remarks
Decrease the character length and try Ship-Out again. In most cases this solved the issue.