Reversing builds

Use Reverse Build if you made a mistake and built a BOM you did not intend to build.

Note: You cannot reverse builds that were built using Sage 200 v2010. These builds are given a status of Can't reverse in the Bill of Materials Build Records List, so they are easily identifiable.

Builds have one of these statuses to help you identify which builds can be reversed.

Built	You can reverse the build, subject to certain conditions.
Can't reverse	The build was done using Sage 200 v2010 and cannot be reversed in Sage 200 v2011.
Reversed	The build has been reversed and cannot be reversed again.

You can reverse only one build at a time and the entire build must be reversed. You cannot reverse part of a build. However, if you built from an allocation in more than one stage, you can reverse each stage separately.

You can reverse a build if:

• The build status is Built.
• You built from an existing allocation, using Confirm Build.
• You built from free stock, using Record Built Items.

Note: You may be prevented from reversing builds. A message will appear giving the reason for prevention. Typically, prevention may occur when stock has been recorded as allocated or issued.

• Assembly stock is reduced by the build quantity.
• Component stock is increased by the build quantity in the locations used for the build.

Note: Stock is added to the bottom of the stock pile, not the top. It is not put back following FIFOFirst In First Out (FIFO) is an assumption that enables the cost of stock to be calculated. When sales are made the items sold are assumed to be the earliest purchased, so the cost of items in stock always reflect the most recent purchases. rules.

• Traceable numbers created in the original build are updated to indicate that they have been reversed and may not be issued. Component traceable numbers become stock, free to be allocated or issued elsewhere.
• If Stock Control was set to produce nominal transactions, reverse nominal transactions are made to offset the nominal postings made during the build. These will use the same transaction date and URNThe unique reference number assigned to a complete transaction to assist in tracing the progress of the transaction through Sage 200. This number is 12 digits long and comprises of: 3 digits for the user number, 2 digits for the source module in which the transaction was created, and a 7 digit sequential reference number..