Page History
Div | ||||||
---|---|---|---|---|---|---|
| ||||||
|
...
...
...
...
...
...
...
...
...
...
...
...
Name | Type | Direction | Description |
---|---|---|---|
connectionString | String | in | Supplies the connection string (optional). |
transactionID | String | in | Supplies the transaction ID of the transaction to be confirmed. |
Parameters of <<SAPIDocComposer>>
...
MultiExcerptName | parameters_sapidoccomposer |
---|
...
...
...
Parameters of <<SAPIDocRecordComposer>>
...
MultiExcerptName | parameters_sapidocrecordcomposer |
---|
...
...
...
...
...
...
Parameters of <<SAPIDocParser>>
...
Parsed IDoc object(s)
The class specifying the type of this parameter must have stereotype <<SAPIDoc>> and <<XML>>.
Note | ||
---|---|---|
| ||
The input object must be named exactly after the root element of the IDoc, e.g. TXTRAW01. If not, the model will throw an exception at runtime. |
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
The receiving object must be named exactly after the root element of the IDoc, e.g. TXTRAW01. If not, the model will throw an exception.
Client Connection Options
Via the SAP alias and the configuration descriptor you can get the protocol and the connection string. This string looks like:
name1="value1" name2="value2" ...;
Example: client="100" lang="D" ashost="10.160.99.122" sysnr="00" trace="1"
Note | ||
---|---|---|
| ||
The connection string must be provided in the following format: <optionName>="<optionValue>"<space><optionName>="<optionValue>"... Failure to conform with the pattern will lead to unrecognized options. Those errors won't be reported, but affect SAP behavior (e.g. you'll get a SAP connection error with |
List of Available Options
...
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.
...
Changes the password during logon
Note | ||
---|---|---|
| ||
On SAP system kernel older than 46C the password is sent in clear text on the network! |
...
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.
- 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 a 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.
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...