IBP UoM Conversion Issue

[willsuus]

I have a key figure (definition below) that is not calculating correctly when I have the @REQUEST level use the MTHPRODCOTUOMTO planning level. The test product I am using has a PC conversion of 1 and the planning view is at PC so I do not know what would be causing this problem.

The other strange thing that is happening is if I just have the planning view with the KF with no UOM conversion in the KF definition, it shows as it is below. If I add in the KF with the UOM conversion in the KF definition, the one without changes to the values in the added KF (i.e. USC1~KF with no UOM conversion changes from 9214 to 9019).

Other key figures that I use the UOM conversion with work fine.

ZCONSENSUSDEMANDBYPRODCOT@REQUEST = SUM("ZCONSENSUSDEMANDBYPRODCOT@MTHPRODCOTUOMTO")

ZCONSENSUSDEMANDBYPRODCOT@MTHPRODCOT = "CONSENSUSDEMAND@MTHPROD" * "HZDELIVQTYENDCUSTPROPBYCOT@PRODCOT"

ZCONSENSUSDEMANDBYPRODCOT@MTHPRODCOTUOMTO = "ZCONSENSUSDEMANDBYPRODCOT@MTHPRODCOT" * "UOMCONVERSIONFACTOR@PRODUOMTO"

[willsuus]

It appears I lost the screen shot I had included in the original message.

KF with no UOM conversion KF with UOM conversion

USC1 Mar 2021 9,214 9,019

USC2 Mar 2021 37,100 36,317

USD1 Mar 2021 371,532 363,679

USD2 Mar 2021 1,334,561 1,306,359

[willsuus]

I did validate that the MTHPRODCOTUOMTO planning level has the UOMTOID as a key.

[Irmi_Kuntze]

Hi Susan

I never saw such behavior as you describe, that 2 independent KF have impact on each other. If MTHPRODCOT and MTHPRODCOTUOM are identical except that the MTHPRODCOTUOMTO has the additional UOMTOID, and MTHPRODCOT has the same attributes from the product then PRODCOT, it should work.

Have you tested to create just a simple storage KF on that level and test the conversion?

Split calculation can lead to "interesting" results when the KF that are involved in the helper are not initialized in all periods, so by removing that split calculation you can check if the planning level is root cause. Here again comparing one storage KF on that level with and one without the conversion.

And check that the UoMconversionfactor is assigned in the field "Convert using:"

If that all does not help, open an OSS message (with screenshots 🙂 )

Good luck

Irmi

[willsuus]

Thank you for your help. I have opened an incident (with detailed explanations and screenshots) as everything you had me check was set up correctly.

[Irmi_Kuntze]

I have to admit that I do not understand what you mean with "f I add in the KF with the UOM conversion in the KF definition, the one without changes to the values in the added KF (i.e. USC1~KF with no UOM conversion changes from 9214 to 9019)." Actually, are you talking about 2 different KF that have the same split logic, but one has UoM and the other not?

But if you have 2 KF that have no dependency between each other, and when you display only KF1 the value is different then f you add KF2 to the view, that indeed would be very weird and might be a bug

Without a more clear description and without system access, I dont see how I could help you, sorry

Irmi

[willsuus]

Yes, it is two different key figures where one has the uom conversion and the other doesn't. And, yes, they have no dependency on each other so it is very strange that the one changes when the other one is brought into the planning view.

I appreciate you trying to help and apologize that I have not been clearer with the issue. As I do not have this issue with any other key figure and the planning level I am using, MTHPRODCOT, is a new planning level. I am thinking that that may be the issue.

[Irmi_Kuntze]

It is a bit hard to understand without screenshot and without knowing what USC2 is (the product? a KF?)

Calculation looks ok to me on first glance

So you do see a value, but not as expected? You have maintained in the uomconversionfactor for your product with uom = PC and uomto = PC the value 1? You have maintained in your product master data the baseUoM = PC?

Screenshot would REALLY help VERY much...

[willsuus]

Thank you for your quick reply. I tried to put a screenshot in, but it didn't save it when I submitted the question.

USC2 is a sales office

Mar 2021 is the date

and the next two values are the two KFs.

I believe there must be an issue with the planning level setup as this is the only key figure I am having issues with with the uom conversion.

I will look more into the planning level configuration to see if I can resolve the issue. The planning level, MTHPRODCOT is basically an existing planning level, MTHPRODCUST (month / product / customer), with the key on the customer field removed and placed on the COT (sales office).