Hello Eddy
I can understand that it makes sense to use cost as an AAK since the value mostly stays uniform across the planning horizon.But thier are few things that you should keep in mind while deciding on AAK vs normal KF.
The length from a to period for a AAK is directly proportional to runtime performance. Hence I would suggest that as long as your from and to are limited to a range of 165 periods, you are good. That mostly will make sense if your planning horizon in in monthly bucket or the AAK you are using is relevant for future and you have approx 2 years in future all in CWK or TWK.
Also having more AAK's and that too with high no periods increases your time seris objects exponentially and thier is a limit of 10 mil time series record, which can be breached if you are using many AAKs within a planning area and that too for bigger period range.
AAKs are frequently used as source KF for copy operators.and if thier is some filter conversion logic in the target KF then in some cases the values will not be populated correctly.
Enough scaring :). In short few AAKs with limted period range within a planning area is ok. But you need to know the limit which depends totally how the solution is designed. Also an chekcpoint please keep a track of your time series history in case you are using many AAKs within a single planinng area.
Regards
Ayan
Bluesky
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.