Professional Documents
Culture Documents
This document covers the baseline principle of setting up a SAP BPC 5.0 data manager package using SSIS in SQL 2005. This document is not intended to provide technical specification on SAP BPC 5.0
2 Introduction
Microsoft has re-architected SQL Server and as such has changed the structure of their ETL tool (removed DTS and added SSIS). Microsoft has provided a backward compatibility for all of our tasks except for the dynamic scripting capability commonly known as evModifyScript.
To edit the new SSIS package you require Business Intelligence Development Studio. It is bundled in the client component of SQL 2005. .DTSX is the SQL2005 packages extension SAP BPC Data Manager has a new interface to manage dynamic parameters
If you choose to convert an old custom DTS packages you must use the Microsoft conversion tool. In SQL2005 there is a conversion tool that allows converting the existing DTS packages in new .DTSX packages. This tool tries to convert all tasks defined in the package. If it cannot convert some tasks, all tasks not converted will be encapsulated in one new task called Execute DTS 2000. In order to use the conversion tool you have to download and install a new component called SQL Server 2000 DTS Designer Component. Once converted you would need to replace the old SQL 2000 custom tasks with the new SQL 2005 custom tasks. The step by step section below can be applied when converting or creating a new SSIS package. Note: SQL 2000 DTS and SQL 2005 SSIS client tools can co-exist on a machine. SAP has not tested this set up and we do not recommend this for the database server.
1. Assuming that SAP BPC is installed in folder C:\Outlooksoft, copy the following files from C:\Outlooksoft\Websrvr\bin to C:\Program Files\Microsoft SQL Server\90\DTS\Tasks\ NOTE: The files must be copied on the server where you will edit the SSIS packages using Visual Studio. On a multi-server, we recommend this be done on the application server tier not the database server tier.
4.2
Register SAP BPC Custom Tasks (only need to do this the first time)
1. From the server you want to edit the SSIS packages, launch the SQL Server Business Intelligence Development Studio.
9. Ensure that all SAP BPC tasks are checked on and click OK.
10. Right click on Control Flow Items and choose Add Tab
4.3
Similar to DTS, you can create a SSIS package by dragging and dropping the appropriate tasks. For the purposes of this document we will use the common tasks of a convert task and a dumpload task. 1. From the server you want to edit the SSIS packages, launch the SQL Server Business Intelligence Development Studio.
8. If youre interested in editing the task, right click on Convert Task and click Edit.
4.4
Dynamic Script
SAP BPC 5.0 design allows for the user to pass parameter via the Data Manager interface into the task flow of a DTS/SSIS package. SSIS has prevented us from using the same method to provide this functionality. Microsoft changed the object model to prevent us from using EVmodifyTask. Therefore, we need a two step process to achieve the same results. 1. Click SSIS on the menu and choose Variables
6. Navigate to your SAP BPC package folder you want to save this package to.
4.5
11. This interface allows you to view the package tasks and their properties for both DTS and SSIS. Take special note of the task names that were used when you registered the custom tasks as they may have changed. For our example we have two tasks in our package - Convert Task, DumpLoad Task.
12. To edit a package (only available for SSIS, not DTS), click Advanced
13. You will see a blank screen. This represents the Modify variable. Here is where you can take an older DTS evModify script and paste it into the new package. For our example the image below shows the standard DTS import package script.
14. Note, the task names do not match the new SSIS package task names. Therefore before we save the task names must be edited. For our example we need to change all references from CONVERT data to Convert Task and from LOAD AND PROCESS to DumpLoad Task as shown below.
15. Click Save. Now the new package can be run from the Data Manager Client.
5 Troubleshooting
Known Issues: 5.1 Error Message Box when you run any Data Manager Package
We have identified a problem with Excel 2003 SP2. The symptom of this problem is an error message box will come up as soon as you run any DM package. This problem will not happen in other Excel version and 2003 SP1.