MB-800 Exam Dumps - Microsoft Dynamics 365 Business Central Functional Consultant

Create a Customer Discount Group

Create an Item Discount Group

Select the Item Discount Group for the Item

Comprehensive Detailed Explanation

To configure sales discounting in Dynamics 365 Business Central, you need to set up the relationship between customers and items so that the system can automatically apply the correct discounts during sales transactions. The process involves both customer grouping and item grouping.

1. Create a Customer Discount Group

This step defines which customers are eligible for group-based discounts (e.g., a retail chain, buying group, or brokers).

By creating a Customer Discount Group, you can later apply uniform discount rules across all customers belonging to that group, instead of configuring each customer individually.

2. Create an Item Discount Group

Next, you create Item Discount Groups to categorize items into discountable product lines (e.g., Olive Oils, Spices, Snacks).

This ensures that discount rules apply consistently across items in the same category, rather than having to define rules item by item.

3. Select the Item Discount Group for the Item

Finally, you link each relevant Item Card to the correct Item Discount Group.

This connection ensures that whenever a sales order/invoice is created for a customer belonging to a discount group and includes items in an item discount group, the system automatically applies the correct Sales Line Discounts.

Why not the other actions?

Define the Sales Invoice Discounts → Used for invoice-level discounts, but here the requirement is item/line-based discounting.

Define the Customer Special Sales Prices & Discounts → Used for customer-specific or promotional pricing, not for group-wide discount structures.

Configure Discount Posting in Sales & Receivable Setup → Relevant for accounting/reporting (whether discounts post separately) but not for setting up how discounts are determined and applied.

Define the Sales Line Discounts → This is the outcome of linking customer discount groups and item discount groups, but it requires the setup steps above first.

Microsoft References

Set Up Customer and Item Discount Groups

Work with Sales Line Discounts

Special Prices and Discounts in Business Central

This sequence makes sense because you first create the series itself, then define the lines (the actual numbers within the series), and finally define the relationships to link the series to the specific data table (like the Accounts table) where it will be used.

Sequence 2: Using a Configuration Package to Manage Data

This sequence focuses on using a configuration package to manage and update data, which might include fixing issues with existing accounts or importing new ones.

Create a configuration package.

Configure the Vendor Table on the configuration package.

Create the Data template.

While this sequence is plausible, it has a significant flaw: the prompt mentions "Accounts," but this sequence specifically mentions the Vendor Table. If we assume the "Vendor Table" is a placeholder for a generic data table like the Accounts table, the sequence makes sense. You create a package, configure it for a specific table, and then create a data template to import the data into that table.

Sequence 3: Resolving Issues by Defining the Number Series on the Configuration Template

This sequence focuses on resolving issues by directly modifying the configuration template within a configuration package.

Create a configuration package.

Create the Data template.

Define the No. Series on the configuration template.

This sequence is logical for a scenario where you're using a configuration package to manage both data and its associated number series. You first create the package, then create the data template (which is a core component of the package), and finally define the number series on that template to ensure the imported data uses the correct number sequencing.

Comprehensive Detailed Explanation

The requirement is to ensure that every transaction posted to a customer account includes the Customer Source dimension (e.g., Cash & Carry, Brokered). This is achieved by creating and enforcing a mandatory dimension rule in Business Central.

Step 1: Create a dimension code to identify the customer source

First, define a Dimension Code such as Customer Source.

This will hold values like Cash & Carry and Brokered.

Dimensions are the foundation for all reporting segmentation in Business Central.

Step 2: Create dimension values for the customer source dimension code

After creating the dimension, define the specific Dimension Values (e.g., Cash & Carry, Brokered).

These represent the business lines the company wants to track.

Step 3: Add the Customer table

To enforce the dimension on customers, link the dimension to the Customer table.

This ensures that every transaction involving a customer account requires this dimension.

Step 4: Set the Value Posting to Code Mandatory

On the Default Dimensions page, set Value Posting = Code Mandatory for the Customer Source dimension.

This forces users (or the system) to provide a dimension value on every transaction involving customers.

Without this, users might skip dimension assignment, leading to incomplete reporting.

Step 5: Select the Dimension Value Code that is used for the customer source

Finally, assign the correct Dimension Value (Cash & Carry or Brokered) to each customer record.

This ensures automatic defaulting during transaction entry, reducing user errors and maintaining consistency.

Why not the other actions?

Chart of Accounts: Not needed here, since the requirement applies to customers, not G/L accounts.

Account Type Default Dimension: Useful for G/L accounts, but here we are applying it at the Customer table level.

Search icon, Customers: While this helps you navigate, it’s not a required setup step in the sequence.

Microsoft References

Work with Dimensions in Business Central

Set Up Default Dimensions for Customers

Dimension Value Posting Options

The requirement is to import vendor opening balances from Excel, where many vendors use foreign currencies. Since balances must be entered via General Journal Lines (table 81), the correct process with configuration packages is:

Create configuration package for table 81 Gen. Journal Line

This table holds general journal transactions and is required to import opening balances.

Select the fields with correct processing order including Currency Code

Since vendors use foreign currencies, the Currency Code field must be included along with Account Type, Account No., Posting Date, Document No., Description, Amount, and Amount (LCY).

Export to Excel and populate the data

Export the template from the configuration package, then copy/paste the vendor balances into Excel.

Import and validate the Excel file, then apply package

Load the populated Excel back into the configuration package, validate the data, and then apply it to the general journal for posting.

Incorrect alternatives:

Options that omit Currency Code would not support foreign currency vendors.

"Import from Excel and then post to the general journal" skips the validation step and configuration package flow.

Microsoft Learn References

Use Configuration Packages to Import Data

General Journal Lines (Table 81)

In Business Central, when you want to import master data (like customers, vendors, items, etc.) using configuration packages, you follow a structured sequence:

Create a configuration package – First, you define the configuration package and select the related tables to be imported.

Export an Excel template and populate the data – Once the package is created, you export the template to Excel. This gives you the correct structure (fields, columns) that match Business Central. Then you (or the customer) fill in the Excel file with the master data.

Import a populated Excel template into the package data – You then import the filled-in Excel file back into the configuration package in Business Central.

Apply the data – Finally, after validation, you apply the data so it is committed to the database tables of the new company.

Why not the others?

Export a configuration package is used to share configuration setups with another environment, not part of this workflow.

Import a populated Excel template into the sales header and lines is only for document data (transactions), not master data imports via configuration packages.

Comprehensive Detailed Explanation

Cash receipt journal batch must use a bank account

In a cash receipt journal, the Bal. Account Type determines where the balancing entry goes.

Since cash receipts go into a bank account, the Bal. Account Type must be set to Bank Account.

This ensures all receipts post against the designated bank ledger account.

Cash receipt customer payments must be archived in posted journals

To retain a copy of the posted journal lines, you configure the Copy to Posted Jnl. Lines option in the journal batch setup.

This archives the entries so users can review historical posted journals for audit and reconciliation.

Other options not correct:

G/L Account under Bal. Account Type → Would post to a G/L account, not the bank account.

Customer/Vendor under Bal. Account Type → Used for transactions affecting subledgers, not for cash receipts batch default.

Posting No. Series → Controls numbering, not archiving.

Suggest Balancing Amount → Used for auto-balancing lines, not archiving.

Reason Code → Tracks reasons for entries, not related to archiving.

Microsoft Learn References

General Journals in Business Central

Journal Batches

On the Vendor Card, the field Lead Time Calculation defines how long it usually takes the vendor to deliver items. If a vendor delivers items within one week after the company orders them, you must configure this field with 1W.

Lead Time Calculation = drives expected receipt dates, planning dates, and automatically updates order promising in purchase orders.

Shipment Method Code = describes the mode of transport (e.g., train, ship, air) but does not control dates.

Location Code = default receiving location; irrelevant to the timing.

Base Calendar Code = defines working days/holidays for date calculation adjustments, but not the actual delivery duration.

Thus, to ensure delivery date calculations reflect the vendor’s one-week lead time, Lead Time Calculation is the correct field.

Microsoft Learn References:

Register Vendors

Set Up Lead Times

Shipment Methods

The Custom Report Layouts page allows you to manage and update layouts (Word or RDLC) for a given report object. However, simply updating the layout does not make a new report object the system default. You must still assign the new report in Report Selection – Purchase. Thus, this solution does not meet the goal.