What’s Changing?
Fourth’s Purchasing & Inventory release 4.6.94 includes new functionality.
Specifically:
Release Date: 8th (EMEA) / 11th July (USA) 2019
Reason for the Change
Sync Product Barcodes from CP to Property and from Enterprise to CP
While managing products at CP and Enterprise there is also a need to be able to manage, push/pull and synchronize barcodes between the Properties, CP and Enterprise. This can now be accomplished for Product barcodes.
Average Price Recalculation - Optimization
As there were growing performance issues, while recalculating the growing client data, this job needed to be optimized. There should now be visible performance improvements around this recalculation.
Customers Affected
All Purchasing & Inventory users.
Release Notes
Sync Product Barcodes from CP to Property and from Enterprise to CP
There is an additional setting under Data Synchronization for Product, called Barcodes with the option to enable Always Sync.
When enabled the user will be prompted with a message. If they proceed, all the product barcodes from the current property will be replaced with the product barcodes from the CP (parent property).
If Always Sync is enabled, barcodes will no longer be editable and new barcodes cannot be added at property level. They should be added/amended at CP. The same logic will apply if Always Sync is enabled at CP - in this case, “Enterprise” is considered the parent property.
When the Always Sync option is enabled and if there are conflicts with barcodes of Recipes at the Property, the sync action will be cancelled and a listing of all conflicts will be displayed. The conflicts should be resolved before the Sync enabling can be completed.
When Pulling/Pushing Products, extra checks are added based on the Always/Never Sync option on Products (as per Fig.1)
If the option is Never Sync, products will be Pushed/Pulled as normal. Barcodes of those products will also be pushed if there are no conflicts with existing barcodes (no barcodes will be replaced if option is Never Sync).
A message will be displayed if there are conflicts on any of the barcodes to notify the user that Push/Pull was partial (without the barcode).
If the option is Always Sync, products will be Pushed/Pulled along with their barcodes. If any of the barcodes of the products being Pushed/Pulled conflict with a Recipe barcode, the action will be cancelled and a listing of the conflicts will be provided.
If there are too many conflicting products in the Property – CP structure, Fourth advises that the barcode synchronization setting as kept as Never Sync.
Fourth’s Purchasing & Inventory release 4.6.94 includes new functionality.
Specifically:
- Sync Barcodes from CP to Property and from Enterprise to CP
- Average Price Recalculation - Optimization
Release Date: 8th (EMEA) / 11th July (USA) 2019
Reason for the Change
Sync Product Barcodes from CP to Property and from Enterprise to CP
While managing products at CP and Enterprise there is also a need to be able to manage, push/pull and synchronize barcodes between the Properties, CP and Enterprise. This can now be accomplished for Product barcodes.
Average Price Recalculation - Optimization
As there were growing performance issues, while recalculating the growing client data, this job needed to be optimized. There should now be visible performance improvements around this recalculation.
Customers Affected
All Purchasing & Inventory users.
Release Notes
Sync Product Barcodes from CP to Property and from Enterprise to CP
There is an additional setting under Data Synchronization for Product, called Barcodes with the option to enable Always Sync.
Fig.1 – Always Sync / Never Sync options for Product barcodes
When enabled the user will be prompted with a message. If they proceed, all the product barcodes from the current property will be replaced with the product barcodes from the CP (parent property).
Fig.2 – Message when “Always Sync” is enabled
If Always Sync is enabled, barcodes will no longer be editable and new barcodes cannot be added at property level. They should be added/amended at CP. The same logic will apply if Always Sync is enabled at CP - in this case, “Enterprise” is considered the parent property.
When the Always Sync option is enabled and if there are conflicts with barcodes of Recipes at the Property, the sync action will be cancelled and a listing of all conflicts will be displayed. The conflicts should be resolved before the Sync enabling can be completed.
Fig.3 – Listing of conflicting barcodes
When Pulling/Pushing Products, extra checks are added based on the Always/Never Sync option on Products (as per Fig.1)
Fig.4 – Selection of Product for Pull
If the option is Never Sync, products will be Pushed/Pulled as normal. Barcodes of those products will also be pushed if there are no conflicts with existing barcodes (no barcodes will be replaced if option is Never Sync).
A message will be displayed if there are conflicts on any of the barcodes to notify the user that Push/Pull was partial (without the barcode).
Fig.5 – Message to notify the User that not all barcodes were pushed
If the option is Always Sync, products will be Pushed/Pulled along with their barcodes. If any of the barcodes of the products being Pushed/Pulled conflict with a Recipe barcode, the action will be cancelled and a listing of the conflicts will be provided.
Fig.6 – Message to notify the User that no Products were pushed
Fig.7 – Message to notify the User that not all Products were pushed
If there are too many conflicting products in the Property – CP structure, Fourth advises that the barcode synchronization setting as kept as Never Sync.
Comments
Please sign in to leave a comment.