The method of moving FLAVOR from DEV120 to DEV110 via the export to file option in 120, and then the import from File in 110, has been the root cause of getting new GUID keys for FLAVORS. Effectively meaning duplicated FLAVOURS created, that then need to be manually cleaned up in the target environment.
New process has been tested successfully by using the PERSOS/ADMIN transaction to put a changed FLAVOUR in 120 onto a Transport, and then doing SCC1 into 110, then in 110 putting the FLAVOR onto a transport and releasing from 110 to QA.. same GUID key for FLAVOUR maintained thru all environments ..
Please consider Question Closed.