Time dependent attributes

[Former Member]

Hello dear BW gurus

I have z-IO with 2 time-dependent attributes.

Both elements has they own validity.

InfoObject

|-> attr1 (01.01.2006 - 31.12.2006)

|-> attr2 (15.01.2006 - 31.05.2006)

The uload schema is like following:

DS1 - > IO

DS2 - |

We are running 2004s.

For DS1 only first attr is mapped nn transformatin (and valid from/to)

For DS2 second attr is used, first has no transformation

Steps:

1) Upload first attr - everythink is Ok

2) run second upload for second attr - > system drops first value and uploads only second ;(

How could I get both attr with different time slots

Many thnaks in advance

_____________________

Valters

[Former Member]

Valters,

If these two are mapped to Valid from and valid to, then they cannot exist as two separate records with their own validaity periods. The validity periods would get split to:

01.01.2006 - 14.01.2006 -> Value of attr 1 only

15.01.2006 - 31.05.2006 -> Value of attr1 and 2

01.06.2006 - 31.12.2006 -> Value of attr 1 only

If you want them to be stored with their own periods, then create two separate infoobjects as attributes to store the validity period. However, teh table will till have three records.

Aneesh

[Former Member]

Hi

Thanks for answer

I would say the topic is little bit more complex at least for me. The proble is, I have 2 DS for the same IO. I would like to update attribute values for my IO. when I load data from second DS system drops old values (from DS1) instead of updating values for missing attributes.

DS1 (for attr1; attr2) -> Transformation1 -> IO

DS2 (for attr3; attr4) -> Transformation2 -> |

Plus DS1 contains data for time independent attributes and DS2 for time dependent

Is it possible to update master data records, instead of overwriting ??

Many thanks

_______________

Valters

[Former Member]

Hi Valters,

If you don't want overwrite for the different attributes you have to change mapping of transfer roules in InfoSource. TR for DS1 will update attr1 and attr2 and no relation has to be mapped for attr3 and attr4, opposite for DS2.

Hope this help.

Ciao.

Riccardo.

[Former Member]

HI

Unfortunately it does not work like this ;(

There are mapped only necessary attributes in each Transformation.

If I check P and Q tables before activation, then we get D- flag for old entries and I-flag for new

We are working on 2004s, and using new Data transfer concept: DS -> Transferations|DTP -> IO. Probably here we have some other new thinks to keep in mind

Many thnaks

_______________

Valters