Microsoft Dynamics 365 Business Central Functional Consultant (MB-800 Deutsch Version) - MB-800 Deutsch Exam Questions

Explanation:

Comprehensive Detailed Explanation
When configuring the Chart of Accounts in Dynamics 365 Business Central, each G/L account requires specific setups to ensure it works properly in financial reporting, reconciliation, and year-end closing.
* Inventory account reconciliation (Direct Posting):
* Inventory accounts should not allow direct postings.
* Their balance must come exclusively from item transactions (value entries).
* Setting Direct Posting = No ensures that the account balances always match the sum of all item value entries.
* Financial Statement reporting (Account Category and Account Subcategory):
* To group G/L accounts into correct sections of financial statements (e.g., Assets, Liabilities, Equity, Income, Expenses), you must assign them to Account Categories and Subcategories.
* These mappings drive the layout of Balance Sheet and Income Statement reports.
* Summarizing other accounts (Account Type):
* Use Account Type = Heading or Total to summarize balances of related accounts.
* Example: A Total account sums several Posting accounts.
* Year-end closing (Income/Balance):
* The Income/Balance field determines whether the account is treated as an Income Statement account (closed to Retained Earnings at year-end) or as a Balance Sheet account (carried forward).
Microsoft Learn References
* Design the Chart of Accounts
* Set Up G/L Accounts
* Year-End Closing and Income/Balance Setup

Explanation:

FIFO is a widely used costing method where the oldest inventory items are sold first. This is a common and straightforward method for valuing inventory.
Automatic cost adjustment is a crucial setting for resolving inventory reconciliation issues. When this is enabled, Business Central automatically adjusts the cost of goods sold (COGS) to match the actual cost of the inventory. This helps prevent discrepancies between the inventory sub-ledger and the general ledger, ensuring that the financial data is accurate.

Explanation:

The Microsoft Power Platform extends the capabilities of Dynamics 365 Business Central by adding automation, analytics, and low-code apps. Here's how the requirements align:
* Real-time financial reporting # Power BI
* Power BI integrates directly with Business Central using OData feeds and APIs.
* Provides dashboards and real-time reports for financial data (sales, budgets, cash flow, etc.).
* Automated customer onboarding # Power Apps
* Power Apps can create custom apps and forms for entering customer data, which integrate back into Business Central.
* Example: A sales rep uses a mobile app to collect customer details # syncs automatically into BC.
* Automated invoice approval workflow # Power Automate
* Power Automate connects BC with approval workflows (e.g., invoice > $10,000 must go to Finance Manager for approval).
* Automates notifications and approval tasks.
* Integrated item scanning capabilities # Power Apps
* Power Apps allows building mobile apps with barcode/QR scanning capabilities.
* Warehouse staff can use phones or tablets to scan items, which update BC inventory in real time.
Other tool (OneDrive): Not relevant in this scenario-it's for file storage, not automation, reporting, or scanning.
Microsoft Learn References
* Integrating Business Central with Power BI
* Power Automate and Business Central
* Power Apps Integration with Business Central

Explanation:

Comprehensive Detailed Explanation
The Over-Receipt functionality in Dynamics 365 Business Central allows a company to accept deliveries that exceed the ordered quantity but within controlled tolerances.
* Over-receipt code setting # Item Card
* On the Item Card, you assign an Over-Receipt Code that determines if and how much extra quantity can be received.
* This links each item to the correct tolerance and approval rules.
* Over-Receipt Tolerance % # Over-Receipt Codes
* The actual tolerance percentage (for example, 10% above the ordered quantity) is defined on the Over-Receipt Codes page.
* Each code defines different rules (e.g., 5%, 10%, unlimited).
* Approval required for over-receipt purchase quantity # Over-Receipt Codes
* On the same Over-Receipt Codes page, you can specify whether approval is required when receiving quantities above the tolerance.
* If enabled, the over-receipt cannot be posted until approved.
Thus, the Item Card determines which over-receipt code applies to the item, while the Over-Receipt Codes page defines tolerance percentages and approval requirements.
Microsoft Learn References
* Set up Over-Receipt Codes
* Over-Receipt Tolerances and Approvals
* Work with Items

Explanation:

Explanation:

In Dynamics 365 Business Central, when creating a purchase return order to return goods to a vendor and apply them against the original purchase, the correct process is:
Step 1. Set Document Type filter to Posted Invoices and select the correct line Since the invoice for the original purchase has already been posted, you need to work from Posted Purchase Invoices as the base document for reversal.
Step 2. Run the Get Posted Doc... to Reverse function
This action pulls in the posted purchase invoice information into the purchase return order, ensuring the return applies directly to the correct vendor invoice.
Step 3. Enable the Show Reversible Lines Only option
This ensures that only lines eligible for reversal (not yet fully returned/invoiced) are displayed, preventing errors.
Step 4. Set the purchase return order's item line Quantity to 50 pieces Since only 50 out of 100 pieces are being returned, the line quantity must be updated to reflect the actual return authorization from the vendor.
Step 5. Post the purchase return order
Finally, post the return order. This updates inventory by reducing stock by 50 pieces and creates the correct vendor credit application in accounts payable.
Why not the other options?
Copy Document function # Used for creating new documents based on existing ones (e.g., copying a purchase order to a new invoice), not the correct method for linking a return to a posted purchase invoice.
Enable the Return Original Quantity option # Would return all 100 pieces instead of 50, so not suitable in this case.

Explanation: Only visible for Pass4Test members. You can sign-up / login (it's free).

Explanation:

Explanation:

Comprehensive Detailed Explanation
* Set up a new fiscal year
* In Business Central, fiscal years are created in the Accounting Periods page.
* To start a new fiscal year, you must Select Create Year, which generates the periods for the new fiscal year.
* Other options like Close Year or Fiscal Year Balance are for closing or balancing, not for initial setup. Correct: Select Create Year
* Define the fiscal year start date
* The case study specifies that the company's fiscal year starts on June 1.
* Therefore, when creating the new fiscal year, you must ensure the first period begins on June 1.
* The correct action is Check New Fiscal Year for June 1. Correct: Check New Fiscal Year for June 1
* Restrict posting
* The business requirement is:
* Restrict users to post only in the current month.
* Only certain accounting users may have broader posting permissions.
* In General Ledger Setup, the Allow Posting From and Allow Posting To fields control the global posting date range.
* For user-specific restrictions or exceptions, User Setup allows overriding posting ranges for individual users.
* Since the requirement is to restrict all users generally, the best action is: In General Ledger Setup, set the Allow Posting From and Allow Posting To options to current dates. Correct: In General Ledger Setup, set the Allow Posting From and Allow Posting To options to current dates Microsoft Learn References
* Accounting Periods (Create and Close Fiscal Years)
* General Ledger Setup - Allow Posting From/To
* User Setup and Posting Date Permissions

Explanation:

The company requires multiple number series for Raw Materials, WIP, and Finished Goods, with unique prefixes, selectable at item creation, and automatic assignment. In Dynamics 365 Business Central, number series are configured in a structured order:
* Create a number series.
* Define unique number series for each item type (e.g., RM-#### for Raw Materials, WIP-####, FG-####).
* Specify starting/ending numbers and format.
* Create relationships between the number series.
* Relationships allow the user to select among multiple number series when creating an item.
* This ensures that at item creation, the correct prefix (series) can be chosen.
* Enable the ability to use default numbers.
* On the number series setup, set Default Nos. = Yes to enable automatic numbering when a new item is created.
* Set the default number series on the Inventory Setup page.
* Finally, assign the relevant number series as the default for items in Inventory Setup.
* This ensures automatic numbering, but still allows selection of other related series when needed.
This sequence satisfies all requirements:
* Unique series per item type # Done in step 1.
* Selectable at creation # Handled in step 2.
* Automatic number assignment # Steps 3 and 4 ensure automation with flexibility.
Microsoft Learn References
* Create Number Series
* Use Number Series in Business Central
* Inventory Setup