How To
- Approve order function.
- Cost Activities
- How does the “Approved Supplier” (QA status) functions work?
- How does the Approve direct purchases onshore work?
- How does the rule-based approval matrix work?
- How To - Set Failure Report Running Number
- How To - Add SQL Server to Windows Firewall Exception
- How To - Access the report template editor
- How To - Accounts and Budget (v. 2.662 and later)
- How To - Active a unit for use with the Incidents Module
- How To - Add same document on multiple components
- How To - Approve Purchase Orders and Change Requests when using Approval Rules and Change Approval
- How To - Assign user rights
- How To - Automatically resize images
- How To - Backup TMv2
- How To - Cancel Job History (Job Signed Out In Error)
- How To - Cancel job history (Video Link)
- How To - Catalogs
- How To - Change a Unit Code in TM Master V2
- How To - Check for File Not Found Error. Document Handling.
- How To - Circulating Components
- How To - Company tags
- How To - Connect the TM Master v2 Client Application
- How To - Connect the TM Master v2 client to more than one database
- How To - Contract Management
- How To - Copy Components, Component Jobs and Spare Parts
- How To - Create a new unit
- How To - Create a New User TM Master v2
- How To - Create and use batch jobs in TM
- How To - Create Credit Note
Rule Based Approval Matrix Introduction
Introduction
Available “order approval” approaches in TM Master
After the quotation process an order should have a total order value, this order value will need to be approved prior to sending it to the supplier. TM Master has three available approaches to approving orders. One of them, the “Approval Level based” is made more or less obsolete by the recently added Rule-based approval function.
- Standard Approval
Users are assigned a user right to approve an order. If a user has the “ApproveAtOffice” user right the user can approve any order, regardless of value or any other details on the order. This is a simple way of approving orders, that may work for small companies, but will most likely be too basic for larger companies
- Approval Level based
Approval level based approval will, by using value levels, differentiate between who will be allowed to approve the order. Each value level can be linked to one or more user groups. Any users within that user group will be allowed to approve an order with a value within the assigned value level. Only when the top value level of the order is approved, will the order technically be approved. However each sub level may also be approved, as in a chain of approvals. Who will approve each level is done by a manual selection among users with the appropriate user rights, by the purchaser. A manual action is required to notify each level’s approver.
This function is made more or less obsolete by the “rule-based” approval matrix. The “rule-based approval” will be able to provide the same functionality, but will also remove the manual actions required for each level
- Rule-based approval
Rule-based approval, will also use approval value levels, but will automatically select who will approve each level using a set of configured rules. The conditions of the rules can be the order’s originating vessel, Order type, Order WBS, account and/or cost code. As with the “approval Level based” approval, only when the top value level of the order is approved, will the order technically be approved. However each sub level may also be approved, as in a chain of approvals. With the rule-based approval, the purchaser will initiate the approval process, by sending a “request for approval” to the user selected for the lowest level , and TM Master will notify each user in turn working its way up to the top approval level.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article