How to find the right primary key for DSO from Business Content

[Former Member]

According to best practice design, it is reccomended to make a DSO where all fields from Business COntent Datasources are transferred.

But, how to find the right primary indeks ?

Any good suggestions ?

For many of the Business Content dataflows there are not DSOs present, so ther e is no tip to get from the dokumentations as gfar as I have found.

best Regards

Ingrid

[Former Member · Accepted solution]

Hi,

depending on your datasource, identify the source tables in your source system and apply use the same keyfields.

regards

Siggi

[Former Member · Accepted solution]

Thank you Siegfried,

but sometimes it is not a table which is the source, but a view or a structure.

Maybe the Business Content people should dokument it in the Business Content Documentation og the datasource.

Ingrid

[Former Member]

Well no easy way it seems. In some cases we have just inserted one single field in the key area, and makes sure it is always getting a unique GUID.

[Former Member]

Ok Ingrid ....the DSO objective is maintain the TRNSACTIONAL data (it means documents) at lower level in BI, infocubes are structures that not allow a line actualization...by example if you need to maintain a infocube with invoices....you must use a DSO because in certain moments you may try to update a single document, the DSO update records when find another record with the same key....the key in this case would be the document number....

If you do not are interested in maintain the data at document level you must use an infocube....DSO are not obligatory for all the cases....

Regards

[Former Member]

Hi Oscar.

I know the differnece between cube and dso on granularity.

My question was:

When you make a DSO from the datasource, and the source in R/3 is not a table you can inherit the key field( primary key) from, how to find out what is the proper key field.

My wish is that in the documentation on the datasource it will be marked, which fields sjould be in the key.

[Former Member]

Hi Ingrid,

Your question will be perfect in case if you are going for a Custom cube.

You will not have any problem when you create a Datasource in R/3 level even if it is been built on a single table or on view.

Only point that you want to know how to design my Key fields in ODS.

This will be purely depends at what level that you want to bring the data.

Egg:-

If you run the data source in RSA3 and check for Each GL if you have 10 liine items and you want all the 10 line items to be transfered to BW.

In this case you need to check what is the unique combination of fields that is making this lineitems to exists as 10.then include all those fields into Your ODS Key Fields.

This way you can have 10 records for that perticular GL in both sides, by which u will make sure that the data is been completely transfered.

If in case if you clude your own Key fields then you will get the correct Total in report for each GL but you can't see all those 10 line items.

For any case you need to figureout how many records that you want to take into BW based on that check the fields that makes it unique and then add them to ODS Keyfields that will solve your requirement.

I think this will clear your doubt.

Best Regards,

VNK.

[Former Member]

In case you are using a view, then the selection condition that you specify in the view will tell you what the primary key should be.

Say for example you are using the join condition in the view with say Kunnr. Now, kunnr will become the primary key.

[Former Member]

Hi,

if you are installaling business content, why you need to think about key fields? it will automatically take care..!!

But if you wanted to create custom DSO, always keep primary keys in key fields in your DSO..

cheers,

VSN.

[Former Member]

Hi vsn.

I want to have a DSO, and for some of the Business Content dataflows, there is no DSO.

Ingrid