kurthatlevik: Retail statement trickle feed (public preview)
Retail statements are one of the most important (and complex) processes a retailer have. It’s where the retail sales and transactions are being transformed to become physical and financial transactions so you can see the sales in finance and in inventory. Retail statement calculation and posting have been covered many times in my blog posts and Microsoft have a large set’s of article on doc’s on the matter. The amount of transactions retail statements calculates and post is to my knowledge THE most intense in the entire Dynamics 365 solution. Imagen that every sale, in every store is being processed. For larger retailers Dynamics 365 for Retail are processing millions of transactions daily. This area really put’s computational pressure in the systems and is also one of the areas where Microsoft is investing heavily.
Since the start of D365 there have been done hundreds of improvements on retail statement posting, and the next “big thing” is Retail Statement trickle feed. One of the pain’s in today’s solution is a significantly delay between the when the retail sales have been conducted, and when the inventory transactions have been financially posted. And in short, when the inventory transaction gets a financial status like “Sold”. Why is this important? Because the inventory transactions define on-hand values, as again it defines how the master planning/replenishment is calculated. We want this to be as accurate and up to date as possible. Any delays in having accurate on-hand influences planned purchase orders. Also the ability to spread out the processing of transactions through the day will reduce the amount of “spikes” in the Azure SQL load, making the nightly timeslot more open for other high intensive transaction processing tasks.
Microsoft have made the following improvements to the statement posting process:
When finally released (GA) I hope that the new the new feature management is used for enabling this.
When this is done, you will see a set of new menu items. Under the menu \Retail\Retail IT\POS Posting.
The sequence of these batch jobs is to be able to financially post most of the transactions, and the financial statement posting will only be used to calculate and post any counting variances. There is no need to run the “Post inventory” job any more.
If we look into the Retail Statement form, we now have the possibility to manually create transaction posting and financial reconciliation (That in the essence is the financial statement).
When creating a “Transactional posting”, we see that the form is a bit changed compared how it was before. There a no lines related to payments, and this is logical as the purpose of the transaction posting is not about payment lines. So no need to have this in this type of statements.
When posting the transactional statement, the following steps are performed:
When calculating and posting a financial statement, you see the more traditional statement posting screen, where you have the payment lines:
The steps in the posting is the following:
The summary of this, is that Dynamics 365 will with trickle feed support a much faster updating frequency to get proper on-hand values and scalability. Since the transaction statement posting will be running more frequently it also means that there will be a very small retail financial statement posting in the evening/night. The transactions will be smaller and therefore also faster to post. But there are a few things to keep in mind. If you trickle feed too often, you will miss out on the transaction aggregation, and will have to process many more sales order invoicing per day. This can again increase the load in your system. This feature will also increase scaling of the system, as posting of transactions can be better load balancing among multiple AOS-batch services. I also have a feeling that there will be more features in this area to come, that will further enable “close to real-time master planning”, “inventory services”, and “close to real-time power-BI reporting”.
Great work to the Microsoft team working on the retail statement processing. Next on customers wish list is a super-duper-fast invoicing service of sales orders(retail), as this still is the most resource demanding task in the processing of retail transactions.
Here is a small joke for all of you that don’t care about retail statement posting
Расскажите о новых и интересных блогах по Microsoft Dynamics, напишите личное сообщение администратору.
|kurthatlevik: D365F&O Retail: Combining important retail statement batch jobs||Blog bot||DAX Blogs||0||19.11.2018 12:11|
|dynamicsaxse: November 2018 Release – Dynamics AX2012 R3 update||Blog bot||DAX Blogs||0||15.11.2018 09:11|
|kurthatlevik: First Aid Kit for Dynamics 365 for Retail; A messy blog post||Blog bot||DAX Blogs||0||10.05.2018 17:11|
|palleagermark: Public Preview of the new Microsoft Dynamics AX is now available on PartnerSource and CustomerSource||Blog bot||Microsoft и системы Microsoft Dynamics||1||21.12.2015 13:30|
|kurthatlevik: New Microsoft Dynamics AX – A guide for using retail sales prices and discounts||Blog bot||DAX Blogs||0||01.12.2015 18:12|
|Опции темы||Поиск в этой теме|