Vendor Rebate Agreement Calculation Date Type in D365 SCM

MB-330 By islever Editorial Last updated

Implement procurement and sourcing

Short answer

A Yes, setting the calculation date type to Created ensures the rebate qualification uses the purchase order creation date, matching the requirement for orders placed within a month.

Question

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might
meet 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 vendor is offering a rebate program on bottles of wine that have purchase orders placed within a month. There is a $5.00 rebate on the purchase of 10-100
bottles and a $6.00 rebate for the purchase of 101-200 bottles. Customers can purchase wine by the bottle or by the case. Discounts apply to all varieties of wine
sold by the vendor.
You need to create a vendor rebate agreement to ensure that the correct rebate amount is claimed at the end of the month.
Solution: On the rebate agreement, set the calculation date type field to created.
Does the solution meet the goal?
  1. Yes Correct Answer
  2. No

Key Takeaways

The trap is confusing 'placed' with 'delivered'. The key insight is that 'Calculation date type' dictates which transaction date validates the rebate eligibility window.

Learn how to configure the calculation date type for vendor rebate agreements in Dynamics 365. Setting it to 'Created' aligns with purchase orders placed within a specific timeframe.

Common mistake: Choosing 'No' because one might think the solution is incomplete without defining the tiered rebate amounts. However, the question focuses on the timing mechanism, which is correctly addressed by setting the date type to 'Created'.

Expert Analysis

The scenario requires configuring a vendor rebate agreement where the qualification is based on purchase orders placed within a specific month. The key constraint is timing: the rebate applies to orders "placed" (created) during that period.

In Dynamics 365 Supply Chain Management, the Calculation date type field on the vendor rebate agreement header determines which date from the transaction line is used to validate if the transaction falls within the agreement's validity period. The options typically include Created, Requested delivery, and Received. Since the requirement explicitly states "purchase orders placed within a month," the system must evaluate the Created date of the purchase order against the agreement's start and end dates.

Setting the Calculation date type to Created ensures that the rebate calculation logic checks the creation date of the PO. This aligns directly with the business rule that rebates are triggered by when the order was placed, not when it is delivered or received. Therefore, this specific configuration step is correct for meeting the stated goal of ensuring the correct rebate amount is claimed based on placement time.

While other settings like validity periods, rebate lines (tiered pricing), and unit conversions are also necessary for a complete implementation, the question asks specifically if setting the calculation date type to 'Created' meets the goal relative to the timing constraint. It does. As noted in community discussions, this setting correctly maps "placed" to the creation timestamp, distinguishing it from delivery-based triggers.

Exam Strategy

When analyzing rebate questions, always map the business trigger word ('placed', 'received', 'invoiced') to the corresponding date field in Dynamics 365. 'Placed' maps to Created date; 'Received' maps to Received date. Verify that the selected date type matches the trigger condition before evaluating other configuration steps.

Frequently Asked Questions

What happens if I set Calculation date type to 'Requested delivery'?

The rebate eligibility would be determined by the requested delivery date of the purchase order, not the creation date. This would fail the requirement for orders 'placed' within the month.

Is setting the date type enough to claim the correct rebate?

It is necessary but not sufficient. You must also define the validity period, rebate lines with tiers, and unit conversion rules. However, for the specific timing constraint, this setting is correct.

More MB-330 FAQ →

Discussion 13 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 13

  1. dmp1985 👍 8
    Why is the answer no? It says purchase orders placed within a month and Calculation date type Created uses the creation date of the purchase order.
  2. andreasraithel 👍 6
    this should be correct, as the previous and following questions are not correct. PO are registered which are "placed" means also "created" in the period.
  3. Naoki 👍 5
    I think, this answer is "Yes". "purchase orders placed within a month." means that it is matter of the order creation date. then calculation date type should be "Create". If request delivery date is matter of this agreement, then calculation date type should be "Requested delivery". Reference; https://docs.microsoft.com/en-us/dynamics365/supply-chain/procurement/vendor-rebates See "Review details of a vendor rebate agreement"
  4. sadiq_d365 👍 3
    There is a gap between the quantity range between this rebate detail and another rebate detail.
  5. globeearth 👍 2 Answered B
    B. No - A complete solution would include: Calculation date type: Created. Validity: Start = 1st of the month, End = last day of the month. Rebate lines: $5.00 for 10–100 bottles, $6.00 for 101–200 bottles. Unit: Bottles, with case conversion. Scope: Vendor and all wine varieties.
Show 8 more comments
  1. Yrshukla 👍 2
    What about the other criteria other than calculation date type not matching? I answer no because it refers to the "Calculation date type = created only. It remains created if the line is blank though.
  2. GJ63 👍 2
    Answer should be Yes
  3. CCexamn 👍 1 Answered B
    The goal is: "ensure that the correct rebate amount is claimed." Setting Calculation date type = Created only determines which date is used (the PO creation date). It does not address: o: purchases by bottle and case (requires Unit of measure rebate option = Convert), o: accumulation across units, o: rebate calculation itself. So: Correct date Not enough to ensure the correct rebate amount Therefore, the solution does not fully meet the goal.
  4. 3a7b7bd 👍 1 Answered A
    The important wording is: Rebates apply to purchase orders placed within a month. Setting Calculation date type = Created makes the rebate qualification align with the creation timing of the purchasing transaction. Microsoft confirms that the vendor rebate agreement header includes a Calculation date type, which determines the date basis used for rebate qualification.
  5. AshrafN 👍 1 Answered B
    In my opinion, the answer doesn't have enough clue. It would have been a correct answer if the start date of the agreement is before the POs creation date.
  6. LucasK69 👍 1 Answered A
    I think, this answer is "Yes". "purchase orders placed within a month." means that it is matter of the order creation date.
  7. H_Incandenza 👍 1 Answered A
    https://learn.microsoft.com/en-us/dynamics365/supply-chain/procurement/vendor-rebates
  8. mqady12545334 👍 1 Answered A
    I think, this answer is "Yes"

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Configure Asset Management for Fuel and Maintenance in Dynamics 365

S-grade

Configuring ABC Model Codes in Dynamics 365 SCM

S-grade

Dynamics 365 SCM Maintenance Round vs Plan

S-grade

Configuring Exporter Reporting for Shipments in D365 SCM

S-grade

← Back to MB-330 Study Guide