Dynamics AX
  RSS Feed  LinkedIn  Twitter
Want to turn you're data into a true asset? Ready to break free from the report factory?
Ready to gain true insights that are action focused for truly data informed decisions?
Want to do all of this across mutliple companies, instances of Dynamics and your other investments?
Hillstar Business Intelligence is the answer then! (www.HillstarBI.com)

Hillstar Business Intelligence for Microsoft Dynamics AX and NAV on Mobile, Desktop, Tablet


Let us prove to you how we can take the complexity out of the schema and truly enable users to answer the needed questions to run your business! Visit Hillstar Business Solutions at: www.HillstarBI.com

Thursday, September 06, 2012

A question around Organization Modeling for AX 2012





I hope that you have had a productive week thus far, filled with all things Microsoft Dynamics! As promised earlier this week, I wanted to post today about a specific question that came from my post on AX 2012 - Understanding & Extending the Organization Model.



The question posed by a reader of that post, is around the modeling of their organization for business units, and associating released products to specific Business Units.

Lets take this possed question a little further, and assume that the business unit association is desired to limit the use of released products.



Since released products, with AX 2012 out-of-the-box, are legal entity specific entities, that is the level of separation that comes as offered. Further out-of-the-box, with configuration, you can have business units used as financial dimensions. Meaning that we could then associate a released product, within a legal entity, to a business unit.



Having this association however, would not by itself limit the use of products, for users of AX, that work within specific business units. We have added something new here right? We can associate business units with released products, as financial dimensions. However the new element that we need to try and achieve is limiting the released products in a legal entity by business unit.

Now let us think about this. We could easily jump right into code driven design, that would allow for releasing products to business units, within legal entities. But why do that? The idea with Microsoft Dynamics AX 2012 is to model more and code less.

Our secret to success in this endeavor then, would be to think in terms of modeling. This includes having Organizational modeling that has an operating model, that gives us legal entities, with business units under them. Further having the financial dimensions modeled and configured so that business units are used as financial dimensions. Finally, we need to model security with the use of Extensible Data Security Framework (XDS).



Now with this, I must warn that there are very specific warnings when using XDS for modeling security. The idea is that it would only be used with Master Data elements, according to best practice. With that warning in mind, my next post on this topic will go into greater detail of how this can be achieved with modeling, and minimum code. Till Next Time!
Follow Me @:
RSS Feed  LinkedIn  Twitter

"Visit the Dynamics AX Community Page today!"

Labels: , , , , , , , , , , , , , ,

0 Comments:

Post a Comment

Links to this post:

Create a Link

<< Home


Copyright 2005-2011, J. Brandon George - All rights Reserved