Validations for merge and purge of replaced part

Validations will be:

• The part being replaced must be unique. In other words, this won't work if you allow duplicate part numbers in the item master and you are trying to use the spreadsheet to replace a part that is duplicate.
• The part being replaced must exist in the item master.
• The 'from' item still exists.
• Serialized parts are not allowed.
• The part being replaced cannot exist on an open transaction if the business parameter has been set to not allow that (the business parameter can be found on the Materials business parameters screen).
• If the Materials business parameter for a Merge Variance has a value, there will be an error if the average cost of the new item varies by more than that percentage compared to the item being replaced.
• You can merge expense items, as long as from AND to part are expense items.
• You can merge a stocked part with a non-stocked part and vice-versa, but with limitations:
• • If the 'from' part is stocked, then the quantity on hand must be zero.
  • If the merge is "mixed", meaning that it is a stock to nonstock or nonsstock to stock, then the 'from' part must not be on an open transaction. If it is, you will get a message indicating so; you can use the Open Transactions for Item option to display the open transactions for that part.
  • To determine if a merge is "mixed", the program looks at the item warehouse records. If a single warehouse has both items defined and defined differently (i.e. a different replenishment method), then it is a mixed transaction.

Note: Merge & Purge requests are created with a status of Merge Requested. There is a scheduled job that processes all those requests. This repeats the standard Merge & Purge validations. If something is invalid, the merge will not continue. All outstanding merge requests can be viewed on the Outstanding Batch Merge Requests display screen. At that point, if there is an error, you can choose the Batch Merge option which will perform the validations interactively, and you can see what prevented the merge from happening.