Hi, I have a client that requires two people to approve the PO. I have set the Approver to “Employees by Filter” in the used Rule Action however once the first user Approves the PO is approving without the second approval.The settings i have used are below. What am i missing? Any help appreciated. Laura
I am trying to create an approval map where if an employee belongs to a Purchase Approval Group then the PO is automatically approved by the Owner of the PO document. I thought the way this worked was fairly simple; but apparently Acumatica does NOT work this way. So I am looking for help to understand how to make this work. Below is the logic in the Rule for the Condition I have set.Step Conditions: If No Approver Found: Reject Document Execute Step: If No Approvers Found at Previous StepsRule Condition: EMPLOYEE Workgroup Equals Purchasing Approval GroupRule Actions: Approver: EMPLOYEE FROM DOCUMENT Employee: ((Document.EmployeeID.Selected)) On Approval : Complete StepAgain, what I WANT to happen is to reject all PO's that reach this step, except for the ones created by an employee in the workgroup Purchase Approval Group.But this does not appear to be the way that Acumatica works.What am I missing?Thank you in advance
Where is the best place to learn about setting up the AP Approval process/Workflow? I have looked in University catalog and nothing seems to really fit. Thanks!
When an approval map condition is set to "AP Transactions > PO Number > Is Not Empty", the approval map engine is unable to assign the approval. Have I done something wrong in the approval map? This started after we upgraded to revision "20.217.0022". Could this be related to the known issue on approvers? Step 1 is never assigned: Step 2 is reached instead: Thank you for your help!
Hello,We are new install and working through our implementation. Have come across an issue that I’m hoping folks on this forum may be able to help with.As soon as we setup Segmented Key for our Project ID, and had 3 of the 4 segments turned on for validation (ie… only certain values can be used in that segment); now our ‘Non-Project’ code we setup in preferences no longer works?Is this a product defect/bug?As soon as I turn the validation off in the segmented keys, the non-project functionality works again. I realize that I can make a ‘dummy’ project that follows the segmented values setup, but that kind of defeats the purpose of this functionality to begin with.Anyone else run into this issue? Perhaps there is a hot fix to address this? Thanks, Lars
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.