BeyondERP.Newsletter
Menu

Setup page · Sales and marketing

Sales agreement classifications

A setup list of sales agreement classifications. Every sales agreement is created in a classification, which groups agreements for search and reporting. The page is shared with Accounts receivable and stored in the same table as purchase agreement classifications.

Used by
Accounts payable manager, Accounts receivable clerk, Accounts receivable manager and 8 more roles
Business process
Manage blanket sales orders
Menu item
SalesAgreementClassification
Main table
AgreementClassification
Data entity
SalesAgreementClassificationEntity
Setup steps
2 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 list of sales agreement classifications. Every sales agreement is created in a classification, which groups agreements for search and reporting. The page is shared with Accounts receivable and stored in the same table as purchase agreement classifications.
What you do hereUse it to create the classifications that users choose from when they create a sales agreement.
ExampleBEAT creates the classifications ANNUAL-VOL for yearly volume commitments and PROJECT for one-off projects. Sales agreement SA-000087 for customer CUS-000214, a value commitment of 120,000.00, is created in ANNUAL-VOL so it can be found with the other annual deals.
Sales agreement classifications 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

Business processManage sales orders › Manage blanket sales orders
Menu pathSales and marketing › Setup › Sales agreements › Sales agreement classifications
Set up firstNumber sequences Microsoft Learn
Used next bySales agreements Microsoft Learn
Related pagesSales agreement classifications (Accounts receivable) Microsoft Learn
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 Sales agreement classifications1 screen

Defines the categories that every sales agreement must be assigned to when it is created, optionally carrying the number sequence and associated purchase classification for agreements of that type.

  1. Screen 1

    Create the sales agreement classification

    Go to Accounts receivable > Setup > Sales agreement classifications

    1. Select New and enter the name and description
    2. On the General FastTab, set the classification category and line matching policy
    1NameBEAT
    DescriptionSales agreement
    Agreement classification categoryDefault
    Line matching policyCompany policy
    Create the sales agreement classification (zoomed on the outlined fields)
    Show the full screenCreate the sales agreement classification
    page title tab to open what to set or check
Plan sales agreement classifications

Decide the small set of classifications that every sales agreement is created in.

Steps from Microsoft

  1. Go to Sales and marketing > Setup > Sales agreements > Sales agreement classifications.
  2. Select New and enter the Name and Description of the classification, for example ANNUAL-VOL.
  3. In the Russian localization only, set Associated classification and Number sequence code on the General FastTab.
  4. Create a sales agreement and check that the classification can be selected in the Sales agreement classification field.

Source: Microsoft Learn

Fields on the page

FieldWhat it meansExampleTable column
Associated classificationRussian localization only: the purchase agreement classification related to this sales agreement classification.Microsoft Learn ANNUAL-PUR
Number sequence codeRussian localization only: the number sequence used to number agreements in this classification; agreements are then numbered within the classification.Microsoft Learn SAgr_RU
NameThe name of the agreement classification.Checked in Dynamics 365Annual volumeName
DescriptionA description of the agreement classification.Checked in Dynamics 365Sales agreementDescription_PSN
Agreement classification categoryThe category of the agreement classification, read from the page.Checked in Dynamics 365DefaultClassificationCategory
Line matching policyThe line matching policy stored with the classification, read from the page.Checked in Dynamics 365Company policyMatchingPolicy

Common errors and fixes

MessageWhat to do
A classification can't be deletedA classification used on existing agreements can't be deleted. Keep it, or use a new classification for new agreements. Microsoft Learn

Test checklist

  1. Create classification ANNUAL-VOL.
  2. Create sales agreement SA-000087 for customer CUS-000214 and select ANNUAL-VOL in Sales agreement classification.
  3. Filter the sales agreement list on ANNUAL-VOL and check that SA-000087 is listed.
  4. Try to delete ANNUAL-VOL and check that the system doesn't allow it.

Source: Microsoft Learn

Functional consultant

4Setup decisions

Setup stepRecommended value and whyDecision, common mistake and test
Set up Sales agreement classificationsOne classification per type of sales agreement, each with its Associated classification and its own Number sequence code.Every sales agreement belongs to a classification, and the Sales agreement ID is set from the number sequence on the classification. Separate classifications give separate numbering and grouping per agreement type.Creating test classifications in the live company and using them on agreements. A classification that's used on existing agreements can't be deleted.
Plan sales agreement classificationsA short list of classifications by agreement type (for example ANNUAL-VOL and PROJECT), created before the first agreement; no test classifications in the live company.Every sales agreement is created in a classification, and a classification that is used on agreements can't be deleted. Outside the Russian localization the classification groups agreements; numbering per classification is a Russian localization extension.How many sales agreement classifications are needed?Expecting each classification to number its own agreements in a non-Russian company. Associated classification and Number sequence code belong to the Russian localization.Test: Classification is used and protected

Feature management and licence

Licence or add-inOn the live system, Sales manager, Purchasing manager, the Accounts receivable roles (clerk, manager, payments clerk, centralized payments clerk), Accounts payable manager, Retail service and the Rental roles use this page.

Checked in Dynamics 365

Solution architect

5Design impact

Shared or per companyShared: classifications are stored once for all legal entities, in the same table as purchase agreement classifications, and are maintained from Sales and marketing and Accounts receivable. Microsoft data model
Can it be undoneHard to reverse: You can't delete an agreement classification that is used on existing sales agreements; plan the list before agreements are created. Microsoft Learn
If you change it laterA classification used on existing agreements can't be deleted, so the list grows with every classification that is used. In the Russian localization the number sequence on the classification decides the Sales agreement ID of new agreements. Microsoft Learn
Technical architect

6Technical

Menu itemSalesAgreementClassification Checked in Dynamics 365
FormAgreementClassification Checked in Dynamics 365
TableAgreementClassificationShown as “Agreement classification” in Record infoKey field: RecIdChecked in Dynamics 365
Data entitiesSalesAgreementClassificationEntitySales agreement classification Microsoft data model PurchAgreementClassificationEntityPurchase agreement classification Microsoft data model
Who can open itPrivilegesMaintain sales agreement classifications SalesAgreementClassificationMaintainView sales agreement classifications SalesAgreementClassificationViewDutiesEnable purchase order to invoice process PurchOrderToInvoiceProcessEnableEnable quotation to sales order process RentalSalesQuotationToSlsOrdProcessEnableEnable quotation to sales order process SalesQuotationToSalesOrderProcessEnableInquire into quotation to sales order reference data SalesQuotationToSalesOrderRefDataInquir
11 security rolesAccounts receivable clerk CustInvoiceAccountsReceivableClerkAccounts receivable manager CustInvoiceAccountsReceivableManagerAccounts receivable centralized payments clerk PaymAccountsReceivableCentralPaymClerkAccounts receivable payments clerk PaymAccountsReceivablePaymentsClerkRental coordinator agent RentalCoordinatorAgentRental manager RentalManagerRental sales manager RentalSalesManagerRetail service RetailServicePurchasing manager TradePurchasingManagerSales manager TradeSalesManagerAccounts payable manager VendInvoiceAccountsPayableManager
Checked in Dynamics 365
Roles to set it up and use itTo set it up or change itSales manager TradeSalesManagerRental manager RentalManagerRental coordinator agent RentalCoordinatorAgentRental sales manager RentalSalesManagerAccounts receivable manager CustInvoiceAccountsReceivableManagerTo use itAccounts receivable clerk CustInvoiceAccountsReceivableClerkAccounts receivable centralized payments clerk PaymAccountsReceivableCentralPaymClerkAccounts receivable payments clerk PaymAccountsReceivablePaymentsClerkGive people one of these roles. On this system, 11 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=SalesAgreementClassification
Integrate withSalesAgreementClassificationEntity data entity Microsoft data model
Data migrationSalesAgreementClassificationEntity (Sales agreement classification): shared by all companies, in Microsoft's default template 330 - Sales and marketing.PurchAgreementClassificationEntity (Purchase agreement classification): shared by all companies, in Microsoft's default template 320 - Procurement and sourcing.Load order: Microsoft's default template 330 - Sales and marketing loads Sales agreement classification at execution unit 1, level 30, sequence 10. Lower levels load first, and entities at the same level load in sequence order.Load first: the default templates at lower levels (System setup to General ledger)Microsoft Learn
Table definitionAgreementClassification columns and relations Microsoft data model
Everyone

8Sources