Announcements
No record found.
basically, we have two legal entities and both are different types of business. right now procurement category we assigned in the association role is showing in both companies.
is there any option to restricting the shared procurement category across legal entities?
Hi You can try this using purchase policy.
Procurement and sourcing > Setup > Purchase policy > Category access rule
docs.microsoft.com/.../set-up-policies-procurement-category-hierarchies
Hello Saurabh,
Thanks for your suggestion. I have tried this but unfortunately, I could not achieve my objective.
we have one procurement category in Company A and we have created another one for Company B. because both companies are having different types of business one is related to retail and another one is related to shipping service.
Right now my procurement category is if I select for Company A then the same is showing in Company B. I believe the procurement category is globally shared.
Hi Think we can do by defining two different policy for each company.
exploredynamics365.home.blog/.../
Follow all steps for both legal entity separately.
In above example , Step-1 select company A
Create another policy and select company B
Rest of the steps are same.
Hello Aslam Ali,
The categories are shared.
What I have seen people doing is that they build sub-nodes.
Example:
Hierarchy
- Company A
* Category 1
* Category 2
* etc
- Company B
Maybe that is a way for you to go forward?!
Best regards,
Ludwig
Hi Ludwig,
That was a fantastic idea but unfortunately when we implemented we name the category with company A name. that is the reason we got confused. now got the idea and need to try in UAT and test.
Thank you
Yes, Saurabh,
this one is also a good option. so I need to set up and test it.
now we need to check our complete scenario for the new legal entity then accordingly configure.
thanks for the support.
I have this same issue in a current multi-national rollout. Unfortunately the code design and implementation is poor - there was no compelling need to share this table and there should be an entity based constraint, but this is what we have.
Your primary control is in the stock posting profiles (which are not shared of course) - if you don't set up a posting profile for a given category in a given entity, the user will see a stop error when submitting to workflow or posting to the order. At least this will alert them to the issue.
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
Congratulations to our 2026 Super Stars!
We are thrilled to have these Champions in our Community!
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Giorgio Bonacorsi 622
André Arnaud de Cal... 553 Super User 2026 Season 1
CP04-islander 430
