We now have the useDefaultReplacementCost parameter set to YES, rather than keying a current price determined by an internet search into the items.replacementprice field when billing for a lost item. We have deleted the replacementprice from our items so the default price is now used. But as new records are created the items.price data is being copied to the items.replacementprice field. An option to prevent the items.replacementprice field being populated for items added to MARC records created via the EDI process or by other ordering/loading methods may not suit everyone, but a copyPriceToReplacementPrice (yes/no) feature would remove the need for our weekly batch item modifications.