cancel
Showing results for 
Search instead for 
Did you mean: 

File-Checkin with NCo 3.0 and BAPI "BAPI_DOCUMENT_CREATE2"

Former Member
0 Kudos

Hi,

we want to checkin files in SAP R/3 with the .NET Connector 3.0. For this we use the BAPI "BAPI_DOCUMENT_CREATE2", which create a new document and then checkin a file to new document. The creation of document is successful, but the checkin fails with error message "RFC callback server not available". The reason is that SAP can not connect to RFCClient and also the sapftp.exe can not start for file transfer.

We think, the problem is the configuration of RFCDestination. The documentation of NCo 3.0 says that the static field "BACK" is responsible by default for creation of callback.

Here is the code for configuration of the RFCDestination:

m_Params.Add(RfcConfigParameters.AppServerHost, aHostname)

m_Params.Add(RfcConfigParameters.SystemNumber, aSystemNumber)

m_Params.Add(RfcConfigParameters.SystemID, aSystemID)

m_Params.Add(RfcConfigParameters.User, aUserID)

m_Params.Add(RfcConfigParameters.Password, aPWD)

m_Params.Add(RfcConfigParameters.Client, aClient)

m_Params.Add(RfcConfigParameters.Language, aLanguage)

m_Params.Add(RfcConfigParameters.PoolSize, "5")

m_Params.Add(RfcConfigParameters.PeakConnectionsLimit, "10")

m_Params.Add(RfcConfigParameters.IdleTimeout, "600") .

Are there other properties to configure? Do you have experience with file transfer through RFC and NCO 3.0?

Thanks

Matthias

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi,

we have solved the problem.

For the file transfer with NCo 3.0 you need essential the SAPGUI. The SAPGUI is started and stopped on the configuration of a RFCDestinationConfiguration-Object (see the SAP .NET Connector 3.0 Programming Guide). This will require the SAP has two modules "SYSTEM_PREPARE_ATTACH_GUI" and "SYSTEM_FINISH_ATTACH_GUI". These two modules must be installed later in the SAP.

There are two approaches:

1. the automatically update with the Solution Manager (difficult, package SAPKB70020) or

2. the manually update with the SAP Note "1258724 " .

We chose the second way. The SAP Note "1258724" is downloadable from SAP-Marktplace. With the SAP-Transaction "SNOTE" you can import the SAP Note "1258724". At last you need a developer key (from "SAP Support Portal") as confirmation of the import.

The second way was recommended to us by the support.

Regards

Matthias