Question on setup and usage of Dimension tables in SAC

[dirk_meyer2]

Situation is as followed:
We have an ODATA connection which looks simplified like this:

Fact table:  Activity (KYF, Activity, Customer_id)
MD Table:  Customer (Customer ID, Name, Adress, …)

There are 3 other of such dimensions to handle, all same same.
Per table there is one ODATA source, which is at the moment not customizable.
The ID is cryptic and not SAP Style. A dimension linkage is all planned stories is out of the question.

As I understood from all the docs I scanned, the usage of dimension tables in SAC works as followed

• I make a model based on the MD Table and create from there a Dim Table based on Customer_id with all the other fields as properties. With the load of that main model the dim table gets loaded indirectly.
• I create the model on the fact table, exchange the customer_id field with the created Dim_table, map the sourcefield to the table.

Problem:

To make a MD model and with that the DimTable I obviously need to have a measure, which I do not have in source.
I tried to solve that with creating a dummy KYF and a data transformation “null = 1”, but this does not work.
There must be a mapping from the source to KYF and I do not have a field that is compatible with dec or int in the source I could load and later overwrite.

To have a transactional data set to derive MD used in other transactional data does not make sense at all since never all MD are used or the other. The whle thing looks not thought out thoroughly.

So how do can I bypass this?

Thanks for help!
Dirk

[William_Yu · Accepted solution]

Hi dirk_meyer2, 

    I feel that I'm not fully understanding your problem. But just want to point out, you can import master data into SAC public dimension independent from model fact data import( through Odata or other import connection type).  I see your source fact table have measures(KYF) which is already good enough.  

Best regards, William 

[dirk_meyer2 · Accepted solution]

Yes, just learned it that you can link from the dim row to the Dim_table and from there via save and Data to mapping.

[dirk_meyer2 · Accepted solution]

... as always, everthing but intuitive. But when you did it once its a gas...