In this Document I will write about the important definitions for  SAP HANA

This can serve as an important document to revise .I will publish more in future documents

indexserver Index server is the main SAP HANA database
  component

      It contains the actual data stores
  and the engines for processing the data.

      The index server processes incoming
  SQL or MDX statements in the context of authenticated sessions and
  transactions.

   

statistic server The
  statistics server collects information about status,

     performance and resource consumption
  from the other

     servers in the system.. The
  statistics server also provides

     a history of measurement data for
  further analysis.

xsengine XS
  Engine is an optional component.

     Using XS Engine clients can connect
  to

    SAP HANA database to fetch data via HTTP.

Name Server The
  name server owns the information about the topology of SAP HANA system.

     In a distributed system, the name
  server knows where the components are running

     and which data is located on which
  server.

Hana Live Real-Time operational reporting
  directly on your Suite on HANA system without any redundancy or latency.
  Alternatively in a sidecar scenario next to your existing SAP Business Suite
  deployment.

   

    SAP HANA Live provides SAP-delivered content (similar in concept like SAP
  BW content), in form of SAP HANA calculation views for real-time operational
  reporting. The content is represented as a VDM – virtual data model, which is
  based on the transactional and master data tables of the SAP Business Suite.
  The SAP HANA Studio is the SAP HANA application where the calculation views
  for these VDM are developed and maintained.

attribute views In the language of SAP Netweaver
  Business Warehouse , attribute views are like Dimension, but with difference
  is that attribute views are fully reusable throughout the system and not
  stuck up to a single model. Simplifying, these are views on one or more table
  that can be reused for different purpose.

   

    Example : An attribute view “FLIGHT” can  show together Airline Code, Airline
  Connection Number and flight Date into one Object. This attribute view can be
  used in analytical and calculation views where entities are relevant.
  Generally attribute views represent master data.But, however technically
  there is no restriction and its possible to make attribute views on
  transaction data.

analytical views Again, in the language on SAP BW
  analytical views can be roughly compared with Info Cubes or Info Sets in SAP
  ERP. As same it joins together one central fact table with contains
  transaction data  to report on, with number
  of tables or attribute views. You can create variables in an analytical view.
calculation views Calculation views can be
  referred as combination of tables, attributes views and analytical views to
  deliver a complex business requirement. They offer to combine different
  analytical views into one source of data for reporting.
To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply