In the area of cost center planning, we have tested the export of Palo with a central SAP Business Warehouse. Palo is a multidimensional OLAP database is powered by Jedox, which makes it simple means to create distributed planning applications. The modeling and data collection done within Excel. Here, for example, the SAP solution BW-BPS (Business Planning and Simulation) is less flexible and more expensive, not least in the implementation. For integration we use a simple interface via text file. Thus a consistent reporting in the BW system is made possible with the actual figures, which come from an SAP R / 3. The planning of the cost is Excel-based with Palo. Once this is completed, the cube out via the "Export Data" from the Palo modeller into a csv file. This can be used via a DataSource of type "flat file" for importing data directly into SAP BW. The information package is first loaded into an ODS object, and then updated in the BW InfoCube. In the update rule, the individual can KEYFIGUREInfoCubes are filled according to the values of specific fields, such as Palo dimension measures. For some of the dimensions have to be imported or master data from Palo (eg cost centers in SAP BW are not yet in R / 3 are maintained). This is done with another csv file that is created from the export attribute Palo cubes are also using the "data". BW can be used for this purpose in each of 2 separate information packages for the attributes and text of the corresponding BW info objects. For the import of hierarchy relations a little more effort would have to be operated, in our scenario, however, this was not necessary. For a simple cost center planning can be the right approach in Palo: This is a particularly positive that is essential for the planning of Excel as a front end only, and that the write-back of data takes place without delay: This increases the acceptance! Through the integration capability with SAP Netweaver BI is still a single, global reporting possible. Author: Andreas Frhlich - JedoxLtd.