Originally written by Will Miller, last updated Feb 14, 2024, on the Swan Retail knowledge base (SRS).
Part of: SRS 7.4
Version 7.4-48
14th February 2024- Fixes
SWAN-4302 - Customer Order Payments - Error when trying to pay orders with an account
Able to pay on account in Customer Order Payments without an error
Support #: SUP-44751
SWAN-4137 - Swan Mobile Update Runner - Can't Over-Receive against Delivered line PO Receiving / warehouse PO Receiving
A parameter to control whether mobile devices are allowed to over-receive has been added to every system through this patch and will default to prevent overreceiving. (mobile_over_rec_po default to N.) Previously this parameter only existed if added manually.
If this parameter is set to N or not set then over-receiving is prevented.
If the parameter is Y to allow over-receiving then mobile with also check that the user is allowed to over-receive (as set in user maintenance in SRS). If the user has over receiving allowed then the program will allow the over receipt of purchase order lines.
Swan mobile is checking to see if over receiving is allowed so the user will only get an event error when the purchase order line is invoiced. This will need to be handled in the back office by reviewing update event errors.
Minimum SRS Version 7.4
Support #: SUP-33869
SWAN-2723 - Purchase Ordering - Items on purchase orders have their description truncated to 80 characters
Purchase Order Detail description size increased to 255 characters to match item setup and prevent detail being lost.
Minimum SRS Version 7.4
Support #: SUP-31589
- Changed
SWAN-4285 - Customer Order Payments - Standard sales order payment report to print payment types
The payment methods are printed to the standard payment print report.
SWAN-4036 - Cygnus - Optimisations of item/branch data from SRS
Query has been optimised and database indexes added to enhance performance (test time to get response before and after)
Minimum SRS Version 7.4
Support #: SUP-40890, SUP-43148
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article