MB-800 Sample Questions & Answers

The Inventory Posting Setup page is the correct location. This page allows you to define G/L accounts for combinations of a Location Code and an Inventory Posting Group. By creating a new line for the new Location and the relevant Inventory Posting Group, you can specify '52110' in the 'Purchase Account' field, which will override the default account from the General Posting Setup for transactions involving that specific location.

This statement is false. While assigning a license in Microsoft 365 makes the user eligible to access Business Central, it does not automatically create the user record inside the application or assign any permissions. An administrator must run the 'Update Users from Microsoft 365' process within Business Central to create the user and then must manually assign appropriate permission sets. No permissions are assigned by default.

The correct approach is to use Depreciation Books. You create a single Fixed Asset card for the vehicle. Then, you create and assign two Depreciation Books to it: one configured for Straight-Line depreciation (integrated with the G/L for financial reporting) and another configured for Declining-Balance depreciation (not integrated with the G/L, used for tax reporting). This allows for parallel depreciation calculations on the same asset.

Many posting batch jobs in Business Central, such as 'Batch Post Sales Invoices', have a specific parameter on their request page (accessible from the Job Queue Entry) that controls error handling. A parameter like 'Skip Companies with Posting Errors' or 'Post and Print if any error occurs' allows the batch process to log an error for a specific document and continue processing the rest of the documents in the batch, rather than failing completely on the first error.

With the FIFO (First-In, First-Out) method, the first units purchased are the first ones sold. The sale of 15 units will be costed as follows: the first 10 units from the June 1st receipt at $10 each (10 * $10 = $100), and the next 5 units from the June 15th receipt at $12 each (5 * $12 = $60). The total COGS is $100 + $60 = $160.

The Approval User Setup page is where you define the relationships between users, such as who a user's approver is, and set their approval limits for sales and purchase documents.

Workflow User Groups allow you to create a sequence of approvers. For the $10,000+ scenario, you would create a group containing the manager and then the director in the correct sequence.

A Workflow Template for Purchase Document Approval must be used and configured. Within this workflow, you will add event conditions based on the amount and set the responses to use the approver types like 'Approver Chain' which leverages the Approval User Setup and Workflow User Groups.

Analysis by Dimensions is the specific tool designed for this purpose. You can create Analysis Views that use up to four dimensions. Then, on the Analysis by Dimensions page, you can specify which dimension values appear on rows (Product Line) and which appear on columns (Region), with G/L balance or budget figures in the matrix cells.

The 'Edit in Excel' feature is designed for this exact scenario. From the Customer list page, the user can open the list in Excel using the Microsoft Dynamics Office Add-in. This will display the current data. The user can then modify the 'Credit Limit (LCY)' column for all customers as needed and use the 'Publish' button within the Excel add-in to write the changes back to Business Central, triggering all business logic and validations.

The best practice for security is the principle of least privilege. You should start with a minimal set of permissions and add only what is necessary. The most effective method is to find a standard permission set that is close to the requirement (e.g., one that allows journal editing), copy it, and then add the specific permissions required to post within the payment journal context (such as Execute permission on specific codeunits). Assigning broad access and then trying to restrict it is less secure and more difficult to manage.

The 'End-Total' account type is used to create a total for a range of accounts. You would place a 'Begin-Total' account before the first operating expense account (60000) and an 'End-Total' account after the last one (69999). The 'Totaling' field on the 'End-Total' account card would then be set to '60000..69999' to automatically calculate and display the sum of that range.