Receive IDOCs from SAP in a Transactional Context using BizTalk Server
Receiving IDOC in a transactional context is similar to receiving tRFCs in a transactional context. In such a case, the IDOC received from the SAP system contains a TID as part of the <TransactionalRfcOperationIdentifier> element. This TID is persisted in a SQL database by the adapter. If the ABAP code in the SAP system that sends the IDOC has a "COMMIT WORK" statement, the TID is deleted from the SQL database after a response is sent back to the SAP system.
The orchestration required to receive an IDOC is similar irrespective of whether the IDOC is received in a transactional context or not. See Receive IDOCs from SAP by Using BizTalk Server. However, you need to perform certain additional tasks to make sure the IDOCs are received in a transactional context.
At design time, generate the schema for an IDOC that you want to receive.
At run time, make sure you set the binding property TidDatabaseConnectionString.
This property takes the connection string that connects to a SQL database to store the TID. A sample connection string would look like the following:
Data Source=<myServerAddress>;Initial Catalog=<myDataBase>;User Id=<myUsername>;Password=<myPassword>;Caution
This example or guidance references sensitive information, such as a connection string or a username and password. Never hardcode these values in your code, and make sure that you protect confidential data by using the most secure authentication available. For more information, see the following documentation:
For more information about the binding property and how to set it, see Read about BizTalk Adapter for mySAP Business Suite Binding Properties.
Important
The BizTalk Adapter Pack setup wizard installs a SQL script, SapAdapter-DbScript-Install.sql, which must be run by the SQL Server administrator to create a database and the database objects in SQL Server. The script is typically installed at <installation drive>:Program FilesMicrosoft BizTalk Adapter Pack.
The SAP adapter uses these objects to persist the TIDs. So, the SQL Server administrator must ensure that the user name provide as part of the connection string has sufficient privileges to execute the stored procedures. You can also opt for Windows authentication provided the Windows user has sufficient permissions to execute stored procedures in the database.
Make sure MSDTC is enabled on the computer where the adapter is installed. Perform the following steps to enable MSDTC.
Start the Component Services MMC snap-in.
In the Component Services MMC snap-in, from the left pane expand Component Services, expand Computers, right-click My Computer, and click Properties.
In the My Computer Properties dialog box, click the MSDTC tab.
In the Transaction Configuration section, click the Security Configuration button.
In the Security Configuration dialog box, select the Network DTC Access check box and within that, select the Allow Remote Clients check box.
In the Transaction Manager Communication section, select the Allow Inbound and Allow Outbound check boxes.
In the Security Configuration dialog box, click OK.
Click Yes in the dialog box informing that the MSDTC service will be restarted. After the MSDTC service is restarted, click OK on the dialog box.
In the My Computer Properties dialog box, click OK.
Add MSDTC to the Windows Firewall exception list, if not already added. Run the following command.
netsh firewall set allowedprogram %windir%\system32\msdtc.exe MSDTC enable