How will I make this work in Multiprovider?

[Loed]

Hi guyz,

I have two DSOs, namely DSO_1 and DSO_2, and on top of the is a Multiprovider..

DSO_1 is composed of:

*Payer

*Material

Amount

DSO_2 is composed of:

*Payer

*Material

*Account

Quantity

NOTE: * means PRIMARY KEY

The report is something like this:

Payer          Material          Account          Amount          Quantity

My question is, how will I make the report above work if I don't have an Account Number in my DSO_1?

EXAMPLE:

DSO_1 contains:

Payer          Material          Amount

10               100               30

10               200               40

DSO_2 contains:

Payer          Material          Account          Quantity

10               100               1010                 50

10               100               1011                 60

10               200               1040                 70

10               200               1045                 80

10               200               1047                 90

How will I get this output? Is this possible?

Payer          Material          Account          Amount          Quantity

10               100               1010                30                  50              

10               100               1011                30                  60

10               200               1040                40                  70

10               200               1045                40                  80

10               200               1047                40                  90

Thanks a lot!

Loed

[anshu_lilhori · Accepted solution]

Hi,

Constant selection at Bex level will help you in getting the data in one line.

You need to apply constant selection on Amount with Char Account as this is not present in this DSO.

For more information on my approach you may search the document with the name.

How to Display Result Row in One Line While Reporting On Multiprovider.

That document will give you step by step navigation on the approach which i mentioned.

Hope that helps.

Regards,

AL

[Loed · Accepted solution]

Thanks mate!

I will be trying this one..

[Loed · Accepted solution]

Just want to ask mate, can I still use CONSTANT SELECTION if I have 3 DSOs in Multiprovider?

By the way, it worked in my problem above! THANK YOU!

Thanks too guyz for helping me achieve this one..=)

Loed

[Former Member]

This message was moderated.

[Former Member]

Did you try infoset DSO1 left-outer-join DSO2?

Br, H

[Loed]

Did not try infoset mate since it is slow in query..Am I right mate?

Is this not possible in Multiprovider?

[Former Member]

Infosets will bring performance issue when it contains infocube and won't be a big problem for DSOs.

And performance is a big factor, add Amount field to your DSO2 and and do a lookup to enrich this field based on the DSO1.

Br, H

[Loed]

Nice! Got an idea!

I will just lookup from DSO_2 to DSO_1 with the AMOUNT field and I will just solely use the DSO_2 in Multiprovider..Is that idea ok mate?

[Former Member]

Multiprovider will do a union of data and hence if by chance you're drilling down data based on underlying infoproviders, it'll show double records as below.

10

100

-

30

-

10

100

1010

-

50

Br, H

[Former Member]

Look-up data should work fine.

Br, H

[Loed]

If ever I lookup the AMOUNT field from DSO_1 to DSO_2, will the report be like this in Multiprovider with DSO_2 ONLY as its component? Hence all the fields below will be coming only from DSO_2 so I think there will be no NOT ASSIGNED..Am I right? Since for every Payer and Material that will be matched from DSO_1 to DSO_2 will be given a specific amount..Is my analysis correct?

Thus,

Payer          Material          Account          Amount          Quantity

10               100                 1010                30                  50             

10               100                 1011                30                  60

10               200                 1040                40                  70

10               200                 1045                40                  80

10               200                 1047                40                  90

[former_member182470]

I feel Infoset DSO2 <- DSO1(Left-Outer Join) will be the best way of design. You have 2 fields in common and joins happens faster on DSOs. You will easily get the required output without any codes for look-ups.

There are ways to optimize Infoset query performance.

RSDIPROP t-code : Set X in Read mode

"Use Selection of Structure Elements" in RSRT-->Properties of the Query

[Former Member]

Yes, you're right, since all primary keys in DSO1 are available in DSO2 and hence you can achieve the results as shown above.

Br, H

[Loed]

Thanks Suman!

I will explore regarding the RSDIPROP tcode..

So INFOSET will be much easier than the lookup something mentioned? Right?

Ok mate,thanks for your suggestion..

[former_member182470]

Yes Loed. Infoset is apt for you. I have similar requirement and achieved with Infoset.

[Loed]

Ok Suman..I will post here later regarding the result..

Thank you!

Loed