+++> 4.Types of Info Cubes

Different Types of Cubes


  1. - TYPES OF INFO CUBE
1. BASIC INFO CUBE
        2. BASIC INFO CUBE WITH REAL TIME DATA
            VIRTUAL CUBE
3. SAP REMOTE CUBE WITH INFO SOURCE
4. GENERAL REMOTE CUBE WITH SOURCE SYSTEM
5. WITH SERVICES

  1. What r info cubes we are creating are the basic info cubes.
  2. Basic info cube with real time data are used for planning by using concept called ip( integrated planning)  in real time u can use this to load data manually to transcational cube by using t-code - rsinput
  3. In virtual cubes u can use sap remote cube with info source. this info cube can't store data. when u run the query on this cube that time it fetch the data from the source system. mainly u can use this when u load data from r/3.
  4. General remote cube u can load data by using bapi (business application programming interface)    
  5. To load data with services infocube u can use functional module types of cubes

      
1. Getting Data From Manual Input

Create IC with Real Time ….Change its behavior (Planning is allowed ,no Data Loading .
T -CODE --- RSINPUT -  Manual will enter records.


2. Getting Data Other Source ( SAP R/3 System)

  1. Create IC with Real Time ….Change its behavior (1 st option - Loading is allowed, no Planning.
  2. Create Datasource & Transformation & load IP & DTP
  3. Change its behavior (Planning is allowed ,no Data Loading .)

3. SAP REMOTE CUBE WITH INFO SOURCE

              1. Data will not be stores in Virtual Info cube .When we execute report it directly fetch data from R/3 System.
1. For The Purpose of Data Reconciliation.
Disadvantage

Performance will be very Slow. ( Retrival time will be very high when compare to Basis Cube)

  1. Based On BAPI -  GENERAL REMOTE CUBE WITH SOURCE SYSTEM

BAPI – Business Application Programming Interface

T.code – BAPI (Programming) .By using BAPI we can get the Data from other source systems. (SAP R/3).

  1. By Using Function Module
TO LOAD DATA WITH SERVICES INFOCUBE U CAN USE FUNCTIONAL MODULE

Semantic Partition object (7.3)

  • Basically the Partitioning is divided the data in InfoCube into multiple, smaller segments.  Ehen er  partitioning the system knows only to read a particular part of the disk to retrieve the data .
  • Partition of a dataset can only be done using one of the two partitioning criteria ‘calendar month’ (0CALMONTH) or ‘fiscal year/period (0FISCPER).
  • At least one of the two Info Objects must be contained in the InfoProvider.
Partitioning

  • DB Partitioning – Maintenance of partitions is higher. Data need to be deleted from the cube. Restriction of using only 2 characteristics 0CALMONTH and 0FISCPER.
  • Logical Partitioning - It requires more initial effort in the development phase. The effort required to generate the metadata objects (InfoProviders, transformations, data transfer processes)
Features

  •  An SPO is based on either a DSO or an Info Cube.
  • Each SPO is made of multiple data providers of the same type with identical structure.
  • Each of the underlying data providers behaves like a “regular” DSO or Cube, with its own metadata tables, data tables, data flows and sources/targets, and are independent of each other.
  • Each SPO will have a so called Master provider, which acts as a template based on which the part providers are built.
  • When a SPO is created, a reference structure keeps track of the partitions.  The structure is placed in the Multi Provider for querying.
  • SPO Wizards create all Data Transfer Processes (DTP), transformations, filters for each data store and a process chain automatically.
Advantages

  • Applicable for DSO and Cubes
  • Better performance with mass data
  • Reduced Query Run time for large data volume.
Close data connection

  • Better Error handling and partitioned data available for reporting and analysis.
Working with different time zones


  • Separation can be done on time zones. Helpful when we have multiple source systems and single BW instance
Subscribe to: Posts (Atom)