17
In the purchase order workflow you cannot select the" is at or below" option for the procurement category header. You must select every category header and sub-category for the approval to follow the correct path. The option is available in the purchase requisition workflow and I would expect the purchase order workflow to follow the same behaviour. Our client wants to only create purchase order as they only have 15 users creating PO's and no procurement team, so no RFQ functionality and also want to use the mobile APP for directors to approve, which has no Req approval. The only option in the purchase order workflow is "is" or "is not" and as you now procurement categories are being added to constantly, so you do not want to have to maintain the workflow every time.
STATUS DETAILS
Needs Votes
Ideas Administrator

Thank you for your feedback. Currently this is not in our roadmap; however, we are tracking it and if we get more feedback and votes, we may consider it in the future.

Comments

G

This is not that complex. MS needs to add the attribute ExpressionHierarchyProvider to the class PurchTableDocument. And they need to extend the switch-case in the class PurchReqExpressionProvider with PurchLine.ProcurementCategory.

Category: Procurement and Sourcing

G

The Vendor Invoice workflow already has this option, we need it for our customers as well for purchase orders. Maintenance then will be limited when creating new subcategories.

Category: Procurement and Sourcing