BeyondERP.Newsletter
Menu

Job page · Retail and Commerce

Retail document operation processing

A batch job of the asynchronous document framework that processes store inventory documents committed from POS to headquarters.

Business process
Import orders from the commerce sites with Dynamics 365 Commerce
Menu item
RetailDocumentOperationProcessingBatchScheduler
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 of the asynchronous document framework that processes store inventory documents committed from POS to headquarters.
What you do hereUse this page to schedule the recurring processing job for inbound, outbound, stock count, adjustment and movement documents, including those that failed or timed out.
ExampleFor example, schedule the job to run every five minutes.
Retail document operation processing 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.

When to run it

When to run itWhen stores commit inventory documents from POS to headquarters through the asynchronous document framework.
How oftenEvery few minutes, at the same interval as the monitor job.
Batch settingsA recurring batch job that processes inbound, outbound, stock count, adjustment and movement documents, including documents that failed or timed out.
What the output showsStore inventory documents from POS are posted in headquarters. Documents that fail show Processing failed in POS with error messages; the store must correct them and submit them again.

Source: Microsoft Learn

Steps from Microsoft

  1. Go to Retail and Commerce > Retail and Commerce IT > Retail document operation processing.
  2. Make sure the Retail document operation identifier number sequence exists; the asynchronous document framework needs it before POS inventory operations can be used.
  3. Schedule the processing job to recur, for example every five minutes, alongside Retail document operation monitor.
  4. After a run, check in POS that Inbound, Outbound, Stock count, Adjustment and Movement documents committed by the store are posted, and correct any document with Processing failed and finish it again.

Source: Microsoft Learn

Test checklist

  1. A receipt committed in POS is posted in headquarters.
  2. A failed document shows Processing failed with an error message in POS.

Source: Microsoft Learn

Solution architect

4Design impact

Can it be undoneNo: Posted inventory documents stay posted. Correct quantities with a new inventory document. Microsoft Learn
If you change it laterPosts store inventory documents committed from POS in headquarters. Microsoft Learn
Technical architect

5Technical

Menu itemRetailDocumentOperationProcessingBatchScheduler Checked in Dynamics 365
FormSysOperationTemplateForm 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=RetailDocumentOperationProcessingBatchScheduler
Everyone

7Sources