Product Requirements

The Product Requirements displays the field products required for the entity throughout the life cycle of the entity as defined in BOM Packages. The product requirements are generated based on the entity and planned head placed. The quantities can be modified prior to the record being posted.

The following sections are outlined in the Product Requirements document:

• Creating Product Requirements
• Editing the Product Requirement Record
• Approving Product Requirements
• Posting Product Requirements

Create Product Requirements

Product Requirements are generated from the Entity Selection index.

1. In BMTS>BIM>Transactions>MRP>Planning, select Entity Selection.
2. Right-click and select `Create Planning`.

 



3. When the process is complete, the Planning flag will be selected.

Edit Product Requirement Record

The Product Requirement record can be edited if the Post Status is set to Active or Reversed and the user has permissions to edit.

1. In the Product Requirements index, select the required record and right-click to select 'Edit'.
2. The Product Requirements edit screen will open. There are two sections on the screen:
1. Calendar - the top section of the screen is a calendar with the transactions assigned to the respective dates. The user can hover over the transaction on the calendar to view more details. The details displayed on the hover can be modified by selecting Options>Define Appointment Bubble/Tool Tip. Users can also drag and drop the bubble to an alternative date and/or time which will also update the planning record.
2. Planning - the bottom section of the screen represents the details of the product requirement record. The details in this section can be modified providing that the user has the required permissions.

 



 

3. Profile No and Profile Name represent the profile that has been assigned to the entity. This will be used for generating global MRP data.
4. Record Type will default from the source entity to indicate if the entity is a Planned entity with is sourced from BPA>Planning>Movements or Actual entity which is sourced from BIM>Master Data>Entities. Planned movement records must be posted to be selected in planning requirements.
5. Ref No is an auto-generated system reference number that uniquely identifies the record within the system.
6. Entity No displays the entity for the Product Requirements record. If the entity is incorrect, the requirement record needs to be voided or deleted and the Create Planning function needs to be generated again.
7. Farm Name is derived based on the selected entity.
8. Placement Date represents the planned or actual placement date depending if the entity is a planned or actual entity.
9. Head Placed represents the number of head that are planned or actually placed. If the Record Type=Planned, the planned head placed will be derived from BPA>Planning>Movements. If the Record Type=Actual, the planned head will be derived from the actual head placed in BIM>Master Data>Entities.
10. Trans Date is the date that the product is required.
11. Event Date will default to the Trans Date but can be modified to represent an alternative date. The Trans Date will be used for all transactions.
12. Product Type represents the type of product that is assigned to the entity. The Product Type can be modified by selecting the drop-down to select a different product type.
13. Product No represents the product that is assigned to the entity. The Product No can be modified by selecting the drop-down to select a different product. The available products will be filtered based on the product type.
14. Product Name is derived from the selected Product No.
15. Units it the calculated quantity based on the head placed and the required quantity per head as defined in BOM Packages. The amount can be modified by manually entering a revised quantity.
16. Usage Mode is derived based on the data defined in Products>Field Products.
17. Cost Center No represents the cost center that will source the product. If the Cost Center No is blank, the product will be purchased and sourced from the entity cost center.
18. Cost Center Name is derived from the Cost Center No.
19. Facility Type is derived from the source Cost Center No and displays the type of facility that will source the product such as warehouse, farm, hatchery.
20. Field Crew No can be selected to assign the field crew to the planning requirement. Field Crew Name will be derived based on the selected Field Crew No. Field crews are defined in Admin>Business>General>Definitions>Field Crews.
21. Veterinarian No can be selected to assign the veterinarian to the planning requirement. Veterinarian Name will be derived based on the selected Veterinarian No. Veterinarians are defined in Admin>Business>General>Definitions>Veterinarians.
22. The Override flag will be selected if any of the fields are modified on the planning requirement record.
23. Void nullifies the planning record for future transactions.
24. Notes are derived from the planned or actual entity. The data will be defined in the source entity record in BPA>Planning>Movements or BIM>Master Data>Entities.
25. Comments is a text field to enter any required details for the planned requirements record.
26. Approval Status must be set to Ready for Approval for the record to be posted. Security can be assigned so that only defined users can approve the planning requirement. The default value is 'Not Set'.

Approve Product Requirements

The Product Requirement must be approved prior to the transaction being posted. Permissions can be established so that only specified users can approve the requirements if necessary.

1. Product Requirements must has the Approval Status set to 'Ready for Approval' prior to final approval.
2. In the Product Requirements index, select the transactions to be approved and right-click to select Approve.

Post Product Requirements

Posting the Product Requirement creates the requisition transaction. Depending on the cost center assignment, the following transactions will occur:

• No Cost Center Defined - If there is no cost center defined on the requisition record, the global purchase requisition will be automatically created for the farm cost center when the product requirement is posted.
• Cost Center Defined - If there is a cost center defined on the requisition record, the transfer requisition will be automatically created for the source cost center when the product requirement is posted.

1. Ensure that the Approval Status for the product requirements is set to Approved.
2. Select the required product requirements to post.
3. Right-click and select Post.
4. The Post status will be set to Post.