Issue with PO line matching policy with some users

(0) Share

Report

Posted on by Community Member

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.

*This post is locked for comments

I have the same question (0)

All responses (18)

Answers (0)

Ludwig Reinhard Microsoft Employee on at

Like (1)

Report

Hi,

Have you made modifications to the standard roles?

Best regards,

Ludwig

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

We have only made an addition to the purchasing agent role, which is allowing users to "generate purchase receiving log report." All the other permissions and contents of the role match the standard permissions listed here; technet.microsoft.com/.../hh527091.aspx

Was this reply helpful? Yes No
Suggested answer

fatihgork 3,817 on at

Like (0)

Report

If they are using the same items, same vendors and getting different results, that sounds like a cache issue.

You can pick one of the problematic users and try to reset usage data, delete AUC files.

Also if your last CIL was succesful, please check if this user have "Execute business operations in CIL" ticked in user settings.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Is "execute business operations in CIL" a setting in AX 2012? I don't see it anywhere.

I reset the usage data for everything pertaining to purchasing. I will have to monitor to see how the POs are processing.

I was able to catch someone in the middle of creating a PO. It looks like when the PO is first created, it generates as a 3-way but when the users go to add lines to the POs that's when it switches over to 2-way. It's very strange. Any suggestions if the usage data doesn't resolve this?

I dug just a little further into it and it appears as though POs created with an item number are generating correctly, but those created with a procurement category are not. Again, I'm stumped as to why it would be doing this, as company policy is set to 3-way matching. I cannot change the setting "allow matching policy override" in the AP parameters under invoice validation, because we do sometimes use 2-way matching. Changing this setting will not allow any POs to be generated at 2-way match level.

Was this reply helpful? Yes No
Suggested answer

fatihgork 3,817 on at

Like (0)

Report

Hi EMasterson,

Please check your procurement policies. If you go to Procurement and sourcing/Setup/Policies/Purchasing policies and create a policy you will see a rule named as "Category policy rule". This is the place to define matching policies per category and when categories are used. You can find more details about it here:

Set up policies for category hierarchies [AX 2012]

Please look for "Category matching policy" in the page.

By the way yes "execute business operations in CIL" is a setting in AX 2012. It is in the form you access by File->Tools->Options. It is located under "Development" tab there.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

I have checked this. All categories are set to "company policy"

And our company policy is set to three-way

But I am still seeing POs using procurement category default to two-way as of this morning when they are created by users with the "purchasing agent" role.

"Execute business operations in CIL" is checked for the user I have been monitoring.

Was this reply helpful? Yes No
Suggested answer

fatihgork 3,817 on at

Like (1)

Report

That doesn't make any sense to me. I would expect it to work as you did.

Can you try to change them to 3 way matching? It will work then. You might use that as a work around.

To solve the issue, can you check if you have another policy? Might another setup be writing this one off? If you have more than one policy, can you hit "Parameters" button and check the sequence in there?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

This policy is the only one. There are no other purchasing policies created.

If I change the policy for a category to three-way, is that going to disable the ability to change the line to 2-way if needed? We do sometimes use 2-way matching but not nearly as frequently as 3-way. I believe it was originally set up as 2-way and 3-way etc when this was first reported, which was around 4 years ago or so (before I was here). Changing it to company policy seems to have not affected anything.

Does this policy override vendor matching policy? Again, sometimes the POs do need to be 2-way rather than 3-way, under some vendors and some categories. I cannot disable the ability to change anything to 2-way.

Was this reply helpful? Yes No
fatihgork 3,817 on at

Like (0)

Report

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.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

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?

Was this reply helpful? Yes No