Method 1 – Recommended one: Using the CTS (Transport)
Prerequisite:
- Identify the correct R900xxx.xxx and K900xxx.xxx to use, for it, read the readme.txt file in the following folder <install_dir>/Business Objects Data Services/admin/R3_functions/transport
- In case of DataServices version before 4.1, you need to check the Unicode or Non-Unicode version of SAP system. To do it, log on to the SAP system, in the Menu Bar, go to ->System -> Status:
![04-11-2013 12-11-10.png]()
Step N° | Screenshot
| Comment |
1 | ![04-11-2013 12-11-33.png]()
| On the SAP Server: - Copy R900xxx.xxx in /usr/sap/trans/data, check write privilege on file (chmod 666 on Unix)
- Copy K900xxx.xxx in /usr/sap/trans/cofiles, check write privilege on file (chmod 666 on Unix)
With Transaction AL11 you could check that both files are present |
2 |
| Launch STMS transaction in SAP Click on , DataServices Transport are not available |
3 | ![04-11-2013 12-12-03.png]() | In Menu Bar, click on ->Extras ->Other Requests ->Add |
4 | ![04-11-2013 12-16-47.png]() | Select the DataServices transport to add. If files copied in folders are: x900yyy.R63, transport request is R63K900yyy. Click on . |
5 | ![04-11-2013 12-17-00.png]() | The DataServices transport is now available, Select it and click on . |
6 | ![04-11-2013 12-18-13.png]() | - Fill the right Target Client
- Mark checkbox “Ignore Invalid Component Version“
Click on . |
7 | ![04-11-2013 12-18-29.png]() | Open SE37 transaction and check if function module starting with /BODS/* are available. Function module name are displayed in DataServices documentation. |
Method 2 - Use .txt file
(See DataServices documentation)