IBP_LPA Static Aggregation Error

[HariMaradana]

Hi All,

My base planning level at QTRPRODLOC and my input KF@MTHPRODLOC.

I wrote an expression as given below:

1) At Request Level:

KF2@REQUEST = SUM("KF2@HRSQTRPRODLOC")

2) Add Calculation Definition

KF2@HRSQTRPRODLOC = IBP_LPA("KF1@HRSMTHPRODLOC")

My check was successful, but while activating I'm getting following error message.

"Activation stopped unexpectedly. Contact system administrator."

[Irmi_Kuntze · Accepted solution]

your input and output planning level must have identical time buckets with the small difference, that in the output there is no root set for any of them. What you try is not correct. What is the use case behind the KF1 and KF2, what are their meanings, why do you think you need to have this kind of calculation that you cannot directly build into the source KF and an additional planning level on monthly level?

My suggestions (as Ivan stated the issue is not due to LPA):

1) unbuild this in order to check if the planning area can be activated otherwise

2) re-build in the solution in correct manner - whatever that means in your case

Yours

Irmi

[HariMaradana]

Thanks Ivan for your response.

Sure, I''ll open an incident. I just want to make sure whether I did the right expression and right levels defined. Can you check and confirm my previous posts.

[former_member654033]

Refer PROJECTEDINVENTORY Key figure in SAPIBP1 as sample configuration for IBP_LPA function.

[former_member194529]

Hi Hari,

The "Activation stopped unexpectedly. Contact system administrator." error message may have a different root cause, not related to the LPA function. If you don't figure out, I suggest reporting an incident on SCM-IBP-CNF-ACT component for further assistance on determining the exact root cause.

Best,

Ivan

[HariMaradana]

Appreciated your time.....Sorry It didn't work...

I did as per your post

O/P PERPRODLOC planning level: Month,Quarter,Year - No root

I/P MTHPRODLOC planning level: Month,Quarter,Year - Month is root

KF2@PERPRODLOC = IBP_LPA("KF1@MTHPRODLOC").

For your information I'm looking a help on static aggregation LPA function.

[former_member654033]

Hi Hari,

Both the planning level HRSMTHPRODLOC and HRSQTRPRODLOC should have same set of attribute (Only difference is output planning level which is HRSQTRPRODLOC in your case, should not have any time attribute as root).

Please check your planning level configuration, if this is correctly setup or not. (Please check SAP Help or model configuration guide for more details)

Thanks

Girish

[HariMaradana]

Thanks Girish for your response.

As you said I have unchecked o/p planning level attribute root. It didn't work.

Here I'm mentioning my planning level config.

QTRPRODLOC - Quarter & Year(o/p level) Quarter is root attribute

MTHPRODLOC - Month,Quarter & Year(i/p level) - Month is root attribute.

While validating getting following warning message:

The HRSQTRPRODLOC calculation definition does not fulfill the attribute sourcing requirements.

Attributes missing from the output planning level:
MONTHWEIGHT,PERIODID3

I have followed the same steps as mentioned in Help config......

AGGRINVENTORY@TECHWKPRODLOC = IBP_LPA("INVENTORY@DAYPRODLOC")

AGGINVENTORY@REQUEST = SUM("AGGINVENTORY@TECHWKPRODLOC")

Only difference my example and help example:

QTR - Month( Parent & Child)

Technical Week - Day( Parent & Child).

[former_member654033]

Hi Hari,

Output planning level should not have any time root attribute, Looks like this is the mistake that you are making. In your case

QTRPRODLOC - Quarter & Year(o/p level) Quarter is root attribute, if you have make Quarter as a root attribute please take it out. Output planning level should have same number of attribute as input time level only difference is no time attribute should be root in output planning level. Please refer below example

Input Planning level - DAYPRODLOC (It will have DAY, PRDID and LOCID as root + other attributes)

Output Planning Level - DAYPRODLOCNOTIMEROOT - (It will have only PRDID and LOCID as root + all other attributes from DAYPRODLOC Planning level including time attribute, time attribute should not be marked as root)

Please refer "PROJECTEDINVENTORY" Key figure configuration in SAPIBP1

Thanks

Girish