Egg Products

Eggs products can be produced at the farm, transferred to the hatchery, purchased from vendors or sold to customers. Different egg categories and classes can be created to classify the eggs are required by the business.

 

Prior to creating an Egg Product, the following items should be created.

 

The following features are outlined in this document:

Create an Egg Product

The Egg Products screen has several tabs that must be completed in the creation process.

General

The General tab contains the base data for the product.

 

  1. In General>General>Products, select Egg.

  2. In the Live Poultry Products index, click to create a new egg product.

  3. Click on the General tab.

  1. Enter the Product No to identify the product within the system (alphanumeric, max 50 characters).

  2. Enter the Product Name as a description for the product (alphanumeric, max 250 characters).

  3. The Egg Class No further defines the type of eggs that are produced and utilized in the system. Egg classes are defined with options of Hatch, Cull, or Table. Multiple egg classes can be defined for each option. Egg classes are defined in Admin>Business>Poultry>HIM>Egg Classes.

  4. Egg Class Name displays the description of the selected egg class.

  5. The Active flag will be selected by default. If the product is no longer utilized, the active flag is required to be unchecked.

  6. Units Count determines the number of inventory units for the egg product. For example, if the product is recorded in dozens, then 12 would be the value entered into this field.

  7. Unit Description provides a manually entered text field to enter the description for the units count.

  8. Products can be Color coded for easy view for planning purposes. If desired, choose the color from the color grid.  

  9. Purchases Max % Over is used when the product has a tolerance percentage for the receiving transaction. (Example: The purchase order has 100 units. Max % Over is defined as 5%, which means the receiving transaction will allow up to an including 5 additional units).

  10. Purchases Allow Any % Over can be selected if there is no limit and the purchaser can receive any quantity over the specified product units.

  11. Sales Max % Over is used when the product has a tolerance sales amount for the receiving transaction.(Example: The sale order has 100 units and the Sales Max % Order is defined as 10%, which means the shipment transaction will allow for an additional 10 units to be shipped).

  12. Sales Allow Any % Over is selected when there is no limit of shipping product units over what the customer has ordered.

Breeds

The Breed tab is optional depending on whether breeds are used for the product being created. Breed Codes must be created prior to creating the product in Admin>Business>Poultry>Definitions>Breed Codes.

 

 

  1. Breed No identifies the breed code (s) that relate (s) to the product. If there are multiple breed codes for the animal, select the required breed codes. These codes are predefined in: Admin>Business>Poultry>Definitions>Breed Codes.

  2. Breed Name corresponds to the selected Breed No.

  3. Generation Code determines the generation of the product. Options are:

  4. Sex defines the sex as Male, Female, or Straight Run for the product breed. Select the sex of the breed code for the animal.

  5. Priority is used if there are multiple breeds assigned to the product. Select the breed that is primarily used for planning and number the remainder accordingly in a numerical order.

Sales

If the product is sold to external sources, a sales sku must be created prior to creating a sales order.

 

 

  1. In the Sales SKU No field, enter a unique code that will be used in creating sales contracts, orders, and price lists (alphanumeric, max 50 characters). This is optional and can be the same as the product code, however the sales sku must be unique within the Sales tab.

  2. In the Sales SKU  Name field, enter a description for the sales SKU. This will normally print on orders and invoices (alphanumeric, max 100 characters).

  3. In the Unit Description No field, select the required unit of measure in which the product will be shipped. The Unit Description No must be predefined in Admin>Business>General>Definitions>Units of Measure prior to being selected on the Sales tab.

  4. The Unit Description Name will default based on the selected Unit Description No.

  5. Inventory Units indicates the number of units that will be removed from inventory when the sales sku is shipped. (Example: If a box of 20 units is shipped, the user will enter 1 box, and the inventory will be decreased by 20 units). This value defaults based on the selected Unit Description No.

  6. New sales skus' will default as Active. If the sales sku is no longer required, de-select the Active flag.

  7. If the product is Taxable, the flag must be checked in order for taxes to calculate on the product. Tax codes must be entered on the price list, sales code, sales contract, or sales order for the taxes to be calculated.

Additional Sales Options

In the child grid within the sales sku, there is the option to define additional details such as added charges, discounts or commissions on the product.

 

Sales Premium/Discount Add-Ons

The addons must be pre-defined before adding to the sales sku. The addons can be configured to be included in the revenue of the product or alternatively, be coded to an entirely different account which is not included in the product revenue.

 

 

 

  1. In the Product No field, select from a list of previously defined premium add-on codes. addons must be selected on the sales sku before being transferred to a contract, price list, or order. addons must be predefined in General>Products>AddOns.

  2.  Product Name displays the description of the selected add-on as defined.

  3. The Transaction Basis is a read-only field that defaults from the selected add-on and determines how the add-on is calculated. Options are: Per Unit, Percentage, Flat Rate, or Free Percentage. Free y percentage is currently only used in poultry products.

  4. Payment Type determines when the add-on payment is made. Options available are:

    1. Transaction: Processed at time of receiving and will be included in the vendor payment.

    2. Rebate: Will record accrual amount at time of receiving but will not transfer to the invoice. Payment/invoice will be processed at a later date.

    3. Internal: An internal transaction that is not invoiced to an external source  (Example: There is an internal haulage department that gets a credit for hauling products).

  5. The Payee Type field is optional. If the add-on is to be processed by an alternative sources, select the source type for the add-on. Options are: Customer, Vendor, Employee, or Cost Center. If the field is left blank, it assumes the customer for the addons.

  6. Transaction Entity ID is a required field if a different Payee Type is selected. Select the appropriate customer or cost center.

  7. Taxable Flag identifies if the item is taxable or non-taxable when the item is purchased. Tax codes must be assigned to the sales order for the taxes to be calculated.

  8. Select Print on Invoice if the add-on is to be printed on the default system invoice. If the add-on is not to be printed on the invoice, the option should not be selected. This option can be further defined in price lists.

Commissions

Commissions are a type of add-on that is typically used to pay employees or other parties based on a percentage or per unit amount.

 

  1. In the Product No field, select from a list of previously defined premium add-on codes. addons must be selected on the sales sku before being transferred to a contract, price list, or order. AddOns must be predefined in General>Products>AddOns.

  2.  Product Name displays the description of the selected add-on as defined.

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

  4. Payment Type determines when the add-on payment is made. Options available are:

    1. Transaction: Processed at time of receiving and will be included in the vendor payment.

    2. Rebate: Will record accrual amount at time of receiving but will not transfer to the invoice. Payment/invoice will be processed at a later date.

  5. The Payee Type field is optional. If the add-on is to be processed by an alternative sources, select the source type for the add-on. Options generally used for commissions are: Customer or Employee. If the field is left blank, it assumes the customer for the add-ons.

  6. Transaction Entity ID is a required field if a different Payee Type is selected. Select the appropriate customer or cost center.

  7. Taxable Flag identifies if the item is taxable or non-taxable when the item is purchased. Tax codes must be assigned to the sales order for the taxes to be calculated.

Order Rules

Order Rules are used for planning purposes in HPA. Based on the rules that are defined for the product, the HPA will process the sales order allocation of product.

 

  1. The Min Flock Age determines the minimum flock age in weeks of the parent flock that will source orders for this product.  

  2. The Max Flock Age determines the maximum flock age in weeks of the parent flock that will source orders for this product.  

  3. The Min Egg Age indicates the minimum egg age in days of the egg that will be set as the source to an order for this order. The egg age is the number of days from the egg production date to the set date.

  4. The Max Egg Age indicates the maximum egg age in days of the egg that will be set as the source to an order for this order. The egg age is the number of days from the egg production date to the set date..

  5. Primary Breed Priority indicates the order of importance to placing the primary breed as defined on the Breeds tab. Each priority should be numbered from 1-4 in the order of which the HPA should consider how to source an order.

  6. Order Rules Priority establishes the order of the rules with 1 being the highest priority. Higher priority products will be processed before lower priority products. .

  7. Flock Age Priority establishes the order of importance for flock age requirements as defined in the flock ages tabs with 1 being the highest priority.

  8. Source Quantity Priority indicates the importance of sorting the largest number of eggs from the fewest sources.

To further explain the priority process, For example, an international order of grandparents, the first consideration is Primary Breed, so "1" would be entered in the Primary Breed box. Flock Age would be #2, Quantity of Sources #3, and Order of Rules #4.  This would first select all sources of the “Breed” to be the highest priority, then perform the next selection based on the sources that fall within the flock age and egg age requirements of the “Flock Age." Next it will sort those selected sources by "Quantity of Sources", and then the “Order Rules” becomes a product of what is available to choose from in the previous selections.

Bill of Materials

The Bill of Materials tab is used to determine the products that must be used to ship the egg product. Based on the products that are entered in this tab, the system will create automatic usage transactions for the products required to ship the egg product.

 

 

  1. Product Type determines the type of product that will be used in the Bill of Materials. Any inventory product type can be selected.

  2. Based on the selected product type, a list of available products will be available. Select the Product No that is required for the product to be shipped.

  3. Product Name will default based on the selected product.

  4. Inventory Units determines how many product units are required for each Bill of Material product. For example, to use the Egg Box example from above, one box will be required for every 200 eggs. Therefore, enter the units as 1/200 = 0.005. This will calculate one box for every 200 eggs.

Instructions

Instructions are default comments that are applicable to the product. These instructions are predefined in Admin>Business>General>Definitions>Instructions. Instructions are generally used to print on specific documents such as sales confirmations, invoices and hatchery work orders.

 

 

  1. From Instruction No, select the instruction for the product that is predefined in Admin>Business>General>Definitions>Instructions.

  2. Instruction Name displays the description of the selected Instruction No. The Instruction Name will be the text that prints on the various forms or reports.

  3. If the instruction is to print on the default system invoice, select the Print On Invoice option. If the instruction is not required to print on the default invoice, the option is not selected. These options can also be used in custom reports.

Vendors

Before a product can be purchased, the vendor/product relationship must be established. This option allows the user to define the unit of measure and any additional costs or discounts associated with the product. If the product is purchased from the same vendor in different units, a vendor sku must be created for each unit.

 

 

  1. Vendor No contains a list of previously defined vendors. Select the vendor where the product is purchased from. Vendors are defined in General>Master Data>Vendors.

  2. Vendor Name displays the name of the selected vendor.

  3. In the Vendor SKU No field, enter the code that is used when ordering the products from the vendor (alphanumeric, max 50 characters) This is optional and can be the same as the product code; however the vendor SKU must be unique to the vendor.

  4. In the Vendor SKU Name field, enter a description of the product that is being purchased. The field will be displayed on purchase orders (alphanumeric, max 100 characters).

  1. In the Unit Description No field, select the required unit of measure in which the product will be purchased. The Unit Description No must be predefined in Admin>Business>General>Definitions>Units of Measure prior to being selected on the Vendors tab.

  2. The Unit Description Name will default based on the selected Unit Description No.

  3. Inventory Units indicates the number of units that will be added to inventory when the vendor unit is received. (Example: If a box of 20 units is purchased from the vendor, the user will receive 1 box and the inventory will be increased by 20 units). This value defaults based on the selected Unit Description No.

  4. Pay Basis determines if the vendor is paid based on received units or shipped units. The default is set to Received, but it can be modified.

 

 

 

  1. The Sales SKU No must be inputted if the product is used for intercompany sales and purchases. Select the sales SKU that corresponds to the vendor SKU.

  2. The system will default the vendor SKU as Active. If the product is no longer purchased from the vendor, de-select the option.

  3. If the product is Taxable, the flag must be checked to calculate taxes on the product. The tax code can be optionally added to the Vendor SKU, but must be added to the purchase order for taxes to be calculated.

  4. In the Attachment section, any type of file can be attached (Example: Word document, picture, music or video clip).

  5. Payment Term No displays the payment terms and defaults from the vendor, with an option to select by product.

  6. Currency No defaults from the vendor and displays the code for the currency, with an option to modify by product.

  7. HS Code represents Harmonized System Code, which is used for international shipments. Enter the code based on the international defined code.

  8. Product Specification is a text field to enter details related to the product vendor SKU.

  9. Product Remarks is a text field to enter any other details specific to the vendor sku.

 

Additional Vendor Options

In the child grid within the Vendor No, there is the option to define the add-ons related to the product. The add-ons must be pre-defined in General>Products>AddOns prior to adding to the vendor sku. Depending on how the add-ons are configured, the cost of the add-on can be included or excluded from inventory cost of the product. The add-ons can be configured to be included in the cost of the product or alternatively, be coded to an entirely different account which is not included in the product cost.

 

Vendor Premium/Discount Add-Ons

There are two types of add-ons:

 

 

  1. In the Product No field, select from a list of previously defined add-ons codes. The add-ons will transfer to purchase orders created for the vendor SKU. Add-ons can be found in: General>Products>AddOns

  2. Product Name is a read-only field that displays the description of the add-on product type.

  3. Transaction Basis is a read-only field that defaults from the selected add-on and determines how the add-on is calculated. Options are: Per Unit, Percentage, Flat Rate, or Free Percentage. Free Percentage is used to receive an additional percentage of free eggs based on the original amount ordered.

  4. Payment Type determines when the add-on payment is made. Options available are:

    1. Transaction: Processed at time of receiving and will be included in the vendor payment.

    2. Rebate: Will record accrual amount at time of receiving but will not transfer to the invoice. Payment/invoice will be processed at a later date.

    3. Internal: An internal transaction that is not invoiced to an external source  (Example: There is an internal haulage department that gets a credit for hauling products).

  5. The Payee Type field is optional. If the add-on is to be processed by an alternative sources, select the source type for the add-on. Options are: Customer, Vendor, Employee, or Cost Center. If the field is left blank, it assumes the vendor sku for the payment of the add-ons.

  6. Transaction Entity ID is a required field if a different Payee Type is selected. Select the appropriate vendor or cost center.

  7. Rate is an optional field to enter a default rate for the add-on. The rate will default to contracts and purchase orders for the vendor, and can be modified as required.

  8. Taxable identifies if the item is taxable or non-taxable when the item is purchased. Tax codes must be assigned to the sales order for the taxes to be calculated.

 

Tax Codes

If the product and/or add-ons are taxable, the tax codes can optionally be defined at the vendor sku. It is recommended that the tax codes are only entered on the vendor sku if that vendor only delivers within the same state or province, as different tax rate can be applied depending on the destination. Tax codes must be previously defined. Rates will default to the purchase order based on the rate that is in effect on the purchase order date.

 

 

  1. Tax No is selected from the predefined in Admin>Business>General>Definitions>Tax Codes. The tax code will default to purchase contracts and purchase orders for the vendor sku.

  2. Tax Name defaults from the selected Tax No.

Internal Mappings

The Internal Mapping tab is used to identify products that can be used interchangeably if the original product is not available. This is used for planning purposes.

 

  1. Select the Product No for the products that can be used interchangeably.   

  2. Product Name will default based on the selected Product No.

Accounts

The Accounts tab defines the account segments that will be used in each journal process throughout the system. If the segment is blank, then the transaction will pick up the account according to the location and stage within of the product. The default accounts will be displayed when the product is created.

 

Internal Add-Ons

Internal add-ons are used when transferring products between facilities. The add-on must be defined on this tab before the pricing is established in Internal Pricing.

 

 

  1. From Add-On Type, select whether the internal add-on is a premium or discount add-on. Premium will increase the cost to the destination cost center while the discount will reduce the cost to the destination cost center.

  2. In the Product No field, click the box to select from a list of previously defined premium or discounts add-ons.   

  3. Product Name displays the description of the selected add-on as defined.

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

  5. Payment Type determines when the add-on cost is recorded. Options available are:

    1. Transaction: Processed at time of transfer and will be included in the transfer journal.

    2. Internal: Used when another department is required to be credited or debited for the add-on  (Example: There is an internal haulage department that gets a credit for hauling products)

  6. The Payee Type field is only required if the Payment Type is set to Internal. If this is the case, then the Payee Type should be set to Cost Center.

  7. Transaction Entity ID is a required field if a Cost Center is selected as the Payee Type. Select the cost center that will receive the debit or credit for the add-on amount.

  8. If the Rate is standard for all transactions, enter the rate in this field. If the rate is defined by the cost center, then rates must be applied in Internal Pricing.  

  9. Accrual is selected if the amount of the add-on is reversed at period end with the internal price of the product. There is a separate period end task that will reverse any add-ons with the accrual option selected. If the option is not selected, the cost of the add-on will not be reversed at period end.

Cost Centers

The system has the ability to identify which cost centers the product applies to. If none of the options are checked, then the product can be supplied to all facilities. If one or more cost centers are selected, then the product can only be utilized at that facility.

 

 

  1. In the Selected field, select the cost center (s) for which the product will be required.

Certifications

The Certification tab is used to define standardization options that are required for the products. Examples are an international standard program, or, products may be defined as organic or standard product types. The farm or facility must contain the same certification for the product to be placed on the farm.

 

 

  1. Click to add a certification to the product. Select the certification as predefined in Admin>Business>General>Definitions>Certifications.

  2. Certification No defaults based on the selected certification.

  3. Certification Name describes the certification and defaults based on the selected Certification No.

  4. The Active flag defaults from the selected certification. The active flag can only be modified in Admin>Business>General>Definitions>Certifications if the certification is no longer valid.  

  5. The Start Date indicates the first date that the certification becomes effective. This concept is typically used in international standard programs that require recertification after a defined period.

  6. The End Date indicates the last date that the certification becomes effective. This concept is typically used in international standard programs that require recertification after a defined period.

  7. The Memo field is a text field to enter details related to the certification.

  8. Attachment displays attachments such as contracts, certification documents or any other required details related to the certification.

 

Egg Product Options

There are three options available for egg products:

 

Reset Default Accounts

The Reset Default Accounts sets the Product>Accounts tab back to the system defined default accounts. This process can be initiated from the index list or directly within the product.

 

  1. Click on the required product from the index or edit the required product.
  2. From the toolbar, select Options>Reset Default Accounts.
  3. The process will reset the accounts to the system defined default accounts.

 

Modify Vendor SKU Add-on Prices

The Modify Vendor SKU Add-on Prices option allows the user to modify the add-on prices from a single data entry screen rather than having to access each product to modify the prices. The feature can be initiated from the product type index to only change add-ons for that specific product type or from General>Products>Master to change the add-on prices for all product types in one screen.

 

  1. From the product index, select Options>Modify Vendor SKU Add-on Prices.
  2. In the Add Ons grid, select the add-on that is required to be modified.
  3. The Modify Product Vendor AddOn Rates will display all of the vendor skus for the selected add-on.
  4. Enter the modified rates on the required vendor sku.
  5. Click OK to update the rate on the vendor sku. This rate will be used for all new purchase orders, but will not be modified on posted purchase orders.

 

 

Auto Refresh

The Auto Refresh option is selected by default. This option updates the index immediately when changes are made to the products. If the auto refresh option is not required, de-select the option and the index must be manually refreshed by the user.

 

  1. From the product index, select Options>Auto Refresh.
  2. If the option is checked, the auto refresh feature is turned on.
  3. Click on the Auto Refresh option to turn the feature off.