AasKF Alternate Configuration

[willsuus]

It seems like I need to reload the ZSMDT master data every day for the AasKFs that I have changed to the Alternate Configuration to work correctly. Is this normal?

So, if I query them before doing the reload but, after I do the reload, they appear. I thought this MDT only had to be loaded once?

[willsuus]

As additional information, I can do a query prior to the reload of the MDT and include ZAAKF as a key figure and it shows it as null with all of the time periods. But, as described previously, the AasKFs that are loaded daily do not show up until after that load.

[willsuus · Accepted solution]

The issue was that the ZSMDT master data needed to be reloaded every day. This is the one line load of "1;<null>". The root cause of the problem was that the "Purge Null KFs" job that is run daily was wiping out this entry. The workaround that we chose was to add a CPI job that reloads this MDT daily.

[AyanBishnu]

Please share the problem statement in details and provide some screenshots if possible. So what i understood from your statement based on that I can confirm the following.

When we create AAK, by default it will be populated with the value that has been mainatined in the attribute for the required MDT. And for how many period you want to display the values is governed by the from and to period that we maintain while creating the AAK.

Now if we make the AAK editable, then that AAK will work like a normal KF to some extent. Lets say i have AAK for exchange rate where the AAK is editable. So I can overwrite the defualt attribute value in the KF from the planning view. Those overwritten values gets stored in the KF as long as we dont chnage the value in the attribute. If the value in the attribute is updated then the AAK will again replace the last updated value witht the new updated attribute value. This is normal behaviour of AAK and ideally we should focus to move away from AAK and convert those AAKs to normal KF wherever posssible, as AAKs have some max time serires restriction of 10 mil records and too many AAKs impacts the performance of the planning view and its associated features.

If this is not what you are looking for please share more details pertaining to your issue