No Data Displayed (No Data Found) in Excel Planning View SAP IBP

[former_member310060]

Hi all, I need your quick help.

For some reason, we can't display our key figure data on Planning views anymore. Master Data with Planning Object sheet is showing, that the data for the key figure is available. Also the planning objects exists. We got Product_Location, Customer_Product, Customer_Source, Unit of Measure conversion Master Data maintained.

Even if we add new Data and Planning objects manual, together with the Master Data and Key Figure Data they are not displayed on Excel Planning View. In one Planning Area all the old data, which was shown the day before, is also not displayed anymore. In another Planning Area, the Old Data (IBP Best Practice Data) is still shown, but new created Objects are not shown. I tried in a third planning area the same thing, and there it worked.

Anyone got an idea what else I can check? I'm running out of ideas.

best regards

Bastian

[Irmi_Kuntze · Accepted solution]

well, I would need to see the system to tell for sure, you should open a ticket to not loose time, and mention the upgrade in the header as that may speed it up.

However:

What happens to your new kf on WKPRODLOCCUSTBU if you do NOT work with Ulm conversion, do values show up then? And what is BU, is it based on an own MD type or just an attribute of whatever? Does BU provide an own new root to the planning level? Can you provide an overview of the roots and non-roots of both (or better to all four) planning levels? And did you add the new non-roots to WKPRODLOCCUSTBUUOMTO as well? (you have to). And if those new attributes would be valid to WKPRODLOCCUST, you should add them there as well, and to all other levels that contain the same roots of the new attributes. With the new configuration you finally can do mass assignments to planning levels.

Check online document on what’s new in model config: https://help.sap.com/viewer/ed738cdf19b24426a396321195f6c65d/1911/en-US/ddbc1baa02824b479a34bd65bc65...

I think you have at least to solve your last error ‚Input Planning Level Does Not Contain All Root Attributes of Base Planning Level; Calculation Is Not Used‘ as docu states ‚Furthermore, the calculation is not used in any REQUEST level calculation in the calculation graph.‘ I don’t have much experience yet myself with 1911, but this does sound as if it could have impact on the request level...

good luck, and please post the result as this may happen to others as well

Irmi

[former_member310060]

I think WKPRODLOCCUST is the previous base planning level. It was changed to WKPRODLOCCUSTBU due to additional attribute requirement. But since other key figures are still using the old calculations, it was not removed. That way it was all working until Thursday. What also happend Thursday, was an add of two new non-root attributes to planning level WKPRODLOCCUSTBU. Usually this shold not affect existing values right? However, still a complete purge and re-upload of all master data and key figure data was done, to make sure no inconsistency appears.

[former_member310060]

I tried to add a complete new key figure to planning level WKPRODLOCCUSTBU and created values for it. This data was not displayed. So I created a new key figure for planning level WKPRODLOCCUST and that worked fine. So I am starting to think our issue is related to our planning level WKPRODLOCCUSTBU. But I can't figure out what this could be. As I said, we added two new non-attribute to planning level WKPRODLOCCUSTBU. Any Idea if this could be the reason?

[former_member310060]

Yes sure. We basically had to suppress all errors. But the one referring to the Key Figure we are most interested in, is just this one.

I already tried to change it, but key figure is still not displayed. Or do I need to add Input from Base Planning level WKPRODLOCCUSTBU instead of WKPRODLOCCUST?

surpressed-error.png surpressed-errors.png calculation.png

[Irmi_Kuntze]

that sounds really weird...

What happened since yesterday, any System upgrade?

In most cases where data do not show up that I know, it is either the Ulm conversion (did you try to change the factor forth and back?), or there is some calculation on request level which is messed up accidentally like summing up values from a wrong kf or wrong planning level.

If younger sure this is not the case, I think you need an OSS ticket because without system access it would be extremely difficult to Analyse the root cause

Irmi

[former_member310060]

Hi Irmi,

The system was upgraded to 1911. I have noticed, that the planning area was activated after that and activation error had to be suppressed. Those error are related to KF calculation. Could this be the reason?

[Irmi_Kuntze]

So your BPL of Actuals is WKPRODLOCCUSTBU? And you use WKPRODLOCCUSTBUUOMTO in request level. So why do you need the calculation on WKPRODLOCCUSTUOMTO at all?
And do both planning levels share completely the same attributes except the additional ones from the ‚BU‘ part?

[Irmi_Kuntze]

could be

So not all if but just some are affected?

Po at so,e Screenshots of the kf calculations and the error message if you please