Inventory Requisitions

Overview

Inventory Requisitions are created for direct items (inventory) used in the manufacturing process, either automatically by the MRP / DRP process or by manual creation.

• An Inventory Requisition can represent the start of the purchasing process.

• The MRP Processing creates inventory requisitions to satisfy demand and/or order policy planning.

• DRP Processing creates inventory Requisitions for the DRP Location Replenishment Maintenance records created with the flag 'Create Purchase Requisition  ' as True to satisfy the replenishment.

• Requisitions that the MRP / DRP Process creates are set to a ‘1-Planned’ status and must go through the Firm and Approve processes before they can be converted to a Purchase Order, using the Requisition Workbench (or by manually advancing the status in the Inventory Requisitions process). Alternatively, Inventory Requisitions may be entered manually by a Rootstock user.

• Manual requisitions are created at a ‘2-Firm’ status. These Requisitions must also be ‘Approved’ before being converted to a Purchase Order.

Navigation

Inventory Requisitions

Processing

From here, create a new Inventory Requisition or edit an existing one.

Fields
 

Division:  This field represents the buying division and will default to the current division of the manufacturing user entering the record. It is display-only and cannot be edited.

Requisition No:  This is the Requisition Number (or Order Number). MRP / DRP generated requisitions are auto-numbered by the system. Manual requisition numbers require a leading alpha character if the 'Auto Number Non-MRP Inventory Reqs' field on the Division Master Auto Numbering Tab is not enabled. If the 'Auto Number Non-MRP Inventory Reqs' field is enabled, the Requisition No will be auto-numbered based on the configuration.

Item No:  The requested item number must be a valid Inventory Item. (Begin typing the item number to allow the auto-complete pull-down to provide you with valid options, then select by clicking on the item in the pull-down window).

Requisition Qty:  The quantity in the Inventory Unit of Measure that this requisition covers.

Due Date:  The date this material needs to be available at your facility. If the requisition is MRP-generated, the due date represents the day the material will be needed for work in process or to cover order-policy demands. It considers any receiving inspection time and vendor indicated on the inventory item master. For manual requisitions, the due date represents the date the user wants the material to be available for use.

Project:  For MRP-generated requisitions, the project will match the project of the demand driving the creation of the requisition if the inventory item is 'Not Home'. Otherwise, the project will be the Home Project. For manually created requisitions, the user may enter any valid project.

  NOTE  When Project Control is active, this is a required field.

Effective Rev:  Display only. If this division is revision-controlled, the current revision for the item specified in the Item No field will be displayed here.

Receipt Site:  If multiple Sites exist for the Division responsible for this Requisition, this identifies the Site where the PO will be delivered. The Main Site from the Division Master is the default, but it can be overridden.

DRP Receipt Location ID:  This field allows for the transfer of the 'Transfer to Location ID' field from the DRP Replenishment process to the Purchase Order Line, where it can eventually become the PO Receive-To Location ID.

DRP Receipt Location Number:  This field allows for the transfer of the 'Transfer to Location Number' from the DRP Replenishment process to the Purchase Order Line, where it can eventually become the PO Receive-To Location Number.

Planner:  Defaults from inventory Item master, Misc. CC Overrides tab. Required entry. Must be a valid planner, as indicated on the ‘Other Indicators’ tab of the manufacturer user's record (Responsible Inventory Planner Indicator).

Req Status:  Possible values are:

Planned:  MRP / DRP creates requisitions at the planned status.

• These must be reviewed and, if accepted, changed to status 2, Firm, Not Approved, and then status 3, Approved, before the requisition can be converted to a purchase order. 

• Planned requisitions are deleted during the next MRP run and the item is re-planned.

Firm, Not Approved:  Manual requisitions are created at this status.

• They must then be approved to convert the requisition to a purchase order. 

• Firm requisitions are not deleted and re-planned by MRP. If requirements change for parts covered by status 2 requisitions, MRP will either create new requisitions to cover additional demand or provide MRP action messages indicating that the demands have changed and some action is necessary to correct the situation.

Approved:  Only approved requisitions can be converted to purchase orders. 

• Status 3 is always manually achieved. MRP will not replan status 3 requisitions but, like status 2, will plan around them, providing appropriate MRP action messages.

Req Item Type:  Possible values are:

• Subcontract:  Indicates that components of the purchased item will be provided to the vendor via a subcontract PO, and the vendor will provide the complete item.

• Purchased:  Denotes a part for which the vendor is responsible. No components are required.

Converted Qty:  Display field only. 

• When a partial quantity of the requisition has been converted to a purchase order but not the full quantity from the requisition, the amount that has been converted will display here. 

• Once the total number from the requisition has been converted to a purchase order, the requisition is deleted, so the user will never see the full quantity from the requisition in this field.

PO Data Tab Fields
 

Purchase Qty:  This is the requisition quantity in the purchasing unit of measure.

Stock Unit:  This display field indicates the unit of measure used in inventory for this part. It defaults from the inventory item master.

Purchase Unit:  This display field indicates the purchasing unit of measure, which defaults from the purchasing item master. 

UOM Conv Factor:  This field displays the unit of measure conversion factor between the inventory unit of measure and the purchasing unit of measure. It is displayed only here and is maintained in the system setup unit of measure conversion table.

Organizational Department:  Not required. If used, this is the organizational department associated with this specific requisition.

Buy Division:  Required for companies with multiple divisions, the buy division defaults from the Inventory Item Master associated with the Purchase Item Master record but may be overwritten here. 

Buyer:  This field displays the buyer associated with the requested inventory item. It defaults from the purchase item master but may be overridden here. 

Assigned Vendor:  Not required. If entered, this represents the vendor requested by the planner who created the requisition. During conversion to a PO, this is the vendor the Purchase Order will be created for unless it is changed during the conversion process. 

Effectivity Date:  Subcontract Items only. 

• The system will determine the components that must be supplied to the vendor for subcontract items based on the BOM in effect on that date.   

• Calculating that date takes into consideration the vendor and inspection lead times.

• No user input allowed.

PO Price Override:  This field value overrides any other PO Price that would otherwise be derived (overrides the Last PO Price or Agreement Pricing).

Key Dates Tab Fields
 

Req Status Date:  Displays the most recent date that the status of this requisition was changed. System calculated and display only.

Actual Firm Date:  Displays the date the order was set to ‘Firm, Not Approved’. System calculated and display only.

Actual Approve Date:  Displays the date the order was set to ‘Approved’. System calculated and display only.

Actual Convert Date:  Displays the date this order was converted to a purchase order.

• If the quantity is split between two or more purchase order lines, this date represents the most recent conversion date.

• System calculated and display only.

Sched Vendor Ship Date:  

• The date the vendor must ship your product to satisfy the dock date. 

• It is calculated based on Vendor ship time from the Item/Vendor Master, but it can be overridden here.

Sched Firm Date:  

• The date of this requisition must be firmed to meet the required dock date.

• This pertains to MRP / DRP-generated requisitions created in the 'Planned' status.

• It is calculated using the vendor lead time and inspection time, but it can be overridden here.

Sched Dock Date:  

• The date the item on this requisition must be on your dock to meet manufacturing requirements.

• This date is calculated by the system by subtracting the inspection lead time from the Due Date, but it can be overridden. 

Sched PO Place Date:  

• The date the Purchase Order must be placed with the Vendor to make the scheduled dock date, based on vendor and inspection lead times.

• This date is calculated by the system but can be overridden.

Calculation of Dates for Requisitions generated by MRP and DRP

  NOTE  The date calculation will also depend on the picklist field 'Schedule Date Type' on the System Defaults as follows:

• When the 'Schedule Date Type' field value is 'Calendar, 7-Day', the system calculates the dates on all seven days in a week without considering any holidays/weekends.

• When the 'Schedule Date Type' field value is 'Shop Calendar' and Saturdays & Sundays are defined as holidays in the Shop Calendar. The system calculates the dates on the weekdays.

  EXAMPLE 1  During DRP processing, consider the 'Schedule Date Type' field value as 'Calendar, 7-Day', 'Sched Firm Date' as '01/19/2024' (Friday), and the 'PO Req Firm Lead Time' as '2'.

The system calculates the 'Sched PO Place Date' as 01/19/2024 + 2, which is '01/21/2024' (Sunday) by considering the holidays/weekends.

  EXAMPLE 2  During DRP processing, consider the 'Schedule Date Type' field value as 'Shop Calendar', 'Sched Firm Date' as '01/19/2024' (Friday), and the 'PO Req Firm Lead Time' as '2'. And in the Shop Calendar, '01/20/2024' (Saturday) and '01/21/2024' (Sunday) are defined as holidays.

The system calculates the 'Sched PO Place Date' as 01/19/2024 + 2, which is 01/23/2024 (Tuesday) by considering the weekends as holidays.

SEE ALSO
 

Inventory Requisition Workbench
Purchase Requisition
MRP Overview
DRP Overview