f$SAP_LoginEx

You can log in to the SAP system with advanced options with this function. This function or the f$SAP_Login function must always be called before using the interface. If you do not, the interface attempts to log in by itself. The data entered in the SAP tab in the ePOS settings is used for this.

Syntax:	Status = f$SAP_LoginEx (Connectstring)
	Argument		Type	Meaning
	Connectstring		String	Connect string for logging in to the SAP system
Result:	Integer	Status of log-in process: -2 : the object cannot be created -1 : cannot log in with this information 0 : successfully logged in
Example:	SAPConn = 'TYPE=3 TRACE=1 CLIENT=020 USER=acbis PASSWD=acbis LANG=de ASHOST=194.180.172.133 SYSNR=00 ' Status = f$SAP_LoginEx (SAPConn)

The syntax of the connect string is: keyword:value keyword:value ...

Please note that the values are case-sensitive.

The following keywords exist:

(extract from the SAP documentation)

TYPE	RFC server type, 2/3/E: R/2 or R/3 or external system (default: 3)
CLIENT	SAP logon client
USER	SAP logon user
PASSWD	SAP logon password
LANG	SAP logon language (1-byte SAP language or 2-byte ISO language)
CODEPAGE	The given codepage is to be used for this connection (default is either 1100 or set by RfcSetSystemCodepage or is set by SAP_CODEPAGE environment variable). Could be rather useful if the sapgui should be started with codepage differs from 1100.
LCHECK	Logon check at OPEN time (0/1: without/with check, Def. 1)
NEWPASS	Changes the password during the logon !!!On SAP system kernel older than 46C the password is sent in clear text on the network!!!!
TRACE	RFC trace (0/1: without/with trace, Def. 0)
DEST	Destination in saprfc.ini if working with saprfc.ini. If the RFC server is an R/2 system this destination must also be defined in the ’sideinfo’ for the SAP gateway.
GWHOST	Host name of the SAP gateway (if server is R/2 or External)
GWSERV	Service of the SAP gateway (if server is R/2 or External)
MSHOST	Host name of the Message Server (if using Load Balancing)
MSSERV	Service of the Message Server (if using Load Balancing)
R3NAME	Name of the R/3 system (if using Load Balancing)
GROUP	Name of the group of application servers (if using Load Balancing)
ASHOST	Host name of a specific application server (R/3, No Load Balancing)
SYSNR	R/3 system number (R/3, No Load Balancing)
TPHOST	Host name of the external RFC server program
TPNAME	Path and name of the external RFC server program or Program ID of an registered RFC server program.
USE_SAPGUI	RFC with SAPGUI, 0/1/2: without/with/invisible SAPGUI between two RFC functions (Default: 0). If the sapgui is to be started with codepage differs from 1100, please use option CODEPAGE to define the codepage you need.
ABAP_DEBUG	RFC with ABAP debugger, 0/1: without/with ABAP debugger (Default: 0)
SNC_MODE	Working with SNC, 0/1: without/with SNC (Default: 0, s. RFC_SNC_MODE)
SNC_QOP	SNC Quality of service (Default: 8 (RFC_SNC_QOP_DEFAULT), s. RFC_SNC_QOP)
SNC_MYNAME	Own SNC name if you don’t want to use the default SNC name
SNC_PARTNERNAME	SNC name of the SNC partner (RFC server) or SNC name of the message server (Load Balancing)
SNC_LIB	Path and name of the SNC-library
SAPLOGON_ID	String defined for SAPLOGON on 32-bit Windows
GRT_DATA	SAProuter connect data for SAPGUI when using RFC with SAPGUI. /H/...... : the whole router string for SAPGUI. /P/password: If the password for the SAPGUI connection is not the same as the one for the RFC connection.
PCS	Partner’s Char Size. The RFC-library determines automatically the partner’s char size at open time (using logon check) or at first call time (without logon check). This flag tells directly the unicode RFC library to open a connection to a system with size of char given by this value. Currently are two values valid 1/2 : Non Unicode/Unicode (Default: 1). If the partner is not an unicode system but the value of the PCS flag is 2 an error will occur (Runtime exception in the remote system). If the partner is an unicode system but the value of the PCS flag is 1 the connection kind will be switched automatically. This field works only with unicode library.
COMM_CP	When communication has to be established between an Unicode Library and a Non Unicode system, all char like data will be converted into codepage which matched to logon language before send them. This codepage is called communication codepage. The effect of this method is that the Non Unicode System is sure to talk an system with communication codepage and not with an unicode system. Usualy the RFC Library determines automatically the communication codepage. Using this option it is possible for the programer to set the communication codepage directly. This option is only active in the unicode version of the RFC library.
ICCE	Ignore Character Conversion Errors, 0/1: Do not ignore/Ignore (Default 0 or defined by environment variable RFC_IGNORE_CONV_ERROR). This flag determines the runtime behaviour of the RFC library concerning character conversion. If this flag is 1, the concerned API will not exit with error, but replace the character which could not be converted with CFIT defined token.
CFIT	Conversion Fault Indicator Token. This flag determines substitute symbol for received unicode characters, which could not be converted by the RFC library (Default: non unicode systems 0x23, unicode systems 0xfffd, or defined by environment variable RFC_REPL_CHAR).
WAN_CONN	RFC via Wide Area Network, 0 = LAN, 1 = WAN (Default: 0). If LAN is used, all tables bigger than 8000 Bytes will be compressed before sent. If WAN is used, all tables bigger than 250 Bytes (or value defined by environment variable RFC_WAN_THRESHOLD) will be compressed before sent. The table size will be calculated as follows: table_length * number_of_rows.
ALIAS_USER	An alias user name, could used instead of user or even together with USER. If both USER and ALIAS_USER are used, than theay have to be match.
MYSAPSSO	SAP Cookie Version 1. Will be used instead of user and password for logon to backend
MYSAPSSO2	SAP Cookie Version 2. Will be used instead of password for logon to backend. In this case, user name is optional.
X509CERT	An X.509 certificate will be used instead of password to logon to R/3 System. In this case, user name is optional.
EXTIDDATA	Contains valid external user’s ID of an external authentification system. User name is optional. External ID is to be defined in the backend (SAP-System).
EXTIDTYPE	Defines the kind of external identity. Valid only with EXTIDDATA. Follow values are not allowed: ID, NT; DN, CA, X, HX.