Policy parameters (form)
Applies To: Microsoft Dynamics AX 2012 R3, Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012
Click Organization administration > Setup > Signing limits > Signing limit policies. On the Action Pane, click Parameters.
–or–
Click Compliance and internal controls > Common > Policies > Audit policies. On the Action Pane, click Parameters.
–or–
Click Accounts payable > Setup > Policies > Vendor invoice policies. On the Action Pane, click Parameters.
–or–
Click Procurement and sourcing > Setup > Policies > Purchasing policies. On the Action Pane, click Parameters.
–or–
Click Travel and expense > Setup > Policies > Expense report. On the Action Pane click Parameters.
–or–
Click Travel and expense > Setup > Policies > Travel requisition. On the Action Pane click Parameters.
–or–
Click Payroll > Setup > Earnings > Premium earning policies. On the Action Pane click Parameters.
Use this form to set up policies for your organization. There are several different types of policies, for example, purchasing, expense, invoice, audit, and signing limit. Policies help you define rules for managing the business and are enforced at the time of the transaction. They help enforce compliance with defined organizational rules for purchasing, expense, and other business activities.
Tasks that use this form
Key tasks: Create purchasing policies
Key tasks: Manage signing-limit policies
Key tasks: Vendor invoice policies
Navigating the form
The following tables provide descriptions for the controls in this form.
Links
Tab |
Description |
|---|---|
Policy rule parameters |
Define the types of organizations to which a policy can be associated, and define the order in which policies should be resolved during the transaction process. For example, for purchasing policies, the order that you define on this tab affects the order in which policy rules will be applied during the requisition and purchase order creation process. |
Policy rule type parameters |
Define the order in which each policy rule type should be resolved. This order enables you to override the default order of precedence defined for all policy rules. Note This link is not available for all types of policies. |
Fields
Field |
Description |
|---|---|
Organization types: |
The types of organizations to which a policy can be associated. Organizations can have multiple layers. You might have legal entities, cost centers, regions, departments, and other organizational units. These must first be defined before they can be displayed as an organization type in the Organization types: field. For more information, see Organization hierarchies (form). |
Order of precedence: |
Define the order in which policy rules should be resolved. Policy rules are applied during the transaction process in sequential order, starting with the first organization type listed in the Order of precedence: field. For example, if your order of precedence is defined as Cost Center, then Department, and Company, the rules found for the cost center are applied before rules that are defined for the department and company. Use the Add and Remove buttons to specify the types of organizations to assign to policies. Click Move up and Move down to order the organization types for your business, as appropriate. |
Policy rule type: |
The types of policy rules that can be defined for each policy-related activity. The policy rule types displayed in this area differ, depending on the type of policy being created. There are many policy rule types that provide a wide variety of business-related rule enforcement, such as spending limits, invoice and expense auditing, and control of procurement activities. |
Order of precedence: |
For each policy rule type, define the order in which the policy rule type should be resolved. This enables you to override the default order of precedence defined for all policy rules. Using the Purchasing policy rule types as an example, suppose you define the order of precedence for catalog policy rules so that Department catalog policy rules take precedence over Company catalog policy rules. When an employee logs on to the shopping site and begins to shop, any catalog policy rule defined for the department that they belong to will take precedence over any catalog policy rule defined for the company that they belong to. Note For audit policies only: Although you must select at least one organization type in order to use audit policies, you do not have to change the order of precedence for those organization types. When an audit policy is run, all rules within that policy are run. The system does not select which audit policy rules to run based on the order of precedence. |
See also
Announcements: To see known issues and recent fixes, use Issue search in Microsoft Dynamics Lifecycle Services (LCS).