cancel
Showing results for 
Search instead for 
Did you mean: 

Fetching Data from Multi provider

0 Kudos
64

Hi,

Iu2019ve created multi provider in which I used 2 cubes, when I am viewing the data through the T-Code: LISTCUBE data is fetching from both the cubes but in BEX report itu2019s fetching from only first cube.

Thanks & Regards,

vikram

Accepted Solutions (0)

Answers (6)

Answers (6)

Former Member
0 Kudos

Hi,

check these

again check data in mp for conformation

selected mp was correct r not check it ok.

check whether you have used any free chars in bex.

0 Kudos

Hi All,

Thank you all, problem is solved.

Thanks & Regards,

Vikram

former_member182516
Active Contributor
0 Kudos

Its purely the design problem ... try to check the identification of the char's.

-> Check the identification of the char n KFs, Make sure the identification for the fields is done on both the ICs in MP design.

-> Make sure the data is not restricted with 0infoprovider in the query level.

Suppose the IO -0costcenter is comming from both the ICs but while identification of IOs you had selected both the ICs im MP, check this for all the IOs.

Regards

KP

former_member182343
Active Contributor
0 Kudos

Hi Vikram,

- Remove if is there any restriction on 0infoprovider(infobject) at query filter level.

- Do assignment perfectly, by maintaining atleast one keyfigure from one infocube.

-See wether those requests in infocubes are available for reporting or not.

-Remove filters or restrictions in query level.

Regards,

rvc

KulDeepJain
Active Participant
0 Kudos

Hi Jaya,

As you are saying you can see data in LISTCUBE and if you feeling here data is OK then identification is correct. Check might be you are using any restriction at Query level.

Former Member
0 Kudos

Hi ,

Check for Identification and filters in Bex query.

Also check if you have used atleast one KF from each cube.

Hope this helps,

Aparna Duvvuri

Former Member
0 Kudos

Hi,

Make sure that identification of characteristics and kF have been done correctly...

also check any restriction on 0INfoprovider(infoobject) in BEx....

Regards,

Satya