BeyondERP.Newsletter
Menu

Job page · Retail and Commerce

Process warranty transactions

A batch job page that processes posted cash-and-carry warranty sales for selected stores and creates the warranty policy records.

Business process
Monitor product feedback
Menu item
RetailWarrantyProcessTransactionScheduler
Show what matters for
PAGE GUIDEWhat the page does and how to use it7 sections. Choose a role to highlight what matters to you.
Everyone

1What it is and why

What it isA batch job page that processes posted cash-and-carry warranty sales for selected stores and creates the warranty policy records.
What you do hereUse this page to run or schedule the job that turns posted warranty transactions into warranty policies, choosing the stores by organization hierarchy node and setting a recurrence.
ExampleFor example, schedule the job nightly for the whole retail hierarchy so that every warranty sold that day receives a policy number customers can be given.
Process warranty transactions 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 processAnalyze product performance › Monitor product feedback
Menu pathRetail and Commerce › Products and categories › Warranty › Process warranty transactions
Set up firstWarranty settings (number sequence for warranty policies) Microsoft Learn Distribution schedule (P-0001 pull job uploads store transactions) Microsoft Learn
Used next byWarranty policies (WARRANTYPOLICY records) Microsoft Learn
Related pagesWarranty groups 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.

When to run it

When to run itAfter cash-and-carry transactions with warranty sales are posted in headquarters.
How oftenAs a recurring batch job after statement posting.
Batch settingsRecurring batch job per store group, after statements are posted.
What the output showsWarranty policies, one per sold warranty, with policy number, warranted item and serial number, sales date, effective and expiration dates and status (Created, Voided, Effective or Expired). A sale without a policy usually means its transactions weren't posted yet, or the store isn't in the selected nodes.

Source: Microsoft Learn

Steps from Microsoft

  1. Go to Retail and Commerce > Products and categories > Warranty > Process warranty transactions.
  2. In the Choose organization nodes dialog box, select an Organizational hierarchy.
  3. In Available organization nodes, select a store, or a node for a group of stores, and use the right arrow to move it to Selected organization nodes.
  4. On the Run in the background tab, set Batch processing to Yes and select Recurrence; enter the start date and time and choose No end date, End after or End by.
  5. Afterwards, look up the warranty policies for a recent warranty sale: each policy has a policy number, the warranted serial number, effective and expiration dates and a status.

Source: Microsoft Learn

Fields on the page

FieldWhat it means
Organizational hierarchyThe hierarchy from which stores are picked for the job.Microsoft Learn
Available organization nodesThe store or hierarchy node whose warranty transactions the job processes.Microsoft Learn
Batch processingSet to Yes to run the job in the background on a schedule.Microsoft Learn
Start dateThe date the recurrence begins.Microsoft Learn
Start timeThe time of day the recurrence begins.Microsoft Learn
No end date / End after / End byHow the recurrence ends: never, after a number of runs, or by a date.Microsoft Learn

Test checklist

  1. Each warranty sold has a policy.
  2. Policy dates match the warranty length.
  3. Policy numbers follow the Warranty policy number sequence.

Source: Microsoft Learn

Solution architect

4Design impact

Can it be undoneNo: Warranty policies are generated automatically and can't be edited by hand. Microsoft Learn
If you change it laterThe policies this job creates are generated automatically and cannot be edited by hand, so the transactions and number sequence must be right before the job runs. Microsoft Learn
Technical architect

5Technical

Menu itemRetailWarrantyProcessTransactionScheduler Checked in Dynamics 365
FormRetailOperatingUnitPicker Checked in Dynamics 365
Roles to set it up and use itTo use itRetail service RetailServiceRetail operations manager RetailOperationsManagerGive people one of these roles. On this system, 2 roles can run this page.Checked in Dynamics 365
Developer

6Developer

Open it by URLhttps://<your-environment>/?mi=RetailWarrantyProcessTransactionScheduler
Everyone

7Sources