{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":50271,"path":"source-to-pay-operations/sourcing-and-procurement-operations/create-approval-rule.md","title":"Create an approval rule","bundle":null,"doc_type":null,"release":"australia","body":"\n# Create an approval rule\n\nApprove a purchase requisition, purchase order, sourcing request, or invoice, by defining an approval strategy and creating approval rules. This is a one-place configuration that can drive any kind of approval process that your organization may need.\n\n## Before you begin\n\nTo create an approval rule, you must have set up your product catalog \\(with the necessary product categories, product models, and supplier products\\) and should be able to raise a purchase requisition or sourcing request. For more information on how to set up your product catalog, see [Create a product category](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/source-to-pay-operations/sourcing-and-procurement-operations/create-product-model-categories.md), [Create a product model](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/source-to-pay-operations/sourcing-and-procurement-operations/create-product-models.md), and [Add a supplier product](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/source-to-pay-operations/sourcing-and-procurement-operations/add-supplier-product.md). You should have also set up the sys\\_user record appropriately to include relevant details such as job codes, managers.\n\nRole required: sn\\_shop.procurement\\_administrator\n\n## About this task\n\nYou can create an approval rule to determine how approval plans are generated and routed when conditions are met, from the Sourcing and Purchasing Automation module.\n\n\\[Omitted image \"create\\_approval\\_rule.png\"\\] Alt text: Approval rule.\n\n## Procedure\n\n1. Navigate to **All** > **Sourcing and Purchasing Automation** > **Administration ** > **Approval Rule **.\n\n2. Select **New**.\n\n3. On the form, fill in the fields.\n\n\n
\n\nField\n\n\n\nDescription\n\n
\n\nNumber\n\n\n\nSystem-generated unique identifier for the approval rule.\n\n
\n\nName\n\n\n\nName you assign to the approval rule.\n\n
\n\nActive\n\n\n\nOption to decide if this rule is used to generate approvals during the purchase requisition process.\n\n
\n\nApproving object\n\n\n\nObject you’re seeking approval for. The following options are available:- Invoice\n- Purchase Order\n- Purchase Requisition\n- Sourcing Request\nIt's defaulted based on the approving object selected. For sourcing request and purchase requisition it’s purchase requisition line, for purchase order it’s purchase order line, and for invoice it’s invoice line.\n\n**Note:** While full approval workflows, including approval engine, state flows, and email notifications, are provided for purchase requisitions and sourcing requests, additional implementation is required in defining state flows and email notifications for purchase order and invoice approval rules.\n\n
\n\nApproving line\n\n\n\nApproving object line you're seeking approval for.\n\n
\n\nApproval rule type\n\n\n\nType of approval rule that determines how approval plans are generated and routed when conditions are met. The following options are available:\n\n - Dynamic Users or Groups\n- Managerial Job Code Hierarchy\n- Managerial Hierarchy\n- Specified Users or Groups\n- Cost Center Managers\n\n**Note:** This option is available only when the approving object is a purchase requisition.\n\n Depending on the rule type you select, the associated fields appear. For more information on these rules, see [Approval rule types](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/source-to-pay-operations/sourcing-and-procurement-operations/approval-rule-types.md).\n\n
\n\nBase approvals on\n\n\n\nBusiness owner who the approval rule is based on.\n\n
\n\nUsers\n\n\n\nSpecified users who should receive the approval based on the approval trigger.\n\n
\n\nGroups\n\n\n\nUsers in the specified groups who should receive the approval based on the approval trigger.\n\n
\n\nApproval sequence\n\n\n\nSequence in which the approval rules should be triggered. For more information on this, see [Approval rule grouping and sequencing](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/source-to-pay-operations/sourcing-and-procurement-operations/approval-rule-sequencing.md).\n\n
\n\nApproval required from\n\n\n\nDetermines the managers who should receive the approval request during the purchase requisition process.\n\n
\n\nAllow automatic approval\n\n\n\nDetermines if self-approval is to be enabled. By default, this flag is checked or set to true, enabling the self-approval functionality, where the requester has the approving authority. However, if the flag is cleared or set to false, the requester is included to be an active approver in the approval engine’s generated approval list, thus overriding the default self-approval functionality. The requester now needs to provide an explicit approval decision by completing an approval task.\n\n
\n\nPurchasing user\n\n\n\nUser for whom approvals are triggered.\n\n
\n\nSend approval to purchasing users\n\n\n\nOptions to send an approval dynamically to a user or group related to the purchasing user.\n\n
\n\nAuthorized job codes\n\n\n\nOne or more job codes that can automatically approve purchases up to the specified limit.\n\n
\n\nApproved purchasing limit\n\n\n\nReference currency threshold within which users with the specified job codes can approve purchase requisitions.\n\n
\n\nApproval routing method\n\n\n\nMethod of routing the approvals. The options are sequentially and in parallel.\n\n
\n\nApproval decision method\n\n\n\nMethod of approving the rule. You can select if all approvers must approve the rule or any approver can approve it.\n\n
\n\nApproval trigger conditions\n\n\n\nConditions based on the approving object that determine the conditions under which an approval plan is created.The trigger conditions are based on the Approving Object table and enable the user to dot-walk. For example, if the user wants to create trigger conditions from the maximum budget of a sourcing request, they should walk from maximum budget to amount, and then create the conditions.\n\n**Note:** Approvals are individually evaluated for each approving object. For example, creating the same approval for a sourcing request and a purchase requisition results in approvals getting triggered twice. To prevent this, the admin can configure approvals from not getting created in a purchase requisition if it's backed by a sourcing request that isn't empty. This is done from the approval trigger conditions.\n\n
4. Select **Submit**.\n\n\n- **[Approval rule types](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/source-to-pay-operations/sourcing-and-procurement-operations/approval-rule-types.md)** \nApproval rule types determine the methods by which approvals are created during the purchase requisition process.\n- **[Approval rule considerations](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/source-to-pay-operations/sourcing-and-procurement-operations/approval-rule-considerations.md)** \nFactors like currency, which includes foreign exchange, reference, and transactional, decide the approval rules to be triggered. Some of the other factors are purchasing limit, line amount, and received lines, among others.\n- **[Approval rule grouping and sequencing](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/source-to-pay-operations/sourcing-and-procurement-operations/approval-rule-sequencing.md)** \nAs a Procurement Administrator, you can associate approval rules with approval groups and define the sequence to determine when these rules should be triggered. With this association, a set of approval rules within a rule group is triggered in sequence, instead of all of them being evaluated simultaneously.\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"}}