InfoCube Star Shcema

I am getting confused. In the documentation, it says the relationship between the Dimension and Fact Table is linked by the Dimension ID.:  (http://help.sap.com/erp2005_ehp_03/helpdata/EN/6f/c7553bb1c0b562e10000000a11402f/frameset.htm)
So say I have 3 InfoObject (2 are InfoObject Master Data) assigned in one Dimension in the InfoCube, then does it mena that there 3 Dimension ID will be stored in the Fact Table?
Please advice, thank you.

Hi Iynn,
Your DIM table will be like this
DIM ID         MATERIAL SID      VENDOR SID         PLAN SID
12                       3                          5                         8
Fact table will be like
DIM ID            QTY
  12                  10
Now we can check how the transaction is coming
suppose your transaction data coming like
MATERIAL     VENDOR      PLAN      QTY
10                    20                 30          10
Now the system will check Material's SID for the material number 10 then it will get it as '3' from the SID table of Material. Like this it will find out for Vendor and Plan. So the system will identify the SIDs of Material, vendor and plan as 3, 5, 8 respectively.
Then it will create an entry in the dimension table as below ::
DIM ID         MATERIAL SID      VENDOR SID         PLAN SID
12                       3                          5                         8
After that using this DIM ID it will link to the Fact table as below ::
DIM ID            QTY
  12                  10
This kind of modeling is known as Extended star schema.
You can refer the below link for Modeling ::
/people/githen.ronney3/blog/2008/02/13/modeling-strategies
Regards
Githen

Similar Messages

  • BIA and process chain

    Hi Gurus
    Would you please advise the steps I have to follow on BW side to make BIA starts working?
    Can I use process chain to include the functionality of BIA? Also as I know we have to create one Index per cube for BIA. Do we need to fill them manually of when we load cube its going to be filled in automatically?
    Do we need to delete the BIA index and recreate it when we load data to the same cube again?
    Do we need to do some settings on BEx analyser for query which we run to execute through BIA?
    Appreciate your quick reply..Thanks for the help
    Thanks

    1)if you drop the InfoCube the BIA index should be dropped automatically.
    This means you have to re-build the InfoCube BIA index.
    Process type -Initial Activation and Filling of BIA Indexes can be used as of SP-13.
    2)Program - RSDDTREX_AGGREGATES_FILL
    When you execute this step, the system starts a process in the background that reads the data in the tables of the InfoCube star schema from the database and writes them to the corresponding indexes on the BI accelerator server. If the index of a master data table (S/X/Y tables) has already been created and filled by another BI accelerator index, only those records that have been subsequently added have to be indexed (read mode/fill mode "D" during indexing).
    If the aggregate was filled successfully, the status in the "Object Status" column on the Index Info tab page switches to GREEN
    https://forums.sdn.sap.com/click.jspa?searchID=5022975&messageID=3855004
    Hope it Helps
    Chetan
    @CP..

  • Web Reporting on Mac

    How different is SAP BW BEx Web Reporting on Apple Macintosh (Safari, Firefox)?
    Thanks

    dear Rekha,
    may behave differently, check following oss,
    recommended is
    Business Explorer Browser in the Web
    Java script is used to display the tree. The required Web Browsers are Netscape >= 4.6 and Microsoft IE >= 5.0.
    For BW 3.5 and higher, the compatible web browser version is IE>= 5.5.
    hope this helps.
    494689
    Solution
    Web Applications
    You can use different functions, depending on the type of browser. A browser identification is carried out on both the server and the client. For this reason, it is important that proxys or firewalls do not make any major changes to the user agent ID in the request.
               Requirements for an unlimited range of functions
                         The full range of functions with context menus, snippet operations and the interactive navigation bar with maps can only be accessed using current browsers that support the DOM level 2 (with dynamic generation of DOM objects), ECMA-262 script, HTML 4.0 and CSS 1.0. The reference browsers here are the Microsoft Internet Explorer (MSIE) and the Netscape Navigator (NS) in the current Windows implementations (MSIE 6.x and NS 6.x). Instances of these browsers on other systems such as Apple Macintosh or Linux may behave differently.
               Minimum requirements
                         Web Applications can be used with browsers that meet HTML 3.2 standards and support basic CSS 1.0 functions.
               Browser variants and range of functions
                         Full context menu range of functions, flicker-free navigation and ad-hoc BEx Query Designer: IE 6.x, 5.x, NS 6.x
                        Context menu, but no dynamic loading of hierarchy branches with the Web item "Hierarchical context menu": IE 4.x, NS 4.x
                         Context menu display as its own Web page: Pocket Internet Explorer (mobile devices with Windows CE), Accessibility mode (suitable for the visually-impaired)
                         No context menu, only limited navigation via icons:
                         Very old browser Web (IE 3.0, Netscape 3), mobile devices (Palm, EPOC...)
                         Limited navigation: WAP-enabled mobile telephones and i-Mode-enabled mobile telephones
    Mobile-Intelligence-Rendering
    Stylesheet information and scripts are embedded in the document on the server.
    EPOC: No script.
    WAP: WML instead of HTML. WBMPs for charts.
    i-Mode: CHTML instead of HTML.
    Web templates that contain corresponding Web items have only limited functions on the respective browsers.
    For more details on the area of mobile intelligence, see Note 453142 "Information about BW BEx Mobile Intelligence"
    Repository metadata
    The text part of the Metadata repository is based on HTML 3.2 and therefore can be used all conventional browsers with version >= 3.0.
    However, the graphics (InfoCube star schema, data flow, query preview), are in a XML-based format (VML) which until now was only supported by Internet Explorer Version 5.
    Business Explorer Browser in the Web
    Java script is used to display the tree. The required Web Browsers are Netscape >= 4.6 and Microsoft IE >= 5.0.
    For BW 3.5 and higher, the compatible web browser version is IE>= 5.5.

  • Splitting Dimensions on Attributes for reporting

    Does anyone have experience or a good idea on how to most efficiently allow splitting a dimension on attributes for reporting custom cells. We are working in 11G. First let me explain
    We have a dimension Brand that has a level based hierarchy.
    Total
    Category
    Brand
    Item
    The Item level has many attributes, of course it has Category and Brand but it also has other Attributes that apply only to the Item level, we will say Flavor and Size for example. The user might want to see a report with Flavors on Columns and Size on rows, or Flavor on columns and Categories on rows.
    We have come up with 4 ways to do this, 3 on the fly and 1 predefined.
    1. We use the BRAND_VIEW view to limit to the chosen attributes and the Item level then join to the CUBE_VIEW and sum BRAND. This only works for measures with all SUM additively
    2. Use the Java API and Source objects to limit BRAND to the ITEMS that meet our criteria, create a custom member in brand and report on it. This gets around the additively problem but is currently not an option til Oracle patches the 11G API to allow session only member creation.
    3. Write a DML program to limit the BRANDS and then report on the TOTAL. Again this only works for SUM.
    4. For the above example we would build 3 dimensions for BRAND instead of 1. We would build the BRAND dimension as defined and a FLAVOR and SIZE dimension. This increased the size of the build and fact data, also greatly increases the build time. Also this forces the User to see many more dimensions then they are use to seeing.
    If anyone has dealt with an issue like this I would greatly appreciate hearing how you handled it.

    Clyde, how are you sir? I was curious on this too - so I took a look into it. Seems that the as long as the attributes are marked navigational they come along into the BIA indexes. See excerpt and link below.
    [http://help.sap.com/saphelp_nw70ehp1/helpdata/en/43/bcf9bfdd052ec5e10000000a11466f/content.htm|http://help.sap.com/saphelp_nw70ehp1/helpdata/en/43/bcf9bfdd052ec5e10000000a11466f/content.htm]
    Step 1: Creating a BI accelerator index
    When you execute this step, the system creates the indexes for the tables of the InfoCube star schema on the BI accelerator server, as long as they have not already been created by other BI accelerator indexes. These tables consist of the fact and dimension tables of the InfoCube as well as the master data tables that contain the required SIDs, the S, X, and Y tables of the InfoObjects
    X = time independent navigational attributes and Y = time dependent navigational attributes, so it looks like these are stored too.
    Hope this helps!
    Justin

  • Cube Transport issue

    Hi All,
    We have an existing cube which is having lots of data.
    We have added a new data field in that cube and activated the same. Now when we are transporting this in Quality system, Is is not getting transported.
    We checked the Transport logs also, but its giving an error as : Program terminated (job: RDDEXECL, no.: 01302300
    With error code 12.
    Any inputs on the same.
    Regards,
    Mayank

    >
    Arun Varadarajan wrote:
    > Ravi,
    > Addition of a characteristic too should be fine - For a cube - if you add characteristics - your dimension tables change - this would mean that you will have to regenerate all the SIDs in the dimension Tables. - this would mean that the DIM table has to be regerared...
    >
    > but the the DIm ID is a key field in the Fact table - this means that you will have to drop and reload data for adding a characteristic. Even if you are adding a characteristic - you would have to add another key into the fact table...which necessitates a data drop.
    Hi Arun,
    In InfoCube Star schema, the key the fact table stores is not individual characteristic SID, but a Generated Dimension Key from each dimension. This is also the reason why an InfoCube cannot have more than 13 customer dimensions as the Fact table is limited by the number of Keys it can have (16 Dimension Keys, 3 standard and 13 customer).
    Hence, Adding a Characteristic is always fine to a Cube. Check t-code listschema for any InfoCube.

  • Reg : Download the data from dashboard to Oracle DB Tables

    Hi,
    I want to download the all data at once from the dashboard without column headings or select(using SQL Query) the data . Is it possible ? Please help me on this .
    Edited by: 999 on Jul 26, 2009 11:44 PM

    hi,
    even i do not understand why you want to do it..
    (Bi just make sql queries at your Db,so the results are the same).Now,in order to compare them it is better ,to do the opposite....
    make a table with 2 columns,which contain result + description......and put it at your star shcema...and so on...
    Otherwise , in your situation,you need write back capabilities ///at every report...in order to fill a table which will be compared with your values.....
    i hope i helped....
    http://greekoraclebi.blogspot.com/
    ///////////////////////////////////////

  • Process chains for deltas

    hello I have one scenario...Can anyone explain how we can implement it?
    I want to load data from R3 into Master Data Attribute in BW/BI..and it should include future delta loading also.....
    and I want to use Process Chains for this....how can we do it.?(I have knowledge of loading data from R3 To MD Attribute using Process Chain but without deltas)
    Thank you
    Regards
    NR

    Hi......
    Sorry for late reply.......
    If we take the second implementation of PC in your abbove post.....as we included fullload in PC....before delta init.....can it be possible that fullload happens all the time as its in process chain?
    yes..........since it is a part of the process chain every time when you will execute the chain.........full upload will also done..............you can do one thing you can copy the chain.......and remove that process......I mean open the chain in Planning view.....in the top where we write tcode......there write Copy...
    then the chain will be copied.........remove the start process and the full upload and init upload.........then create a new start process.........look you have to create a new start process.......because you cannot use the same start variant twice..........
    whats the use of attrib change run in PCs in general?
    Attribute change run is used to activate the master data.......ie to convert the master data from M version to A version..........because upon activation of master data SID will generate...........which is needed to link the master data to transaction data ie dimension table.........in extended star shcema............Also Once active, the data is available in your reports........
    Attribute change run also adjust aggregates........
    Another thing......This process is just required for Attributes and Hierarchies, not for Text data.
    Hope this helps..
    Regards,
    Debjani........
    Edited by: Debjani  Mukherjee on Nov 4, 2008 2:11 PM

  • How to display BI Content provided infocube as star schema

    I go to Matadata Repository>BI content> and then where to next?
    There is supposedly a a setting somewhere in the MDR to choose schematic display as star schema. 
    FYI I want to view one of the available infocubes 0cca_c11 as start schema layout in the BI7 version.
    And I also do not see how to view only acivated objects in the BI content or metadata repository....
    Thanks
    Edited by: natalie marma on Apr 13, 2009 10:21 PM

    Hi Natalie,
      you can use the tcode listschema  to display the cube in schematic view.
    we can get the active objects informations from these tables.
    for info objects : RSDIOBJ make appropriate selections like version as A and status as ACT - active and executable
    RSDODSO for data store objects
    RSTRAN for transformations
    RSDCUBE for cubes
    RSDS for data sources (give source system and version)
    you can find the active objects information from these tables in se11 or se16
    Thanks,
    Sathish.

  • Creating a Infocube in BI 7.0

    Hello,
    I am new to BI 7.0 version. I know how to create a InfoCube in BW 3.5 but in BI 7.0 huge difference. If any body have step by step screen short instructions please post for me I would appreciate.
    Regards,
    Alex

    hi Alex,
    BI 7.0
    Uploading of Transaction data
    Log on to your SAP
    Transaction code RSA1—LEAD YOU TO MODELLING
    5. Creation of Info Objects
    • In left panel select info object
    • Create info area
    • Create info object catalog ( characteristics & Key figures ) by right clicking the created info area
    • Create new characteristics and key figures under respective catalogs according to the project requirement
    • Create required info objects and Activate.
    6. Creation of Data Source
    • In the left panel select data sources
    • Create application component(AC)
    • Right click AC and create datasource
    • Specify data source name, source system, and data type ( Transaction data )
    • In general tab give short, medium, and long description.
    • In extraction tab specify file path, header rows to be ignored, data format(csv) and data separator( , )
    • In proposal tab load example data and verify it.
    • In field tab you can you can give the technical name of info objects in the template and you not have to map during the transformation the server will automatically map accordingly. If you are not mapping in this field tab you have to manually map during the transformation in Info providers.
    • Activate data source and read preview data under preview tab.
    • Create info package by right clicking data source and in schedule tab click star to load data to PSA.( make sure to close the flat file during loading )
    7. Creation of data targets
    • In left panel select info provider
    • Select created info area and right click to create ODS( Data store object ) or Cube.
    • Specify name fro the ODS or cube and click create
    • From the template window select the required characteristics and key figures and drag and drop it into the DATA FIELD and KEY FIELDS
    • Click Activate.
    • Right click on ODS or Cube and select create transformation.
    • In source of transformation , select object type( data source) and specify its name and source system Note: Source system will be a temporary folder or package into which data is getting stored
    • Activate created transformation
    • Create Data transfer process (DTP) by right clicking the master data attributes
    • In extraction tab specify extraction mode ( full)
    • In update tab specify error handling ( request green)
    • Activate DTP and in execute tab click execute button to load data in data targets.
    8. Monitor
    Right Click data targets and select manage and in contents tab select contents to view the loaded data. There are two tables in ODS new table and active table to load data from new table to active table you have to activate after selecting the loaded data . Alternatively monitor icon can be used.
    bi7.0 differences..
    http://help.sap.com/saphelp_nw2004s/helpdata/en/a4/1be541f321c717e10000000a155106/content.htm
    Hope that helps...assign points if so
    REGARDS
    partha

  • Infocubes and info objects

    Hi guys,
            i'm new to BI. can any one differentiate between Infocubes and info objects..
    please be a bit specific.....

    Hi,
    An InfoCube describes (from an analysis point of view) a self-contained dataset, for example, for a business-orientated area. You analyze this dataset in a BEx query.
    An InfoCube is a set of relational tables arranged according to the star schema: A large fact table in the middle surrounded by several dimension tables.
    Use
    InfoCubes are filled with data from one or more InfoSources or other InfoProviders. They are available as InfoProviders for analysis and reporting purposes.
    Structure
    The data is stored physically in an InfoCube. It consists of a number of InfoObjects that are filled with data from staging. It has the structure of a star schema.
    The real-time characteristic can be assigned to an InfoCube. Real-time InfoCubes are used differently to standard InfoCubes.
    ODS versus Info-cubes in a typical project scenario
    ODS
    why we use ods?
    why is psa  & ods nessasary
    InfoObject: Basic building block of BW.. ( Its like a field )
    Definition
    Business evaluation objects are known in BI as InfoObjects. They are divide into characteristics (for example, customers), key figures (for example, revenue), units (for example, currency, amount unit), time characteristics (for example, fiscal year) and technical characteristics (for example, request number).
    Use
    InfoObjects are the smallest units of BI. Using InfoObjects, information is mapped in a structured form. This is required for constructing InfoProviders.
    InfoObjects with attributes or texts can  themselves also be InfoProviders (if in a query).
    Regards,
    Ram.

  • Which one is better ODS-INFOCUBE for reporting in BW

    Hello expert's
    1.I want to know which one ODS or INFOCUBES are better (technically/functionally) for reporting  purpose in BW.if some one is having any comparisons on ODS/INFOCUBE then plz pass on to me.
    2.Are Z tables reliable in case of data updation and fetching when we create ODS/INFOCUBE.
    3.HOW RELIABLE THE "Z"(*TABLES/REPORTS) are in SAP-BW/R/3-ABAP.

    1.Cubes are optimized for reporting..due to star schema structure.Use cubes for reporting aggregated data to be accessed by large number of users.
    ODS are for detailed level reporting.ODS structure is like flat DB table.
    usually drilldown is setup from cube report to the ODS report.
    2.Are u referring to custom ODS and cubes..then they have the Z tables internally..reliability depends on ur design.But always try to use BC content,else copy BC content and change/enhance it.else if no BC content found then create Z-content directly.
    3.Again,depends on the design.But always using BC content is suggested.
    cheers,
    Vishvesh

  • Regarding Extended star schema

    Hi Friends,
    In Extended star schema,master data will load separately ,which will connect through sid's to dimension table .
    My question is.. This master data tables can be used other than this cube ?
    Please tell me i am in confusion.
    Thanks in advace,
    Regards,
    ramnaresh.

    Hi
    InfoCubes are made up of a number of InfoObjects. All InfoObjects (characteristics and key figures) are available independent of the InfoCube. Characteristics refer to master data with their attributes and text descriptions.
    An InfoCube consists of several InfoObjects and is structured according to the star schema. This means there is a (large) fact table that contains the key figures for the InfoCube, as well as several (smaller) dimension tables which surround it. The characteristics of the InfoCube are stored in these dimensions.
    An InfoCube fact table only contains key figures, in contrast to a DataStore object, whose data part can also contain characteristics. The characteristics of an InfoCube are stored in its dimensions.
    The dimensions and the fact table are linked to one another using abstract identification numbers (dimension IDs) which are contained in the key part of the particular database table. As a result, the key figures of the InfoCube relate to the characteristics of the dimension. The characteristics determine the granularity (the degree of detail) at which the key figures are stored in the InfoCube.
    Characteristics that logically belong together (for example, district and area belong to the regional dimension) are grouped together in a dimension. By adhering to this design criterion, dimensions are to a large extent independent of each other, and dimension tables remain small with regards to data volume. This is beneficial in terms of performance. This InfoCube structure is optimized for data analysis.
    The fact table and dimension tables are both relational database tables.
    Characteristics refer to the master data with their attributes and text descriptions. All InfoObjects (characteristics with their master data as well as key figures) are available for all InfoCubes, unlike dimensions, which represent the specific organizational form of characteristics in one InfoCube.
    Integration
    You can create aggregates to access data quickly. Here, the InfoCube data is stored redundantly and in an aggregated form.
    You can either use an InfoCube directly as an InfoProvider for analysis and reporting, or use it with other InfoProviders as the basis of a MultiProvider or InfoSet.
    See also:
    Checking the Data Loaded in the InfoCube
    If the above info is useful, please grant me points

  • Z Infocube based on existing Infocube

    Hello Experts,
    I have a requirement in which I have to create a Z infocube by creating Z infoobjects in (say systemB) based on Infoobjects used in Infocube which is in another system (say systemA).
    I dont have any kind of access to the existing infocube (systemA) neither dev nor display.
    Available data resources:
    (1)All I have is display access to query designer of systemA so that I can view the dimensions, infoobjects....etc by selecting queries on that Infocube.
    (2)And also I am going to get technical details for custom infoobjects used in the infocube of system A and hierarchie structures.
    (3)Both master data and transaction data in the form of flatfiles exported from systemA
    (4) Star schema
    This is the way I am planning to do it.
    (a) Identify the infoobjects from query designer as I have display access and create Z infoobjects (Reason for creating Z infoobjects is because the systemB already have infoobjects and client want to keep master data seperate instead of loading the data I am getting from another systemA into the same masterdata infoobjects)
    (b) Apply attributes, texts based on the identification from query designer.
    (c) Build custom infoobjects, hierarchies based on technical document provided as I mentioned in step # 2 above.
    (d) Load master data from flatfile and build infocube and finally load transaction data from flatfile
    Experts please tell me a better way if anything.
    The only question I have is as I am creating Z infoobjects in system B instead of using BC or already existing infoobjects do I need to create zinfoobjects for all the attributes, transitive attributes etc to maintain data seperate?
    Please let me know.
    Thanks.

    Hello Des,
    Thanks for your reply. I assigned you the points but not sure as I am getting an error while assigning them.
    Coming to the concern you raised, systemA is another company and I tried to convince them to get display access so that the modeling part in systemB would be easier for me.
    But I couldnt.
    Is there a chance to give display access to only Infocube and infoobjects pertaining to that IC? I am not sure whether that kind of option is possible.
    Please let me know.
    Thank you again.

  • Different table used in infocube dataloading?

    hii
       we load  data in to the cube by using star schema and extended star schema
      here differnt data we have to load
      here different ids like dimid and sid also generated
    now my question is
      1.  which are the different table where the record and ids are stored?
      2.  how and when  the dimid and sid are generated?
      3. can we see the dim id and sid?if we can then where?
    4.  this ids are stored in which tables?
    thanxxx

    Hi Deepa,
    Whenever you want to analyze the star schema of a particular cube, execute LISTSCHEMA transaction in your system. Once you execute this transaction you will see the list view of star schema and you will get to know all the underlying tables in which cube stores the data and reads data.
    which are the different table where the record and ids are stored?
    In case of infocube mainly Fact table and Dimension tables are used to store the transaction specific data.
    2. how and when the dimid and sid are generated?
    In the infocube design you can see the various dimensions and underlying characteristics in each dimension. During data loading one DIMID is created for each unique combination of all the characteristic values. Dimension table stores the SID's of each characteristic. For e.g. Your dimension consists of Material and customer then it will have different DIMID's as follows,
    DIMID          MATERIAL          CUSTOMER
    1                  MAT1                  CUST1
    2                  MAT1                  CUST2
    3                   MAT2                 CUST1                 and so on.... In reality you will see SID's in DIM table.
    3. can we see the dim id and sid?if we can then where?
    You will have to check data in SID and DIM tables, use LISTSCHEMA transaction to get the table names.
    4. this ids are stored in which tables?
    SID and DIM tables.
    Regards,
    Durgesh.

  • Give me step by step procedures to create an infocube in BI 7

    Hello Experts,
    Can any one provide me with step by step procedures to create an infocube in BI 7 ?
    Thanks in advance,
    Jessica.

    Hi,
    ) Create a data source
    RSA1->Source Systems->FILE(File)->PC_FILE(Filesourcesystem)->Create Application Component(optional)-Create Data source
    2) Create infoPackage
    Right click on the data source and do
    3) Create the data provider
    4) Create Transformation
    Right click on the data provider, choose 'create transformation' and choose your data source (give relevant data source and its type)
    Just connect the relavant fields between your data source and data provider.
    4) Create DTP
    Then Double click on the DTP node created under yous transformations. choose the extraction mode as delta.
    5) Load the data: there are 2 ways:
    you can run the infopackage and DTP separately or create a process chain consisting of these infopackage and DTP and run.
    Hope this helps.
    Uploading of master data
    Log on to your SAP
    Transaction code RSA1—LEAD YOU TO MODELLING
    1. Creation of Info Objects
    • In left panel select info object
    • Create info area
    • Create info object catalog ( characteristics & Key figures ) by right clicking the created info area
    • Create new characteristics and key figures under respective catalogs according to the project requirement
    • Create required info objects and Activate.
    2. Creation of Data Source
    • In the left panel select data sources
    • Create application component(AC)
    • Right click AC and create datasource
    • Specify data source name, source system, and data type ( master data attributes, text, hierarchies)
    • In general tab give short, medium, and long description.
    • In extraction tab specify file path, header rows to be ignored, data format(csv) and data separator( , )
    • In proposal tab load example data and verify it.
    • In field tab you can you can give the technical name of info objects in the template and you not have to map during the transformation the server will automatically map accordingly. If you are not mapping in this field tab you have to manually map during the transformation in Info providers.
    • Activate data source and read preview data under preview tab.
    • Create info package by right clicking data source and in schedule tab click star to load data to PSA.( make sure to close the flat file during loading )
    3. Creation of data targets
    • In left panel select info provider
    • Select created info area and right click to select Insert Characteristics as info provider
    • Select required info object ( Ex : Employee ID)
    • Under that info object select attributes
    • Right click on attributes and select create transformation.
    • In source of transformation , select object type( data source) and specify its name and source system Note: Source system will be a temporary folder or package into which data is getting stored
    • Activate created transformation
    • Create Data transfer process (DTP) by right clicking the master data attributes
    • In extraction tab specify extraction mode ( full)
    • In update tab specify error handling ( request green)
    • Activate DTP and in execute tab click execute button to load data in data targets.
    4. Monitor
    Right Click data targets and select manage and in contents tab select contents to view the loaded data. Alternatively monitor icon can be used.
    BW 7.0
    Uploading of Transaction data
    Log on to your SAP
    Transaction code RSA1—LEAD YOU TO MODELLING
    5. Creation of Info Objects
    • In left panel select info object
    • Create info area
    • Create info object catalog ( characteristics & Key figures ) by right clicking the created info area
    • Create new characteristics and key figures under respective catalogs according to the project requirement
    • Create required info objects and Activate.
    6. Creation of Data Source
    • In the left panel select data sources
    • Create application component(AC)
    • Right click AC and create datasource
    • Specify data source name, source system, and data type ( Transaction data )
    • In general tab give short, medium, and long description.
    • In extraction tab specify file path, header rows to be ignored, data format(csv) and data separator( , )
    • In proposal tab load example data and verify it.
    • In field tab you can give the technical name of info objects in the template and you not have to map during the transformation the server will automatically map accordingly. If you are not mapping in this field tab you have to manually map during the transformation in Info providers.
    • Activate data source and read preview data under preview tab.
    • Create info package by right clicking data source and in schedule tab click star to load data to PSA.( make sure to close the flat file during loading )
    7. Creation of data targets
    • In left panel select info provider
    • Select created info area and right click to create ODS( Data store object ) or Cube.
    • Specify name fro the ODS or cube and click create
    • From the template window select the required characteristics and key figures and drag and drop it into the DATA FIELD and KEY FIELDS
    • Click Activate.
    • Right click on ODS or Cube and select create transformation.
    • In source of transformation , select object type( data source) and specify its name and source system Note: Source system will be a temporary folder or package into which data is getting stored
    • Activate created transformation
    • Create Data transfer process (DTP) by right clicking the master data attributes
    • In extraction tab specify extraction mode ( full)
    • In update tab specify error handling ( request green)
    • Activate DTP and in execute tab click execute button to load data in data targets.
    8. Monitor
    Right Click data targets and select manage and in contents tab select contents to view the loaded data. There are two tables in ODS new table and active table to load data from new table to active table you have to activate after selecting the loaded data . Alternatively monitor icon can be used.
    Create info package by right clicking data source and in schedule tab click star to load data to PSA.( make sure to close the flat file during loading )
    • Activate DTP and in execute tab click execute button to load data in data targets.
    BW is mainly for Reporting purpose on Organizations Historical Data.
    It is a Data Warehousing solution developed by SAP in 1997. Using this we can analyze .....Subject Specific.....Integrated....Non volatile....Time variant Data in support of DECISION MAKING.
    BW is offering End-End solution...like From Modeling to Repoting.
    We can Extract data from 8 different source systems.
    Business content is a big advantage.
    Web Application Designer and integration to Portals are some other features of BW.
    In ABAP ( R/3) Tables contain current data.
    In BW Cubes contain historical Data.
    R/3 is designed for Transactional purpose ( OLTP ).
    BW is designed for Analysis purpose ( OLAP ).
    Regards,
    Medha.

Maybe you are looking for

  • Can Key Mapping details be available as a serach parameter in MDM DM?

    Hello Experts, Is there any way that we can display or search certain Records in Data Manager/Portal based on the Key Mapping details (Remote System/Key Value assigned for any remote system). The scenario where I am trying to apply this is: I have sa

  • Error while deploying EAR from commandline

    Hi, I am getting the following error when i am trying to deploy EAR using commandline in Oracle 10gAS 10.1.2 Error: Unexpected error during lookup : Lookup error: javax.naming.AuthenticationException: Invalid username/password for default (ias_admin)

  • HT2305 I have a new computer and had to install ITunes on it, but the site does not recognize my ipod.

    I have a new PC and have to install the software so Apple will recognize my IPOD 4th generation and be able to sync it.  I down loaded the software, but when I connect my IPOD it does name the IPOD and list the contents of it.  What doe I need to do

  • Depreciation Run -"Last Posting run terminated Restart in period 03 2010"

    Hello Friends, Please help me for this. I am trying to run depreciation for a CoCd 2002 in production. When I do AFAB for FY 2010 Period 04. It gives a error message "Last Posting run terminated, restart in period 2010 003" Diagnosis* The last postin

  • Black Levels in MPEG-2 files

    This is a problem I've been trying to solve for months. Whenever I encode an MPEG-2 file, regardless of what program I'm using (After Effects CS3, Sorensen Squeeze, among others), the black levels are milky grey, not black. This is a short film origi