Reasons (form) [AX 2012]

Updated: February 23, 2011

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 > Financial reasons.

–or–

Click General ledger > Setup > Ledger reasons.

–or–

Click Fixed assets > Setup > Asset reasons.

–or–

Click Accounts payable > Setup > Vendors > Vendor reasons.

–or–

Click Procurement and sourcing > Setup > Vendors > Vendor reasons.

–or–

Click Accounts receivable > Setup > Customers > Customer reasons.

–or–

Click Cash and bank management > Setup > Bank reasons.

Use this form to create and maintain financial reason codes. Reason codes help explain why some types of transactions were entered or why some field values were changed. For example, you can create reason codes to use with write-down adjustments or modifications to the Sales value field in Fixed assets.

You can use the Financial reasons form in Organization administration to create the same codes to use across various modules, or you can alternatively open a reasons form from a specific module to set up reason codes for only that module. In Organization administration, you can assign the reason code to any of the modules, but in the other modules, you can assign the reason code only to that module. For example, if you open the Vendor reasons form in Accounts payable, the account type is automatically set to Vendor, and the reason codes that you create can be used only with vendor transactions.

NoteNote

In most modules, you create reason codes to use only with transaction entry and reversals. However, in Fixed assets, you can also enter a reason for a change to the service life, depreciation periods, expected scrap value, and sales value for an asset. Use an account type of Asset to create reason codes that you can use both with fixed asset transactions and field changes.

Reasons can be used along with descriptions, and you can sort and analyze transaction history by reason code. Also, auditors can use reason codes to verify the purpose for transactions or field changes. Depending on how your organization uses reason codes, you might want to give users guidelines about when to use each reason code.

The following table provides descriptions for the controls in this form.

Field

Description

Reason code

Enter a unique identifier for the reason code. For example, you might use ADJ as a reason code for general adjustments.

Default comment

Enter a default comment for the reason code.

Users can change this comment when they enter reason codes. The comment that you enter here is displayed as the default comment when this reason code is selected.

Asset

Select this check box to use this reason code for fixed asset transactions.

Bank

Select this check box to use this reason code for cash and bank management transactions.

Customer

Select this check box to use this reason code for customer transactions.

Ledger

Select this check box to use this reason code for general ledger transactions.

Vendor

Select this check to use this reason code for vendor transactions.

Purpose code

Select this check box if the reason code is used as the purpose code for the letter of guarantee.

This field is available only when the Enable letter of guarantee field is selected in the General ledger parameters form and you open the form from Organization administration or Cash and bank management.

Cancellation reason

Select this check box if the reason code is used to cancel the letter of guarantee.

This field is available only when the Enable letter of guarantee field is selected in the General ledger parameters form and you open the form from Organization administration or Cash and bank management.


Announcements: To see known issues and recent fixes, use Issue search in Microsoft Dynamics Lifecycle Services (LCS).

Community Additions

Show: