Microsoft Connector for SAP BI is a set of managed components for transferring data from or to an SAP NetWeaver BI 7 system. The component is designed to be used with the Enterprise and Developer editions of SQL Server 2008 Integration Services.
1. Microsoft Windows Vista, or Microsoft Windows XP Professional with Service Pack 2, or Microsoft Windows 2003 and above.
2. Microsoft SQL Server 2008 Integration Services. Microsoft Connector 1.0 for SAP BI needs to be installed on the same computer where Integration Services is installed.
3. Windows Installer 4.5 and above.
4. Extracting data using Microsoft Connector 1.0 for SAP BI from SAP BI system requires the SAP Open Hub license. For more info about SAP licensing, please consult your SAP representative.
5. SAP NetWeaver SPS 14 (BI SP 16) is required. BI SP 17 or higher is strongly recommended.
6. To use Microsoft Connector 1.0 for SAP BI in 32-bit (64-bit) mode on any 32-bit (64-bit) operating system, The 32-bit (64-bit) version of librfc32.dll needs to be put under folder %windir%\system32.
7. To use Microsoft Connector 1.0 for SAP BI in 32-bit mode on the 64-bit operating system, the 32-bit librfc32.dll needs to be put in folder %windir%\SysWow64.
1. Librfc32.dll is a component owned by SAP. Microsoft does not support this SAP component and assumes no liability for its use.
2. Microsoft Connector 1.0 for SAP BI does not support SAP BW 3.5 and earlier versions.
3. Extracting data using Microsoft Connector 1.0 for SAP BI from SAP BI system only supports Open Hub Destinations. It does not support InfoSpoke as InfoSpoke is obsolete in SAP NetWeaver BI 7.
1. In an SAP BI system, users can define different separators to customize number formats. However, SAP BI Connector only supports the default separators, which are the thousands separator "." and the decimal separator ",". Thus the only supported number format is "12.345,00".
2. An SAP BI destination component can be configured in "Wait Mode", which means it does not start any InfoPackage. Instead, it waits for a third party to start the InfoPackage. Currently SAP BI Connector only supports a single "Wait Mode" destination component in a package. Customers cannot load data in parallel if the package has multiple "wait mode" SAP BI destination components.
3. Although Microsoft Connector 1.0 for SAP BI has the ability to exchange Unicode data with an SAP BI system, the connector only exchanges non-Unicode control info with SAP BI. When you create an RFC destination or Source System, you need to keep "Communication Type with Target System" at its default value of non-Unicode.
4. When using a data transfer process (DTP) to extract data to an open hub destination, which has the type "3rd party tool", if no new data is extracted, the status of the request remains yellow. You cannot extract new data. This is an issue with SAP BI and you can find detailed information in SAP Note 1180294. To prevent this situation, go to the Advanced Page of the SAP BI Source Editor, input the current Request ID, and click the Reset button. This sets the request status to "G" (green) and allows later extraction.
5. If multiple users access the same RFC Destination/Source System at the same time, it may lead to a time-out result when extracting data from an SAP BI system or loading data to it. It is recommended to use a different RFC Destination for each OHS Destination and InfoSource, and to try to avoid using the same RFC Destination or Source System concurrently.
6. If SAP executes a data transfer process (DTP) in parallel, it may lead to a time-out result when using Microsoft Connector 1.0 for SAP BI to extract data from SAP BI or load data to SAP BI. To avoid the issue, you can set Number of Processes to 1 in DTP's setting for Batch Manager.