x

When receiving IDocs from SAP (SAP listener component), the Advanced option for IDoc confirm is exposed. This option can be set to true or false. The default setting is false, which performs no operation. If true is selected, then upon receipt of an IDoc, a STATUS IDoc (SYSTAT01) will be dispatched to the sending party of the IDoc from the header information, with status 12, Dispatch OK. This feature allows for a complete audit trail of IDocs between the SAP server and iWay Application Adapter for mySAP, as IDocs sent from SAP will have status 03, Dispatch OK and all IDocs received through the adapter will, after receipt of the STATUS IDoc, change to status 12. This can be monitored in one location in SAP, using the WE02 transaction. Failed IDocs can be tracked or resent using the sm58 transaction.

Note: When this feature is used, resources are consumed to prepare and send the Status IDoc. You may want to consider alternatives, such as using collected IDocs, in high volume environments.

x

When receiving IDocs from SAP (SAP listener component), it is possible in the SAP Partner Profile (WE20 transaction) on the SAP server to change the release of the segment version of the IDoc when sending to a partner with a lower release level of SAP. For example, if the sending SAP release is 700, but the IDoc receiving partner is on SAP release 46C, then the entry for segment version in the partner profile should be 46C. This ensures that the IDoc is not sent with extra fields that the partner system will not understand.

When composing an IDoc from data sent from SAP, the adapter needs access to the correct version of the metadata for the IDoc being sent. In the mySAP listener configuration, IDoc release provider is now exposed for the Advanced option. If you select Automatic check, the adapter will read the partner profile of the IDoc receiver, and select the correct version of the metadata automatically without further configuration. This is done the first time an IDoc type for a partner is detected and cached, so performance impact is minimal.

The following configuration options are available:

• SAP release. Use the logon release of the SAP server for the metadata release.
• DOCREL field. Use the document release field of the IDoc to obtain the metadata.
• User Input. Requires you to provide a value in the IDoc release field of the channel configuration. This is per channel and not per message.

x

In the SAP system, most remote function modules are implicit commit, which means that a commit is triggered on the database when the end of the remote function is encountered. There are times when you may require to issue an explicit commit to achieve control of the commit process if performing a program call or other command. During target creation for an SAP connection, two new parameters are now available to control commit functionality:

• On the System tab, the Explicit Commit parameter can be set to true to have the BAPI_TRANSACTION_COMMIT function called after every function call in the adapter. Use this functionality only if you require explicit commit functionality as it can add to processing time. This command enables commit asynchronously. The commit function is called and returns immediately. It is still possible for the database commit to fail, but no notification would be received. This command is the equivalent to the COMMIT WORK ABAP statement.
• On the Advanced tab, the Commit With Wait parameter is available. This must be used in combination with the Explicit Commit parameter set to true, and sets the commit behavior to synchronous commit. The commit function will wait until the actual database commit occurs or an error occurs. This process is time intensive, but the most accurate. If an error occurs, it is returned in an exception message.