BAPIoutboundProcess
The service runs a BAPI in an SAP system. This transport service can handle both asynchronous and synchronous execution of a BAPI.
- Input parameters
-
- serverName
- Optional. Alias of the SAP system to which the connection must be established. The name must match a configured RFC connection alias at SAP® ERP. If serverName is set, it overrides the value of transportParams/serverName.
- transportParams
- A document with the following key/value pair:
- serverName. The SAP system alias on which to run the BAPI. The alias must match a configured RFC connection alias at SAP® ERP.
- mode. Allows to restrict the way how the BAPI can be started.
- no restrictions. Is run as the client requested.
- synchronous only. Only synchronous calls are allowed, if client passes a $tid (indicating an asynchronous call) an exception is returned.
- asynchronous only. Only asynchronous calls are allowed, if client does not pass a $tid (indicating a synchronous call) an exception is returned.
- $tid
- Optional. TID of the transaction.
- $action
- Optional. Transaction state. Specify one of the following codes:
- 1. Default. Run.
- 4. Confirm.
- $queueName
- Optional. Name of the SAP system inbound queue. Specify a value for a qRFC scenario.
- objectName
- Optional. Name of the business object.
- bapiName
- Optional. Name of the BAPI method.
- Return values
- A pipeline that represents the response or an exception of the run BAPI.