Showing results for 
Search instead for 
Did you mean: 

Key date in package link (BPC 10)

Former Member
0 Kudos


When setting up a package link (in BPC) containing packages loading from BW infoobjects, you specify a key date used for selection of time dependant characteristics in BW (for instance 0COSTCENTER).

When you create the package link, today's date is defaulted. However, when scheduling the package link to run on a regular basis, the key date is kept static. This means, it will not transfer the latest (time dependant data) but instead the records valid on the day of scheduling.

Right now, we are bypassing this by setting the key date in the future (e.g. '31.12.9999'). This however, has another short-coming future data are transferred instead of the data valid right now (for instance if cost centres are created with validity as of 2013.01.01 already now).

Is there any way to fix this problem (making the key data dynamic for instance)?


Kind regards,


Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos


In our BW upload, we have to different solutions:

a) use delta load (you don't need to have a dynamic date, because only load new data.

b) the BW infoobject has only the data we want. For example, only the last ten days.

I hope it helps!

Best Regards,

Ana Teresa

Active Participant
0 Kudos

Hello Karsten,

I am facing a similar situation with the key date. Master data is getting pulled from BW to EPM

Was wondering if you have found a solution for your issue.

Does this key data signify the "Date To" field or it should fall anywhere between "data to" and "date from" in master data in BW.

How is this date mapped to BW, I did not get the connection here.