Requisitions |
The Requisitions tab enables you to specify defaults for requisitions, including whether approval is required, default statuses, and default purchase type.
Enterprise purchasing options
Require approval
Require approval should be enabled if Approval Types will be required on <Object Type>.
Note: Replace <Object Type> with Requisitions, Purchase orders, Request for B/Q/P or Responses to RFB/Q/P as appropriate.
Default approval type
Default approval type. This field has a list box. Required if the Require approval field has a check. Review which purchasing objects where the approval types will be used. Enable approvals to be required on Enterprise Setup - Purchasing - Options screen for Requisitions, Purchase orders, Request for B/Q/P or Responses to RFB/Q/P where the approval types will be used.
Note: If the stage requires approval, you need to set a default approval type with a PENDING state.
In Enterprise Purchasing, approval types are defined on the Data -> Enterprise Purchasing -> Setup -> Approval Types screen.
Default initial status
Default initial status. Applies to headers and line items. If the stage requires approval, the status must have a PENDING state. If the stage does not require approval, the status may have an OPEN state. This field has a list box. This field is required.
In Enterprise Purchasing, statuses are defined on the Data -> Enterprise Purchasing -> Setup -> Statuses screen.
Default updated status
Default status that indicates that key information was changed on an open line item. Update statuses enable you to easily identify items that may need to be resent to the vendor. This field has a list box.
If approvals are required, you may want to specify a PENDING state to ensure that the line item goes through the approval process again. If approvals are not required, you may specify a status with an OPEN state. In Enterprise Purchasing, statuses are defined on the Data -> Enterprise Purchasing -> Setup -> Statuses screen.
Note: Key information includes part-suffix, other ID, description, quantity, and unit price.
Default closed status
Default status that indicates that a line item was closed automatically. This field has a list box. Must be a status with a CLOSED state. Required. In Enterprise Purchasing, statuses are defined on the Data -> Enterprise Purchasing -> Setup -> Statuses screen.
Note: Actions that close a line item automatically include receiving all or more of the ordered quantity on a purchase order.
Automatically update requisition header status when all line items are closed
If this field has a check, the requisition header is automatically updated to the value specified in the Header status on line close field once all line items have been fully received.
Header status on line close
Status to assign to the header once all line items on a requisition have been fully received. This field has a list box of statuses that are allowed on requisitions. This field is optional.
Note: Applies to the Data -> Enterprise Purchasing -> Requisitions and Data -> Enterprise Purchasing -> Receipts screens.
Combine similar line items
If this field has a check, two or more line items that have all of the following information in common are combined together rather than listed separately on the PO.
Part ID and suffix
Line item type
Unit price
Unit of measure
Discount percentage
If you have multiple requisitions to purchase similar items (for example, all have the same part ID), you can add them to the same purchase order. If this option is selected, when similar items are added to the same purchase order, The system increases the quantity of the existing line item rather than create a new line item.
Default purchase type for generated requisitions
Purchase type to be used if the next stage of the purchasing process does not support the purchase type on the originating item (i.e., the requisition). This field has a list box.
Purchase types are defined on the Data -> Enterprise Purchasing -> Setup -> Purchase Types screen.
Default required date to today if not set
If this field has a check, the date required for line items defaults to the current date. Applies to the required date or needed-by date on the header and line items. If a needed-by date is specified on the applicable Basic Info tab, however, that date will be used instead.
Note: If this option is not selected and a date is not specified, the date remains blank.
Default expected delivery date to today if not set
If this field has a check, the expected delivery for line items defaults to the current date. Applies to the expected delivery date on the header and line items. If an expected delivery date is specified on the applicable Basic Info tab, however, that date will be used instead.
Minimum lead days
Minimum number of days of lead time required by the vendor.
If the Minimum lead days field on the Purchasing Info tab of the Data -> Setup -> Organization Structure -> Vendors -> Primary Information screen specifies 0, this field is used to determine the expected delivery date on the Line Items tab of the Data -> Enterprise Purchasing -> Requisitions screen.
Require account code before requisition is approved - This option applies to requisition header account code and line item account code.
If enabled, this requires that an account ID has been provided when approving a requisition or a requisition line item.
Require miscellaneous 1, 2, 3, 4, 5, 6 has data before requisition is approved
If enabled, this would require that the specified miscellaneous files section has data in order to approve a requisition.
Allow inactive employees to be used on requisitions
If enabled, this allows inactive employees to be used on requisitions. This is helpful in scenarios where EAM integrates with 3rd party systems that may be sending over inactive employee IDs to create requisitions and those initial orders are requested by an employee who leaves before it is approved.