eFashion unv

Home Forums SAP Business Objects eFashion unv

Tagged: ,

This topic contains 8 replies, has 3 voices, and was last updated by  Sal 5 years, 4 months ago.

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • #3260
    Profile photo of Sal
    Sal
    Participant

    Can anyone explain the two contexts in the eFashion unvirse..what is the purpose of them? Much appreciated.

    #3261
    Profile photo of Mim
    Mim
    Member

    If i remember right, eFashion Universe has 2 fact tables. Which is why it has two context. Every fact table requires a separate context.

    #3262
    Profile photo of Sal
    Sal
    Participant

    So all tables connected to that fact table need to be part of that context?

    #3263
    Profile photo of Mim
    Mim
    Member

    Yep.

    #3266
    Profile photo of Sal
    Sal
    Participant

    And so a seperate context for each chasm/fan trap as well?

    #3304
    Profile photo of Mim
    Mim
    Member

    Setting up context or creating alias tables takes care of fan/ chasm trap.

    #3305
    Profile photo of Sal
    Sal
    Participant

    I understand, but I mean..one context per fact table which includes all dim tables is a must have and then seperate context for a chasm trap?

    #3318
    Profile photo of Sid
    Sid
    Member

    Chasm trap ‘usually’ occurs when two fact tables converge on a dimension table. Therefore if you follow what Mimshad said and define two different context per each fact table you would have already solved the chasm trap issue.

Viewing 8 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic.