I'm curious to hear the experiences of others with AX 2012 workflow, particularly as relates to Purchase Orders and Purchase Requisitions.
Our company (Planar, high-tech electronics manufacturing for the display industry) has found the default functionality of PO approval workflow, for example, lacking and not very realistic. As I understand it, any change to an approved PO including: expected receipt date, description, dollar variance, splitting line items, even partial receipts, must go through the re-approval cycle. That doesn't seem very real-world.
We'd like to change the workflow so that it ignores some of the constraints. Obviously we do need to maintain financial controls, but some of these changes are either outside that or not material. What we're finding, though, is that making these changes to workflow involves a significant amount of work and some question about whether it's possible.
This doesn't match my perception of what a modern workflow framework should be. I would expect a good workflow to be visual, flexible and intuitive enough that a business analyst could make changes to rules and notifications fairly quickly.
I'm admittedly not a technical resource so sharing my perspective from a high level, but interested in the experiences of others with 2012 workflow. Also interested in knowing - are we missing something in terms of default PO workflow?
thanks in advance!Jeff Maurer
We are undergoing through the same problem & want reapproval feature where the purchase order should go to workflow only for few field changes otherwise should get auto approved.
AX 2012 R2 releasing on 1st december seems to have this feature:
Can you advise any solution you have thought or any answers you recd. from forums?
Thanks & regards,
Purchasing policy supports these efforts.