Skip to Content

Time Fence KF Values from Attributes in IBP

I have a custom compound Opportunity MD type that has been successfully added to my planning area. Is it possible to have an custom Attribute of Start Date and End Date that are respected within IBP? That way I can have a calculated KF that only returns a value, if the time bucket is within the 'fence'?

I tried to using an interger and uploading values ZSTARTDATE = 20200501

And then within the calculation saying

if("zstartdate" > periodid5, value returned, NULL)

This did not work. Is this going to be possible?

Add comment
10|10000 characters needed characters exceeded

4 Answers

  • Best Answer
    Posted on Mar 26 at 09:22 AM

    Alternatively to the PERIODID-approach, you can add an integer attribute to your time profile that has the start date of the period. example: For the daily bucket for March 26, the value of your attribute would be 20200326, for the weekly attribute it would be the Monday of the week 20200323, etc.

    If you than have your integer attribute for start and end (as described by yourself already), you can compare both attributes as they have same format. Disadvantage is that you need additional attributes to time profile - but only once

    The usage of PERIODID has the disadvantage that the values are rather cryptical, as in the screenshot above the value 26802 being 1/1/2016, so your start and end dates would need to translate to that for the maintenance - for very entry. However, the IBP standard solution using PERIOD has the advantage that you can easily identify today by e.g. comparing IF( PERIODID4 >= $$PERIODID4CU$$, - without the need of any additional integer attribute to the time profile

    Using time stamp attributes is not so easy as you cannot directly compare them to PERIODID.

    Add comment
    10|10000 characters needed characters exceeded

  • Posted on Mar 26 at 06:49 AM

    Hi Dan,

    Along with the Start Date & End Date Attributes, Also add the attributes to specify PERIODID. ie,. Add Start Date(TP) and End Date(TP) where TP is Technical Periods.

    Eg: You will populate TP as 26802 if date is 1/1/2016. Then change your calculation to Start Date(TP), it will work.

    ibp-cal.png (13.8 kB)
    Add comment
    10|10000 characters needed characters exceeded

  • Posted on Apr 15 at 02:22 PM

    Thank you for both your suggestions. I ended up adding an extra time attribute (as suggested by Irmhild) and it works like a champ. For our users, being able to utilize a 'YYYYMMDD' attribute was easier, rather than using PERIODID.



    Add comment
    10|10000 characters needed characters exceeded

  • Posted on Apr 29 at 02:19 AM

    Hi Dan,

    Please check if you can use DAYSBETWEEN Function.

    DAYSBETWEEN (LONGDATE(''2017-01-30 23:59:59''), "FORECASTENDDATE" ) - ( "$$PERIODID0CU$$" - 27197 )

    Note – 27197 denotes PERIOD ID for ''2017-01-30 23:59:59'' from respective time profile of day level. and FORECASTENDDATE is like a master data TIMESTAMP attribute maintained in YYYY-MM-DD format



    Add comment
    10|10000 characters needed characters exceeded