Microsoft Dynamics 365 Community

Dynamics 365 can be automated quite a lot with the use of batch jobs. With batch jobs, your Dynamics 365 solution becomes “alive”, and we can set up the system to automate many manually processes. Lets say to have the following “vanilla process”, and wants to automate as many steps as possible.

This document covers the Batch jobs needed to be setup for this process to be as automated as possible. I wanted to put a structured system on all the batch jobs that is typically used in a production system. But this also generates a lot of data, that you don’t normally need. It is therefore common to create both functional batch jobs that processes and executes functionality, and also execute cleanup jobs that removes irrelevant data.

Batch job Naming conventions

To make it simpler to understand the batch jobs a simple structure of naming the batch jobs have been created. The first character is just “A”, to make sure that the sorting of the batch jobs is in the best possible way, and that the batch jobs can be sorted according to name. The next is a 3 digit number and at the last there is a then a description that explains the batch job.

ID	Description
A001-A099	System administration batch jobs
A100-A199	Data management batch jobs
A200-A299	General ledger batch jobs
A300-A399	Procurement and sourcing batch jobs
A400-A499	Sales and marketing batch jobs
A500-A599	Retail batch jobs
A600-A699	Inventory management batch jobs
A700-A799	Warehouse management batch jobs

Reach of these ranges are then set up as batch groups, and you can better control what AOS servers is executing what type of batch jobs:

In this blog post more than 87 batch jobs have been specified, and that keeps the Dynamics 365 system updated and as automatic as possible

Job description

A001 Notification clean-up

A002 Batch job history clean-up

A003 Batch job history clean-up (custom).

A004 Daily Diagnostics rule validation

A005 Weekly Diagnostics rule validation

A006 Monthly Diagnostics rule validation

A007 Named user license count reports processing

A008 Databaselog cleanup

A009 Delete the inactivated addresses

A010 Scan for orphaned document references.

A011 Report data clean up

A012 Cryptography crawler system job that needs to regularly run at off hours.

A014 Updates system notification states.

A015 Deletes non-active and orphaned system notifications.

A016 Database compression system job that needs to regularly run at off hours.

A017 Database index rebuild system job that needs to regularly run at off hours

A018 Deletes expired email history.

A019 Process automation polling system job

A020 Scan for document files that have been scheduled for physical deletion.

A021 System job to clean up expired batch heartbeat records.

A022 System job to seed batch group associations to batch jobs.

A023 System job to clean up unrecovered user session states.

A024 Change based alerts

A025 Due date alerts

A026 Email distributor batch

A027 Email attachment distributor

A103 Entity Store Deploy measurement

A103 Refresh data entity

A200 Clean up ledger journals

A201 Import currency exchange rates

A205 Create a scheduled task that will execute the batch transfer of subledger journal entries.

A205 Update purchase and sales budget

A206 Source document line processing

A207 Source document line processing queue cleanup

A208 Ledger journal monitor

A300 Purchase update history cleanup

A301 Delete request for quotation

A303 Draft consignment replenishment order journal cleanup

A303 Run Forecast planning

A304 Run Master planning

A305 Post product receipt

A403 Sales update history cleanup

A405 Order packing slip

A406 Order invoice

A407 Calculate sales totals

A500 All retail distribution jobs (9999)

A501 Upload all channel transactions (P-0001)

A502 Process Assortment

A503 Update listing status

A504 Product availability

A505 Generate related products based on customer transactions

A506 Process delivery modes

A507 Synchronize orders job

A508 Update search Product data

A509 Update search Customer data

A510 DOM batch job

A511 DOM fulfillment data deletion job

A512 Default channel database batch job

A513 Recommendation batch job

A514 Retail scheduler history data removal batch job

A515 Create customers from async mode

A516 Retail transaction consistency checker orchestrator

A517 Retail transactional statement calculate batch scheduler

A518 Retail transactional statement post batch scheduler

A519 Retail financial statement calculate batch scheduler

A520 Retail financial statement post batch scheduler

A521 Process loyalty schemes

A522 Post earned points in batches

A523 Process loyalty lines for other activities

A524 Retail time zone information job

A600 Calculation of location load

A601 Inventory journals clean-up

A602 Inventory settlements clean up

A605 On-hand entries cleanup

A606 Warehouse management on-hand entries cleanup

A607 On-hand entries aggregation by financial dimensions

A608 Cost calculation details

A609 CDS – Post integration inventory journals

A700 Work creation history purge

A701 Containerization history purge

A702 Wave batch cleanup

A703 Cycle count plan cleanup

A705 Work user session log cleanup

A706 Wave processing history log cleanup

A707 WMS Replenishment

A708 Automatic release of sales orders

I will not go in detail of all the jobs, but here I at least refer to where you can find the menu item or what class is used in the batch job tasks. Also take a look at blog post by the D365 Solution architecture team, that is a subset of the batch jobs presented in this blog post.

System administration batch jobs

These are general system batch jobs that can perform cleanups and other general executions.

ID	Name, path and recurrence	Description and recurrence
A001	A001 Notification clean-up System administration > Periodic tasks > Notification clean up Daily	This is used to periodically delete records from tables EventInbox and EventInboxData. Recommendation would also be if you don’t use Alert functionality to disable Alert from Batch job.
A002	A002 Batch job history clean-up System administration > Periodic tasks > Batch job history clean-up Daily	The regular version of batch job history clean-up allows you to quickly clean all history entries older than a specified timeframe (in days). Any entry that was created prior to – will be deleted from the BatchJobHistory table, as well as from linked tables with related records (BatchHistory and BatchConstraintsHistory). This form has improved performance optimization because it doesn’t have to execute any filtering.
A003	A003 Batch job history clean-up (custom). System administration > Periodic tasks > Batch job history clean-up (custom) Manually	The custom batch job clean-up form should be used only when specific entries need to be deleted. This form allows you to clean up selected types of batch job history records, based on criteria such as status, job description, company, or user. Other criteria can be added using the Filter button.
A004	A004 Daily Diagnostics rule validation System administration > Periodic tasks > Diagnostics rule validation Daily	Incorrect configuration and setup of a module can adversely affect the availability of features, system performance, and the smooth operation of business processes. The quality of business data (for example, the correctness, completeness, and cleanliness of the data) also affects system performance, and an organization’s decision-making capabilities, productivity, and so on. The Optimization advisor workspace is a tool that lets you identify issues in module configuration and business data. Optimization advisor suggests best practices for module configuration and identifies business data that is obsolete or incorrect.
A005	A005 Weekly Diagnostics rule validation System administration > Periodic tasks > Diagnostics rule validation Weekly	Performs a weekly validation and diagnostics.
A006	A006 Monthly Diagnostics rule validation System administration > Periodic tasks > Diagnostics rule validation Monthly	Performs a monthly validation and diagnostics based on the rules.
A007	A007 Named user license count reports processing Class : SysUserLicenseMiner Daily	Batch job that counts number of users that have been using the system. The data is used in the Named user license count report. D365 creates this execution automatically, but you have to rename it to fit this structure.
A008	A008 Databaselog cleanup System administration > Inquiries > Database > Database Log Weekly	This job cleans up the database log, and makes sure that only (let’s say) 100 day’s of history remains. In the query criteria I set created date time less than “d-100”, to ensure that I keep 100 day’s of database log. This is general housekeeping and dusting in the system, and keeping the system nice and tidy.
A009	A009 Delete the inactivated addresses Organizational administration > Periodic >Delete inactivated addresses Weekly	Deletes addresses that have been set to inactive.
A010	A010 Scan for orphaned document references. Class : DocuRefScanOrphansTask Daily	Batch job that is setup automatically by the system, and scans for document references where the source record is deleted.
A011	A011 Report data clean up Class: SrsReportRunRdpPreProcessController Daily	Cleans up any data generated for SSRS reports.
A012	A012 Cryptography crawler system job that needs to regularly run at off hours. Class: SysCryptographyCrawlerTask Every 3 days	Auto created at D365 setup …Not sure what this is, yet…..
A013	A013 Data cache refresh batch System administration > Setup > Data cache >Data cache parameters Every 10 minutes	The data cache framework is used to cache data sets and tiles. Enabling of the data cache framework will redirect certain queries against a cache table instead of executing them against the underlying source tables.
A014	A014 Updates system notification states. Class : SystemNotificationUpdateBatch Every minute	Updates notifications,
A015	A015 Deletes non-active and orphaned system notifications. Class : SystemNotificationScanDeletionsBatch Daily	Deletes non-active and orphaned system notifications
A016	A016 Database compression system job that needs to regularly run at off hours. Class: SysDatabaseCompressionTask Daily	Compresses the database
A017	A017 Database index rebuild system job that needs to regularly run at off hours Class: SysDatabaseIndexRebuildTask Daily	Rebuilds indexes to ensure good index performance
A018	A018 Deletes expired email history Class: SysEmailHistoryCleanupBatch Daily	Deletes expired email history
A019	A019 Process automation polling system job Class: ProcessAutomationPollingEngine Every minute	Using business events, the polling use case can be re-designed to be asynchronous if it is triggered by the business event. Data will be processed only when it is available. The business logic that makes the data available triggers the business event, which can then be used to start the data processing job/logic. This can save thousands of batch executions from running empty cycles and wasting system resources.
A020	A020 Scan for document files that have been scheduled for physical deletion. Class: DocuDeletedFileScanTask Hourly	Scan for document files that have been scheduled for physical deletion
A021	A021 System job to clean up expired batch heartbeat records. Class : SysCleanupBatchHeartbeatTable Daily	Cleans up the new internal monitoring BatchHeartbeatTable table (Only after PU32), and used for priority-based batch scheduling.
A022	A022 System job to seed batch group associations to batch jobs. Class: SysMigrateBatchGroupsForPriorityBasedScheduling Daily	See priority-based batch scheduling.
A023	A023 System job to clean up unrecovered user session states. Class: SysUnrecoveredUserSessionStateCleanup Daily	Cleans up sessions that is unrecovered.
A024	A024 Change based alerts System administration > Periodic tasks > Alerts > Change based alerts Hourly (or faster)	Events that are triggered by change-based events. These events are also referred to as create/delete and update events. See also Microsoft docs.
A025	A025 Due date alerts System administration > Periodic tasks > Alerts > Due date alerts Hourly (or faster)	Events that are triggered by due dates. See also Microsoft docs.
A026	A026 Email distributor batch System administration > Periodic tasks > Email processing > Email distributor batch	Send emails. See also Microsoft docs.
A027	A027 Email attachment distributor	Send emails, with attachments. For workflow.

Data management batch jobs

Data management executions can generate a lot of data, and to maintain performance and avoid data growth, it is relevant to clean up staging tables and job executions. Also document any of your recurring executions to make it easy and simple to maintain a overview of your data imports and exports that are recurring.

ID	Name, path and recurrence	Description
A100	[Cannot be executed in batch] Data management workspace > “Staging cleanup” tile Manually	Data management framework makes us of staging tables when running data migration. Once data migration is completed then this data can be deleted using “Staging cleanup” tile.
A101	A101 Job history cleanup Data management workspace > Job history cleanup Daily	The clean up job will execute for the specified amount of time. If more history remains to be cleaned up after the specified about of time has elapsed, the remaining history will be cleaned up in the next recurrence of the batch job or it can be manually scheduled again.
A102	A102 BOYD Data management export Data management workspace >export in batch Hourly	If you have a data management export to BYOD, then this can be executed in batch. There are other options that also can be evaluated for this purpose. See A102 BOYD Data management export
A103	A103 Refresh data entity System administration à Setup à Entity Store Monthly	To refresh the entity store (the built in embedded power BI). The refresh updates the aggregated measurements, and is only relevant of there are updates or changes that affect these.

General ledger batch jobs

ID	Name, path and recurrence	Description
A200	A200 Clean up ledger journals Periodic tasks > Clean up ledger journals Weekly	It deletes general ledger, accounts receivable, and accounts payable journals that have been posted. When you delete a posted ledger journal, all information that’s related to the original transaction is removed. You should delete this information only if you’re sure that you won’t have to reverse the ledger journal transactions.
A201	A201 Import currency exchange rates Currencies > Import currency exchange rates Daily	Automatically imports exchange rates from the bank.
A202	A202 Purchase budget to ledger Inventory management > Periodic tasks > Forecast updates > Purchase budget to ledger Monthly	Posts the purchase budget to ledger
A203	A203 Sales budget to ledger Inventory management > Periodic tasks > Forecast updates > Sales budget to ledger Monthly	Posts sales budget to ledger
A204	A204 Update purchase and sales budget Inventory management > Periodic tasks > Forecast updates > Update purchase and sales budget Monthly	Updates the purchase and sales budget.
A205	A205 Create a scheduled task that will execute the batch transfer of subledger journal entries. General Ledger > Periodic tasks > Batch transfer for subledger journals Daily	Batch transfer for subledger journals
A206	A206 Source document line processing Class: SourceDocumentLineProcessingController Every 10 minutes	Used for accounting distribution. See Microsoft docs.
A207	A208 Source document line processing queue cleanup Class: SourceDocumentLineProcessingQueueCleanupController Weekly	Used for cleaning up accounting distribution. See Microsoft docs.
A208	A208 Ledger journal monitor Class: LedgerJournalTableMonitorController Every 6 hours	Monitors if ledger journals should be blocked or opened.

Procurement and sourcing batch jobs

ID	Name, path and recurrence	Description
A300	A300 Purchase update history cleanup Periodic tasks > Clean up > Purchase update history cleanup Weekly	This is used to delete all updates of confirmations, picking lists, product receipts, and invoices generate update history transactions.
A301	A301 Delete request for quotation Periodic tasks > Clean up > Delete requests for quotations Manually	It is used to delete requests for quotation (RFQs) and RFQ replies. The corresponding RFQ journals are not deleted, but remain in the system.
A302	A302 Draft consignment replenishment order journal cleanup Periodic tasks > Clean up > Draft consignment replenishment order journal cleanup Weekly	It is used to cleanup draft consignment replenishment order journals.
A303	A303 Run Forecast planning Master planning > Forecasting > Forecast planning Weekly	Demand forecasting is used to predict independent demand from sales orders and dependent demand at any decoupling point for customer orders. See also at Microsoft docs, where using additional azure services to perform the calculation.
A304	A304 Run Master planning Master planning > Master planning > Run > Master planning Daily	Master planning is used to generate planned (purchase) orders, based on the coverage settings. We expect this service to be enhanced with more real-time oriented planning engine. The master planning batch job execution is located at. Also check out the Microsoft docs on this (large) subject.
A305	A305 Post product receipt Procurement and Sourcing > Purchase orders > Receiving products > Post product receipt	Automatically post purchase receipt when all lines have been registered,

Sales and marketing batch jobs

ID	Name, path and recurrence	Description
A400	A400 Delete sales orders Periodic tasks > Clean up > Delete sales orders Manually	It deletes selected sales orders.
A401	A401 Delete quotations Periodic tasks > Clean up > Delete quotations Manually	It deletes selected quotations.
A402	A402 Delete return orders Periodic tasks > Clean up > Delete return orders Manually	It deletes selected return orders.
A403	A403 Sales update history cleanup Periodic tasks > Clean up > Sales update history cleanup Weekly	It deletes old update history transactions. All updates of confirmations, picking lists, packing slips, and invoices generate update history transactions. These transactions ca be viewed in the History on update form.
A404	A404 Order events cleanup Periodic tasks > Clean up > Order events cleanup Weekly	Cleanup job for order events. Next step is to remove the not needed order events check-boxes from Order event setup form.
A405	A405 Order packing slip Sales order > Ordershipping > Post Packingslip Hourly	Set up automatic packingslip posting of the sales order is completely picked. (If this is the process). This means that as soon as the WMS have picked the order it gets packingslip updated.
A406	A406 Order invoice Accounts payable > Invoices > Batch invoicing > Invoice Hourly	Set up automatic invoice posting of the sales order is completely packingslip updated. (If this is the process).
A407	A407 Calculate sales totals Periodic tasks > Calculate sales totals	Recalculate the totals for the sales order. This is typically used in scenario’s when the sales order is part of a “Prospect to cash” scenario. See docs.

Retail batch jobs

ID		Name, path and recurrence	Description
A500		A500 All retail distribution jobs (9999) Retail and Commerce > Retail and Commerce IT > Distribution schedule Hourly	This batch job is sending all distribution jobs to the retail channel database. This data like products, prices, customers, stores, registers etc. The distribution job is a “delta” distribution, meaning that only new and changed records are sent. There is a lot of more to be discussed on how to optimize the 9999-distribution job, and for really large retail installations some deep thinking is required. For smaller installations it should be OK to just use the setup that is automatically generated when initializing D365 retail/Commerce.
A501		A501 upload all channel transactions (P-0001) Retail and Commerce > Retail and Commerce IT > Distribution schedule Hourly	The P-0001 is sending the retail transactions back from the POS to the D365 HQ, where the retail transactions can be posted and financially updated.
A502		A501 Process Assortment Retail and Commerce > Retail and Commerce IT > Products and Inventory > Process Assortment Hourly	This job processes the assortment based on the assortment categories set on an item, and based on the assortment set up, puts the items in the relevant stores’ assortment. When defining an assortment, you have in D365 the possibility to connect organization hierarchies to retail category hierarchies. The process assortment will perform the granulation of this, so that D365 have a detailed list of each product that is present in each store. The assortment is setup under Retail and Commerce à Catalogs and assortments à Assortments and more details is available on Microsoft docs.
A503		A503 Update listing status Retail and Commerce > Retail and Commerce > Products and Inventory > Update listings Daily	The listing status is related to publishing a retail catalog to an online store. The Microsoft documentation is not the best in this area, and the closes explanation I have is that it is related to the listing status on the catalog.
A504		A504 Product availability Retail and Commerce > Retail and Commerce > Products and Inventory > Product availability Daily	The batch job for product availability is calculate if a product is available on online store. Checkout this blogpost for further details. SiteCore eCommerce integrations can benefit from this, and in essence it populates the data needed for distribution job 1130, and that maintains the following tables into the channel database
A505		A505 Generate related products based on customer transactions Retail and Commerce > Retail and Commerce IT > Products and Inventory > Generate related products Daily	This job will automatically populate related products based on sales transaction purchase history. The two relationships created are ‘customers who bought this item also bought’ and the ‘frequently bought together’ relation types. This data can then further be used in eCommerce scenario’s. Fore deep details, take a look at the class ‘RetailRelatedProductsJob’
A506		A506 Process delivery modes Retail and Commerce > Retail and Commerce IT > Products and Inventory > Process delivery modes Daily	This job sets up delivery modes on a new store when added to organization hierarchy ‘retail store by department’. On the modes of delivery you can assign a organizational hierarchy, and this batch job assigns the specific modes of deliveries to each store. The modes of delivery is used in omnichannel scenario’s where the customer can have their products sent home etc.
A507		A507 Synchronize orders job Retail and Commerce > Retail and Commerce IT > Synchronize orders Hourly	If you have setup your channels to create sales order asynchrony, this job will create the sales orders and post payments. Also take a look at the following Microsoft docs on how sales orders and payments are synchronized from an online store.
A508		A508 Update search Product data Sales and marketing > Setup > Search> Search criteria Daily	Create an indexed search of products, that makes it faster and easier to search for products in the call center.
A509		A509 Update search Customer data Sales and marketing > Setup > Search> Search criteria Daily	Create an indexed search of customers, that makes it faster and easier to search for customers in the call center.
A510		A510 DOM batch job Workspace > Distributed Order Management > Dom processor job setup Hourly	Run distributed order management on retail sales orders to determine what warehouse should deliver the sales order
A511		A511 DOM fulfillment data deletion job Workspace > Distributed Order Management > DOM fulfillment data deletion job setup Daily	Cleans up the DOM data that is no longer the valid calculation.
A512		A512 Default channel database batch job Class : RetailCdxChannelDbDirectAccess Every 3 minutes	This job main duty is to check all Download sessions and Upload sessions with status “Available”, then it will apply the data to respective target DB’s (AX or channel DB). See also this blog.
A513		A513 Recommendation batch job Class FormRunConfigurationRecommendationBatch Weekly	Se Microsoft docs.
A514		A514 Retail scheduler history data removal batch job Retail and Commerce > Headquarters setup > Parameters > Retail scheduler parameters Class: RetailCdxPurgeHistory Daily	Deletes CDX history. Typical only keeping 30 days of CDS history
A515		A515 Create customers from async mode Retail and Commerce > Retail and Commerce IT > Customer > Create customers from async mode Hourly	If customers should be created async (parameter), then this job will create the customer.
A516		A516 Retail transaction consistency checker orchestrator Retail and Commerce > Retail and Commerce IT > POS posting > Validate store transactions Hourly	Performs validation on the unposted POS transactions. See Microsoft docs.
A517		A517 Retail transactional statement calculate batch scheduler Retail and Commerce > Retail and Commerce IT > POS posting > Calculate transactional statement in batch Hourly (of faster)	Retail statement Trickle feed transactional calculate. Creates transactional statement. Se the following blog post.
A518		A518 Retail transactional statement post batch scheduler Retail and Commerce > Retail and Commerce IT > POS posting > Post transactional statement in batch Hourly (of faster)	Retail statement Trickle feed transactional calculate. Create and posts sales orders. Se the following blog post.
A519		A519 Retail financial statement calculate batch scheduler Retail and Commerce > Retail and Commerce IT > POS posting > Calculate financial statement in batch Daily	Retail statement Trickle feed financial statement calculate. Creates financial statement. Se the following blog post.
A520		A520 Retail transactional statement post batch scheduler Retail and Commerce > Retail and Commerce IT > POS posting > Post financial statement in batch Daily	Retail statement Trickle feed financial calculate. Posts shift declaration Se the following blog post.
A521		A521 Process loyalty schemes Retail and Commerce > Retail and Commerce IT > Loyalty > Process loyalty schemes	Processes loyalty schemes. See Microsoft docs.
A522	A522 Post earned points in batches Retail and Commerce > Retail and Commerce IT > Loyalty > Post earned points in batches		Loyalty points should be posted in batch. See Microsoft docs.
A523	A523 Process loyalty lines for other activities Retail and Commerce > Retail and Commerce IT > Loyalty > Process loyalty lines for other activities		Other Loyalty points in batch. See Microsoft docs.
A524		A524 Retail time zone information job Monthly	Generates timezone information up until 2054. Ensures that timezone used in the store does not causes inconsistent dates.

Inventory management batch jobs

ID	Name, path and recurrence	Description
A600	A600 Calculation of location load Inventory management > Periodic tasks > Clean up > Calculation of location load Daily	WMSLocationLoad table is used in tracking weight and volume of items and pallets. Summation of load adjustments job can be run to reduce the number of records in the WMSLocationLoad table and improve performance.
A601	A601 Inventory journals clean-up Inventory management > Periodic tasks > Clean up > Inventory journals cleanup Weekly	It is used to delete posted inventory journals.
A602	A602 Inventory settlements clean up Inventory management > Periodic tasks > Clean up > Inventory settlements cleanup Manually/Yearly	It is used to group closed inventory transactions or delete canceled inventory settlements. Cleaning up closed or deleted inventory settlements can help free system resources. Do not group or delete inventory settlements too close to the current date or fiscal year, because part of the transaction information for the settlements is lost. Closed inventory transactions cannot be changed after they have been grouped, because the transaction information for the settlements is lost. Canceled inventory settlements cannot be reconciled with finance transactions if canceled inventory settlements are deleted.
A603	A603 Inventory dimensions cleanup Inventory management > Periodic tasks > Clean up > Inventory dimensions cleanup Manually/Yearly	This is used to maintain the InventDim table. To maintain the table, delete unused inventory dimension combination records that are not referenced by any transaction or master data. The records are deleted regardless of whether the transaction is open or closed. Inventory dimension combination record that is still referenced cannot be deleted because when an InventDim record is deleted, related transactions cannot be reopened.
A604	A604 Dimension inconsistency cleanup Inventory management > Periodic tasks > Clean up > Dimension inconsistency cleanup Manually/Yearly	This is used to resolve dimension inconsistencies on inventory transactions that have been financially updated and closed. Inconsistencies might be introduced when the multisite functionality was activated during or before the upgrade process. Use this batch job only to clean up the transactions that were closed before the multisite functionality was activated. Do not use this batch job periodically.
A605	A605 On-hand entries cleanup Inventory management > Periodic tasks > Clean up > On-hand entries cleanup Monthly	This is used to delete closed and unused entries for on-hand inventory that is assigned to one or more tracking dimensions. Closed transactions contain the value of zero for all quantities and cost values, and are marked as closed. Deleting these transactions can improve the performance of queries for on-hand inventory. Transactions will not be deleted for on-hand inventory that is not assigned to tracking dimensions.
A606	A606 Warehouse management on-hand entries cleanup Inventory management > Periodic tasks > Clean up > Warehouse management on-hand entries cleanup Weekly	Deletes records in the InventSum and WHSInventReserve tables. These tables are used to store on-hand information for items enabled for warehouse management processing (WHS items). Cleaning up these records can lead to significant improvements of the on-hand calculations.
A607	A607 On-hand entries aggregation by financial dimensions Inventory management > Periodic tasks > Clean up > On-hand entries aggregation by financial dimensions Weekly	Tool to aggregate InventSum rows with zero quantities. This is basically extending the previously mentioned cleanup tool by also cleaning up records which have field Closed set to True! The reason why this is needed is basically because in certain scenarios, you might have no more quantities in InventSum for a certain combination of inventory dimensions, but there is still a value. In some cases, these values will disappear, but current design does allow values to remain from time to time. If you for example use Batch numbers, each batch number (and the combined site, warehouse, etc.) creates a new record in InventSum. When the batch number is sold, you will see quantity fields are set to 0. In most cases, the Financial/Physical value field is also set to 0, but in Standard cost revaluation or other scenarios, the value field may show some amount still. This is valid, and is the way Dynamics 365 for Finance and Operations handles the costs on Financial inventory level, e.g. site level. Inventory value is determined in Dynamics 365 for Finance and Operations by records in InventSum, and in some cases Inventory transactions (InventTrans) when reporting inventory values in the past. In the above scenario, this means that when you run inventory value reports, Dynamics 365 for Finance and Operations looks (initially) at InventSum and aggregates all records to Site level, and reports the value for the item per site. The data from the individual records on Batch number level are never used. The tool therefore goes through all InventSum records, finds the ones where there is no more quantity (No open quantities field is True). There is no reason to keep these records, so Dynamics 365 for Finance and Operations finds the record in InventSum for the same item which has the same Site, copies the values from the Batch number level to the Site level, and deletes the record. When you now run inventory value reports, Dynamics 365 for Finance and Operations still finds the same correct values. This reduced number of InventSum records significantly in some cases, and can have a positive impact on performance of any function which queries this table.
A608	A608 Cost calculation details Inventory management > Periodic tasks > Clean up > Cost calculation details Monthly	Used to clean up cost calculation details.
A609	A609 CDS – Post integration inventory journals Inventory management > Periodic tasks > CDS integration > Post integration inventory journals	Fetches journals from the CDS (Common Data Service) and posts them. This applies only of the CDS is in use.

Warehouse management batch jobs

ID	Name, path and recurrence	Description
A700	A700 Work creation history purge Warehouse management > Periodic tasks > Clean up > Work creation history purge Weekly	This is used to delete work creation history records from WHSWorkCreateHistory table based on number of days to keep the history provided on dialog.
A701	A701 Containerization history purge Warehouse management > Periodic tasks > Clean up > Containerization history purge Weekly	This is used to delete containerization history from WHSContainerizationHistory table based on number of days to keep the history provided on dialog.
A702	A702 Wave batch cleanup Warehouse management > Periodic tasks > Clean up > Wave batch cleanup Weekly	This is used to clean up batch job history records related to Wave processing batch group.
A703	A703 Cycle count plan cleanup Warehouse management > Periodic tasks > Clean up > Cycle count plan cleanup Weekly	This is used to clean up batch job history records related to Cycle count plan configurations.
A704	A704 Mobile device activity log cleanup Warehouse management > Periodic tasks > Clean up > Mobile device activity log cleanup Weekly	This is used to delete mobile device activity log records from WHSMobileDeviceActivityLog table based on number of days to keep the history provided on dialog.
A705	A705 Work user session log cleanup Warehouse management > Periodic tasks > Clean up > Work user session log cleanup Weekly	This is used to delete work user session records from WHSWorkUserSessionLog table based on number of hours to keep provided on dialog.
A706	A706 Wave processing history log cleanup Warehouse management > Periodic tasks > Clean up > Wave processing history log cleanup Weekly	This is used to clean up history records related to Wave processing batch group.
A707	A707 WMS Replenishment Warehouse management > Replenishment > Replenishments	Calculate location replenishments on the warehouse locations.
A708	A708 Automatic release of sales orders Warehouse management > Automatic release of sales orders	Releases sales orders to the warehouse so that the picking can start.

Monitoring Distribution jobs

The Retail IT workspace is specifically created to monitor all distribution jobs, sending data to RCSU and POS. If there are failed sessions, they will be seen here. Also the current download (To RCSU) and Upload (From RCSU) is shown here.

Monitoring Batch jobs

The best place to monitor all current batch jobs is through the system administration workspace. Here all failed, running, waiting and withheld batch jobs are shown. This workspace also has additional system administration features.

As a consultant meeting with prospective manufacturing business clients, the first thing I want to examine is the data structures in their current ERP system. Often, the data structures and what’s stored there can tell me a lot about the workings of a business.

Analyze the warehouse table

The warehouse table can reveal a ton about a company’s supply chain. One of the trickiest parts of managing a multichannel brand is allocating the right products to the right channels. Sometimes organizations create virtual warehouses to “set aside” inventory for different customers or channels. The problem with warehouse tables arises when they become so numerous that they can no longer serve their purpose. How does that happen?

Because an ERP system can slice, dice, and segment your data almost any way you want, there is a tendency to overuse virtual warehouses. If your company serves multiple regions with multiple channels and customer tiers, you may have created dozens of virtual warehouses. Perhaps a certain region is a best buyer and needs to be serviced first. Or perhaps one of your customers has been with you from the start, and when the time comes to serve them, you want to guarantee that the inventory is there to fulfill their demand. It sounds like good business practice, right?

But what happens next? As you create more virtual warehouses for certain regions, customers, products, or circumstances, you may start to have virtual inventory overages and shortages. Nobody can forecast the future exactly. The demand distribution among regions, channels, and customers will vary, even if the total demand stays the same across time. If you have segmented the inventory virtually to match your demand slices, you may have caused yourself a bunch of virtual inventory problems. The more granular the segmentation, the worse the problem becomes. In a warehouse with a single physical location for a product, there may be three or four virtual locations in the system, causing all kinds of fulfillment issues.

Having too many virtual warehouses leads to other problems

When you realize that these virtual inventory issues are getting out of hand, you may come up with yet another brilliant solution - virtual transfers. What a great tool. Now you can start moving inventory virtually across these virtual warehouses to solve your virtual inventory problems. That seems like a solution, but it can quickly become confusing, and time-consuming. There are so many issues to resolve that you simply give up and ask your IT team to write algorithms to automate the virtual transfers. And on and on.

Stop the madness

This is where a good soft allocation system comes in handy. Instead of segmenting inventory, soft allocation pulls from a single inventory point, and allocates product based on rules-driven and prioritized demand and supply. It ends the madness of too many virtual warehouses and gives you a clear picture of exactly where you stand.

However, soft allocation isn’t one of the core features in Dynamics 365 or Dynamics AX – so you’ll need a solution to implement this effectively. Sunrise 365 for Supply Chain was designed for omnichannel companies to optimize their supply chains, and provides the tools, analytics, and dashboards to do so.

If you would like to know more about soft allocation and how it can relieve the pain of too many virtual warehouses, contact us at Sunrise Technologies.

You can read more on my blog: Virtual Warehouse Best Practices

By Cem Item for Sunrise Technologies, sunrise.co

About the Author

As the SVP of Global Business Development for Sunrise Technologies, Cem Item is a trusted advisor to many C-level executives in apparel, footwear, fashion, furniture, and consumer goods. His customers rely on his deep supply chain understanding in manufacturing, distribution and retail operations as well as hands-on technical and functional knowledge on Enterprise Resource Planning (ERP), Customer Relationship Management (CRM), Retail Management and Business Intelligence (BI) systems.

How to Increase Workplace Productivity with Arbela Workflow Manager

Video-2020 Enhancements to PrintVis Presented by ArcherPoint

Video: Highlights of the 2020 Enhancements to PrintVis

How Microsoft Dynamics 365 Delivers CRM – Part 3: Customer Service

Batch Jobs; Take control of the executions

Correctly connect to an Excel file in a Canvas PowerApp

[Model-Driven Apps] Learn how to sort Activities and control which fields to show on the Timeline Control in Unified Interface

Bundling and Sales Order Processing: Revenue Recognition in Microsoft Dynamics 365 Finance, Part 5

Phone Call Regarding Object Type in Microsoft Flow - Power Automate

Cdn Payroll Basic Personal Amount calculator

The spreadsheet

How to create a Dynamics 365 Sandbox environment

Customer Reminders – Notify Customers about Overdue Invoices

MSDyn365: Revenue recognition

D365 CE: Adding icons to views

Customer Insights and Dynamics 365 Customer Cards

Encumbrance Summary Inquiry Amounts Do Not Match Detail in Microsoft Dynamics GP

Collect does not collect Lookup value from CDS data source by default – Limitation?

Power Chat with Andre Margono

Checklinks “the keys record has been removed”

File Maintenance Error Message

What does this mean?

How can you check this yourself?

Virtual Warehouses: How Many is Too Many?

Analyze the warehouse table

Having too many virtual warehouses leads to other problems

Stop the madness

Using Patch function in canvas app to update a CDS record based on value of non-primary key field.

Video: Highlights of the 2020 Enhancements to PrintVis

The spreadsheet

File Maintenance Error Message

What does this mean?

How can you check this yourself?

Analyze the warehouse table

Having too many virtual warehouses leads to other problems

Stop the madness

Related Posts