D365 Finance & Operations and Dynamics AX Forum

Expand all | Collapse all

Purchase Requisition workflow

  • 1.  Purchase Requisition workflow

    Posted 29 days ago
      |   view attached
    I have set one of my conditional decisions to be 'Yes or no, line.Net Amount<$5000'. It works well with a single line req, but if for example line 1 of the req is $10k and line 2 is $50.00, the purch req. will require no approval. This is bad. Has anyone else experienced this? I am hopeful I can make it work so it will catch any line that is greater than $5k.

    Thanks everybody

    ------------------------------
    Jeff Retzak
    Stella and Chewys
    Oak Creek WI
    ------------------------------


  • 2.  RE: Purchase Requisition workflow

    Posted 29 days ago

    Hi Jeff, 

    Are you able to use PurchaseRequistion.Invoice Amount ? this should count all the line values. 

    Thanks, 



    ------------------------------
    Graeme Thom
    AX Administrator
    Hunter Boot Ltd
    Edinburgh
    ------------------------------



  • 3.  RE: Purchase Requisition workflow

    SILVER CONTRIBUTOR
    Posted 29 days ago
    Hi Jeff,
    Are you using the "purchase requisition review" or "purchase requisition line review" workflow template? Our workflow looks at the field "purchase requisitions.approval amount excl tax" and we have a signing policy that determines which job level can approve what amounts. I am not sure this helps you, just wanted to share how we do it if it is an option for you.
    Good luck!
    Kerstin

    ------------------------------
    Kerstin Newman
    Business Analyst
    StarTech.com
    London ON
    ------------------------------



  • 4.  RE: Purchase Requisition workflow

    TOP CONTRIBUTOR
    Posted 29 days ago
    As Kerstin said, there is line review and header review.  We have had a requirement as well on multiple clients to check the line information and either route or change the approval path based on line information.  We have found that anytime you set a condition that includes line information on the header review workflow, it only looks at one line (usually the first during our testing).  Therefore, you really need a line level workflow to test each line - unfortunately, that means that an approval needs to happen on every single line.

    Since we didn't want that, we were able to use header workflow and policies at one client (purchase requisition expenditure reviewers) to check dimension information.  For another client, we used line item workflow and a customization that approved multiple lines at a time.  We had the same code in 2012 and also had to create the mobile app to do the same thing, so it made sense to go that direction.

    I have heard that in the future, the multiple line approvals will be incorporated into the product, but that is not a confirmed item or included in any release information - hopefully that is the case as this is a common request.


    ------------------------------
    Shirley Adams
    Solution Architect
    AKA Enterprise Solutions
    New York NY
    ------------------------------



  • 5.  RE: Purchase Requisition workflow

    Posted 9 days ago
    Thanks everyone, it's been a while but I wanted to follow up as this has been resolved. I changed the conditional statement to "purchase requisitions.approval amount" (thank you Kerstin) and it works exactly how we want it to now. It now considers the net amount of the entire requisition.

    Cheers! - Jeff


    ------------------------------
    Jeff Retzak
    Stella and Chewys
    Oak Creek WI
    ------------------------------



  • 6.  RE: Purchase Requisition workflow

    SILVER CONTRIBUTOR
    Posted 9 days ago
    Hi Jeff,

    Glad to hear you got it working as needed! Happy to help :)

    ------------------------------
    Kerstin Newman
    Business Analyst
    StarTech.com
    London ON
    ------------------------------



If you've found this thread useful, dive deeper into User Group community content by role