In some companies, a transactional system such as R/3 may no longer be enough to handle all HR reporting needs. Evaluate certain circumstances in which a BW system can more effectively cater to a particular reporting requirement.
To create a comprehensive reporting environment in SAP HR, you need support from your SAP BW environment. If you diligently analyze, design, and build the online transaction processing (OLTP, in this case SAP HR) and online analytical processing (OLAP, in this case SAP BW) systems, they can coexist in harmony. Although the SAP-delivered business content in BW is a good starting point, you may need to build new InfoProviders (objects into which you load data, including InfoCubes and operational data store [ODS] objects) for HR reporting in your BW system. Developing the new InfoProviders requires that you understand several factors: the reporting and drill-down requirements and the nature of data, especially legacy data.
You can develop your HR reporting strategy to take advantage of the strengths of both the online analytical processing (OLAP) SAP BW system and the online transaction processing (OLTP) SAP R/3 or mySAP ERP Central Component (ECC) system. While you can still conduct many HR processes in your R/3 or ECC system, BW, with its standard SAP BW business content for HR, is better suited for many analytical tasks. I’ll give an overview of the factors to consider in selecting a reporting option and show how legacy data migration affects your decision.