Multiprovider with diff number of key fields

[Former Member]

Hello Experts,

I have a Multiprovider created joining 2 ODS's. One ODS has 5 key fields and the second one has 3 key fields. The 3 in the second one is common to 3 in the first. Can we join 2 ODS's with different number of key fields? We are having incorrect data shown in the reports for example the ODS which has just 3 key fields doesn't display certain characteristics which are unique to itself in the reports.

Any idea or suggestion would be greatly appreciated.

Thanks,

Priya

Actually none of the data in the ODS with 3 key fields are shown in the report. Is there any criteria to choose while creating a multiprovider and if so what am I missing?

[Former Member · Accepted solution]

Hi Priya,

When you create the Multiprovider , In the identification tab check from which ODS are you picking up the fields..

Depending upon your requirement see if you can satisfy it by creating an infoset.

Hope this helps..

Ashish.

[Former Member · Accepted solution]

Hello Gupta and Ashish,

I did check the selection, I selected all the fields which are common to both and respectively individual one's. Example Comp code exists in both ODS and so I selected from both and fin class exists just for the second ODS and so selected that from second and same way with first ODS fields.

What do you mean by creating an infoset? Is it totally a separate one or join that with Multicube

Priya

[Former Member · Accepted solution]

Hi Priya,

According to my understanding the field which is there only in the second ODS will not show up if its not common to both the ODS.The reason being you have 2 Key fields which are not present in the second ODS..hence there is no connection between the key field and the characteristic..hope I have made this clear enough..

I would suggest make a seperate infoset joining the 2 ODS. This should solve your problem.Let me know..

Thanks

Ashish.

[Former Member · Accepted solution]

Priya,

Well u have checked the chars identification tab. What about the key figures indentification tabl. Make sure you to the key figures tab > identification > select the ones which u want from the both the ods.

BWer

[Former Member · Accepted solution]

Hello Ashish,

I did create an Infoset as you said between 2 of my ODS's but the report says no applicable data. I am not sure what I am missing. I selected all the objects which are common to both in the link maintenance. Can u give me steps to follow:

example

<b>ODS1 ODS2</b>

xxx xxx ( key fields )

yyy yyy

aaa ( key fields )

bbb

ccc

ddd

Priya

[Former Member · Accepted solution]

Hi,

I did check the key figures selection tab too and I did select all and there is no common key figures between both the ODS's.

Thanks

Priya

[Former Member · Accepted solution]

Hi Priya,

To create an Infoset;

1. Identify the Characteristics that are common to both the ODS which will make each record unique.

2. The Idea is not to join every Key field..but to join the Fields you think will give you the level of granularity you desire...

EG:

ODS 1 has ;

Doc no. , postg date , company code , amount

ODS 2 has ;

Doc no. , company code , Clrg Date , amount

Your join can just be on Doc no. and Company code..

If the Granularities differ or if the data set of one ODS is Greater than other a LEFT OUTER JOIN will help.

To see how the data exactly looks after the join , In transaction RSISET you can look at the data in the Infoset. That will give you a fair idea ..to make any more changes in the way you join ..if required..

Its difficult to put down everything in words..but I hope this helps..

feel free to ask if you need any clarifications on anything specific.

Ashish.

[Former Member · Accepted solution]

Hello Ashish,

Thanks a lot for your help, I was successful in creating the set and also got the exact data as required but I have a question.

Isn't it very confusing for us to create a query based on an infoset as we have 3 different objects. i.e 2 ODS and one infoobject ( had to create one infoobject as the 2 ODS were not bringing in the attributes and the navigational attribute ). I mean the query designer shows the key and attribute for every object and it looks too difficult for an end user to build queries, what is your thought on this?? Isn't there a simpler way becoz most of our design is the same. So a solution to one would resolve all the issues.

Thanks,

Priya

[Former Member · Accepted solution]

Hi Priya,

Navigational Attributes cannot be used in an Infoset.

As you mentioned we have to pull in the InfoObject.

To make it a bit simpler all I would suggest is only select the required fields from the 2 ODS objects and Infoobject.

You can do this in the Infoset creation by only checking the Boxes against the Info Objects u want to use..

Then look at the Data in RSISET for the Infoset which will show you only chosen fields...which will make it a lot easier to analyze and interpret the data.

Cheers

Ashish.

[former_member188975]

Hi Priya,

When creating a multiprovider you need to carefully look at the Identification for Chars and Selection for KFs...did you look into these to see if the IOs from both ODS are appropriately selected?