How to do a standard purchase order approval process where we use standard approve and close buttons and only specific roles at specific tiers have access to it?

AI generated answer (using internal Slack threads):

****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ****** To implement a standard purchase order approval process where only specific roles at specific tiers have access to it, you can use NetSuite's built-in approval workflows. Here are the steps: 1. Navigate to Customization > Scripting > Scripted Records. 2. Look for Purchase Order and see what customization it has. If there is a workflow that hides the button by role, you might need to adjust it to fit your needs. However, if you need more complex rules, such as approvals per line item or tiered approval, you might need to create a custom workflow or script. Please note that creating a custom workflow or script can be more involved and may require a good understanding of SuiteScript. If you're using a native role and the approve button is not displaying, it could be due to a workflow or script that is hiding the button. You can check this by going to Customization > Scripting > Scripted Records and looking for any customizations on the Purchase Order. Remember, if you're in a full access role you can set the employee to whomever you want, or leave it blank so it would make the approval routing hierarchy a 2 foot high fence. Limiting create/edit access to POs to only A/P, inventory management and employee center is a pretty clean way to go. Also, please note that the approval routing hierarchy works when purchasing requests are made through the Employee Center role. This is because if you're in a full access role you can set the employee to whomever you want, or leave it blank, which would make the approval routing hierarchy less effective. If you need to build a custom PO approval process using workflow, you can set any rules you want including approval for POs created with a full-access role. However, you'd need to build the whole thing from scratch and wouldn't be able to leverage the native routing hierarchy for purchase and approval limits.