clientInvokeTransaction
The service starts a tRFC function module on an SAP system.
- Input parameters
-
- serverName
- SAP system alias on which the function module is started. The name must match a configured RFC connection alias at SAP® ERP.
- $rfcnamep
- Name of the function module to be started.
- $tid
- Transaction the start is assigned to.
- $queueName
- Optional. Name of the SAP system inbound queue. Specify a value for a qRFC scenario.
- $client
- Optional. Client for the session. If no client is specified, the client that is specified in the SAP system alias settings is used.
- $user
- Optional. Username for the session. If no user is specified, the default user is used.
- $pass
- Optional. Password for the session. If the password is not specified, then the user and password is looked up in the SAP User store.
- $language
- Optional. Language used during the session. If no language is specified, the default language is used.
- Return values
-
- $runtime
- Total invocation time (ms), including processing time within SAP® ERP.
- $rfctime
- Time (ms) spent within the RFC library to complete the invocation.
- $encoding
- MIME-compliant character set corresponding to the session's SAP code page.
- $call
- A flag that indicates whether pipeline represents a request or response of a function module.
- true for request.
- false for response.
Example
The service is used in outbound flows and can handle both synchronous and transactional RFC calls. Therefore, it can be seen as a generic wrapper for clientInvoke, clientInvokeTransaction, and clientConfirmTID.