Scribd Logo
Upload

Welcome to Scribd!

  • 439 views

    Sap BW On Hana (Lesson1-3)

    Uploaded by

    Azfar Raza
    1) SAP HANA stores data in both column and row storage, allowing for fast read speeds from column storage and handling of insert/update/delete from row storage. 2) In SAP BW, data is stored in multiple layers and locations for reporting, while in HANA data is loaded at the catalog level and modeling is done at the view level with no physical data storage. 3) When moving data from ECC to HANA, only tables being reported on are imported, without relationships, which must then be created during modeling by defining primary and foreign keys between tables.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd

    Sap BW On Hana (Lesson1-3)

    Uploaded by

    Azfar Raza
    439 views18 pages
    1) SAP HANA stores data in both column and row storage, allowing for fast read speeds from column storage and handling of insert/update/delete from row storage. 2) In SAP BW, data is stored in multiple layers and locations for reporting, while in HANA data is loaded at the catalog level and modeling is done at the view level with no physical data storage. 3) When moving data from ECC to HANA, only tables being reported on are imported, without relationships, which must then be created during modeling by defining primary and foreign keys between tables.

    Original Description:

    lesson 1 to 3

    Original Title

    Sap Bw on Hana(Lesson1-3)

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    1) SAP HANA stores data in both column and row storage, allowing for fast read speeds from column storage and handling of insert/update/delete from row storage. 2) In SAP BW, data is stored in multiple layers and locations for reporting, while in HANA data is loaded at the catalog level and modeling is done at the view level with no physical data storage. 3) When moving data from ECC to HANA, only tables being reported on are imported, without relationships, which must then be created during modeling by defining primary and foreign keys between tables.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    439 views18 pages

    Sap BW On Hana (Lesson1-3)

    Uploaded by

    Azfar Raza
    1) SAP HANA stores data in both column and row storage, allowing for fast read speeds from column storage and handling of insert/update/delete from row storage. 2) In SAP BW, data is stored in multiple layers and locations for reporting, while in HANA data is loaded at the catalog level and modeling is done at the view level with no physical data storage. 3) When moving data from ECC to HANA, only tables being reported on are imported, without relationships, which must then be created during modeling by defining primary and foreign keys between tables.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    of 18

    Lesson 1

    SAP BW ON HANA
    ERP System : Integrate various systems such as FI, MM, HR for decision maker.

    HANA stores data in two instances ( columns storage and row storage).
    Column Storage : allow to read data at very fast speed using SAP HANA.
    Row Storage: SAP HANA also stores a copy of data in row storages to handle insert, update,
    delete.
    Advantage: internal processing is done by database instead of Application Server.

    Business Warehouse
    Login to BW using GUI
    Run RSA1 (Data Warehousing Workbench)
    Modelling Info Area: is folder who organize related object together.
    Info Objects : is equivalent of field in BW(e.g. Customer No, Price etc).

    SAP HANA
    Login to SAP HAN Studio
    Catalog: Contain different schemas which holds tables and data.
    Content: Modelling is done in content.
    Package: is used to organize different modelling objects. The main modelling objects as
    following.
    1- Attribute View
    2-Analytic View
    3-Calculation View
    4- Analytic Privileges
    5-Procedure
    6- Decision Table
    In BW data is stored in multiple locations in different layers which will be used for reporting.
    In HANA data is loaded at catalog level and modelling is done at view level which does not
    have hold data physically but structure only.

    When we move data from ECC to SAP HANA, We bring only tables which we have report
    on. The imported tables will not have relationship among them. We need to create primary
    keys and foreign keys between tables during the modelling process.

    Lesson 2
    1- Select InfoProvider in Modelling Tab of Data Warehousing Workbench. Right Click to
    Create Info Area.
    Note: Naming convention must start with Y or Z for any Object and name can be 3 to 8
    character longs.

    2- Create Characteristics Catalog and activate it.

    2- Create Key Figure characteristics and activate it.

    3- Select Characteristics info object catalog and right click to Create PROD Info Object.

    4-General Tab of Info Object:

    5-Business Explorer tab of Info Object:

    6- Master Data/Texts

    7-Hierarchy

    8- Attribute

    9-Compound

    10- Activate the info object:


    Create New Info Object

    Create Key Figures


    Right Click on Key Figure Catalog to Create Key Figures.

    Step-1

    Step-2

    Step-3

    Activate the Info Object


    Create another Info Object:

    Activate Info Object:

    Lesson 3

    When Week entities are defined as navigation attribute and they can be used as drill down or
    drill across as strong entities.
    One data target should contain maximum 5 Navigation Attribute.

    Cube can have up-to 16 dimensions and three are system(Time, Unit, Data Packet) are
    defined. You can create 13 custom dimension only.

    Limitation of Star Schema:


    1. Redundancy (reload for master data in every InfoCube e.g. Customer data in Sale or
    Account InfoCube).

    2. Performance due to Alphanumeric values in fact table.


    3. Limited analysis due to restricted to 13 custom dimension.

    Star Schema

    Extended Star Schema

    Dimension Table is added to info cube which connects to SID table and it add extra join and
    will not improve the performance at all.

    You can connect Dimension table with 248 SID Tables or Master Data Tables. In addition to
    this 6 fields are reserved for SAP and one is key field of Dimension Table.
    In total you can have 3224 SID tables to InfoCube.
    Note: Less no of dimension are better and Dimension table size should be less than 20% fo
    the fact table size.

    One Fact table maximum 255 columns.


    Reserved for Dimensions = 16
    Reserved for SAP
    = 6
    Remaining for Key Figure= 233

    You might also like