You’re offline. This is a read only version of the page.
Announcements
We have a curious issue where when some users are creating POs, the matching policy is defaulting to 2-way even though company policy is 3-way matching. I have checked the vendor, and it is set to company policy. This only seems to happen with users that have the "purchasing agent" role. Users with the "purchasing manager" role do not have this issue. Any ideas? It's creating issues in our purchasing department because they are manually having to change the matching policy back to 3-way after the PO has been created.
We are using AX 2012.
Hi EMasterson,
There are classes out-of-box which clear security, user, AOS caches etc. But experts who are more technical are the ones to call it.
Sorry I couldn't help any further. It can't see anything wrong with the configuration.
I was just able to verify this (this reply may show up on the second page of comments.) I had a user entering POs that were defaulting correctly. When I reviewed her roles, she had the "purchasing manager" role. When I removed it and replaced it with "purchasing agent" her POs began defaulting to 2-way.
According to our purchasing group, that is correct. I'm unable to replicate in test.
Item number POs appear to generate as 3-way POs. If a PO is created, it starts off as 3-way but when procurement category is selected (regardless of matching policy for the vendor or category) it changes to 2-way. So at this point I'm more inclined to believe it's an issue with the role rather than the procurement category. Of course this could be wrong - I just don't have another explanation at this point considering the policy for the category, company policy, and vendor policy are all set to 3-way. I have watched the users enter POs and they are not changing the line policy themselves.
I checked on LCS about a bug pertaining to POs and was unable to find anything.
As for your question, that's correct. The vendor is set to 3-way, and the procurement category is set to 3-way, but it is still defaulting to 2-way. For some reason, users with the "purchasing agent" role are getting this error but "purchasing manager" are defaulting to 3-way as expected. Obviously, I can't give everyone who enters POs the manager role. What's even more strange is the fact that we cannot replicate this in test.
Thanks for your help.
Hi Emasterson,
I understand, I did exactly your setup in demo company. When I set my category policy to company policy and set company policy to 3-way match, it worked.
If you do not have any customization, you can check issue search on LCS to see if your version had such a bug. If so, there will be a hotfix for it as well.I can't think of anything other than what we tried so far.
Did you change your category policy to 3-way match, and is it still setting 2-way when you select this category?
The vendor's policy is company policy, which (also shown in my screenshot above) is three-way. This entire thing is very confusing. I know that we allow two-way matching but they should be defaulting to three-way based on our settings and it simply isn't doing this. Is there anything else I can try?
Hi,
yes you can change it back to 2-way matching on purchase order line if you need since your parameter allows users to change to a lower policy than company policy as well.
Can you check this vendor's default matching policy as well?
It is in invoice tab on vendors form.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
290,142
Super User 2024 Season 2
#2
Martin Dráb
227,979
Super User 2024 Season 2
#3
nmaenpaa
101,148
Share
Report
All responses (
Answers (