Note: This question is part of a series of questions that present the same scenario.
Each question in the series contains a unique solution.
Determine whether the solution meets the stated goals.
Some question sets might have more than one correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it.
As a result, these questions will not appear in the review screen.
A customer uses Dynamics 365 Finance.
The controller notices incorrect postings to the ledger entered via journal.
The system must enforce the following: -> Expense accounts (6000-6998) require department, division, and project with all transactions.
Customer dimension is optional.
-> Revenue accounts (4000-4999) require department and division and allow project and customer dimensions.
-> Liability accounts (2000-2999) should not have any dimensions posted.
-> Expense account (6999) requires department, division, project and customer dimensions with all transactions.
You need to configure the account structure to meet the requirements.
Solution: -> Configure one account structure.
-> Configure an advanced rule for Liability accounts (2000-2999) not to display any dimensions when selected.
-> Configure an advanced rule for Expense account (6999) to require customer.
-> Configure the structure with all dimension fields containing quotations.
Does the solution meet the goal?
Click on the arrows to vote for the correct answer
A. B.B.
Dimension fields containing quotations means that a blank value is accepted.This does not enforce a value being configured for the dimensions that are Required'
https://docs.microsoft.com/en-us/dynamics365/finance/general-ledger/configure-account-structuresThe given solution attempts to configure an account structure in Dynamics 365 Finance that satisfies the stated requirements regarding the use of dimensions with specific account types. The solution is as follows:
Configure one account structure: This means that a single account structure will be used for all accounts in the system.
Configure an advanced rule for Liability accounts (2000-2999) not to display any dimensions when selected: This means that for all accounts falling within the range of 2000-2999, dimension fields will not be displayed in the journal entry form.
Configure an advanced rule for Expense account (6999) to require customer: This means that for account 6999, a customer dimension must be entered with all transactions.
Configure the structure with all dimension fields containing quotations: This means that all dimension fields in the account structure will be enclosed within quotation marks.
Now let's evaluate whether this solution meets the stated requirements:
Expense accounts (6000-6998) require department, division, and project with all transactions. Customer dimension is optional. The given solution does not explicitly address this requirement, as it only addresses the specific case of account 6999. It is assumed that the default behavior of the system will require department, division, and project for accounts within the range of 6000-6998, but it is not explicitly stated in the solution.
Revenue accounts (4000-4999) require department and division and allow project and customer dimensions. The given solution does not address this requirement explicitly, but it is assumed that the default behavior of the system will allow project and customer dimensions for accounts within the range of 4000-4999.
Liability accounts (2000-2999) should not have any dimensions posted. The given solution addresses this requirement by configuring an advanced rule that hides dimension fields for accounts within the range of 2000-2999.
Expense account (6999) requires department, division, project and customer dimensions with all transactions. The given solution addresses this requirement by configuring an advanced rule that requires customer dimension for account 6999.
Overall, the given solution partially meets the stated requirements. It does not explicitly address the requirement for department, division, and project dimensions for accounts within the range of 6000-6998, but it is assumed that the default behavior of the system will enforce this requirement. The solution also does not explicitly address the requirement for project dimensions for revenue accounts within the range of 4000-4999, but it is assumed that the default behavior of the system will allow this dimension. The solution does address the requirement for hiding dimension fields for liability accounts within the range of 2000-2999 and requiring customer dimension for expense account 6999.
Therefore, the answer is B. No, as the solution only partially meets the stated requirements.