transfers

Movement Transfers are used when transferring entities. When birds are transferred, the period end process will calculate the costs and move the costs with the birds. Transfer occur when the birds reach a certain age, typically around 20 weeks.

The following is the validation that will occur at post for all animal transfers. The validation only occurs if the Validate Transfer Health Status option is selected in the registry for poultry:  Admin>System>Registry>Poultry Registry>Poultry>Broiler Breeder>General>Validate Transfer Health Status. All posting validation is done based on a lab test code.

a.       Posting will first look to farm status. If there is no farm status defined, it will look to entity status.

b.     If the lab test code has a Transfer Control Status = Not Tracked, no validation will be performed on the transfer.

c.     If the lab test code has a Transfer Control Status = Tracked, no validation will be performed on the transfer.

d.     If the lab test code has a Transfer Control Status = Transfer to Same Status, entities can only be transferred to farms or entities with the same status

e.      If the lab test code has a Transfer Control Status = No Transfer, entities cannot be transferred.

There are three types of transfer transactions:

• Brood to Brood: Transfers from one brood entity to one or more brood entities.
• Brood to Lay: Transfers from brood entity to one or more lay entities.
• Lay to Lay: Transfers from lay entity to one or more lay entities.

Once birds reach a designated age cap (often around 25 weeks when birds begin to lay eggs), capitalization will begin on the entity, and a Capitalization transaction can be created.

The Receiving Entity must be creating before a Movement Transfer can be created.

The following components are outlined related to creating a Movement Transfer transaction:

• Creating a Transfer
• • General
  • Sources
  • Add Multiple Source Entities
  • Destinations
• Posting a Transfer
• Molt Transfer

Create a Transfer

General

The General tab contains the general information related to the transfer. This section consists of two components:

• General
• Derived

General

1. In LMTS>LIM>Movements, select Transfers.
2. In the Transfers main index, selectto create a new transfer.
3. Click on the General tab.

4. From the Movement Type drop-down menu, select the source and destination stages for the transfer. Available options are: Brood Brood, Brood Lay, or Lay Lay.
5. In the Trans Date Time field, enter the date that the transfer occurred. This date will be used for all inventory and accounting transactions.
6. Event Date defaults to the same date as the transaction date, and can be modified if required. This date does not affect inventory or accounting.
7. Ref No is an automatically-generated unique number that identifies the transfer transaction.
8. Load No is an optional field to assign a number to the load.
9. From Ship To Customer No, select the customer to whom the product will be shipped.
10. Bill To Customer No defaults in from the Ship To customer.
11. From Deliver To Customer No, select the deliver-to customer.
12. Vendor No identifies the vendor.
13. Driver No is an optional field to identify the internal driver used for the transfer. Drivers must be set up prior in: Admin>Business>General>Definitions>Drivers.
14. Vehicle No is an optional field to identify the internal vehicle used for the transfer. Vehicles must be set up prior in: Admin>Business>General>Definitions>Vehicles.
15. In the Start Time field, enter the time that the animals will begin loading.
16. In the End Time field, enter the time that the animals will be finished loading.
17. Select the Truck Wash flag to indicate if the truck was washed at exit.
18. Select the Health Papers flag if health papers were complete and sent with the transfer.
19. Selecting the Void flag will void the transaction and exclude it from the entity's statistic.
20. Gross is an optional field to enter the gross weight of the load in lbs or kgs.
21. Tare is an optional field to enter the tare weight of the vehicle in lbs or kgs.
22. Net is an optional field to enter the net weight of the vehicle in lbs or kgs.
23. In the Comments field, enter any additional information relating to the transfer.
24. The Transfer History flag should be selected to create entity history records for the source and destination entities. The flag will be selected by default but can be de-selected if required.
25. From Population Mode, select the type of transfer that is being completed. Available options are:

    1. 1. Molting - is used on Lay to Lay transfers for entities that will be Molted – the destination lay entity is set to “Pre-Cap” entity stage Brood, the unamortized dollars from the source entity become the pre-cap inventory value of the destination entity.  If the entity is checked as a molt the BPA recognizes that and looks for a corresponding MOLT Standard. Click here to view the process related to molting an entity.

       2. Population - Moves bird inventory and cost based on the transfer percent to the destination entity.

       3. Spiking - If the source entity is a male only entity, costs will be transferred. If the source entity is a mixed entity, no costs will be transferred.

26. Customer PO No identifies the customer purchase order number.

Derived

The fields in the Derived tab default in from the information entered in the Sources and Destinations tabs. The information in these fields is read-only and cannot be modified.

1. Head Shipped indicates the number of animals transferred out from the source entity.
2. Head Received indicates the number of animals that were received at the destination entity. This field will be populated after the destination data is entered.
3. Head Variance is a calculated field that indicates the variance in the amount of animals shipped and the amount of animals received, if applicable. Head Variance = Head Shipped - Head Received.
4. Ship To Customer Name displays the ship-to customer.
5. Bill To Customer No displays the bill-to customer.
6. Deliver To Customer No displays the delivery-to customer.
7. Vendor Name displays the vendor.
8. Driver Name displays the driver used for the transfer.
9. Vehicle Name displays the vehicle used for the transfer.
10. Order No indicates the order used.
11. Purchase Order No indicates the purchase order used for the transfer.
12. Creation Date indicates the date the transfer transaction was created.
13. Last Mod Date indicates the date the transaction was last modified.

Sources

The Source tab defines the entities from where the animals are being transferred. Entities can be added one at a time, or there is also an option to add multiple entities at one time.

1. In the Sources tab, clickto add a new source line.

2. From Complex Entity No, select or enter the farm where the birds were transferred from.
3. Farm Name defaults from Complex Entity No and displays the name of the farm where the birds were transferred from.

4. Select the Sex of the birds being transferred.

5. In the Head Shipped field, enter the number of birds that were shipped from the source entity.

6. Head Received indicates the number of birds received. This will default in from the Destinations tab.

7. Head Variance displays the variance in the number of birds shipped versus the number of birds received, if applicable.

8. Transfer % calculates the transfer percentage of birds transferred to the bird inventory, if all of the birds are not transferred.

9. The Uniformity field represents the consistency of the weight of the birds. If applicable, enter the uniformity number.

10. Enter the number of birds Culled in the transfer process.

11. The unit Price will default in if internal pricing is used.

12. Enter the average Weight of the birds that were transferred.

13. Inventory Quantity displays the total number of birds in the transferring entity`s inventory.

14. Enter the Time that the transfer was completed.

15. Ref No displays an automatically-generated unique reference number for the transaction.

16. Head Received indicates the number of birds that were received at the destination entity. This will default in from the Destinations tab.

17. Select the Final Transfer flag if the final transfer has been made from the house. This clears the house inventory and  moves the dollars at period end.

18. Select the Final Farm Transfer flag if the final transfer from the farm has been made. This clears the farm inventory and  moves the dollars at period end.

19. Employee No is an optional field to identify the employee who performed the transfer.

20. Sales SKU No identifies the sales SKU invoice product.

21. Sales SKU Name displays a description of the product.

Add Multiple Source Entities

There is also an option to select multiple source entities from one single farm. *Note: This option is only available in version 7.26 and up.

1. In the Sources tab, click thedrop-down menu and select `Multiple`.  
   
   
2. The Select Entities dialog box will appear with all available source entities.

3. Select all the source entities required by clicking the Selected flag. *Note: Only entities from one single farm can be selected at a time.
4. Click the OK button and all selected entity lines will appear.

Destinations

The Destinations tab identifies the entities that the animals are being transferred to. This section consists of two components:

• Destinations
• Destination Detail

Destinations

The Destinations should be entered to the house/pen to which  the entity is transferred. If the source is transferred from one house on the source to four pens on the destination, a line will need to be entered for each of the four pens.

1. In the Destinations tab, clickto add a new destination line.

2. From Complex Entity No, select or enter the entity that the birds were transferred to.
3. Farm Name defaults from Complex Entity No and displays the name of the farm where the birds were transferred to.
4. Enter the Sex of the birds that were transferred to the destination entity.
5. In the Head Received field, enter the number of birds that were received at the destination entities.
6. Enter the total Weight of the birds received. The weight is entered in lbs or kgs depending on the unit of measure.
7. Employee No is an optional field to identify the employee who received the transfer.
8. Employee Name will default from Employee No and displays the name of the employee who received the transfer.
9. Movement Status identifies the type of movement.
10. Enter the Time that the transfer was completed.
11. Ref No displays a unique reference number used to identify the transfer. This can be manually or automatically entered.
12. In the DOA field, enter the amount of birds that were dead on arrival (DOA).
13. Receiving Ref No is an optional field to enter a reference number for the receiving.

Destination Detail

The Destination Detail section displays the sources for the selected destination. For example, if there were four source houses that supplied one destination house, the details defines how many birds were received from the individual sources. The total number in Destinations must match the Destination details. Some of the fields in the Destination Detail section default in from the information entered in the Sources and Destination tabs. The other fields will need to be entered to represent information for each house if the entity has multiple houses.

1. Source Complex Entity No displays the entity where the birds were transferred from.
2. Farm Name displays the name of the farm where the birds were transferred from.
3. In the Head Shipped  field, enter the number of birds that were shipped to the destination entity/house.
4. Head Variance displays the variance in the number of birds shipped versus the number of birds received, if applicable.
5. Enter the total Weight of the birds received at the entity or house. The weight can be entered in lbs or kgs.
6. Ref No displays the automatically-generated reference number for the transfer.

Post a Transfer

Once the Movement Transfer as been created and saved, the transfer needs to be posted. The posting process locks the transfer to prevent edits. , and creates a record or capitalization transfer to record the liability. The UnPost option unlocks the transfer and reverses the record. A journal transaction will not be created in the posting process unless there is an internal price associated with the product that is being transferred. At period end, the journal created from the internal price will be reversed and the actual journals entered. If there is no internal price, there are no journals until period end where the costs are transferred from one entity to another

1. In the Transfers main index, select the required transfer 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 transfer record, select the required transfer and right-click to select 'Unpost'.  This process will set the record status to 'Reversed' status, which allows the record to be edited.

Molting Transfer

Molt entities are producing lay entities that stop production for a period of time and then restart producing eggs after the molt process. Costs incurred in the molt process are capitalized to the molt entity and then depreciated while the molt entity is producing eggs.

1. Create a Lay-to-Lay movement as outlined in Creating a Transfer.
2. The transfer should occur on the date of molt to accurately account for molt cost and performance.
3. On the General tab, set the Population Mode to Molting. Selecting this option will move the non-amortized amount of the source entity to the destination molt entity. This transferred amount will establish the beginning balance of the molt entity. Entities are not re-aged in v7, however there is an option in order shipments to enter an alternate entity number and entity age for reporting purposes to the customer.
4. The molt entity will be created was a Farm Stage = Lay and Entity Stage = Brood.
5. All costs recorded to the entity while the Entity Stage = Brood will be included in the capitalization cost along with the un-depreciated amount transferred from the source entity.
6. The molt entity will have a new POL date to facilitate the tracking of KPI's specific to molted entities.
7. When the molt entity comes back into lay, a Capitalization transaction will be created to establish a new POL date. The capitalization transaction will capitalize the un-depreciated amount of the source entity and any costs incurred during the molt process to establish a capital cost of the molt entity
8. The molted entity will depreciate based on the assigned amortization table.
9. There are further details related to molted entities in BPA Entity History.