[62488] in SAPr3-news
Re: SAP RFC
daemon@ATHENA.MIT.EDU (ein_westfale_in_muc)
Tue Jun 1 04:40:19 2010
To: sapr3-news@mit.edu
Date: Tue, 01 Jun 2010 10:38:57 +0200
From: ein_westfale_in_muc <ein_westfale_in_muc@t-online.de>
Message-ID: <hu2gv1$dtq$00$1@news.t-online.com>
xnoise schrieb:
> On Tue, 01 Jun 2010 09:15:43 +0200, ein_westfale_in_muc
> <ein_westfale_in_muc@t-online.de> wrote:
>
>> DEST=BIN # Comment
>> TYPE=B # needs to be 3 for R/3 System
>> R3NAME=BIN # Name of R/3 Instance. Instance name is the
>> # name of the Directory under /usr/sap or
>> # x:\usr\sap in capital letters
>> MSHOST=binmain # your R/3 Server name
>> GROUP=PUBLIC # Check it with TA SMLG in TA SMLG, if you have
>> # access to SAP with GUi
>> RFC_TRACE=0
>> ABAP_DEBUG=0
>> USE_SAPGUI=0
>
> Anchors I don't understand the function of DEST.
> Is it the label that through "connect_param" identifies the group of
> parameters to use in the saprfc.ini?
>
> Example:
> in connect _param I write: DEST=BIND
>
> in saprfc.ini I have:
>
> DEST=BIN
> TYPE=B
> R3NAME=BIN
> MSHOST=binmain
> GROUP=PUBLIC
> RFC_TRACE=0
> ABAP_DEBUG=0
> USE_SAPGUI=0
>
> DEST=BIND
> TYPE=B
> R3NAME=BIN
> MSHOST=hs0311
> GROUP=PUBLIC
> RFC_TRACE=0
> ABAP_DEBUG=1
> USE_SAPGUI=0
>
> RfcOpenEx () it uses the series of parameters identified by BIND?
>
>
> thanks
Hi
that is just a name. In the file SAPRFC.INI it must be unique.
Michael
