What's new: Company and organization framework
Important
This content is archived and is not being updated. For the latest documentation, see Microsoft Dynamics 365 product documentation. For the latest release plans, see Dynamics 365 and Microsoft Power Platform release plans.
Applies To: Microsoft Dynamics AX 2012 R3, Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012
Microsoft Dynamics AX 2012 has a new organization framework that supersedes the simple company feature that earlier versions had. The framework lets you create organizations and structure the organizations into hierarchies. Therefore, you can better model the separate legal and operational entities of a global corporation, and the hierarchical relationships between those entities.
Overview
Item |
Description |
|---|---|
Required feature |
Yes |
Product areas affected |
All |
Stakeholders |
Business decision makers Technical decision makers Implementation team members Independent software vendors (ISVs)/developers Partners |
New functionality
The organization model functionality in AX 2012 lets you create more detailed hierarchy models that better reflect your business structure and processes. You can also more easily share data between organizations. This data includes reference information, master data, and transactions. Earlier versions of Microsoft Dynamics AX had limited capabilities for hierarchies and business modeling. Additionally, earlier versions did not share data between organizations, except in certain cross-company and virtual company scenarios.
What’s new in AX 2012
What can you do? |
Microsoft Dynamics AX 2009 |
AX 2012 |
Why is this important? |
|---|---|---|---|
Create organizations, such as legal entities and operating units. |
Each organization in the business was created as a “company,” regardless of the type or hierarchy of the organization. In tables, the dataAreaId field identified each company and therefore determined the security boundary for each company’s data. Some organizational concepts were independent of one other. For example, in the dimensions functionality, cost centers and departments were independent of each other. Likewise, in Human resource management, departments and organization units were independent of each other. Because these organizational concepts were independent of one other, they could not be maintained or managed in one location. |
Concepts such as the organization, legal entity, and operational unit have replaced by the simple concept of a company. You can create legal entities to represent the legal structure of your business, and you can create several types of operating units to represent how your business operates. All organization types are included in the organization model and can be used in hierarchies. |
Business models more accurately reflect your business. |
Create organization hierarchies. |
Hierarchical relationships between companies could not be represented. |
New organization types can be arranged into hierarchies to model the legal and economic dimensions of any real business. |
Business models more accurately reflect your business. |
Create multiple operating unit hierarchies. |
The feature was not supported. |
You can build specialized hierarchies to report on various perspectives of the business. You can also use hierarchies to aggregate data from related business units. |
Reporting can be more complex and accurate. |
Share parameters, policies, and transactions between organizations. |
Because companies provided the security boundary for data, it was difficult to share data across companies. For the same reason, parameters and reference data had to be set up for every company. To share data, you had to create virtual companies. |
Many tables are shared by all organizations. Therefore, users can access data in those tables, regardless of the company or organization context. |
It is easier to access and share data. Data and security can be managed independently. |
Perform tasks and view data in multiple organizations. |
Tasks could be performed only in the context of a company. Company information could be accessed only when users were logged on to that company. |
Users can view or modify data in different organization structures. The organization structures that users can access depend on the business process that the users are working in, not the company that they are logged on to. |
It is easier to access and share data. Data and security can be managed independently. |
Set up security based on the organization model. |
Companies provided the data security boundary. Data was secured based on the company that it was associated with. |
You can use the data security framework to help secure data based on any condition. You can associate a user in a particular role with any organization or with an organization hierarchy. If you associate the users in a particular role with a hierarchy, user permissions change as the hierarchy changes. For example, if organizations are added to the hierarchy, users who have been granted access to the hierarchy automatically gain access to the new organizations. |
Data and security can be managed independently. |
Use the organization structure to control economic resources and operational processes. |
The feature was not supported. |
For more information, see How to use organization hierarchy purposes. |
Business models more accurately reflect your business. |
Special considerations
Before you set up the organization structure, you should plan a hierarchy of organizations that meets your organizational and reporting requirements. For more information about how to plan organization structures, see Plan the organizational hierarchy.
The organization model supports data sharing that you previously might have implemented by using virtual companies. If you are currently using virtual companies, we recommend that you evaluate whether the organization model meets your requirements. Virtual companies are still required in some cases. For more information, see Upgrade company accounts and virtual company accounts.
Note
AX 2012 changes the way that hierarchies are created for all operational units. These operational units include departments. After upgrade, you must re-create the hierarchies for departments.
More information
For more information about organization modeling, see Organizations and organizational hierarchies.
Developers can extend the organization model by adding elements to some base enumerations and extending some classes. For more information about the developer experience, see Extending the Organization Model.