In general business scenario, it is a common requirement to restrict the employees of different departments to be able to raise the purchase requisitions for different set of items. AX2012 provides this functionality out of the box, which is possible by setting up the organization hierarchy and procurement policies in proper way.
In my previous post, a new procurement hierarchy has been created with two categories “Desktops” and “Laptops”. I am considering that hierarchy and going on.
Scenario: An organization operates its business as Head office and regional office and it has Administration departments set in both the offices. The organization wants its Head office – Administration department employees to be restricted to raise the requisition for only the “Laptops category” whereas the regional office –administration department should be restricted to “Desktop computers” Category.
In the above case, let us create “Head office” and “Regional office” as Business units for the organization and “HO-Admin”, “RO-Admin” as the departments.
Create the Organization hierarchy “Demo Hierarchy” which looks like below and publish the hierarchy by clicking “publish and close” button as highlighted.(I am not explaining the creation of organization hierarchies as it is been discussed in some other blogs. You can refer to Sandeep chaudhary’s blog http://sandeepchaudhury.wordpress.com/2012/09/03/organization-modeling-made-easy-in-microsoft-dynamics-ax-2012/)
Important note: After creating the Hierarchy, assign the purpose “Procurement Internal control” to have the hierarchy reflected in the procurement policies.
Procurement policies setup:
To create new policy go to Procurement and sourcing>Setup> Policies> Purchasing policies> click new
Give the name as “HO-Admin policy” and click the parameters button and add the “Demo Hierarchy” to the order of precedence. By adding the hierarchy, we can set up the policies for any element(either business unit or department) in the hierarchy.
Expand the fast tab>Policy organizations> Select organization hierarchy as “Demo hierarchy” (refresh the form if you don’t see the created hierarchy) and add the legal entity node, business entity and department nodes to “Selected organization nodes”.
Let us define “Category access policy rule” under “policy rules” fast tab. Click “Create policy rule” to define the rule. Focus on the “Laptop Category” and click “Select” button to move them to the Selected Categories.
Now, for “HO-Admin” department, only the laptop category is applicable. If any user from this department create a purchaser requisition then, only the items under category “Laptops” can be seen and user can request only those items.
Let us check the end result by setting these dimensions to the employee.
Go to System administration>select your user id(the one which you are currently logged in with) click the button to see the employee you are linked to. (copy the same)
Goto HR> Employees form > filter the employee with the copied employee name>Edit
Click the Employment tab and specify the Business unit – HO, department – HO-Admin under Financial dimensions fast tabs.
Go to Procurement and sourcing and open “All purchase requisitions” form to create a new purchase requisition. When a new PR is created, the current user’s linked employee will be considered as preparer. So, system will allow the items that are available in “Laptop category”.
You can see only the “Laptop category” available for the selection and “Desktop Category” will not be shown. Using organization hierarchy in a proper way we can set the purchasing policies as required by the organization.
I know this looks like a lengthy post, but couldn’t make it shorter than this :).
Hope somebody will await for my next post ;).