I like to elaborate more about the use of SAP query, since I find this one the most flexible and robust option.ДЄn SAP query can be executed in the background, and the output of the query can be written to a dedicated location on the SAP server, in a specified format (this will require the implementation of an SAP User Exit). The upside is, everything is posiible, the downside is,В for any future changes you will require programming skills. Third, the use of SAP query, where it is possible to join tables and add additional fields.ДЇinally, and this is completely custom build, is the use of an ABAP program.

To a certain extend these can be sufficient. Second, reports that make use of customized tables like the Profitability Analysis (COPA) and Logistic Information Systems (LIS). Typically for financial related extractions, for example to feed a consolidation tool, these are sufficient. Obviously, the first and easiest choice that comes to mind is the use of the standard reports in SAP. For future maintenance it is always recommended to use the standard as much as possible, but sometimes it is needed to build custom solutions. In general, there are four options available that all have a certain level of standard SAP versus custom build. However, when data is needed for a regular robust maintainable process, and there are no ETL tools available, what options are there? Extracting data from SAP ECC for analyses and reporting purposes is usually done using BI ETL tools, for example SAP Business Warehouse.

Sap ecc reporting tools