cancel
Showing results for 
Search instead for 
Did you mean: 

How to refer to a fixed time period for KF calculations

Former Member
0 Kudos

Hi,

Whats the best method to refer to a fixed time period in a KF calculation. For example:

KF1: qty stored in Oct 2016 bucket.

KF2 calculation requires to refer to this specific time period value only.

Thanks!

Accepted Solutions (1)

Accepted Solutions (1)

mkorndoerfer
Contributor
0 Kudos

Hello Pravin,

Can you please explain what you're trying to achieve?

I don't think it's possible to define a fixed time period in a Key Figure calculation. According to our Model Configuration Guide - Using Time Periods in Key Figure Calculations, we have only 2 ways to define periods in a KF calculation:

  • $$PERIODIDCUn$$: Fixed variable for the current period.
  • PERIODIDn: Time period attribute

Best regards,
Matheus

Answers (3)

Answers (3)

ankpatel
Contributor
0 Kudos

Hi Praveen

Can you send mock-up example in excel?

Regards

Ankur

chakon
Explorer
0 Kudos

HI Pravin,

You can try HCI to extract the data for Product Dates and KF values and based on your required logic transform the data and update it in IBP.

Thanks,
Chandra

Former Member
0 Kudos

Thanks Matheus,

What we are trying is to have a KF2 populated with values from KF1 where the target time buckets are different at product level. Each product has a different start and end month and values need to be copied from a KF1 to target KF2 to those dates which are product specific. KF1 has values in historical time buckets which are different than the target time buckets where these values need to go and sit. These start and end dates can be made available for each product within additional attributes of the product.

Could the Copy Operator work with different product level offsets?

Thanks!

Pravin

mkorndoerfer
Contributor
0 Kudos

Hi Pravin,

Yes, Copy Operator accepts offset for periods. You can parameter PERIOD_OFFSET, in which negative values are for past periods.
See our SAP Help Portal Copy (COPY) Operator .

Best regards,
Matheus