Export (0) Print
Expand All

How to use organization hierarchy purposes [AX 2012]

Updated: May 9, 2013

Applies To: Microsoft Dynamics AX 2012 R3

When you create an organization hierarchy in Microsoft Dynamics AX, you must assign a purpose to the hierarchy. The purpose that you assign to a hierarchy determines the types of organizations that can be included in the hierarchy. The purpose also defines the application scenarios that the hierarchy can be used in.

A hierarchy that is created for a purpose may not reflect the actual legal structure of the business. For example, the approval process for requisitions may involve multiple legal entities and positions that don’t report to each other. For instance, the CFO might be required to approve a requisition of a certain amount, even though the organization that submits the requisition does not report to the CFO.

Hierarchies can be used for the following purposes.

Organizations that include multiple legal entities can create and manage payments by using a single legal entity that handles all payments (known as centralized payments). When you centralize payments, the same transaction does not have to be entered in multiple legal entities, and the following processes for cross-company payments are simpler: payment proposals, settlements, modification of open transactions, and modification of closed transactions.

To use a hierarchy in this scenario, you must assign the Centralized payments purpose to the hierarchy. For more information, see:

A policy is a collection of rules that controls a process for an organization. Policies enable internal management of organizations and help improve cost control, fraud detection, operating efficiency, and performance. To use a hierarchy to set up policies, you must assign an appropriate purpose to the hierarchy. For more information about how to set up policies, see Set up policy parameters.

The following table lists the processes that you can control by using policies. It also includes the hierarchy purpose that corresponds to each process.

Process

Description

Hierarchy purpose

More information

Purchasing

Controls the requisition process for a group of requisitioners. Purchasing policies help create a policy structure that is aligned with the organization's needs for strategic purchasing.

Procurement internal control

About purchasing policies

Key tasks: Create purchasing policies

Vendor invoicing

Enables you to evaluate vendor invoices for compliance with policy rules that you create.

Vendor payment internal control

Key tasks: Vendor invoice policies

Auditing

Helps you implement the compliance strategy for your organization.

Audit internal control

Key tasks: Audit policies

Expenses

Controls the process for expense reports.

Expenditure internal control

About travel and expense policies

Create policies

Signing limits

Controls the level of financial commitment that a worker is authorized to make on behalf of his or her employer. As a result of the worker's approval activity, the employer may enter into a contractual relationship with a third party, such as a purchase order with a vendor.

Signature authority internal control

About signing limit setup

Key tasks: Manage signing-limit policies

Benefits eligibility

Define and exercise eligibility rules for each benefit your organization offers to workers. You can use these rules to identify the specific benefits that a given worker is eligible for.

Benefit eligibility control

NoteNote

This control is available only if Microsoft Dynamics AX 2012 R2 or AX 2012 R3 is installed.

Key tasks: Benefit eligibility policies

An organization chart defines the relationships between departments, jobs, and positions. To use a hierarchy in this scenario, you must assign the Organization chart purpose to it. For more information, see Key tasks: New worker positions.

A user's access to data in Microsoft Dynamics AX can be granted based on the user's relationship to an organization. To use a hierarchy in this scenario, you must assign the Security purpose to it. You must also create data security policies to help secure the organizations in the hierarchy. Then, when you associate a user who is in a particular role with a hierarchy, the user's access to data changes automatically when the hierarchy changes. For more information, see Overview of Security Policies for Table Records and Organizations for the automatic role assignment rule (form) or Organizations for the user (form).

The following table describes the Retail scenarios where organization hierarchies can be used.

Task

Description

Hierarchy purpose

More information

Manage retail assortments

Identify the products that are available in each retail channel, such as a brick and mortar store or an online store.

Retail assortment

NoteNote

This control is available only if Microsoft Dynamics AX 2012 R2 or AX 2012 R3 is installed.

About setting up assortments

Manage retail replenishment

Group stores to replenish inventory based on replenishment rules.

Retail replenishment

NoteNote

This control is available only if Microsoft Dynamics AX 2012 R2 or AX 2012 R3 is installed.

Set up replenishment hierarchies

Set up replenishment rules

Report data for stores

Group stores for reporting.

Retail reporting

NoteNote

This control is available only if Microsoft Dynamics AX 2012 R2 or AX 2012 R3 is installed.

About retail stores

Post inventory, calculate statements, or post statements for a group of stores

Create a group of stores that can be assigned to a batch job. When you define a batch job to post inventory, calculate statements, or post statements, you can specify which hierarchy the job applies to. When stores are added to or removed from the hierarchy, you don’t have to modify the batch job.

Retail POS posting

NoteNote

This control is available only if Microsoft Dynamics AX 2012 R2 or AX 2012 R3 is installed.

About working with store inventory

Create and post a statement

Set up budget planning processes to meet your organization’s policies, procedures, and requirements for budget preparation. You can use budget planning to perform the following tasks:

  • Associate budget planning processes with budget cycles, ledgers, and organization hierarchies.

  • Consolidate multiple budget plans from a lower level of the organization into a single parent budget plan at a higher level in the organization. You can also develop a single budget plan at a higher level of the organization and allocate the budget to lower levels of the organization.

To use a hierarchy in this scenario, you must assign the Budget planning purpose to the hierarchy.

NoteNote

This control is available only if Microsoft Dynamics AX 2012 R2 or AX 2012 R3 is installed.

For more information, see Budget planning overview and Key tasks: Configure budget planning and set up budget planning processes.

The All projects list page displays a list of pending project transactions and posted project transactions. You can view these transactions by organization, if you have set up a hierarchy for project management.

To use a hierarchy in this scenario, you must assign the Project management purpose to the hierarchy.

NoteNote

This control is available only if Microsoft Dynamics AX 2012 R2 or AX 2012 R3 is installed.

For more information, see View project transactions.


Announcements: To see known issues and recent fixes, use Issue search in Microsoft Dynamics Lifecycle Services (LCS).
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft