cancel
Showing results for 
Search instead for 
Did you mean: 

DSO keys and activation

Former Member
0 Kudos

Hi guys,

I have two simple doubts.

1.Its regarding DSO keys.Suppose I have following structure in DSO.

Keyfields:

Char1

Char2

Char3

Datafields:

Char4

Char5

KF1

KF2

From answers to my previous post,I understood that we choose keyfields for two reasons in DSO.One is to determine overwrite functionality and also to determine 'unique records' setting.Now my doubt is:

since in the above mentioned example,we have characteristics both in Keyfields and Datafields area,do we still consider only characteristics in Keyfields area as KEYS for determining Overwrite functionality and Unique records settings or do we consider charcateristics in Datafields area also for this purpose?

2.I tried to activate data in DSO manually by clicking on 'Activate' button in Manage tab of DSO...Then I am getting message with red light saying --' Activation SID for DSO changes from xxxx to xxxx' ...what does this mean?

3.I observed that in all our live DSOs,the settings --'Activate data automatically' is choosen but still we use 'Activate data in DSO' variant in Process chain....whats the need for it when we are already choose the setting in DSO?

Thanks for your guidance.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

since in the above mentioned example,we have characteristics both in Keyfields and Datafields area,do we still consider only characteristics in Keyfields area as KEYS for determining Overwrite functionality and Unique records settings or do we consider charcateristics in Datafields area also for this purpose?

Characteristics only mentioned in the Key field area are considered for overwrite and unique record functionality and not the characteristics mentioned in data fields area.

2.I tried to activate data in DSO manually by clicking on 'Activate' button in Manage tab of DSO...Then I am getting message with red light saying --' Activation SID for DSO changes from xxxx to xxxx' ...what does this mean?

I also came across this message and somehow I think sap tries to change SID values.

I observed that in all our live DSOs,the settings --'Activate data automatically' is choosen but still we use 'Activate data in DSO' variant in Process chain....whats the need for it when we are already choose the setting in DSO?

First thing is this option works only with 3.X data flow and not with BI 7.0 data flow and I read that though you mark this option it is mandatory to include the activation step in process chain.

Regards,

Durgesh.

Answers (3)

Answers (3)

former_member188080
Active Contributor
0 Kudos

Hi,

You should always have charateristics as a key fields of DSO.

Unique records you need to check when you are doubly sure that same record will not get repeated from source system ,else DSO activation will fail.

also SID check is required in case you are going to carry out reporting on DSO ,else you can remove the check in the DSO setting. If you want to continue creating it,see master data is also loaded correctly before loading or check in DTP option for not checking the master data.

In BI7 DSO activation doesn't happen automatically although you check for setting,separate step is required to carry this out.

Thanks and regards

Kiran

Former Member
0 Kudos

Hello Hayward,

1. Key fields in DSO will overrite the changes and will give you unit records...

2. Here this error came because SID does'nt exist for that value

So first you load the master data

Or, if you dont want to generate SID's then,

Go to the change mode of ur ODS.

In the Settings --- > uncheck option --> SID's Generation Upon Activation.

So, that activation process also get fast.

3. For activation data automatically just go through this link,

Hope it clears your doubts,

Thanks,

Santosh

Former Member
0 Kudos

Hi,

1. Yes it considers only the Key fields for overwrite fuctionality and unique record settings.

2. The new SID of the Activted request will be changed from xxxx to xxxx.

3. In Proces chain the flags "Activate data automatically" , "Update Subsequently into Data targets" "Activate Hierarchy Automatically" and "Update Data Automatically" will be ignored so there is need to add these processes i teh Process chain

Thanks,

Nagarjuna

Edited by: Nagarjuna Reddy on Oct 24, 2011 9:39 AM