Hi Zoey Mattison

To be clear, Sage X3 has not a velocity field in the data model. But, I expect we have all information needed to make the calculation (statistic? bespoke calculation?)

X3 manages ABC class to set the frequence for cycle count. The way ABC class are calculated is explained in the online hep:

https://online-help.sageerpx3.com/erp/12/staticpost/abc-class-calculation/

The process is based on a formula given you some flexibility on how the ABC class are assigned (based on quantity sold, or revenue generated or number of receipts and issues for instance). Past activities would be stored in tables ITMMVT and ITMMVTHIS accessible in the formula. 
If you are recently live with Sage X3, you won't have enough information to run this process for the moment. In addition, I believe only event in the current year are processed so you usually run this process at the end of the year and not in january.

Julien Patureau Thanks!

We have been using sage since June of 2020, so it's been about 2 and a half years. I don't think a single ABC calculation has been done. I noticed in the screen (FUNSTKA) there is blocks where you can change the percent, which is great so we can match it up to Netstock's percents. (A: 80, B: 16, C: 4). But the problem is calculating their velocities, which I read here: https://www.netstock.com/blog/how-to-create-an-effective-abc-analysis-to-optimally-manage-inventory/ 

is done by issues in a year times by forecasted demand instead of product cost.. Do you know if forecasted demand like that is stored somewhere in Sage? I could use some logic to apply it to the product formula field in cycle counts.

Zoey Mattison said:

Do you know if forecasted demand like that is stored somewhere in Sage?

If you are using the forecast function (GESORZ) or SOS import template, then you can stored in ORDERS table forecast events. To ensure to select only forecasts you need to check that WIPTYP = 1 and WIPSTA = 3.

But the problem is ORDERS is not accessible in the formula so I am afraid you would need some development here.

Or you create a bespoke field in ITMMVTHIS which would be the forecats demand in 12 months for the related product - site and period. After populated the information from a custom import, you should be able to use it in the formula.

Thank you for your answers as always Julien Patureau!

Since Netstock overrides our Sage ABC codes and displays its own extended calculation with velocity anyways, we've decided to use the ABC Calculation tool to set our internal sage % for ABC to match the Netstock % brackets (I noted above what they are). And then we just won't worry about the velocity part, and will instead ensure all of our stock is categorized as A B or C properly. (It's all 'D' right now lol). For the purpose of a cycle count I think this will be sufficient since I am only trying to count 150 SKUs per day of our "OK" status items (custom field), and being able to further limit that to A status will be a big help in making sure our fastest and highest price items are the ones getting counted first.

Unfortunately I do not know enough to implement the development you've mentioned there. It is an interesting idea, so I will pass it on to my leader.