cancel
Showing results for 
Search instead for 
Did you mean: 

Key figure calculation to use current technical week

reddyatoz
Explorer
0 Kudos

Hi All,

We have a requirement to sum the KF1 values in KF2.

For that i have used cumulative aggregation in KF2. but when i aggregate from technical week to week all values are doubling where technical week present. To over come that i have used same calculation as projected stock.

Now the system is taking values from TWb only, but business requirement is to calculate current running week. ie., TWa. If current running week is TWb then system has to calculate accordingly.

Need KF calculation to overcome this issue.

Br

Kumar

Accepted Solutions (1)

Accepted Solutions (1)

riyazahmed_ca2
Contributor
0 Kudos

Hi Kumar,

I have the below understanding on your requirement.

1) You want to perform a sum based cumulative aggregation of KF1 and show the result on KF2.

2) Cumulative Aggregation is doubling the numbers wherever split weeks are available for months.

3) Start Period of your calculation do not respect starting technical weeks as it sees the calendar week on whole. You are expecting If starting TW is A, then calculation should start at A, or if starting TW is B, then calculation should start at B.

Assuming that you acknowledge me all the 3 above, below are my suggestions. You can follow either of them for your calculations.

1) Perform Aggregation as Avg, Min or Max of KF1 value before using them in Cumulative Aggregation on KF2

Lets say you have KF1 at PL1 Planning level and KF2 at Planning Level PL2. Copy the PL2 and create PL2_COPY Planning Level. Then you will have below calculations.

KF1

KF1@REQUEST = SUM( KF1@PL1[Stored] )

KF2

KF2@REQUEST = SUM(KF2@PL2[Calculated])

KF2@PL2 = IBP_CAGGR(KF2@PL2_COPY[Calculated], ''Sum'', ''Forward'', ''CURRENTFUTURE'')

KF2@PL2_COPY = AVG(KF1@PL1[Stored]) or KF@PL2_COPY = MAX(KF1@PL1[Stored]) or KF@PL2_COPY = MIN(KF1@PL1[Stored])


2) Determine which Period of Technical Week to be exposed for Cumulation.

Lets say you have KF1 at PL1 Planning level and KF2 at Planning Level PL2. Now you have to create one more KF called KF3 on PL1 planning Level.

KF3 will be used for determining which period has to be considered for cumulation if there is a week split. We can do this by updating 1 and 0 for representing period inclusion and exclusions.

Then we have have below calculations.

KF1

KF1@REQUEST = SUM( KF1@PL1[Stored] )

KF2

KF2@REQUEST = SUM(KF2@PL2[Calculated])

KF2@PL2 = IBP_CAGGR(KF2@PL1[Calculated], ''Sum'', ''Forward'', ''CURRENTFUTURE'')

KF2@PL1= KF1@PL1[Stored] * KF3@PL1[Stored].

PS: KF3 need not be defined as PL1, instead any higher level above PL1. Eg: If PL1 can be TWPRODLOCCUST, KF3's base Planning level can be TWPROD, TWPRODLOC, TWPRODCUST, TWCUST or TWLOC level. If you want to perform at period level, then introduce the attribute ATTR1(eg,.) to time profile and add 1 and 0 in that attribute at time periods. 

Then the 3rd calculation of KF2 will be as below.KF2@PL1 = KF1@PL1[Stored] * ATTR1


Let me know for any queries/concerns.

Best Regards,

'Riyaz'

Answers (1)

Answers (1)

Irmi_Kuntze
Advisor
Advisor
0 Kudos

Your question is a bit confusing, which I assume is that no one has answered yet.

Can you provide a mockup of what you want to achieve best case with formula, in which format data is available and which level is target?

If you e.g. have technical weekly values and want to display in weekly sum the cumulation, you cumulate directly on weekly level. if you want to have both display in weeks and technical weeks the cumulation, you would calculate technical week level and work with last period aggregation IBP_LPA.

I am off for vacation now, so please don't expect any further replies, sorry. Hopefully the LPA link might help you

Happy Holidays, Irmi