SAP R/3 or SAP ECC Reporting Limitations

1. SAP R/3(OLTP) offers a collection of more than 2700 powerful and flexible business reports.
These reports are spread across several applications. Navigating through several multilevel
menus to fetch a particular set of reports is a time consuming process.
 
2. Several reports are designed(delivered by default) to meet operational or transaction needs only.
 
3. Most of the reports are predefined, list oriented & provides very limited OLAP functionality.
 
4. Several business applications and their associated reporting tools make it hard to select a
specific reporting tool.
 
5. These reporting tools are inconsistent, designing & creating a report is a complex process.
 
6. Maintenance of thousands of available reports for software upgrade (VERSION UPGRADE) is
a complex task.
 
7. Knowledge of how often a particular report is used are every period is not available.
 
8. As a consequence( Consequently) all reports are need to be maintained regardless of their
usage.
 
9. Performance impact on SAP R/3 OLTP Operations is a major issue.
 
10. SAP R/3 OLTP system are designed & configured to meet high transaction rates( No of
transactions for a time period)
 
11. Creating a robust report & generating OLAP environment( Reporting environment) under
OLTP environment (Transaction Environment) needs different configuration parameters.
 
12. These settings will affect the OLTP operations intern.
 
13. SAP R/3 OLTP reports are flat reports ( 2 dimensional ), where as BW reports are Multi-
dimensional, MultiLingual, Several levels of hierarchies are supported in SAP BW reporting. Master data makes resusability - [Attributes, Texts, Hierarchies] in SAP BW.
 
14. Creation of report takes more time in SAP R/3 Where as it takes very less time in SAP BW.
 
15. SAP R/3 or ECC reports are application specific where as BW reports are subject specific.

Comments

Anonymous said…
Thanks for sharing this Information. Got to learn new things from your Blog on SAP HANA

http://thecreatingexperts.com/category/sap-hana-training-in-chennai/

contact 8122241286
August 2, 2017 at 4:49 AM
Anonymous said…
Thanks for sharing this Information. Got to learn new things from your Blog on SAP HANA

http://thecreatingexperts.com/category/sap-hana-training-in-chennai/

contact 8122241286
August 2, 2017 at 4:50 AM
Post a Comment

Popular posts from this blog

One stage stop to know all about BW Extractors-Part1

Image
Types of Extractors:               Application specific BW content extractors: Lo Extraction: Logistics refers to the process of getting a product or service to its desired location upon request which involves transportation, purchasing, warehousing etc. Main areas in logistics are: Sales and Distribution (SD) : application 11, 13, 08 (in LBWE T-code) Materials Management (MM) : application 03, 02 Logistics Execution (LE) : application 12 Quality Management : application 05 Plant Maintenance (PM) : application 04, 17 Customer Service (CS) : application 18 Project System (PS) : application 20 SAP Retail : application 40,43,44,45 How the data extraction happens? Extraction can be done using either Full update/delta update. Full load: Incase of logistic application, Full/Initiali
Read more

Generic Extraction via Function Module

How does the extraction API work in case you are extracting data using a self defined function module with generic delta? Sometimes, if your application or requirement makes it necessary, you have to create your own function module to extract the data from whatever sap system to bw. Therefore you normally make a copy of the standard fm 'RSAX_BIW_GET_DATA_SIMPLE'. To make this new function work for you, you have to realize the following. 1) The FM gets called by the extraction API for at least 2 times. First time is for initialization and from the 2nd time on it is for data extraction. 2) Right after the last data package (somehow you need to make sure that it is the last one) you have to raise the exception no_more_data. Example with lots of comments FUNCTION RSAX_BIW_GET_DATA_SIMPLE. *"-------------------------------------------------------------------------- *"*"Local interface: *" IMPORTING *" VALUE(I_REQUNR) TYPE SRSC_S_IF_SIMPLE-REQUN
Read more

COPA Extraction Step By Step in SAP BW

Image
COPA Extraction Step by Step: SAP R/3 or SAP ECC: 1. SAP R/3 or ECC goto T.Code KEB0 , In Function: Select Create  Control Parameters: Provide a New CO-PA DataSource Name:1_CO_PA%CL%ERK 2. Select your O perating C oncern, e.g.,IDES. 3. Select radio button Costing-based or Account-based as OC . 4.Select field names for partitioning.e.g. BUKRS (Company Code), Check 5.Click on Info Catalog (F7) 6. Select the Characteristics & Value fields & Keyfigures 7. Select the Package/Development Class for Workbench request 8. Edit your DataSource to select/Hide fields, Save. Datasource created successfully. 9. Extractor Checker or RSA3, extraction. SAP BW:   1. Replicate DataSource 2. Assign InfoSource 3. Transfer all the datasource elements to an InfoSource 4. Activate InfoSource 5. Create a InfoCube (Copy Str from InfoSource) 6. Create Dimension & Define and Assign it. 7. Check & Activate. 8. Create Transformation (Insert or Modify KF
Read more