|
• Value of the request – approval is based on the total value of the document
• Change since the previous approval – approval is based on the net change in the value of the document. For example, if the document was approved for $1000 and then redrafted and changed to $1,150, re-approval is required for the $150 difference.
• Work order purchases are approved after the work is approved – any purchase requirements must be approved separately
• Value of the work order – approval is based on the total value of the document
• Change since previous approval – approval is based on the net change in the value of the document. For example, if the document was approved for $1000 and then redrafted and changed to $1,150, re-approval is required for the $150 difference.
• All planned costs – approval is required for the total value of the document
• Only the selected types of requirements – approval is required for costs on the selected requirements
• Value of the project – approval is based on the total value of the document
• Change since previous request – approval is based on the net change in the value of the document. For example, if the document was approved for $1000 and then redrafted and changed to $1,150, re-approval is required for the $150 difference
• Requisitions are approved: When a requisition is sent for approval, the entire requisition is sent to a single approval route. This is the default value.
• Requisition lines are approved: When a requisition is sent for approval, each line must be approved separately. The approval requestor will be able to select a different approval route for each line.
• Value of the request – approval is based on the total value of the document
• Change since previous approval – approval is based on the net change in the value of the document. For example, if the document was approved for $1000 and then redrafted and changed to $1,150, re-approval is required for the $150 difference.
When the GL accounts option is selected, the system filters the list of approval routes to include only those routes for the GL account being charged on the purchase order.When the Buyer option is selected, the system filters the list of approval routes to include only those routes for the buyer responsible for the purchase order.
• Value of the order – approval is based on the total value of the document
• Change since previous approval – approval is based on the net change in the value of the document. For example, if the document was approved for $1000 and then redrafted and changed to $1,150, re-approval is required for the $150 difference.
• Value of the contract – approval is based on the total value of the document
• Change since previous approval – approval is based on the net change in the value of the document. For example, if the document was approved for $1000 and then redrafted and changed to $1,150, re-approval is required for the $150 difference.
• Value on the price difference – approval is based on the total value of the line
• Change since previous approval – approval is based on the net change in the value of the line. For example, if the line was approved for $1000 and then redrafted and changed to $1,150, re-approval is required for the $150 difference.
• Value of the price difference – approval is based on the total value of the line
• Change since previous approval – approval is based on the net change in the value of the line. For example, if the line was approved for $1000 and then redrafted and changed to $1,150, re-approval is required for the $150 difference.
• Value of the price difference – approval is based on the total value of the line
• Change since previous approval – approval is based on the net change in the value of the line. For example, if the line was approved for $1000 and then redrafted and changed to $1,150, re-approval is required for the $150 difference.
• The employee responsible for the document being approved: The “employee responsible for the document being approved” is determined based on the context:
• Projects: Project manager
• Work orders: Primary task’s Requestor. If no requestor is entered, the Planner is used.
• Work requests: Requestor
• Asset transfer documents: “Transferred by” employee
• Requisitions: “Requested by” employee
• Purchase orders: “Requested by” employee
• Contracts: Buyer
• Invoices: “Created by” employee
• Invoice lines: “Created by” employee