TransactionMode Property

Determines whether remote functions can be called multiple times without affecting the state of the SAP database, or if the transaction must only be executed once.

Syntax

[VB.NET]
Public Property TransactionMode As SapclientTransactionModes

[C#]
public SapclientTransactionModes TransactionMode {get; set;}


enum SapclientTransactionModes {
  tmNotTransactional,
  tmTransactional
}

Remarks

If you wish to ensure that a function called via CallFunction is executed only once, set the TransactionMode to tmTransactional and call CreateId first. The TransactionId will then contain a an Id that was created by the R/3 system. This transaction Id will then be used when you use CallFunction. If the CallFunction fails due to an error or a timeout, you may try again later with the same TransactionId. The R/3 system will check to see if has already processed a transaction with that TransactionId, and if so will return the results of that call. If it has not received a transaction using that Id, the call will proceed normally.

If you call CallFunction in transactional mode without first calling CreateId or setting TransactionId with a previously created Id, the component will first attempt to create an Id before executing CallFunction

Note that if an error occurs when calling CreateId, the client program has to reconnect later and must try to repeat this call until a TransactionId has been successfully retrieved.

Examples of NonTransactional function calls would be retrieving SAP system attributes, requesting a list of functions, checking inventory quantities, etc. It does not matter if these calls are executed several times. Examples of a Transactional function call would be updating inventory amounts, debiting an expense account, charging a customer account, etc. It is essential that these types of transactions are executed only once.

Default Value

0