Embryo products are set up to handle embryo sales from the setter. An egg product will be received to the hatchery and set in the setter. The embryo product will be sold from the setter.
The following features are outlined in this document:
Prior to creating an Embryo Product, the following items should be created.
The Embryo Products screen has several tabs that must be completed in the creation process.
The General tab contains the basic information related to the embryo product. .
In General>General>Products, select Embryos
In the Embryo
Products index, click 
to create a new embryo product
Click on the General
tab
Enter the Product No to identify the product within the system (alphanumeric, max 50 characters).
Enter the Product Name as a description for the product (alphanumeric, max 250 characters).
The Active flag will be selected by default. If the product is no longer utilized, the active flag is required to be unchecked.
Products can be Color coded for easy view for planning purposes. If desired, choose the color from the color grid.
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).
Purchases Allow Any % Over can be selected if there is no limit and the purchaser can receive any quantity over the product units.
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).
Sales Allow Any % Over is selected when there is no limit of shipping product units over what the customer has ordered.
If the product is sold to external sources, a sales sku must be created prior to creating a sales order.
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.
In the Product Name field, enter a description for the sales SKU. This will normally print on orders and invoices (alphanumeric, max 100 characters).
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.
The Unit Description Name will default based on the selected Unit Description No.
The Active flag will be selected by default. If the product is no longer utilized, un-check the Active flag.
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.
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.
The add-ons must be pre-defined before adding to the sales sku. The add-ons 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.
Premium add-ons add to the price of the product.
Discount add-ons reduce the price of the product.
In the Product No field, select from a list of previously defined premium add-on codes. Add-ons must be selected on the sales sku before being transferred to a contract, price list, or order. Add-ons must be predefined in General>Products>AddOns.
Product Name displays the description of the selected add-on as defined.
Payment Type determines when the add-on payment is made. Options available are:
Transaction: Processed at time of receiving and will be included in the vendor payment.
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.
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).
The Payee Type field is optional. If the add-on is to be processed by an alternative source, 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 add-ons.
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 Quantity. Free Quantity is currently only used for poultry products.
Transaction Entity ID is a required field if a different Payee Type is selected. Select the appropriate customer or cost center.
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.
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 are a type of add-on that is typically used to pay employees or other parties based on a percentage or per unit amount.
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.
Product Name displays the description of the selected add-on as defined.
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.
Payment Type determines when the add-on payment is made. Options available are:
Transaction: Processed at time of receiving and will be included in the vendor payment.
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.
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.
Transaction Entity ID is a required field if a different Payee Type is selected. Select the appropriate customer or cost center.
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.
The Bill of Materials tab is used to determine the products that must be used to ship the embryo 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 embryo product.
Product Type determines the type of product that will be used in the Bill of Materials. Any inventory product type can be selected.
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.
Product Name will default based on the selected product.
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 embryos. Therefore, enter the units as 1/200 = 0.005. This will calculate one box for every 200 embryos.
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.
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.
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.
Breed Name corresponds to the selected Breed No.
Generation Code determines the generation of the product. Options are:
PED (Pedigree)
GGGP (Great-great-great Grandparent)
GGP (Great-great Grandparent)
GP (Grandparent)
P (Parent)
Sex defines the sex as Male, Female, or Straight Run for the product breed. Select the sex of the breed code for the animal.
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.
Vendors are not currently used in embryo products.
Internal Add-Ons are not currently used in embryo products.
Internal mappings are not currently used in embryo products.
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.
In the Selected field, select the cost center (s) for which the product will be required.
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.
There are three options available for embryo products:
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.
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.
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.