Skip to Content

Master Data Planning with BPC 11.0 with time dependency

I implemented the AO Solution for masterdata planning with a compounded, time dependent object like it was described in

https://blogs.sap.com/2018/03/15/improvements-of-bpc11-planning-engine-in-q1-2018/comment-page-1/#comment-430973

I can define the time dependent "valid from" and "valid to" objects in the aggregation level only as keyfigure. In an input ready query that makes no sense because the compounded key is only unique with the "valid to" object. But now it is input ready and i can not change an excisting line and create a new line with the "same" key. How is this designed from sap? Is there any best practice how to implement that solution in frontend with time dependency?

Object in BW:

Aggregation Level it is not possiple to get valid to in the KeyPart:

Thanks for an answer

Christian

5ipdv.png (209.2 kB)
j6q02.png (209.2 kB)
tw568.png (128.1 kB)
Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

3 Answers

  • Best Answer
    Posted on Feb 11, 2019 at 08:59 AM

    Hi Christian,

    you have overlooked the fact that all queries have a key date and this key date is used to read the time-dependent attributes and texts. This basic design is not invalidated by input-ready queries used for master data maintenance.

    Observe also that the technical key field DATETO of attributes and texts, respectively, are independent. Thus one would need more than just one table in the result set in the general case, but a query has only one result set.

    The approach with the key date allows to put time dependent attributes and texts in 'one line', the corresponding time intervals are available as key figures. To be able to maintain different section of the time intervals use a variable based on key date to switch between different key date values. The following constraints are checked by the system:

    1. DATEFROM(old) < DATEFROM(new) <= KEY_DATE(query) <= DATETO(new) < DATETO(old) for time dependent attributes
    2. TXTDATEFROM(old) < TXTDATEFROM(new) <= KEY_DATE(query) <= TXTDATETO(new) < TXTDATETO(old) for time dependent texts

    To change attributes or texts in the future you can use a key date value to get the interval DATEFROM(old), 31.12.9999 (german time format), set DATEFROM(old) < DATEFROM(new) <= KEY_DATE(query) and change the attribute or text.

    Regards,

    Gregor

    Remark

    Observe that master data are not time dependent, only attributes or texts can be time dependent. If you create a new key (combination, in case of compound characteristics) the time interval is always complete (01.01.1000 - 31.12.9999).

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Feb 15, 2019 at 11:15 AM

    Hi Gregor, tnx for the answer and the hints.

    i have some questions regarding your constraints:

    DATEFROM(old) < DATEFROM(new) <= KEY_DATE(query) <= DATETO(new) < DATETO(old)

    How could the DATETO(new) be smaller than the DATETO(old)? The new DATETO should be 31.12.9999, right?

    So in an example when i set the querydate to the 03.01.2019 and wanna change the keys like this:

    Then the Formula would look like this:

    01.01.1000 < 03.01.2019 <= 03.01.2019 <= 31.12.9999 < 02.01.2019

    and then i get an error message when i am trying to save that that row already exists.

    As i understand your example:

    To change attributes or texts in the future you can use a key date value to get the interval DATEFROM(old), 31.12.9999 (german time format), set DATEFROM(old) < DATEFROM(new) <= KEY_DATE(query) and change the attribute or text.

    i didn't need the "valid to" keyfigure in the input ready query when i try to create new datasets. I tried that also but it didn't work. Key_Date is set to 01.01.2019. First dataset is created with 01.01.1000 to 31.12.9999. When i try to create a second dataset i can not save it:

    1.

    2.

    3.

    Any thougts on that? Maybe i didn't understand your answer completly ;-)

    Thanks for any help on that issue

    Best regards

    Christian


    thgtx.png (44.0 kB)
    nhdxs.png (8.0 kB)
    0gs15.png (30.6 kB)
    n6qc0.png (41.2 kB)
    ovxvh.png (108.2 kB)
    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Feb 15, 2019 at 11:39 AM

    Short update from my side. I found my mistake. It is NOT neccesary to create a new line and i can update in the valid from date directly:

    Then i works fine :-)


    02drk.png (34.9 kB)
    ir4yd.png (62.4 kB)
    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.