Queries reg BW/HANA DB

[former_member197527]

Hi,

We are planning to perform an implementation to BW 7.4 based on HANA DB (Complete new system)

I only worked on conventional flows on BW 7.0 (On RDBMS) - Datasource -> S.DSO (Staging) -> S.DSO (Biz) -> Cube -> MP -> Bex -> BO

Curious about how i can use the same with some advanced objects like Advance DSO (ADSO) and composite providers or SPOs. Have few queries. Pls some one help me understand:

1. Can i replace S.DSO by A.DSO and remove cubes as ADSO can act like cube. Flow like (Datasource -> classic SDSO/ADSO (That acts like SDSO) ->ADSO (That acts like SDSO for Biz layer) -> Composite provider -> Bex -> BO)?
2. Heard some issues with navigational attributes in composite provider -> I have gone thru but couldnt understand. Is this valid and if so, whats the alternative for in our system, we tend to have lot of nav attr being used across reports via Multiproviders/cubes.
3. HANA Transformation to be used in place of regular TRFN between 2 DSOs? Is it mandatory to avoid ABAP routines? I read ADMP to be used to embed ABAP code? Pls confirm once - complex lookups and calculation can be written only in end/start routines. How to overcome this? Any script to be called and same logic to be written?
4. I also read that no nav attrs turn on in ADSOs like before and only mapping needed in Composite providers.

Please confirm on these to understand the design.

[Former Member · Accepted solution]

hi Aditya,

1. Yes you can remove the sDSO and replace with ADSO. This will improve performance also.

2. The nav attribute issue with composite provider has been resolved from SPS08/09 onward. What SPS are you on?

3. You can use regular transformation.

4. Not sure on the last point.

Regards,

Anupama

[former_member197527 · Accepted solution]

Hi Anupama,

Thank you. BW is on 7.4 SP11. So this shouldn't be an issue right? I am not clear as to what was the issue for i never worked on it.

If a normal TRFN is used, it is like regular ABAP coding. But for performance aspects, we want to use the HANA transformation. Is it possible? Any issues in using it?

[former_member189845 · Accepted solution]

Hi Aditya Sai,

I'm also on your track, where in my consolidation project thinking of making use of 7.4 objects.

Please update more on modeling ib BW on HANA

Thanks,

Siva

[Former Member · Accepted solution]

hi Aditya,

There was no issue as such. Nav attribute was just not supported before that release.

For transformation details check the below link, Check the not supported section for more clarity.

HANA Transformations (BW 7.4) - SAP NetWeaver Business Warehouse - SCN Wiki

Regards,

Anupama

[former_member197527 · Accepted solution]

One more query reg point 1,

Can i make use of SPOs in the staging layer instead of ADSO? Flow something like below:

Datasource -> SPO -> ADSO -> Composite provider -> Bex -> BO ?

Issue is that we have common tables to be used for 2 different plants, and can an SPO help as common layer for these 2 plants? ADSO can be split later i guess? Kindly advise on this object and possibility of using same datasource and same SPOs for 2 plants till staging layer?

[former_member184884 · Accepted solution]

Hello Aditya,

Yes, you can use SPO's in your data flow but bear below 2 points...

• If the SPO is made up of InfoCubes, deltas can be updated to the target InfoProvider using DTPs without any restrictions.

• If the source is a SPO’s that is made up of DSO’s, only full DTPs can be created. If you want to update using deltas, you have to select the partitions of the semantically partitioned object as the source, rather than the semantically partitioned object itself.

Regards,

Harish    

[former_member197527 · Accepted solution]

Hi Harish,

Datasource -> SPO -> ADSO -> Composite provider -> Bex -> BO ?

Issue is that we have common tables to be used for 2 different plants, and can an SPO help as common layer for these 2 plants? ADSO can be split later i guess? Kindly advise on this object and possibility of using same datasource and same SPOs for 2 plants till staging layer?

I had studied them, but asking if the above correlates to the design here which i guess to be?

[former_member184884 · Accepted solution]

Hello Aditya,

As far as your requirement is concerned above data flow looks feasible option you can go for it.

Please go through discussion on below thread which given more insight..

https://scn.sap.com/thread/3844292

Thanks & Regards,

Harish

[former_member197527]

Hello,

Datasource -> SPO -> ADSO -> Composite provider -> Bex -> BO

SPO on classic DSO.

Now i want to use Nav attr feature, but heard ADSO doesn't an option as such.

In conventional flow, it was like assigning attributes in DSO and then cube and MP.

How about here? If there is a master attribute in ADSO which is in composite provider, can the switch on of NAV attr in composite suffice? Pls confirm

[Former Member]

Yes it will work.

Regards,

Anupama

[former_member184884]

Aditya in the initial 7.4 SPs this drawback was there, but with SP9/SP11 on-wards we can include navigational attribute in ADSO & COPR.

Regards,

Harish

[former_member200967]

Hallo Harish,

Are you sure that we can use Navigational Attributes in aDSO's?

According to the latest version of the SAP NOTE http://service.sap.com/sap/support/notes/2185212

Nav attirbutes cannot be used in aDSO and should be ticked in the HCPR. Although while extracting data from aDSO you can use the option "Use nav attributes for extraction" .

Can you please share any documentation that states otherwise as I too am planning to use a similar scneario but I was under the assumption that Nav attributes cannot be used in aDSO based on above Note.

Regards,

Manpreet Singh

[former_member184884]

Hi Manpreet,

Yes, you're right navigational attribute can't be enabled in ADSO.

Sorry for passing wrong info and thanks for empowering me.

Regards,

Harish

[former_member197527]

Hi harish,

so it means, i can use the nav attr via composite provider which has an ADSO directly without any mappings in ADSO as such?

Earlier, we had to assign them in standard DSO as well as MP. But in ADSO this is not possible but we can directly assign in Composite provider righ?

[former_member184884]

Yes, you're understanding is correct putting HCPR on top of your ADSO you can use navigational attributes, anyway you'll be building reports on top of HCPR so no worries about ADSO mappings.

Regards,

Harish