cancel
Showing results for 
Search instead for 
Did you mean: 

BI 7 - Multiple loads to single ODS : Aggregation problem

Former Member
0 Kudos

Hello everyone,

I have problem concerning multiple loads to a single ODS. Several datastores contains different fields concerning the employees. I combine all these fields in one datastore to which I connect all the other datastores. The key of this datastore is basically the employee. I load all these fields from different datastores and after activating all the requests at the same time I would expect the datastore to aggregate according to the employee so all the fields are filled for each person in a single record.

I've done the same on BI 3.5 and it works great, but on version 7 (patch 12) only the fields of the last activated request are filled, the others are empty.

Does anyone have an idea what is going on? I'm using a Standard ODS, with only 'Set Quality Status to 'OK' Automatically' flagged. I've tried it also with 'SIDs Generation upon Activation' flagged, but the result is the same.

Thank you for your help

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

hi,

hope ur issue is infoobjects gets value only for the last request activated.

have u find the contents of other requests in the new data table. have you tried and chked the content after each request activations.

Ramesh

Former Member
0 Kudos

Hello Ramesh,

When I load from the first datastore and activate, the fields are filled. When I load from another ODS and activate, the new fields are filled, but the first fields are now empty.

Normally (at least in 3.5) all the fields should be filled. Perhaps there is a new setting somewhere on the ODS, that I don't know about?

Thank already for your interest

Former Member
0 Kudos

hi,

chk if any start routine is availble in the transformation that takes the look up of the active table of ur ods and updates the value.

Ramesh

Former Member
0 Kudos

Well, I have written an end routine which splits the datapackage from the source datastores into days. But as it only splits the records, it should not update any of the other records.

I've tried the same split in the start routine, but there also the values of a previous load are overwritten by blancs, although they are not linked in the update rule.