Time dependant Master data issue

[Former Member]

Dear Experts,

I have a master data object 0DF_HRPOSTN which is time denpendant in that a position will have validity dates like when its first loaded as below

BI

Pos1001 01.01.1000 to 31.12.9999

later from source system this position validity might be ended like

pos1001 01.01.1000 to 31.12.2010

the problem is the infoobject is having key as position and end to date now even though this position validity is changed to 31.12.2010 BI is still holding the reocrd 31.12.9999 which is creating lot of issues, what can i do to rectify.

Thanks and Regards

Neel

[Former Member · Accepted solution]

Neel,

For time dependent attribute, there must be an entry that starts from 1/1/1000 and an entry that ends in 12/31/9999. Initially there is one record with start date 1/1/1000 and end date 12/31/9999. Once you enter a new value, for example date from: 3/1/2009 and date to 4/11/2009, the system automatically adjust the entries so you end up with

1 record 1/1/1000 - 2/28/2009

1 record 3/1/2009 - 4/11/2009

1 record 4/12/2009 - 12/31/9999

Hope this helps.

Mark

[Former Member · Accepted solution]

Hi Diogo & Mark,

Actually the issue is see for example

John--

---

Manager-- 01.01.1000 to 31.12.2009

John----

---

Sr Manger -

---

01.04.2009 to 31.12.2010

John -

---

Sr Manager-----01.04.2010 to 31.12.9999

Here John is no more in company so his position is stopped but as per standard BI now also has the thrid record

So when i want to select all the people who are active then i will get even john positions becuase condition will be like End to date

Greater than system date

I think that when we want to stop a positions validity then its should not get another entry ending to 31.12.9999.

So kindly help me selecting right records in my transformation and reports

Thanks and Regads

Neel

[Former Member · Accepted solution]

Neel,

There a couple of things I would have done differently.

1) I would make sure the entries are continuous. No breaks in dates.

2) I would create a value for position that represents "No Position".

My values would look like this:

John--

---

NONE-- 01.01.1000 to 31.12.2009

John--

---

MANAGER-- 01.01.2010 to 31.03.2010

John--

---

SR MANAGER01.04.2010 to 25.05.2010

John -

---

NONE-----26.05.2010 to 31.12.9999

This way you query where position <> 'NONE' for a key date. I would even add more details, instead of NONE, replace with RESIGN/FIRED/Etc.

Regards,

Mark

Edited by: Mark Larson on Jun 23, 2010 2:11 AM

[Former Member]

Hi here,

BI system will alsways have 31.12.9999 as the most accurate record (up to date) for time dependent IO.

What's the issue with that record? You should use it (the date to 31.12.9999), since it should contain the most current data.

Diogo.