Model SAP BW DSO in PowerDesigner

[former_member217396]

Hi,

just a quick question: what's the best approach to model a SAP BW DSO in PowerDesigner?

Just wondering, which diagram would fit best, which database type (in case I decide to go with PDM) to pick ...

Any thoughts. I don't see a "native" integratioin of SAP BW DSOs in PD.

This is only for documentation purposes...no code generation required

Regards,

Rafal

[former_member185199]

Hi rafal,

to use PDM "databaseindependend" or with an unknown targetDB you can use ANSI2.

CreateModel(PdPDM.cls_Model, ModelFileName & "|DBMS=ANSI Level 2")

HTH

dj

[former_member217396]

Hi Dirk,

it's not realy database independand ... the database underneath is SAP HANA, so the active table behing the DSO is a HANA table.

My idea is to document the DSOs in a LDM, and based on this LDM model generate a PDM model for HANA.

So in fact what I will have are:

1. Physical model (HANA) of the STAGING area

2. Logical model of the DSOs

3. Generated PDM (from LDM) for HANA DSO base tables

4. Data Movement Model defining the ETL between STAGING PDM and DSO PDM

Wher I'm still not sure, is how to model for example:

1. A constant in the DMM

2. A IF-THEN-ELSE in the DMM

as for now I would use Data Calculator for it, nut I'm not sure it's correct. Honestly, this is not rocket science, and I'm not sure what is the reason I can't do that in the standard mapping editor...

We will not generate any code from the DMM models ... it's only for documentation, linage/impact analysis purposes.

Any suggestions?

[former_member185199]

As you are not generating Code from it and you are using it only for impact lineage (as we do also for
importet and automatically matched objects from informatica), why you care about any operations then ?

If table1.a = table2.a + table3.b

then just generate mappings

table1.a --> table2.a

table1.a --> table3.b

IMHO the documentation facilities of most ETL tools are much more powerful as what you can get with PD  in this case

dj

[former_member217396]

Hi Dirk,

this is what I've done ...

1. I have a physical mapping of two source attributes into one target attibute in the mapping editor -> for linage/impact analysis purposes

2. A textual description of the logic in the source expression ... it's SQL, but could be also free text

Looks like this:

This is my only idea how to document this in a way we can utilize some of the tools standard functionality (line linage/impact analysis) and have also the logic documented somehow...

So finaly the impact/linage shows this:

What do you think?

Regards,

Rafal

[former_member185199]

For me this looks okay, but i am not your customer

[Former Member]

Hi Rafal,

If it is for ETL, try the Data Movement Model.

If it is for datastructures use CDM,LDM,PDM.

Hans

[former_member217396]

Hi Hans,

it is for both. What I'm trying to do at the moment is:

1. Model the DSO in PD

2. Map/Link this DSO model to the Finance & Risk Analytics model (LDM) extracted from BA using the FAR extraction routine

After this is done, we have to model the data flow (here I will use DMM).

Regards,

Rafal