repack

Repacking is used when eggs are received in one buggy, but then must be transferred before being placed in the setter as the setter buggy is not the same size as the received buggy. The inventory of the buggy or setter is adjusted when the repack happens. Multiple received buggies may be repacked to one setter buggy, or vice versa.  For instance, if a received buggy had 10 trays that each held 12 eggs on each tray but the setter buggy was 10 trays that only held 10 eggs on each tray, the amount of eggs is adjusted when repacking is done, based on the capacity of that buggy/setter.

The following must be created prior to creating a Repack transaction:

• Physical Inventory transaction
• Buggies

The following options are outlined in this document

• Creating a Repack
• Posting a Repack

Create a Repack

1. In TMTS>HIM>Transactions>Eggs>Egg Room, select Repack.
2. In the Egg Room Repack main index, click to create a new repack transaction.
3. In the New Record dialog box, from Hatchery No, select the hatchery where the eggs are located.
4. Enter the Date of the transaction, and then click 'OK'.
5. In the Repack screen, click to add a new repack product.
6. The Repack Eggs screen will appear with all current inventory products listed.

7. From the New Buggy No drop-down menu, select the new setter buggy where the eggs will be placed. Buggies must be created prior to use in: Admin>Business>Poultry>HIM>Buggies.

8. In the Units Entered field, enter the number of units to be repacked.

9. The fields in the Egg Room Repack screen will auto-populate based on the associated physical inventory transaction.

10. WOL displays the number of weeks in lay that the entity produced eggs.

11. Egg Trans Code indicates the type of transaction. The record will create both a credit and debit transaction.

    1. Regrade (Credit) - Will transfer out from the original product receiving.

    2. Regrade (Debit) - Will transfer in to the new product.

12. Tracking No is a unique identification code used to identify the receiving transaction.
13. Complex Entity No identifies the farm.
14. Farm Name displays the name of the farm where the eggs were produced.
15. Product No identifies the required product for the repack.
16. Product Name displays a description of the repack product.
17. Breed No identifies the breed of the product that is being repacked.
18. Breed Name displays a description of the repack product.
19. Generation is used to identify the generation of the eggs.

20. Production Date indicates the date the product was produced.

21. Received Date indicates the date the eggs were received at the hatchery.

22. Egg Age indicates the age of the eggs.

23. Flock Age indicates the age of the flock.

24. Units displays the number of units to be repacked.

25. Eggs displays the number of eggs to be repacked.

26. Units Per defines the number of eggs per unit.

27. Ref No displays a defaulted optionally-entered unique reference number to identify the farm receiving transaction.
28. Load No displays the load number of the delivery.

29. Egg Weight displays the weight per egg, or a single average weight of all the eggs being regraded. Enter a value.

30. Uniformity M indicates the consistency of the weight of the toms.

31. Egg CV Uniformity indicates the coefficient variable for the weight samples.

32. Buggy No identifies the buggy that the product is being repacked on.
33. Buggy Name displays the name of the buggy used for repacking.
34. Base Hatch defaults from the standard table assigned to the entity.
35. Projected Hatch adjusts the based hatch percent on the egg age if an egg age decline table is used as well as recent hatch transactions.
36. Projected Poults will calculate how many poults will hatch from this group of eggs if the egg is an HE (Hatch Egg).
37. In the Notes field, enter any additional information relating to the repack transaction.
38. Sales SKU No indicates the sales SKU number if the sales SKU is defined.
39. Sales SKU Name displays the sales SKU name, if applicable.
40. Package No displays a unique reference number used to identify the packaging transaction, if the product was packaged.
41. The Final Egg Pickup flag will be selected if this is the last or final egg pickup of the entity.   

Post a Repack Transaction

Once the Repack transaction has been created and saved, the transaction needs to be posted. The posting process locks the record to prevent edits, and debits and credits the inventory to the correct product.

1. In the Repack main index, select the required transaction and right-click to select 'Post'. Alternatively, click the green check mark  in the top menu bar and select 'Post'.
2. To un-post a repack transaction, select the required transaction and right-click to select 'Unpost'.  This process will set the transaction status to 'Reversed' status, which allows the transaction to be edited.