Scribd Logo
Upload

Welcome to Scribd!

  • Hana Modeling Hands On Requirement: Purchase Order Cube: Schema Used: SAP - HANA - DEMO Fact Table

    Uploaded by

    SravanVajra
    22 views7 pages
    The document outlines the requirements for building a purchase order cube in HANA including: 1) The fact and dimension tables needed from the SAP_HANA_DEMO schema including fields from the PO Header, PO Item, Product, Business Partner, and Employee tables. 2) The attributes and fields required in each dimension view including Product, Business Partner, and Employee views. 3) The fields, calculated columns, and hierarchy required in the final analytic view as well as defined filters, variables, input parameters and semantic assignments.

    Original Description:

    views

    Original Title

    Finding CDS Views

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    The document outlines the requirements for building a purchase order cube in HANA including: 1) The fact and dimension tables needed from the SAP_HANA_DEMO schema including fields from the PO Header, PO Item, Product, Business Partner, and Employee tables. 2) The attributes and fields required in each dimension view including Product, Business Partner, and Employee views. 3) The fields, calculated columns, and hierarchy required in the final analytic view as well as defined filters, variables, input parameters and semantic assignments.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    22 views7 pages

    Hana Modeling Hands On Requirement: Purchase Order Cube: Schema Used: SAP - HANA - DEMO Fact Table

    Uploaded by

    SravanVajra
    The document outlines the requirements for building a purchase order cube in HANA including: 1) The fact and dimension tables needed from the SAP_HANA_DEMO schema including fields from the PO Header, PO Item, Product, Business Partner, and Employee tables. 2) The attributes and fields required in each dimension view including Product, Business Partner, and Employee views. 3) The fields, calculated columns, and hierarchy required in the final analytic view as well as defined filters, variables, input parameters and semantic assignments.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    of 7

    HANA MODELING HANDS ON REQUIREMENT

    Purchase Order Cube :

    Schema used : SAP_HANA_DEMO

    Fact Table:

    DB Tables used :

    • PO Header

    • PO Item

    Fields Required :

    PO Header :

    • Purchase Oder ID

    • History.createdby.empoyeeid

    • Partner.partnerid

    • Orderingstatus

    PO Item :

    • Purchaseorderitem

    • Product.productid

    • Currency

    • Grossamount

    • Netamount
    • Taxamount

    • Quantity

    • Quantityunit

    • Deliverydate

    Attribute Views:

    • Product View

    • Business Partner View

    • Employee View

    Product View :

    Table used : MD.Products

    Fields Required :

    • Product ID

    • TYPECODE

    • Category

    No Filters

    Business Partner View :

    Table used : MD.Businesspartner

    Fields Required :

    • Partnerid

    • Partnerrole
    • Emailaddress

    • Companyname

    • Legalfrom

    No Filters

    Employee View :

    Table used : MD.Employees

    MD.Address

    Fields Required :

    • EmployeeI.D

    • Name.First ( hide at semantics )

    • Name.Last ( hide at semantics )

    • PhoneNumber

    • AccountNumber

    • BankName

    • City

    • Street

    • Building

    • Country

    • Region

    Calculated column : Emp_name ; concatenation of ( namefirst + namelast )

    Hierarchy : level Hierarchy :

    Level 1. Region

    2. country
    3. city

    4. Street

    5. Building

    Analytic view :

    Fields Required in final analytic view output : (hide the fields not listed below ) :

    • Purchaseorderitem

    • purchaseorderid

    • Product.productid

    • Currency

    • Grossamount

    • Netamount

    • Taxamount

    • Quantity

    • Quantityunit

    • Deliverydate

    • Ukurs

    • Orderingstatus

    • Productid

    • Category

    • Partnered

    • Companyname

    • Employeeid

    • Emp_name
    • Country

    • City

    • Accountnumber

    Calculated Columns :

    • Calculated Attribute : Acc_Desc

    = accountnumber + Input parameter ( Varchar(15) , Direct )

    B ) Calculated Measure : cost = "GROSSAMOUNT"/"QUANTITY"

    • Calaulated measure : cost_price = ("marked_amount"*100)/(100


    +<input_parameter( integer , static list ( 20, 30 , 40 , 50 ))> )

    • Calculated measure : marked_price = ("GROSSAMOUNT"*100)/(100 + < input


    parameter ( integer , direct) > )

    Filters :

    Variables : category ( multiple single values , mandatory )

    purchaseoreditem ( Range , mandatory )

    Input parameter : Currency : ( column , Reference : Currency )

    Assign Semantics for all Measures

    Perform Currency conversion for NETAMOUNT : target currency : EUR

    You might also like