Adapter for SAP 10.1 | webMethods Adapter for SAP Documentation | webMethods Adapter for SAP Installation and User’s Guide Documentation | Built-in Services | Transport Services | pub.sap.transport.BAPI:OutboundProcess
 
pub.sap.transport.BAPI:OutboundProcess
Executes 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 is established. The name must match a configured RFC connection alias at Adapter for SAP.
If serverName is set, it will override the value of transportParams/serverName.
transportParams
A document with the following key/value pair.
Key
Description
serverName
SAP system alias on which to execute the BAPI. The alias must match a configured RFC connection alias at Adapter for SAP.
mode
Allows to restrict the way how the BAPI can be invoked:
Value
Meaning
no restrictions
Will be executed as the client requested.
synchronous only
Only synchronous call is allowed, if client passes a $tid (indicating an asynchronous call) an exception is thrown.
asynchronous only
Only asynchronous call is allowed, if client does not pass a $tid (indicating a synchronous call) an exception is thrown.
$tid
Optional. TID of the transaction.
$action
Optional. Transaction state. Specify one of the following codes:
*1 - Execute (default)
*4 - Confirm
$queueName
Optional. Name of the SAP system inbound queue. Specify a value in case of 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 executed BAPI.
$metabapi
Optional. Document created if the BAPI was executed. Contains the BAPI metdata (for example, the internal name, the external name, and the RFC name). It also contains information about whether it is static (yes/no), dialog (yes/no), or factory BAPI (yes/no).
$abapexception
Optional. Document created if the execution of the BAPI caused one or more ABAP exceptions with severity of 3 or higher. The document contains the name, the severity, and the message attributes of the general BAPI failure. It also contains the document attributes that contain the complete collection of all exceptions that have occurred during execution of the BAPI, with a detailed description and the message attributes for each exception.
$runtime
Total invocation time (ms), including processing time within Adapter for SAP.
$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
Flag indicating whether pipeline represents a request (true) or a response (false) of a function module.