Siebel Connector for SAP R/3 - Version: 7.5.3  and later [Release: V7 and later]
Siebel Connector for Oracle Applications - Version: 7.5.3  and later [Release: V7 and later]
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.5.3 
Database: Oracle 8.1.7
Application Server OS: Microsoft Windows 2000 Server SP 2
Database Server OS: Microsoft Windows 2000 Server SP 2
This document was previously published as Siebel SR 38-1584223851.
***Checked for relevance on 01-NOV-2010***
SymptomsWhile attempting to run a workflow process that would send an IDOC to the SAP system, the error that appeared in the log was:
Required property 'SAPRfcUserName' is not set for Business Service 'EAI SAP BAPI Adapter' (SBL-EAI-04167)
It was verified that the Siebel server was able to communicate with the SAP server by running the out of the box workflow process "TestSAPConnection" by using a web client and the workflow process simulator.
The workflow was amended to explicitly passed in connection information by specifying input arguments for SAPRfcConnectString, SAPRfcUserName and SAPRfcPassword though and did not work without these parameters.
CauseSAP specific parametersare such as SAPRfcConnectString, SAPRfcUserName and SAPRfcPassword are not available as component parameters.
They are available only at enteprise level.
SolutionSpecifying values for the SAPRfcUserName and SAPRfcPassword at the Siebel Server level solved the original issue but a new error was observed :
SAP error calling 'RfcOpenEx' for Rfc method ". Message: "Missing R3Name=... or ASHOST=... in connect_param in RfcOpenEx', group 'h', key: 'RFC_ERROR_SYSTEM_FAILURE' (SBL-EAC-00158)
To solve this last error, please add a value for the SAPRfcConnectString at the server level
In summary, the solution was to specify values at ENTERPRISE level for :
BUG: 10482925 has been logged to request that it be possible to set SAP specific parameters at component level.
ReferencesBUG:10482925 - ADD SAP SPECIFIC COMPONENT PARAMETERS TO THE INTERACTIVE OBJECT MANAGERS
Applies to: Siebel Test Automation Interfaces - Version: 126.96.36.199 SIA  and later [Release: V7 and later ]
Information in this document applies to any platform.
Is it possible to implement SAP's Secure Network Communication (SNC) when calling the EAI SAP BAPI Adapter to send data from Siebel to SAP? If so, how can it be implemented?
SolutionThe customer was sending data to SAP by calling the Execute method on the EAI SAP BAPI Adapter. The requirement was to configure the applications so that they communicate using SAPâ€™s Secure Network Communication (SNC).
The following information was provided as part of a SR that was raised by a customer using Version 6:
"The Siebel eBusiness Connector for SAP R/3, uses the SAP RFC SDK 'LIBRFC32.DLL' library for IDOC and BAPI integration functionality to establish an RFC connection to SAP R/3 System.
The SAP Secure Network Communication (SNC) provides an underlying security interface level (for Secude as well), that allows to secure an RFC connection. This is applicable for RFC connections, used by Siebel SAP R/3 Connector. Please refer to accordant SAP Documentation and related SAP OSS Notes on how to setup the SNC functionality as well as on known performance issues. You may consider to refer to SAP OSS Note '0150699 Latest patches for SNC-related problems' for the list of necessary SAP patches for your SAP R/3 Release.
The "Secure Network Communications SNC User's Guide" SAP Guide discusses setup for RFC communication with SNC. As it follows from this guide, you can use the Siebel SAP R/3 Connector with SNC if you define the correct parameters in the 'saprfc.ini' file. The Siebel software does not make use of any additional calls to SNC in the RFC library (as a such library call should support SNC by default). This means that an SNC interface implementation of your security software should use this standard RFC configuration file."
In this case, the customerâ€™s SAP team reported that for the SNC to work Siebel should not pass SAPRfcUserName and SAPRfcPassword to SAP.
The customer tested the functionality using the TestSAPConnection workflow, which calls the MakeConnection method on the EAI SAP BAPI Adapter. SAPRfcUserName and SAPRfcPassword were removed from all of the places where they can be specified but the EAI SAP BAPI Adapter failed with:
â€œRequired property 'SAPRfcUserName' is not set for Business Service 'EAI SAP BAPI Adapter'(SBL-EAI-04167)â€
Optional flag is checked for SAPRfcUserName in Tools.
The SAP Connector is no longer being actively developed. Therefore, raising a CR/FR to enhance the application so that SAPRfcUserName is not required or so that it works with SNC was not an option. The recommendation is to use AIA/web services going forward.