D365 Finance & Operations and Dynamics AX Forum

Expand all | Collapse all

Workflow with Managerial Hierarchy always goes to next level approver

  • 1.  Workflow with Managerial Hierarchy always goes to next level approver

    Posted Sep 09, 2019 12:55 PM
    We are trying to finish up testing our workflows here at Tillamook and we have not been able to figure out an issue with the functionality we have setup.  Even if my signing limit is $125,000, when I create a PO for $25, it still goes to my next level manager for approval.  Nothing is jumping out at us with the setup.  Wondering if anyone in the community here has run into this.

    ------------------------------
    Travis Pierce
    Director IT
    Tillamook County Creamery Association
    Tillamook OR
    ------------------------------
    Conference-AXUG_200x200


  • 2.  RE: Workflow with Managerial Hierarchy always goes to next level approver

    SILVER CONTRIBUTOR
    Posted Sep 10, 2019 11:34 AM
    Hi Travis,

    We only use this for purchase requisitions, so I am not 100% sure about the availability of fields for POs.

    For Purchase Requisitions, we use the managerial hierarchy for approvals, and the stop condition is
    Where Employee.Spending limit.Purchase requisition >= field Purchase requisitions.approval amount excl tax
    The hierarchy options are set to assign to all users retrieved.
    We then have a signing limit policy in place that assigns certain @ limits to job titles, those are set up on the employee records.

    I hope this helps.
    Kerstin



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

    Conference-AXUG_200x200


  • 3.  RE: Workflow with Managerial Hierarchy always goes to next level approver

    Posted Sep 10, 2019 12:57 PM
    Travis,

    One thing that has tripped us up is if the user / worker are not tied together. You may need to verify that the user has a relationship with the employee. Also, you may need to also verify that the user and worker are set up in the company that the requisition is tied to. In 2012 R3 that is going to workers -> employment history and verifying that the correct company shows up.

    Just two thoughts that might help.

    ------------------------------
    Robert Shannon
    ERP Analyst
    Leatherman Tool Group
    Portland OR
    ------------------------------

    Conference-AXUG_200x200


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