IBP Price attribute as key figure

[peter_casper]

Dear community,

I am currently struggeling with some basic feature which I don't get working.

I have attached a custom attribute PRICE and CURRID to the MDT PRODUCT.I marked PRICE as attribute as a key figure at LOCPRODCUSTCURRWEEKLY level. Additionally the prices have been maintained for MDT PRODUCT.

I also put a key figure calculation as following in place:

Now I am struggeling to get the price value displayed in every weekly bucket. Effectively this key figure is empty. Which calculations do I miss? Is it necessary to add something else to get the single price value displayed for every week which is attached to the Product?

Seems to be some basic steps I am missing.

Thanks upfront

Peter

[peter_casper]

Hi all,

after a couple of trial and errors sessions I finally made it work getting the product related price attribute properly published and converted (Currency + UoM) on a weekly level. I am still not sure why it wasn't successful by incorporating all calcualtions into one KF only nevertheless I would like to share my approach.

1. Step

I split the calculation into two portions / key figures. The first step just published the product related price attribute on a weekly level.

2. Step

I added a new stored KF and included the conversion calculations. This will be the key figure which I am going to use for further revenue calculations.

Perhaps this is also helpful for you in case someone faces the same challenge.

Cheers, Peter

[piyush_parekh · Accepted solution]

Hi Peter,

Are non-time root attributes of the base planning level of this attribute as a key figure same as that of key attributes in Product MDT to? Assuming key attribute of Product MDT is product ID, you can create attribute as key figure at WKPROD base planning level in which product ID will only be a root attribute.

Please refer below section in model configuration guide for more details.

https://help.sap.com/viewer/bf99e931b8d44aafb4e306ec3602cbdd/1908/en-US/c3bfcf3581bb4973813452b3c347...

Regards,

Piyush

[peter_casper · Accepted solution]

Hi Piyush,

the SAP documentation is known but frankly spoken it's not very comprehensive in this regards. But your assumption is correct, the non-root attributes of the base planning level of this attribute aren't the same like in the PRODUCT MDT. I will try as you proposed and create a new planning level. Will let you know if it worked out.

regards Peter

[peter_casper · Accepted solution]

Hi Piyush,

somehow I don't get it working. I oriented myself at the key figure EXCHANGERATE where the actual exchange rate gets stored at MDT level with the same name. The key of this MDT is CURRID and CURRTOID. The calc of KF EXCHANGERATE looks like this:

EXCHANGERATE@REQUEST = AVG( "EXCHANGERATE@CURRFRTOWEEKLY" )

The planning level CURRFRTOWEEKLY consists out of 3 keys, i.e. week, CURRID and CURRTOID. The exchange rate gets properply published for each week although it's a static master data attribute (as a key figure).

It did the same for MDT PRODUCT which has an attribute called price. Additionally I defined a planning level called PRODWEEKLY with the key week and PRDID. The KF calculation looks as following:

IBPPRICE@REQUEST = AVG( "IBPPRICE@PRODWEEKLY" )

Unfortunately I don't get the KF displayed in the frontend. I would first need to create planning objects at PRODWEEKLY level which does not help either.

Any ideas which step I am missing?

regards Peter

[piyush_parekh · Accepted solution]

Hi Peter,

You are on the right track and referring a perfect example of an attribute as a key figure. Please refer below steps if you're missing anything -

1. Create an attribute of type "Decimal" (only decimal is supported) and add it in Product MDT - say ZPRICE. Click on Save.

2. Click on Planning Areas and Details section. Search for ZPRICE after selecting Available Attribute from the dropdown. You should find it under Product MDT. Click on Key figure checkbox. Here, you will get a pop-up.

3. Key figure ID will be same as that of attribute ID. Choose planning level at which key figure is to be created. Select planning level PRODWEEKLY in your case from Choose Planning Level dropdown. Click on OK to continue. Addionally, you can define "From" and "To" periods (optional)

4. Move to Key Figures section and search for ZPRICE. Mark it as "Stored". Change the Aggregation mode to "AVG" and disagg mode to "COPY". Select appropriate Weekweight factor. Add a request level calculation as -

ZPRICE@REQUEST = AVG (ZPRICE@PRODWEEKLY). Click on validate and make sure ZPRICE as "Stored" in this calculation. Activate the planning area.

(Add any additional calculation if required - e.g. Currency conversion calculation will be as follows -

ZPRICE@PRODWEEKLYCURRCURRTO = "ZPRICE@PRODWEEKLY" x "EXCHANGERATE@CURRFRTOWEEKLY"

You may need to create a new planning level "PRODWEEKLYCURRCURRTO". Post which, change the request level calculation and mark input key figure as calculated. Refer any standard revenue key figure having currency conversion. May be as a first step, you can configure ZPRICE without any conversion and add currency conversion later.)

5. Add a new product MDT record and maintain a value in ZPRICE attribute. It should reflect in ZPRICE key figure. In case of configuring it with currency conversion, make sure you've maintained values in Exchange Rate MDT/key figure.

Hope it helps!

Regards,

Piyush

[peter_casper · Accepted solution]

Hi Piyush,

your comprehensive step by step guideline actually did the trick. I had already applied the same steps like you sketched out but I overlooked to make this key figure being editable by the system. Now it gets properly displayed in each week according to the product master data value. I will now continue to enhance the calculation by adding currency conversion capability as well.

Thanks a lot for taking the time. Highly appreciated from my side.

best regards, Peter

[peter_casper]

Hi Piyush,

sorry for keeping bothering you. I continued now with incorporating currency conversion according to standard setup and the proposal which you made. I configured a new planning level PRODWEEKLYCURRCURRTO which consists out of Product, Currency and CurrencyTo.

Accordingly I adjusted the base planning level of the attribute as key figure IBPPRDPRICE and changed it from PRODWEEKLY to PRODWEEKLYCURRCURRTO, incl. the calculations as well.

Calculation logic

Input key figure settings @PRODWEEKLYCURRCURRTO

Input key figure settings @REQUEST

So far, so good. The activation worked w/o an error but I can't update the Product master data which issues an error message.

MD upload error

Actually the values seem to be assigned wronly now. The yellow marked column displays the intended unit price and the unit price would actually be the productid. It looks like that there is still a wrong or even a missing calculation.

Maybe you know what went wrong.

regards Peter

[piyush_parekh]

Hi Peter,

I understood the next set of requirement from your another question posted in the forum and what exactly are you trying to achieve. In the absence of "CURR" dimension in price key figure, it will not be possible to configure currency conversion as simply there in no common attribute against which system can convert the values. Please refer standard currency key figures. It would be similar to below calculation -

Actualsrev@WKPRODLOCCUSTCURRCURRTO = Actualsrev@WKPRODLOCCUSTCURR x Exchangerate@MTHCURRCURRTO

The missing part of the puzzle is "CURR" dimension. I realized a mistake in my earlier comment where I missed out on this part. Apologies for the same. To bring in "CURR" dimension, I have a suggestion -

Configure another MDT - PRODUCTCURRENCY with product, currency as root attributes and configuring PRICE attribute as key figure here at WKPRODCURR level which meets the requirement. However, you will need to additionally maintain data in this MDT. You can use this key figure to multiply with quantity key figures having product dimension and arrive at revenue without any additional intermediate key figures. Further currency conversions can be added as usual. Please refer any standard rev/price key figures for currency conversion logic.

Another suggestion, if you are looking for a price key figure at PRODLOCCUSTCURR level only, you can create MDT at PRODLOCCUSTCURR level (instead of PRODCURR as mentioned above).

Regards,

Piyush