Purchase requisition
A purchase requisition represents a request that is sent internally within an organization to obtain purchased goods or services. It consists of items that need to be ordered, and may need to go through approvals for a purchase order to be created.
A purchase requisition is created in either of the following scenarios:
- When a shopper selects Request to buy from a product details page on ShoppingHub.
- When a supplier is selected after providing quotes in a sourcing request.
Through a purchase requisition, the purchasing department understands details of the items that are requested, the quantity, supplier, cost, and reason for purchase.
Purchase requisition.
| Field | Description |
|---|---|
| Number | System-generated unique identifier of the purchase requisition. |
| Requisition type | Indicates if this requisition is net new or a revision.The shopper can revise the quantity of the product or delivery location for on order from ShoppingHub or the buyer can submit a revision from the Sourcing and Purchasing Automation module. To understand how revisions are handled, see Purchase revisions. |
| Assigned to | User who is responsible for the purchase. Determined using purchasing assignment rules. |
| Primary contact | Person within the procurement team working on the purchase who can be contacted with questions. This field is populated or updated with the same user in the Assigned to field on the purchase requisition. |
| Business owner | User who submitted the purchase request. |
| Submitted by | User who has shopped and submitted the purchase. |
| State | Status of the purchase requisition.Note: This is a read-only field. |
| Purchase | Unique ID of the purchase. |
| Negotiation | Negotiation associated with this purchase requisition. |
| Purchase order | Purchase order associated with this purchase requisition. |
| Short description | Brief description of the purchase requisition. |
| Summary Details | |
| Supplier | Indicates the supplier who provides the product. |
| Order type | Indicates whether the resulting order is a standard or blanket order.During the checkout of a product or service, if the shopper selects a time frame for the delivery based on date range or term, the order type is considered as Blanket. Otherwise, the order type is considered as Standard. |
| After the fact | Indicates if the purchase requisition is after the fact or not.After a purchase line is created and grouped into a purchase requisition, if the created on date is either within or after x number of days of the expected delivery date or start date, then the entire purchase requisition would be considered as after the fact. For a purchase requisition that has multiple purchase lines, if at least one line is after the fact, the entire purchase requisition is considered after the fact. |
| Requested delivery | Requested delivery date.Note: This can be a date or date range that is in the past, present, or future. For the date to be in the past, the After the fact field must be set to Yes. |
| Shipping method | Details of the carrier, the applicable suppliers, and the valid delivery location countries for those suppliers.For more information on shipping methods and handling fees, see Handling fees. |
| Total estimated tax | The estimated sum of all taxes related to purchase lines within a purchase requisition. |
| Total estimated shipping | Estimated sum of all shipping costs related to purchase lines within a purchase requisition. |
| Discount percentage | Discount provided if the minimum spend requirement is met.This field isn’t displayed for a blanket order type. |
| Minimum spend | Minimum amount that must be spent to avail a discount.This field isn’t displayed for a blanket order type. |
| Total amount | Total cost of purchase requisition calculated as the sum from all purchase lines. |
| Accounting Details | |
| Payment term | Payment term as agreed with the supplier. This value defaults from the referenced supplier record. |
| Legal entity | This value defaults from the associated business owner. |
| Purchasing entity | This value defaults from the associated business owner. |
| Cost center | This value defaults from the associated business owner.Note: This value must be filled on the Business Owner record for it to be populated on the purchase requisition. |
The following are the related lists of a purchase requisition:
| Related list | Description |
|---|---|
| Purchase Lines | Provides information of the individual lines under a purchase requisition for the referenced supplier. Handling fees, if applicable, are added as a purchase line for this purchase requisition. For more details, see Purchase lines.For information on shipping methods and handling fees, see Handling fees. |
| Purchasing Tasks | Provides information of all purchasing tasks that must be completed prior to creation of a purchase order.For more details, see Purchasing tasks and procurement cases. |
| Purchasing SLAs | Provides SLA information for tasks and approvals. The underlying SLA definitions are defined through purchasing SLA definitions, which is an administration module. |
| Cases | Displays all the cases associated with this purchase requisition. |
| Related Contracts | Provides information of all active and draft contracts for the referenced supplier. |
| Purchasing Permissions | This related list is conditionally displayed for purchase requisitions whose order type is Blanket.Purchasing permissions enable a user to define a list of pre-approved users, groups, departments, or cost centers. Any purchases made by these users against the blanket purchase order don’t require an approval process. By default, the business owner on the originating purchase requisition of order type Blanket is added as a user that can create a standard release against a blanket purchase order. |
| Related Purchase Requisition | This related list is conditionally displayed for revised requisitions. It shows the relationship between the original and revised purchase requisitions. |
| Approval Plans | Displays all the approval plans created against this purchase requisition. |
| Approvals | Displays the list of approvers that must approve the purchase requisition. |
| Contract Requests | Displays all the associated contract requests against this purchase requisition.Note: This field is displayed only if you have the Source-to-Pay Operations with Contract Management Pro plugin (sn_spend_clm) installed. |
| Draft Emails | Associated email communication that is saved as drafts. |
| Sent Emails | Associated email communication that has been sent. |
The key purchasing properties relevant to a purchase requisition are:
- sn_shop.atf.threshold.days
- sn_shop.spend.requisition.autoorder
sn_shop.spend.requisition.autoorder.threshold
For more information on how the auto-order properties affect purchase order creation, see Purchase requisition auto-order.
sn_shop.approval.reassessment.resend
For the list of all purchasing properties, see Purchasing properties. If you have the role of a procurement administrator, you can access the Purchasing Properties module by navigating to Sourcing and Purchasing Automation > Administration.
The default states that are available for a purchase requisition are listed.
- Pending Review
- Pending Approval
- Awaiting Task Completion
- Final Review
- Pending Submission
- Closed Complete
- Closed Canceled
- Closed Rejected
- Pending Cancellation
- Pending Revision
- Pending Supplier Confirmation
For a list of all purchase requisition states and the conditions that trigger each state change, see Purchase requisition, purchase order, and sourcing request states.
- Handling fees
Configure the conditions of a purchase request that, met, add a handling fee to that purchase request. Any field on the Purchase Request table can be used as part of the conditions to determine if a handling fee is to be applied for a purchase.
Parent Topic:Sourcing and Purchasing Automation