Overview of Merge Adjustment Transaction

Overview

When inventory is introduced through PLANT or PURCHASE transaction, a batch identity (BatchID) is assigned to the crop.

Merge Adjustment is a transaction used when two crop batches become the same crop:

1. The quantities are combined
2. The system compared the planted dates
3. It looks at how large the incoming quantity is compared with existing crop.
4. The 25% or 75% system setting determines which BatchID should represent the combined crop. The percentage only decides which batch identity and planted date the combined crop keeps.
5. If the BatchID changes old BatchID is closed using Merge Adjustment. For a PLANT this appears as MERGE ADJUSTMENT; for a MOVE/SHIFT it appears as MERGE-IN / MERGE-OUT.

A Merge Adjustment does not change the total number of plants. It records that one batch has been folded into another batch.

Example:

Adding a Younger Crop to an Older Crop

Let's say we already have: Existing Crop

BatchID	Date	Ready	Location	Bed	Qty
100	June 1	Spring	Field	None	1000

Then we plant or purchase another 200 in same location and ready on June 15 The new planting is younger

Then system compares the new quantity to what was already there: 200/1000 = 20%

Then setting says the younger crop needs to be at least 25% of the existing crop before the younger BatchID takes over.

Since 20% is below the setting, the original batch stays. The result is:

BatchID	Date	Ready	Location	Bed	Qty
100	June 1	Spring	Field	None	1200

What if we planted or purchased 300 into same location and bed?

Using the same example:

• Existing crop: 1000
• New addition: 300

Now: The system sees: 300/1000 = 30% That is above the 25% setting.

So the newer BatchID becomes the identity of the whole crop.

The result now will look like:

BatchID	Date	Ready	Location	Bed	Qty
101	June 15	Spring	Field	None	1300

The original BatchID 100 is then closed through a Merge Adjustment.

Adding an Older Crop to Younger Crop

The system handles the opposite situation differently.

Lets say we already have:

BatchID	Date	Ready	Location	Bed	Qty
200	June 15	Spring	Field	None	1000
300	June 1	Fall	Field	None	600

600 plants from BatchID 300 are moved - via a ready date change from Fall to Spring.

Then system compares: 600/1,000 = 60%

Then setting says the older crop needs to be at least 75% of the existing crop before the Older BatchID takes over.

Since 60% is below that setting, the existing younger BatchID (200) stays. Result is:

BatchID	Date	Ready	Location	Bed	Qty
200	June 15	Spring	Field	None	1600

What is qty for BatchID 300 planted June 1 is now 800?

Now the comparison is: 800/1000 = 80% That is above the 75% setting

In this case, the older incoming batch (BatchID:300) becomes the identity of the combined crop. Result is:

BatchID	Date	Ready	Location	Bed	Qty
300	June 1	Spring	Field	None	1800

BatchID 300 becomes the BatchID for the combined Spring crop. The existing BatchID 200 is closed through the MERGE-OUT transaction, while the combined inventory is recorded under BatchID 300 through MERGE-IN.

Why 25% One Way and 75% the Other?

The settings favor keeping the crop represented by the younger planted date.

A younger planting only needs to be 25% of the existing quantity before it can become the main batch.

An older crop has to be much more significant - 75% of the existing quantity - before it changes the crop back to the older planted date.

So with 1,000 plants already in inventory:

• 250 younger plants can cause the younger batch to take over.
• It takes 750 older plants before the older batch can take over.

One Important Detail

The percentage is compared to the quantity that was already there. For example:

• Existing crop = 1,000
• Incoming crop = 250

The system sees: 250/1,000 = 25% So the 25% setting is net.

It is not calculating the percentage against the final 1,250 plants.