27th Sept 16

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

Sync
Updated – version 11.9

Testing
against AP Young (downloaded from their server tonight)

Core
Lines Added/Removed legitimately has about 263 new lines and 843 removed lines
(approx 40 pages).

I
don’t know why they have so many changed lines, but the logic is correct.
Subsequent syncs should only display a few parts added and removed.

Core
lines are now matched on SKU only.

If
it cannot find a matching SKU, but the Part already exists, the Core product is
not added to the system to avoid duplicates.

This
means a store will not have 100% of the core lines in their system, but close
to it.

If
a SKU matches, but the Barcode is different, old barcode and part is added to
F7 with a suppcode = “AB S/S” (this will appear on the supersession report)

If
a SKU matches, but the Part is different, change Part number is triggered. We
do not create the AB S/S entry in F7 for this instance.

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
peach Members Profile Find Members Posts Admin Group THE BOSS Joined: 01-Jan-2006 Status: Offline Points: 1295	Post Options Post Reply Quote peach Report Post Thanks(0) Quote Reply Topic: 27th Sept 16 Posted: 27-Sep-2016 at 15:16
	Sync Updated – version 11.9 Testing against AP Young (downloaded from their server tonight) Core Lines Added/Removed legitimately has about 263 new lines and 843 removed lines (approx 40 pages). I don’t know why they have so many changed lines, but the logic is correct. Subsequent syncs should only display a few parts added and removed. Core lines are now matched on SKU only. If it cannot find a matching SKU, but the Part already exists, the Core product is not added to the system to avoid duplicates. This means a store will not have 100% of the core lines in their system, but close to it. If a SKU matches, but the Barcode is different, old barcode and part is added to F7 with a suppcode = “AB S/S” (this will appear on the supersession report) If a SKU matches, but the Part is different, change Part number is triggered. We do not create the AB S/S entry in F7 for this instance.

peach Members Profile Find Members Posts Admin Group THE BOSS Joined: 01-Jan-2006 Status: Offline Points: 1295	Post Options Post Reply Quote peach Report Post Thanks(0) Quote Reply Posted: 27-Sep-2016 at 12:56
	The Supersession report now works and has a date range. Reminder the 1^st and second column are the same part,not old and new and the Barcode in F7 should be the old one. What are we doing about labels after a supersession? We should be able to print those out? I tried to determine if this was done but after an hour of trying to work out the logic I give up. What do Label Required, Cost Changed, PriceAChanged fields do. Seems to be driven from Last Modified date only? So just to confirm we need labels to print if – Price A changes Price F Changes where product Ticked use PriceF & Cash Sale Customer Ticked Use Price F is ticked or unticked Edited by peach - 27-Sep-2016 at 13:10