Receivings

 

The Egg Room Receivings transaction is used to receive purchased eggs to the hatchery.

 

A Purchase Order must be completed and posted prior to the eggs being received to the hatchery. In addition to the purchase order, external entities must be defined to establish entity data for the eggs to be received. This process is handled in the LMTS>BIM>Master Data> Entities.

 

The following procedures are outlined in the Egg Room Receiving document:

 

Create a Receiving Transaction

Receiving Header

The header contains the base data to outline the egg room receiving. The header is divided into two sections. The information in the Derived tab defaults in and is derived from the General tab.

General

The General tab contains the base data to outline the receiving.

 

  1. In LMTS>HIM>Transactions>Eggs>Egg Room, select Receivings.
  2. In the Egg Room Receivings main index, click to create a new receiving transaction.
  3. Click on the General tab.
  1. From the Hatchery No drop-down menu, select the hatchery that is receiving the eggs.
  2. In the Trans Date field, enter the date that the eggs will be received.
  3. From Vendor No, select the vendor that is supplying the eggs.

  4. Location ID is an optional field to enter the location from which the vendor shipped the eggs.

  5. From Haulage Vendor No, select the vendor that hauled the product if the purchase order had 'Excluded' or 'Delayed' freight selected. Alternatively, select the purchase order vendor.

  6. In the Total Eggs field, enter the total number of eggs being received into the hatchery.

  7. Ref No is an automatically-generated unique reference number that identifies the egg room receiving transaction.
  8. Vehicle No is an optional field to identify the internal vehicle that is delivering the eggs. Vehicles must be set up prior to use in: Admin>Business>General>Definitions>Vehicles.
  9. Driver No is an optional field to identify the internal driver that is delivering the eggs. Drivers must be set up prior to use in: Admin>Business>General>Definitions>Drivers.
  10. Enter the number of Miles that the vehicle travelled to the hatchery.
  11. Shipment No is an optional field that is used to transfer the supplier reference from the purchase order.
  12. In the Notes field, enter any additional information relating to the receiving transaction.

 

Derived

  1. Hatchery Name displays the name of the hatchery that is receiving the eggs.
  2. Vendor Name displays the name of the vendor that is supplying the eggs.

  3. Location Name displays the location from where the eggs are being shipped, if applicable.

  4. Haulage Vendor Name displays the name of the vendor hauling the eggs.

  5. Vehicle Name displays a description of the vehicle used to deliver the eggs.
  6. Driver Name displays the name of the driver that is delivering the eggs.
  7. Purchase Trans Code displays the type of purchase transaction initially used to purchase the eggs..
  8. Selecting the Void flag will cancel the receiving.
  9. Creation Date indicates the date the transaction was created.
  10. Last Mod Date indicates the date the transaction was last modified.

 

Details

The line details relate to the eggs that are being received from the vendor. The child grid for the line item also contains details related to add-ons and taxes. These amounts will default as defined from the purchase order and cannot be modified at receiving. If there is freight assigned to the product, two lines will appear in the details for each product received.  The first line will be relating to the product details and amount ,with the second line referencing the freight amounts.

 

  1. Click on the Details tab and select to create a new line detail.
  2. The Purchase Order Inventory dialog box will appear.

 

 

  1. Select the required purchase order from the list, and from the Complex Entity No drop-down menu, select the entity that produced the eggs.
  2. In the Tracking No field, enter a unique identification code to be used to track the product.
  3. Enter the number of Eggs to be received, and then click 'OK'.
  4. The details will then default in.

 

  1. Complex PO No indicates the purchase order that is being received. Purchase orders must be in 'Posted' status. Purchase orders will be filtered based on the cost center and vendor selected in the header.
  2. Product No indicates the product that is being received.
  3. Product Name displays a description of the product being received.
  4. Complex Entity No identifies the entity that produced the eggs.
  5. Farm Name displays the name of the farm that produced the eggs.
  6. Breed No is a derived field based on the selected entity, and is used to identify the breed of the eggs.
  7. Breed Name displays a description of the breed code.
  8. Generation is a derived field based on the selected external entity, and is used to identify the generation of the eggs. Available options are: GGP, GP, Parent or Pedigree.
  9. Tracking No defaults in based on the number entered in the Purchase Order Inventory dialog box. The number identifies the receiving transaction., and is usually the number from the egg ticket.
  10. Prod Date indicates the date that the eggs were produced, to determine egg age.
  11. Received Date indicates the date the eggs will be received.
  12. Vendor Units indicates the number of vendor units that are being received. For example, the eggs are received in boxes. Depending on a setup switch that determines whether the receiving transactions are recorded based on inventory units or vendor units, this field may be automatically calculated.
  13. Eggs displays the number of eggs received. This is a calculated field based on the number of units received and the eggs per unit received.
  14. Units Per indicates the number of units in each vendor unit.
  15. Unit Description displays the unit of measure in which the product was purchased from the vendor.

  16. Amount is a calculated field. Amount = Vendor Units x Unit Price.

  17. Total Add-ons is a calculated total amount of premium add-ons that will be added to the vendor payment based on the amounts defined in the purchase order. Details are located in the child grid.

  18. Total Discounts is a calculated total amount of discount add-ons that will be deducted from the vendor payment based on the amounts defined in the purchase order. Details are located in the child grid.

  19. Taxes is a calculated amount based on the taxable product and/or add-ons as defined in the purchase order. Details are located in the child grid.

  20. Total Amount is the calculated total amount of the receiving transaction based on the amounts that are defined in the purchase order.

  21. Buggy No will indicate the buggy used if the eggs are received to a buggy.

  22. Buggy Name displays the name of the buggy.

 

  1. Base Hatch defines the hatchability percentage. If there is a standard assigned to the external entity, the projected hatch will default based on the age of the entity, otherwise the base hatch will default based on the default hatchability as defined in the registry.
  2. 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.
  3. Projected Chicks is a calculated field for the estimated number of chicks, based on the eggs being received multiplied by the projected hatch.
  4. Egg Weight is an optional field to enter the average weight of the eggs received.
  5. Bill of Lading is an optional field used to enter the bill of lading reference for the receiving line.
  6. The Consignment flag will be selected if the eggs were purchased using a Consignment Purchase Order.
  7. Currency No defaults based on the currency assigned to the purchase order as defined, with no option to modify.

  8. Currency Name displays a description of the currency type.

  9. Select the Prepaid Final Receiving flag if the order was prepaid and this is the last delivery or receiving for the prepaid purchase order.

 

Additional Details

Within the Houses tab, there is a child grid with additional details relating to the receiving add-ons. The details will default from the purchase order.

 

Premium and Discount Add-Ons

The add-ons must be pre-defined in General>General>Products>AddOns prior to adding to the receiving transaction. 

 

  1. Click on the Complex PO No field to display the child grid.

 

 

  1. Product No displays the code of the selected add-on.
  2. Product Name displays a description of the add-on.

  3. Transaction Basis is a read-only field that defaults from the selected add-on and determines how the add-on is calculated on orders. Options are: Per Unit, Percentage, Flat Rate, or Free Percentage.

  4. Payment Type is a read-only field that derives from the purchase order and determines when the add-on payment is made.

  5. Payee Type is an optional field that indicates the source type for the premium or discount add-on.

  6. Transaction Entity ID is a required field if a different Payee Type is selected. If Payee Type is set, the selected  vendor or cost center name will appear in this field.

  7. Pay Calculation Type defaults from the vendor sku and determines the base amount of the add-on calculation.

    1. Product Amount - the add-on is calculated based on only the product amount and does not include any other add-on in the calculation of the amount.

    2. Net Amount - the add-ons is calculated based on the net amount of the transaction based on the product amount including other add-on amounts, but excluding taxes.

  8. Vendor Calculation Type  determines if the payment is calculated based on the base add-on logic using Transaction basis or if the add-on amount is only deducted from the vendor payment.
      1. Normal - the add-on is calculated based on the rules established by Transaction Basis and the Payment Type defined in the vendor SKU and sales SKU.

      2. Deduction Only - the add-on is calculated based on the rules established by Transaction Basis, however the add-on is only deducted from the vendor payment.

  9. Taxable identifies if the item is taxable or non-taxable when the add-on is purchased. The flag will be selected if the item is taxable.

  10. Currency No defaults based on the currency assigned to the purchase order as defined, with no option to modify.

  11. Currency Name displays a description of the currency type.

  12. Rate displays the total cost of the add-on.

 

Taxes

If the eggs and/or premiums/discounts are taxable, the tax code must be assigned on the Taxes tab. The tax amount will then be calculated based on the taxable order amounts. Tax codes as defined on the purchase order will default to the receiving transaction. The amount will be calculated based on the rate that is in effect on the receiving date. There are two types of taxes.

    1. Accrual Taxes - will record the tax accrual and record the journal transaction at time of receipt.

    2. Invoice Taxes - will calculate the tax at time of receipt, however, the journal transaction is not created until the purchase invoice is processed. Invoice taxes are generally used for federal taxes that are reimbursed to the company by the government and cannot be actually recorded until vendor invoice is received.

 

  1. Tax No identifies the tax code to be applied to the product and premiums/discounts for the selected line item. The Taxable flag must be selected in the product and premiums/discounts for taxes to calculate.

  2. Tax Name describes the selected tax code.

  3. Amount is the total amount of tax applicable on the product.

 

Post a Receiving Transaction

Once the egg room receiving transaction is saved and closed, the transaction can be posted. The posting process locks the transaction to prevent edits, and will also create the journal transaction to record the amounts for receiving. Once posted, the product will be displayed in inventory at the recorded value.

  1. In the Receivings main index, select the required transaction, rick-click and select 'Post.' Alternatively, click the green check mark in the top menu bar and select 'Post'.
  2. To un-post an egg room receiving 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.

Journal Transaction

The journal transaction is created to debit the egg room inventory of the hatchery and credit the accounts payable.