Unified Operations & Dynamics AX Forum

Purchase Requisition Workflow and Singing Limits

  • 1.  Purchase Requisition Workflow and Singing Limits

    Posted 23 days ago
    Hi,
    we are currently on D365 v 7.2 and are in the process of setting up Procurement. Background: All P-Req's will be raised against a project. Every project will have a Project Manager, Project Controller and a Sales Manager defined on the Project master (tab "General"). Every worker (i.e. Project Manager/Controller, Sales Manager) will have a maximum singing limit assigned (worker position is linked to a certain compensation group).
    The P-Req workflow needs to work by routing P-Req's to (in this order) the Project Manager, Project Controller and Sales Manager for approval. The approval workflow needs to stop as soon as one of the 3 approvers with a sufficient singing limit approves the P-Req.
    Does anyone have experience with a similar requirement? Because based on our test results I don't think standard D365 can be configured this way. In order to utilize singing limits, the workflow assignment method would have to be "Hierarchy". However, the requirement to route the P-Req to the Project Manager/Controller and Sales Manager would require a workflow assignment method "Expenditure Participant". The problem with "Expenditure Participant" is that it doesn't seem to respect the signing limits. In addition, approval related fields such as "Expenditure Reviewer's approval limit" are not available to define conditions in the workflow configuration for method "Expenditure Participant".
    We also looked a Purchase Order workflow and P-Req line specific workflow configurations but they appear to have the same limitation.
    Does anyone have experience with a similar requirement?
    Many thanks,
    Helmut


    ------------------------------
    Helmut Pechtold
    Functional Analyst
    Vancouver
    ------------------------------