I believe that this is a new function within BW 3.0.. The DataSource now have an option “DataSource transfers double data records” on the “Processing” tab. Then there is a flag to “Ignore double data records”.
Not sure of the workaround for lesser versions of BW.
Two Topics: Automating your InfoCube deletes, and using an ODS to track deltas.
TOPIC 1
——-
If you do not COMPRESS the current fiscal period’s data in your target cube (which eliminates the Request ID,) you can automate the process of deleting the prior request when you reload your data every day. You accomplish this through configuration on the InfoPackage with which you load the data:
A) Go in to InfoPackage maintenance
B) Click the Data Targets tab.
C) For your selected data target, click the icon which looks like the Greek sigma, under the column labeled “Automatic loading of similar/identical requests in the InfoCube.” You can also type DELE in the command field. A popup window entitled “Deleting Request from InfoCube after Update” will appear.
D) On the popup window, you have the option of selecting “Always delete existing requests if delete conditions are found” and “Only for the same selection conditions.” If you select these options, then BW will automatically delete (or reverse if you have aggregates) any prior request for the same selection criteria which has not been compressed.
You can configure your InfoPackage in this manner, and then compress the request when you go to a new fiscal period and no that you will not load any more data for the prior fiscal period.
TOPIC 2
——-
It sounds like you may be reloading every day in order to catch changes to the data. You may know this already, but just in case: You can use an ODS object to capture deltas, and then send only the changes to your cube. This eliminates the need to delete the prior request from your cube, and simplifies the use of cube compression and aggregates.
You then would load the current period’s full set of data into your ODS every day, and the built-in functionality of the ODS object would detect the differences and send only these on to your target cube. You can read more about this scenario in the white paper at service.sap.com/bw entitled “Data Staging Scenarios.”
Finally, using an ODS object as the data staging area eliminates (I think) your issues with the PSA. Instead of having your application read the PSA, have it read from an ODS object instead. Every ODS object has a unique key, so you won’t get duplicate records as you can with a PSA. You can also report on ODS data in BEx queries, if you have any need to, which is yet another advantage this method has over the use of PSA.
We use Cube 0COOM_CO1, which has a time characteristic of fiscal period. We manually load the current period into this cube daily. But to ensure that we do not have duplicate data in the cube we manually delete the previous day’s request before loading the period again. There has to be an easier way to do this, any suggestions on how to automate this process?
Also, the same with the PSA. We have an application reading the PSA, and to avoid duplicate records in the PSA, we are deleting the PSA load before loading it again the next day. Unfortunately with the PSA, the only way to delete a specific request that I can find is to go into the request and mark it as a status of NOT OK, then delete all requests with errors.
You can automate the data deletion process from the InfoPackage. If you look under the “Data Targets” tab of the InfoPackage, there is a Checkbox to “delete the entire content of the data target”. Setting this checkbox will ensure that the data is deleted before the new load.
About the PSA, there is feature by which data can be deleted from the PSA.
Here are the steps for this -
1. Go to the PSA menu under the Admin. Workbench.
2. Navigate to the DataSource for which you want to the set the deletion criteria.
3. Highlight the DataSource and right-click. You will see “Delete PSA Data” in the context menu. Select that.
4. On the next screen, you can now maintain the deletion parameters. The deletion of PSA data can be done based on Date or Days. You can also select successful & error requests for deletion.
5. Create a background job after setting the deletion parameters and schedule it.
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.
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.
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 ).
Infocubes have a multidimensional structure with dimension tables(max 16, 13 custom) and one fact table. they are meant for summarised records.
ODS store data at a more granular level. they have flat structures like a table in R/3. They have a unique feature “overwrite” which is absent in case of cubes.
You can use ODS to load to cube further.
Anyway, one major difference is the manner of data storage. In ODS, data is stored in flat tables. By flat we mean to say ordinary transparent table whereas in a CUBE, it composed of multiple tables arranged in a STAR SCHEMA joined by SIDs. The purpose is to do MULTI-DIMENSIONAL Reporting
Another difference is : In ODS, you can update an existing record given the KEY. In CUBES, theres no such thing. It will accept duplicate records and during reporting, SUM the keyfigures up. Theres no EDIT previous record contents just ADD. With ODS, the procedure is UPDATE IF EXISTING (base from the Table Key) otherwise ADD RECORD.
ODS
Stores line item level detail, more granular Can’t create aggregates on ODS ODS are based on flat tables Only two dimensional reporting possible on ODS. Overwrite feature available while loading records
Infocube
- Stores summarized data, less granular.
- Aggregates can be created on top of Infocubes for better performance of Queries.
- Multi-dimensional reporting possible on Infocube.
- Theres no overwrite feature while loading records.
Infocubes are MDM objects that fact table and dimension table are available whereas ODS is not a MDM object there are no fact tables and dimension tables. It consists of flat transparent tables.
In infocubes there are characteristics and keyfigures but in ods key fields and data fields. we can keep non key characteristics in data fields.
Some times we need detailed reports we can get through ODS. ODS are used to store data in a granular form i.e level of detail is more. The data in the infocube is in aggregated form.
From reporting point of view ods is used for operational reporting where as infocubes for multidimensional reporting.
ODS are used to merge data from one or more infosources but infocubes does not have that facility.
The default update type for an ODS object is overwrite for infocube it is addition. ODS are used to implement delta in BW. Data is loaded into the ODS object as new records or updating existing records in change log or overwrite existing records in active data table using 0record mode.
You cannot load data using Idoc transfer method in ODS but u can do in infocube.
You cannot create aggregate on ODS. You cannot create infosets on infocube.
ODS objects can be used.
When you want to use the facility of overwrite. If you want to overwrite nonkey characteristics and key figures. If you want detailed reports you can use ODS.
If you want to merge data from two or more infosources you can use ODS. It allows you to drill down from infocube to ODS through RRI interface.
ODS objects can be used in the following scenarios. ODS is not a mandatory but depending on the requirements we have to use it.
When you want to use the facility of overwrite. If you want to overwrite nonkey characteristics and key figures in the data fields column.
If you want detailed reports, you can use ODS.
If you want to merge data from two or more infosources you can use ODS.
It allows you to drill down from infocube to ODS through RRI interface if u want detailed data from ODS.
If you want to create an external file.
The most important difference between ODS and BW is the existence of key fields in the ODS. In the ODS you can have up to 16 info objects as key fields. Any other info objects will either be added or overwritten! So if you have flat files and want to be able to upload them multiple times you should not load them directly into the info cube, otherwise you need to delete the old request before uploading a new one. There is the disadvantage that if you delete rows in the flat file the rows are not deleted in the ODS.
I also use ODS-Objects to upload control data for update or transfer routines. You can simply do a select on the ODS-Table /BIC/A00 to get the data.
ODS is used as an intermediate storage area of operational data for the data ware house . ODS contains high granular data . ODS are based on flat tables, resulting in simple modeling of ODS . We can cleanse transform merge sort data to build staging tables that can later be used to populate INOFCUBE .
An infocube is a multidimentionsl dat acontainer used as a basis for analysis and reporting processing. The infocube is a fact table and their associated dimension tables in a star schema. It looks like a fact table appears in the middle of the graphic, along with several surrounding dimension tables. The central fact is usually very large, measured in gigabytes. it is the table from which you retrieve the interesting data. the size of the dimension tables amounts to only 1 to 5 percent of hte size of the fact table. Common dimensions are unit & time etc.
There are different type of infocubes in BW, such as basic infocubes, remote infocubes etc.
An ODS is a flat data container used for reporting and data cleansing/quality assurance purpose. They are not based on star schema and are used primaily for detail reporting rather than for dimensional analyais.
An infocube has a fact table, which contains his facts (key figures) and a relation to dimension tables. This means that an infocube exists of more than one table. These tables all relate to each other. This is also called the star scheme, because the dimension tables all relate to the fact table, which is the central point. A dimension is for example the customer dimension, which contains all data that is important for the customer.
An ODS is a flat structure. It is just one table that contains all data. Most of the time you use an ODS for line item data. Then you aggregate this data to an infocube.
ODS holds transactional level data..Its just as a flat table. Its not based on multidimensional model. ODS have three tables 1. Active table 2. change log 3. New table
Cube holds aggregated data which is not as detailed as ODS. Cube is based on multidimensional model. Cube have 2 tables 1. E table 2. F table.
Validation allows solid data entry regarding special rules. According to previous rules, the system can evaluate an entry and a message can appear on the user’s terminal if a check statement is not met. A validation step contains prerequisite statement and check statement. Both of them are defined using Boolean Logic or calling an ABAP/4 form.
Data Reconcialtion:
Reconcilation is the process of comparing the data after it is transferred to the BW system with the source system. The procedure to do reconcilation is either you can check the data from the SE16 if the data is coming from a particular table only or if the datasource is any std datasource then the data is coming from the many tables in that scenario what I used to do ask the R/3 consultant to report on that particular selections and used to get the data in the excel sheet and then used to reconcile with the data in BW . If you are familiar with the reports of R/3 then you are good to go meaning you need not be dependant on the R/3 consultant ( its better to know which reports to run to check the data ).
How to do Reconciliation?
There are two ways for Reconciliation:
1) Create Basic Cube and load the data from the source system. In the same way create another cube of type Virtual cube. After creating those two cubes, create one multiprovider by using the Basic Cube and Virtual Cube, in the Identification of the Multiprovider select two cube. Then go to reporting create the query and write on formule to compare the values of these two cubes.
2) See the contents of the basic cube which is there is BW. In that screen one Button is there as “SAVE AS”. Click that button and select as “Spread sheet”. Save as .xls. In the Source system side also go to T-Code RSA3, select your data source which you assigned to the basic cube. Click on execute and see the contents.
Now again here also select the “SAVE AS” button and select the spread sheet and save under .xls file. Ok now your two flat file are ready. Now move one file into other by using “move copy”. Now two flat files are in one excel sheet only in different sheets. Now write a formula to compare the values of sheet 1 and sheet 2 in either in sheet1 or sheet2.
It is operational data store. ODS is a BW Architectural component that appears between PSA ( Persistant Staging Area ) and infocubes and that allows Bex ( Business Explorer ) reporting. It is not based on the star schema and is used primarily for details reporting, rather than for dimensional analysis. ODS objects do not aggregate data as infocubes do. Data are loaded into an IDS object by inserting new records, updating existing records, or deleting old records as specified by RECORDMODE value. *– Viji
1. How much time does it take to extract 1 million of records from an infocube?
2. How much does it take to load (before question extract) 1 million of records to an infocube?
3. What are the four ASAP Methodologies?
4. How do you measure the size of infocube?
5. Difference between infocube and ODS?
6. Difference between display attributes and navigational attributes? *– Kiran
1. Ans. This depends,if you have complex coding in update rules it will take longer time,orelse it will take less than 30 mins.
3. Ans:
Project plan
Requirements gathering
Gap Analysis
Project Realization
4. Ans:
In no of records
5. Ans:
Infocube is structured as star schema(extended) where in a fact table is surrounded by different dim table which connects to sids. And the data wise, you will have aggregated data in the cubes.
ODS is a flat structure(flat table) with no star schema concept and which will have granular data(detailed level).
6. Ans:
Display attribute is one which is used only for display purpose in the report.Where as navigational attribute is used for drilling down in the report.We don’t need to maintain Nav attribute in the cube as a characteristic(that is the advantage) to drill down.
*– Ravi
Q1. SOME DATA IS UPLOADED TWICE INTO INFOCUBE. HOW TO CORRECT IT?
Ans: But how is it possible?.If you load it manually twice, then you can delete it by request.
Q2. CAN U ADD A NEW FIELD AT THE ODS LEVEL?
Sure you can.ODS is nothing but a table.
Q3. CAN NUMBER OF DATASOURCE HAS ONE INFOSOURCE?
Yes ofcourse.For example, for loading text and hierarchies we use different data sources but the same infosource.
Q4. BRIEF THE DATAFLOW IN BW.
Data flows from transactional system to analytical system(BW).DS on the transactional system needs to be replicated on BW side and attached to infosource and update rules respectively.
Q5. CURRENCY CONVERSIONS CAN BE WRITTEN IN UPDATE RULES. WHY NOT IN TRANSFER RULES?
Q6. WHAT IS PROCEDURE TO UPDATE DATA INTO DATA TARGETS?
Full and delta.
Q7. AS WE USE Sbwnn,SBiw1,sbiw2 for delta update in LIS THEN WHAT IS THE PROCEDURE IN LO-COCKPIT?
No lis in lo cockpit.We will have data sources and can be maintained(append fields).Refer white paper on LO-Cokpit extractions.
Q8. SIGNIFICANCE OF ODS.
It holds granular data.
Q9. WHERE THE PSA DATA IS STORED?
In PSA table.
Q10.WHAT IS DATA SIZE?
The volume of data one data target holds(in no.of records)
Q11. DIFFERENT TYPES OF INFOCUBES.
Basic,Virtual(remote,sap remote and multi)
Q12. INFOSET QUERY.
Can be made of ODSs and objects
Q13. IF THERE ARE 2 DATASOURCES HOW MANY TRANSFER STRUCTURES ARE THERE.
In R/3 or in BW??.2 in R/3 and 2 in BW
Q14. ROUTINES?
Exist In the info object,transfer routines,update routines and start routine
Q15. BRIEF SOME STRUCTURES USED IN BEX.
Rows and Columns,you can create structures.
Q16. WHAT ARE THE DIFFERENT VARIABLES USED IN BEX?
Variable with default entry
Replacement path
SAP exit
Customer exit
Authorization
Q17. HOW MANY LEVELS YOU CAN GO IN REPORTING?
You can drill down to any level you want using Nav attributes and jump targets
Q18. WHAT ARE INDEXES?
Indexes are data base indexes,which help in retrieving data fastly.
Q19. DIFFERENCE BETWEEN 2.1 AND 3.X VERSIONS.
Help!!!!!!!!!!!!!!!!!!!Refer documentation
Q20. IS IT NESSESARY TO INITIALIZE EACH TIME THE DELTA UPDATE IS USED.
Nope
Q21. WHAT IS THE SIGNIFICANCE OF KPI’S?
KPI’s indicate the performance of a company.These are key figures
Q22. AFTER THE DATA EXTRACTION WHAT IS THE IMAGE POSITION.
After image(correct me if I am wrong)
Q23. REPORTING AND RESTRICTIONS.
Help!!!!!!!!!!!!!!!!!!!Refer documentation
Q24. TOOLS USED FOR PERFORMANCE TUNING.
ST*,Number ranges,delete indexes before load ..etc
Q25. PROCESS CHAINS: IF U ARE USED USING IT THEN HOW WILL U SCHEDULING DATA DAILY.
There should be some tool to run the job daily(SM37 jobs)
Q26. AUTHORIZATIONS.
Profile generator
Q27. WEB REPORTING.
What are you expecting??
Q28. CAN CHARECTERSTIC CAN BE INFOPROVIDER ,INFOOBJECT CAN BE INFOPROVIDER.
Of course
Q29. PROCEDURES OF REPORTING ON MULTICUBES.
Refer help.What are you expecting??.Multicube works on Union condition
Q30. EXPLAIN TRANPORTATION OF OBJECTS?
Dev —> Q and Dev —> P
By : Ravi at http://www.sap-img.com/
1. What is table partition?
A: SAP is using fact table partitioning to improve the performance. you can partition only on 0CALMONTH or 0FISCPER
2. What are the options available in transfer rule and when ABAP code is recquired during the transfer rule what important variables you can use?
A: Assign info object, Assign a Constant , ABAP routine or a Formula
3. How would you optimize the dimensions?
A: Use as many as possible for performance improvement; Ex: Assume that u have 100 products and 200 customers; if you make one dimension for both ,the size of the dimension will be 20000; if you make individual dimensions then the total number of rows will be 300. Even if you put more than one characterstic per dimension, do the math considering worst case senerio and decide which characterstics may be combined in a dimension.
4. What are the conversion routines for units and currencies in the update rule?
A: Time dimensions are automatically converted; Ex: if the cube contains calender month and your transfer structure contains date, the date to calender month is converted automatically.
5. Can you make an infoobject as info provider and why?
A. Yes, When you want to report on characterstics or master data, you can make them as infoprovider. Ex: you can make 0CUSTMER as infoprovider and do Bex reporting on 0 CUSTOMER;right click on the infoarea and select ‘Insert characterstic as data target’.
6. What are the steps to unload non cumulative cubes?
A: 1. Initialize openig balance in R/3(S278)
2. Activate extract structure MC03BF0 for data source 2LIS_03_BF
3. setup historical material docus in R/3.
4. load opening balance using data source 2LIS_40_s278
5. load historical movements and compress without marker update.
6. setup V3 Update
7. load deltas using 2LIS_03_BF
7. Give step to step approach to archiving cubex.
A: 1. double click on the cube (or right click and select change)
2. Extras -> Select archival
3. Choose fields for selection(like 0CALDAY, 0CUSTOMER..etc)
4. Define the file structure(max file size and max no of data objects)
5. Select the folder(logical file name)
6. Select the delete options (not scheduled, start automatically or after event)
7. activate the cube.
8. cube is ready for archival.
8. What are the load process and post processing?
A: Info packake, Read PSA and update data target, Save Hierarchy, Update ODS data object, Data export(open hub), delete overlapping requests.
9. What are the data target administration task
A: delete index, generate index, construct database statistics, initial fill of new aggregates, roll up of filled aggregates, compression of the infocube,activate ODS, complete deletion of data target.
10. What are the parallel process that could have locking problems
A: 1. heirachy attribute change run
2. loading master data from same infoobject; for ex: avoid master data from different source systems at the same time.
3. rolling up for the same info cube.
4. selecting deletion of info cube/ ODS and parallel loading.
5. activation or delection of ODS object when loading parallel.
11. How would you convert a info package group into a process chain?
A: Double Click on the info package grp, click on the ‘Process Chain Maint’ button and type in the name and descrition ; the individual info packages are inserted automatically.
12. How do you transoform Open Hub Data?
A: Using BADI
13. What are the data loading tuning one can do?
A: 1. watch the ABAP code in transfer and update rules;
2. load balance on different servers
3. indexes on source tables
4. use fixed length files if u load data from flat files and put the file on the application server.
5. use content extractor
6. use PSA and data target inparallel option in the info package
7. start several info packagers parallel with different selection options
8. buffer the SID number ranges if u load lot of data at once
9. load master data before loading transaction data.
14. What is ODS?
A: Operations data Source . u can overwrite the existing data in ODS.
15. What is the use of BW Statistics?
A: The sets of cubes delivered by SAP is used to measure performance for query, loading data etc., It also shoes the usage of aggregates and the cost associated with then.
16. What are the options when definging aggregates?
A: * – groups accotding to characterstics
H – Hierarchy
F – fixed value
Blank — none
17. How will you debug errors with SAP GUI (like Active X error etc)
A: Run Bex analyzer -> Business Explorer menu item -> Installation check; this shows an excel sheet with a start button; click on it; this verifies the GUI installation ;if u find any errors either reinstall or fix it.
18. When you write user exit for variables what does I_Step do?
A: I_Step is used in ABAP code as a conditional check.
19. How do you replace a query result from a master query to a child query?
A: If you select characterstic value with replacement path then it used the results from previuos query; for ex: let us assume that u have query Q1 which displaysthe top 10 customers, we have query Q2 which gets the top 10 customers for info object 0customer with as a vairable with replacement path and display detailed report on the customers list passed from Q1.
20. How do you define exception reporting in the background?
A: Use the reporting agent for this from the AWB. Click on the exception icon on the left;give a name and description. Select the exception from query for reporting(drag and drop).
21. What kind of tools are available to monitor the overall Query Performance?
22. What can I do if the database proportion is high for all queries?
23. How to call a BW Query from an ABAP program?
24. What are the extractor types?
25. What are the steps to extract data from R/3?
26. What are the steps to configure third party (BAPI) tools?
27. What are the delta options available when you load from flat file?
28. What are the table filled when you select ABAP?
29. What are the steps to create classes in SAP-BW
30. How do you convert from LIS to LO extraction?
31. How do you keep your self-updated on major SAP Develppments, Give an analytical *– Anil Bommu
Why there is frequent load failures during extractions? and how they are going to analyse them?
If these failures are related to Data,, there might be data inconsistency in source system..though you are handling properly in transfer rules. You can monitor these issues in T-code -> RSMO and PSA (failed records).and update .
If you are talking about whole extraction process, there might be issues of work process scheduling and IDoc transfer to target system from source system. These issues can be re-initiated by canceling that specific data load and ( usually by changing Request color from Yellow – > Red in RSMO).. and restart the extraction.
How To…Create a generic extractor from SAP R/3
What is reconciliation in bw? What the procedure to do reconciliation?
Reconcilation is the process of comparing the data after it is transferred to the BW system with the source system. The procedure to do reconcilation is either you can check the data from the SE16 if the data is coming from a particular table only or if the datasource is any std datasource then the data is coming from the many tables in that scenario what I used to do ask the R/3 consultant to report on that particular selections and used to get the data in the excel sheet and then used to reconcile with the data in BW . If you are familiar with the reports of R/3 then you are good to go meaning you need not be dependant on the R/3 consultant ( its better to know which reports to run to check the data ).
SAP NetWeaver Business Warehouse (SAP NetWeaver BW) unites a powerful business intelligence platform, a comprehensive set of tools, planning and simulation capabilities, and data-warehousing functionality – delivered through sophisticated and user-centric enterprise portal technology to provide a coherent, comprehensive solution.
SAP BW has three layers:
Business Explorer: As the top layer in the SAP BW architecture, the Business Explorer (BEx) serves as the reporting environment (presentation and analysis) for end users. It consists of the BEx Analyzer, BEx Browser, BEx Web, and BEx Map for analysis and reporting activities.
Business Information Warehouse Server: The SAP BW server, as the middle layer, has two primary roles:
• Data warehouse management and administration: These tasks are handled by the production data extractor (a set of programs for the extraction of data from R/3 OLTP applications such as logistics, and controlling), the staging engine, and the Administrator Workbench.
• Data storage and representation: These tasks are handled by the InfoCubes in conjunction with the data manager, Metadata repository, and Operational Data Store (ODS).
Source Systems: The source systems, as the bottom layer, serve as the data sources for raw business data. SAP BW supports various data sources:
• R/3 Systems as of Release 3.1H (with Business Content) and R/3 Systems prior to Release 3.1H (SAP BW regards them as external systems)
• Non-SAP systems or external systems
• mySAP.com components (such as mySAP SCM, mySAP SEM, mySAP CRM, or R/3 components) or another SAP BW system.
