{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":50482,"path":"source-to-pay-operations/sourcing-and-procurement-operations/purchase-requisition.md","title":"Purchase requisition","bundle":null,"doc_type":null,"release":"australia","body":"\n# Purchase requisition\n\nA 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.\n\nA purchase requisition is created in either of the following scenarios:\n\n-   When a shopper selects **Request to buy** from a product details page on ShoppingHub.\n-   When a supplier is selected after providing quotes in a sourcing request.\n\nThrough a purchase requisition, the purchasing department understands details of the items that are requested, the quantity, supplier, cost, and reason for purchase.\\[Omitted image \"create\\_purchase\\_requisition.png\"\\] Alt text: Purchase requisition.\n\n<table id=\"table_a5j_d3r_flb\"><thead><tr><th>\n\nField\n\n</th><th>\n\nDescription\n\n</th></tr></thead><tbody><tr><td>\n\nNumber\n\n</td><td>\n\nSystem-generated unique identifier of the purchase requisition.\n\n</td></tr><tr><td>\n\nRequisition type\n\n</td><td>\n\nIndicates 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.\n\nTo understand how revisions are handled, see [Purchase revisions](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/source-to-pay-operations/sourcing-and-procurement-operations/purchase-revisions.md).\n\n</td></tr><tr><td>\n\nAssigned to\n\n</td><td>\n\nUser who is responsible for the purchase. Determined using purchasing assignment rules.\n\n</td></tr><tr><td>\n\nPrimary contact\n\n</td><td>\n\nPerson 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.\n\n</td></tr><tr><td>\n\nBusiness owner\n\n</td><td>\n\nUser who submitted the purchase request.\n\n</td></tr><tr><td>\n\nSubmitted by\n\n</td><td>\n\nUser who has shopped and submitted the purchase.\n\n</td></tr><tr><td>\n\nState\n\n</td><td>\n\nStatus of the purchase requisition.**Note:** This is a read-only field.\n\n</td></tr><tr><td>\n\nPurchase\n\n</td><td>\n\nUnique ID of the purchase.\n\n</td></tr><tr><td>\n\nNegotiation\n\n</td><td>\n\nNegotiation associated with this purchase requisition.\n\n</td></tr><tr><td>\n\nPurchase order\n\n</td><td>\n\nPurchase order associated with this purchase requisition.\n\n</td></tr><tr><td>\n\nShort description\n\n</td><td>\n\nBrief description of the purchase requisition.\n\n</td></tr><tr><td class=\"sub-head\" colspan=\"2\">\n\nSummary Details\n\n</td></tr><tr><td>\n\nSupplier\n\n</td><td>\n\nIndicates the supplier who provides the product.\n\n</td></tr><tr><td>\n\nOrder type\n\n</td><td>\n\nIndicates 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**.\n\nOtherwise, the order type is considered as **Standard**.\n\n</td></tr><tr><td>\n\nAfter the fact\n\n</td><td>\n\nIndicates 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.\n\n</td></tr><tr><td>\n\nRequested delivery\n\n</td><td>\n\nRequested 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.\n\n</td></tr><tr><td>\n\nShipping method\n\n</td><td>\n\nDetails 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](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/source-to-pay-operations/sourcing-and-procurement-operations/handling-fees.md).\n\n</td></tr><tr><td>\n\nTotal estimated tax\n\n</td><td>\n\nThe estimated sum of all taxes related to purchase lines within a purchase requisition.\n\n</td></tr><tr><td>\n\nTotal estimated shipping\n\n</td><td>\n\nEstimated sum of all shipping costs related to purchase lines within a purchase requisition.\n\n</td></tr><tr><td>\n\nDiscount percentage\n\n</td><td>\n\nDiscount provided if the minimum spend requirement is met.This field isn’t displayed for a blanket order type.\n\n</td></tr><tr><td>\n\nMinimum spend\n\n</td><td>\n\nMinimum amount that must be spent to avail a discount.This field isn’t displayed for a blanket order type.\n\n</td></tr><tr><td>\n\nTotal amount\n\n</td><td>\n\nTotal cost of purchase requisition calculated as the sum from all purchase lines.\n\n</td></tr><tr><td class=\"sub-head\" colspan=\"2\">\n\nAccounting Details\n\n</td></tr><tr><td>\n\nPayment term\n\n</td><td>\n\nPayment term as agreed with the supplier. This value defaults from the referenced supplier record.\n\n</td></tr><tr><td>\n\nLegal entity\n\n</td><td>\n\nThis value defaults from the associated business owner.\n\n</td></tr><tr><td>\n\nPurchasing entity\n\n</td><td>\n\nThis value defaults from the associated business owner.\n\n</td></tr><tr><td>\n\nCost center\n\n</td><td>\n\nThis 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.\n\n</td></tr></tbody>\n</table>The following are the related lists of a purchase requisition:\n\n<table id=\"table_r2v_bmr_flb\"><thead><tr><th>\n\nRelated list\n\n</th><th>\n\nDescription\n\n</th></tr></thead><tbody><tr><td>\n\nPurchase Lines\n\n</td><td>\n\nProvides 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](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/source-to-pay-operations/sourcing-and-procurement-operations/purchase-lines.md).For information on shipping methods and handling fees, see [Handling fees](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/source-to-pay-operations/sourcing-and-procurement-operations/handling-fees.md).\n\n</td></tr><tr><td>\n\nPurchasing Tasks\n\n</td><td>\n\nProvides 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](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/source-to-pay-operations/sourcing-and-procurement-operations/purchasing-tasks.md).\n\n</td></tr><tr><td>\n\nPurchasing SLAs\n\n</td><td>\n\nProvides SLA information for tasks and approvals. The underlying SLA definitions are defined through purchasing SLA definitions, which is an administration module.\n\n</td></tr><tr><td>\n\nCases\n\n</td><td>\n\nDisplays all the cases associated with this purchase requisition.\n\n</td></tr><tr><td>\n\nRelated Contracts\n\n</td><td>\n\nProvides information of all active and draft contracts for the referenced supplier​.\n\n</td></tr><tr><td>\n\nPurchasing Permissions\n\n</td><td>\n\nThis 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.\n\nBy 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.\n\n</td></tr><tr><td>\n\nRelated Purchase Requisition\n\n</td><td>\n\nThis related list is conditionally displayed for revised requisitions. It shows the relationship between the original and revised purchase requisitions.\n\n</td></tr><tr><td>\n\nApproval Plans\n\n</td><td>\n\nDisplays all the approval plans created against this purchase requisition.\n\n</td></tr><tr><td>\n\nApprovals\n\n</td><td>\n\nDisplays the list of approvers that must approve the purchase requisition.\n\n</td></tr><tr><td>\n\nContract Requests\n\n</td><td>\n\nDisplays 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.\n\n</td></tr><tr><td>\n\nDraft Emails\n\n</td><td>\n\nAssociated email communication that is saved as drafts.\n\n</td></tr><tr><td>\n\nSent Emails\n\n</td><td>\n\nAssociated email communication that has been sent.\n\n</td></tr></tbody>\n</table>The key purchasing properties relevant to a purchase requisition are:\n\n-   sn\\_shop.atf.threshold.days\n-   sn\\_shop.spend.requisition.autoorder\n-   sn\\_shop.spend.requisition.autoorder.threshold\n\n    For more information on how the auto-order properties affect purchase order creation, see [Purchase requisition auto-order](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/source-to-pay-operations/sourcing-and-procurement-operations/pr-auto-order.md).\n\n-   sn\\_shop.approval.reassessment.resend\n\nFor the list of all purchasing properties, see [Purchasing properties](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/source-to-pay-operations/sourcing-and-procurement-operations/installed-with-FSC.md). If you have the role of a procurement administrator, you can access the Purchasing Properties module by navigating to **Sourcing and Purchasing Automation** &gt; **Administration**.\n\nThe default states that are available for a purchase requisition are listed.\n\n-   Pending Review\n-   Pending Approval\n-   Awaiting Task Completion\n-   Final Review\n-   Pending Submission\n-   Closed Complete\n-   Closed Canceled\n-   Closed Rejected\n-   Pending Cancellation\n-   Pending Revision\n-   Pending Supplier Confirmation\n\nFor a list of all purchase requisition states and the conditions that trigger each state change, see [Purchase requisition, purchase order, and sourcing request states](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/source-to-pay-operations/sourcing-and-procurement-operations/pr-po-sr-states.md).\n\n-   **[Handling fees](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/source-to-pay-operations/sourcing-and-procurement-operations/handling-fees.md)**  \nConfigure 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.\n\n**Parent Topic:**[Sourcing and Purchasing Automation](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/source-to-pay-operations/sourcing-and-procurement-operations/purchase-experience-workflow.md)\n\n"}}