You’re offline. This is a read only version of the page.
30
On our older projects we have preferred to use the legacy statement posting process. The main reason is the aggregation of sales - we have many anonymous sales on POS that can be aggregated on store + day level. We are also using the inventory reservation job to decrease the inventory during the day.
Now the legacy statement posting method is to be discontinued. Are there some ways how to achieve as much aggregation as possible with the trickle feed? Any thoughts / best practices?
Our eCommerce solution is not integrated via channel database and we mainly need the availability updated for the eCommerce (=in D365). So for us it is choosing from two evils - running the transactional posting less often, with more aggregation but delayed onhand update, or more often, with more accurate inventory but less aggregation and more transactions.
BTW, how do you setup the aggregation with the trickle feed?
The main functionality that you are going to miss with trickle feed will be the Post Inventory job to reserve the items during the day. "Channel side inventory calculation" should keep you somewhat informed about the current inventory levels if all the stores are connected to the same channel database. However, if you do frequent inventory transactions (Transfer orders, PO Receiving, DOM fulfillment) on the store warehouses, the data may not be very reliable.
As for maximum aggregation, the best option will be to set the trickle feed to run only once or twice a day.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,253
Super User 2024 Season 2
#2
Martin Dráb
230,188
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (