BeyondERP.Newsletter
Menu

Setup page · Sales and marketing

Merchandising event category

A setup page where you create categories for your organization's merchandising events, each with a default event type.

Used by
Marketing manager, Accounts receivable clerk, Sales manager
Business process
Manage trade allowances
Menu item
TAMMerchandisingEventType
Main table
TAMMerchandisingEventType
Setup steps
1 on this page
Show what matters for
PAGE GUIDEWhat the page does and how to use it8 sections. Choose a role to highlight what matters to you.
Everyone

1What it is and why

What it isA setup page where you create categories for your organization's merchandising events, each with a default event type.
What you do hereUse this page to group merchandising events, such as holiday discounts or seasonal sales, for trade allowance agreements.
ExampleBEAT creates category DISPLAY with default type Lump sum for in-store display fees and SEASONAL with default type Off invoice. When a 2,000.00 display event is added to an agreement, choosing DISPLAY proposes the Lump sum type automatically.
Merchandising event category page in Dynamics 365
The page in Dynamics 365. page title tab to open what to set or check
Functional consultant · Solution architect

2Where it fits

End user · Functional consultant

3How to do it

About the examples: Examples and screenshots in this guide use BEAT, a demo company in a Dynamics 365 test environment. Use your own company's codes and values instead of copying them.

Step by step, with screenshots

Set up Merchandising event category1 screen

Use this page to group merchandising events, such as holiday discounts or seasonal sales, for trade allowance agreements.

  1. Screen 1

    Create a merchandising event category

    Go to Sales and marketing > Setup > Trade allowance > Merchandising event category

    1. Select New
    2. Enter the category code and description
    3. Select the default type, such as Off invoice
    4. Select Save
    5. Select the category on merchandising events in trade allowance agreements
    1CategoryBEAT-MEC
    DescriptionSeasonal sale
    Default typeOff invoice
    Create a merchandising event category (zoomed on the outlined fields)
    Show the full screenCreate a merchandising event category
    page title tab to open what to set or check

Steps from Microsoft

  1. Go to Sales and marketing > Setup > Trade allowance > Merchandising event category.
  2. Select New.
  3. In the Category field, enter the category name and a short description.
  4. In the Default type field, select the category type for the event.

Source: Microsoft Learn

Fields on the page

FieldWhat it meansExampleTable column
CategoryThe name of the event category, with a short description.Microsoft Learn DISPLAYTAMMerchEventType
Default typeThe merchandising event type proposed for events in this category: Bill back, Lump sum or Off invoice.Microsoft Learn Lump sumMerchEventCategory
DescriptionA short description of the category.Microsoft Learn In-store display feesDescription

Common errors and fixes

MessageWhat to do
A merchandising event gets the wrong typeSet the right Default type on the category; the agreement's three event types are bill back, lump sum and off-invoice. Microsoft Learn

Test checklist

  1. Create category DISPLAY with default type Lump sum.
  2. On a trade allowance agreement, add a merchandising event in category DISPLAY.
  3. Check that the event type is Lump sum and that the agreement lines list 1 event.

Source: Microsoft Learn

Functional consultant

4Setup decisions

Setup stepRecommended value and whyDecision, common mistake and test
Set up Merchandising event categoryOne category per kind of merchandising activity, each with the event type the business normally pays it with (for example DISPLAY with Lump sum).Agreements cover bill back, lump sum and off-invoice events, and each type is processed differently, so the right default avoids events being paid the wrong way.Which default type should each category have?Setting Off invoice as default for activities that are paid after performance, so no lump sum is created to approve.Test: Category proposes its event type

Feature management and licence

Licence or add-inOn the live system, Marketing manager, Accounts receivable clerk and Sales manager use this page.

Checked in Dynamics 365

Solution architect

5Design impact

Shared or per companyPer company: each legal entity has its own records. Microsoft data model
Can it be undoneReversible: Categories can be edited at any time; existing events keep their type. Microsoft Learn
If you change it laterThe default type is proposed when an event is created; the event type decides whether the reward is a bill back claim, a lump sum or an off-invoice discount. Events already on agreements keep their type. Microsoft Learn
Technical architect

6Technical

Menu itemTAMMerchandisingEventType Checked in Dynamics 365
FormTAMMerchEventType Checked in Dynamics 365
TableTAMMerchandisingEventTypeShown as “Merchandising event type” in Record infoKey field: TAMMerchEventTypeChecked in Dynamics 365
Who can open itPrivilegesMaintain merchandising event types TAMMerchandisingEventTypeMaintainDutiesMaintain trade allowances TAMMaintain
3 security rolesMarketing manager CRMMarketingManagerAccounts receivable clerk CustInvoiceAccountsReceivableClerkSales manager TradeSalesManager
Checked in Dynamics 365
Roles to set it up and use itTo set it up or change itSales manager TradeSalesManagerMarketing manager CRMMarketingManagerAccounts receivable clerk CustInvoiceAccountsReceivableClerkGive people one of these roles. On this system, 3 roles can open this page.Checked in Dynamics 365
Actions on the pageOptions: Personalize, Page options, ShareChecked in Dynamics 365
Developer

7Developer

Open it by URLhttps://<your-environment>/?mi=TAMMerchandisingEventType
Data migrationLoad order: Merchandising event category has no data entity in Data management. Create the categories by hand in each legal entity before trade allowance agreements are loaded.Checked in Dynamics 365
Table definitionTAMMerchandisingEventType columns and relations Microsoft data model
Everyone

8Sources