Frequently Asked Questions

A partner profile in the SAP system is configured to 'collect IDocs' to publish IDocs in a batch. How can I configure an adapter to publish IDocs in batches?

The exploded batch format of IDoc publication allows adapters to bunch and publish IDocs in completely self-describing format in one batch. The size of the batch is equal to the packet size configured in the SAP system for the partner profile.

At times the CPIC error occurs in an adapter, but after some time, the adapter continues processing the message. Is this something to worry about?

The CPIC error usually occurs when the adapter fails to connect to the SAP system because of the network overload, glitches, or some transient network problems. To verify this issue, you can set up the connection from the SAP GUI installed on the same machine where the error occurs.

Can an adapter configuration connect to different SAP systems?

If needed, the adapter can connect to different SAP systems from one adapter configuration. However, if the schemas across those SAP systems are different, it is good practice that you configure different adapter configurations for different SAP systems separately.

For inbound processing of message, how can I take advantage of multiple application servers in the SAP landscape?

For inbound processing of messages, to make maximum use of multiple application servers, you can configure the client connection to the Load Balancing type and select the Disable Connection Pooling check box.

How can I debug my ABAP code when executing the program by using an adapter?

To debug the ABAP code by using an adapter, you have to enable the usage of the SAP GUI. Then you can debug the ABAP code, when the ABAP program is called and the adapter starts the SAP GUI. You have to install the SAP GUI on the machine where you start the adapter. For how to start the SAP GUI, see.

How can I update my repository, when there is a change in the schema of an IDoc in the SAP system, without losing my mappings?

Whenever there is a change in an IDoc, you have to re-download the IDoc and recreate an adapter service for the re-downloaded IDoc. If the change in the IDoc does not disturb the mapped parameters, the mappings cannot be affected. For example, if you add additional fields to an existing segment. In your mappings, you can find the additional fields along with the other mappings. If you delete a field mapped from the schema, the mapping for that field is lost.

How can I turn on RFC trace for outbound communications without making changes to the TRA properties file?

You can use the SAP transaction SM59 to enable the RFC trace in the SAP system.

How can I use the Load Balancing feature of adapters on the inbound side?

To enable the inbound Load balancing feature, you have to use the Distributed Queue feature of the adapter. For the detailed information on configuration and its usage, see.

How can I use the Load Balancing feature of adapters on the Outbound side?

To enable the outbound Load balancing feature, you have to use TIDManager. To set up TIDManager, during the adapter service configuration, configure the outbound TIDManagement options on the All Publication Services panel in the Advanced tab of an adapter configuration. For more information on this configuration, see. Ensure that you set up TIDManager before you add adapter services.

How do I know which version and patch level of the adapter and TIBCO Runtime Agent I am using?

For the exact information about the TIBCO Runtime Agent build, you can check the version.txt file in the TIBCO_HOME/TRA/Release number directory. When you start an adapter, a banner shows the adapter version and patch level.

How many connections can a SAP ID have?

Maximum connections for each SAP ID must not exceed 300. This limit is imposed by SAP systems. SAP licensing is based on user names, not the number of connections.

I am subscribing to an IDoc by using an inbound adapter service. What can happen to the IDoc if the connection to the SAP system goes down before the adapter receives the IDoc or while processing the IDoc?

On receipt of an IDoc, a Subscription Service service can check for the validity of the connection to the SAP system before posting. If the connection is invalid, the adapter immediately starts a timer to check for connections to the SAP system periodically and suspends the IDoc subscriber so that no further messages are received. The sending system cannot receive confirmation whether the IDoc message is received.

When the SAP system comes up again, the adapter re-establishes connectivity and restarts itself automatically to receive the unconfirmed IDoc message.

The polling interval of the connection timer is configurable. This recovery mechanism is also available for the inbound one-way Request-Response messages.

I want to open Support Call. What information should I include in my request to avoid unnecessary delays?

If you want to open Support Call just for information purposes, the request have to include the adapter version and patch level, the platform where you start the adapter, and the version of the SAP system.

If you open Support Call because problems or errors occur, the request also have to include the followings:

• TIBCO ActiveMatrix Adapter for SAP (TIBCO Business Studio) version and patch level.
• TIBCO Runtime Agent version and patch level.
• TIBCO Business Studio version and patch level.
• TIBCO ActiveMatrix BusinessWorks version and patch level.
• Platform where the adapter is been running.
• Fresh adapter log files if error occurs during adapter execution, and TIBCO Business Studio Console Output if errors occur during configuration.
• The repository where errors occur and the adr3.tra file.
• The SAP release and SAP Kernel version.
• The SAP JCo libraries version.
• Additional information about other components, such as TIBCOActiveMatrix BusinessWorks, if they are sources of messages to the adapter.
• Your contact information.

An IDoc is created in the SAP system and is in status 03, but why does not the outbound adapter receive the IDoc?

Check transactions currently in queue by using the SAP transaction SM58. If a transaction is in error, it can either be retried manually or retried automatically by the SAP system by using the configuration defined for the corresponding RFC destination. It is not good practice to retry manually unless the outbound adapter is been running. If the manual retry fails then the automated SAP retry ceases and the manual intervention is required.

The number of server connections in an outbound adapter is increased, but there is no improvement in performance or inactivity of connections is observed.

When changing the maxConnections property of a server connection pool in an outbound adapter service, change the connection value maintained for the corresponding the RFC destination by using the SAP transaction SMQS.

What do I have to do if I do not want to have a permanent connection to the SAP system, but want the adapter to establish a connection if required?

You can dynamically set up connection to the SAP system when the adapter receives a message. When using the Dynamic Logon feature, your user credentials can be passed at the time the request is sent to the adapter. For more information about its configuration, see Event Driven Inbound Connections.

When an error occurs in a Subscription Service service, where is it displayed?

Errors that occur in the Request-Response Service service are sent to the client. Errors that occur in the Subscription Service service are logged to a log file. The log file path and name are set in the TRA file corresponding to the adapter service. All logs are sent to the<install_path>\adapter\<adapter name>\<version>\logs directory unless otherwise specified.

When can I use the remote TIDManagement?

You can use TIDManagement to avoid duplication on the outbound side when multiple adapter services publish the same IDoc or tRFC.

When an adapter publish IDocs to the SAP system, why does the processing of IDocs is displayed to be slow in the adapter logs?

If the inbound partner profile is set to immediate processing, processing in the SAP system can block the thread sending the IDoc from processing the next IDoc. It is good practice that the inbound partner profile be set to trigger by the background program and processing be managed by the SAP system.

When saving an adapter configuration to a project, if an error occurs, where is it logged?

TIBCO Business Studio error messages are logged to the ProjectName.R3AdapterConfiguration file in the User_Home\workspace\.metadata\.log directory.

When the SAP system is sending IDocs to an adapter, the adapter does not receive the IDocs but the SAP system shows that the IDocs have been sent without any error. Why does not the adapter receive the IDocs?

The reason can be that you have more than one adapters listening to the same program ID. Ensure that each adapter is configured for a separate program ID. Check you program ID is not used by another adapter at any given time. In the SAP system, execute the transaction SM59. Go to your program ID under the TCP/IP connection folder, and then click Test Connection. The test connection fails if the adapter configuration is not been running, otherwise the other adapter listens to this program ID.

When starting an adapter, what if the repository is not found?

Start the repository server before starting the adapter. If you are starting a remote repository, ensure that TIBCO Enterprise Administrator Repository is installed on the remote location, that a correctly configured TRA file is available in the path specified (local or remote), and that the RepoUrl has been specified accurately in the TRA file.

When an outbound adapter receives data from the SAP system, the data looks garbled or the call to the adapter fails.

Check to ensure that the port type for the RFC destination is correct by using SAP Transaction SM59. When a new RFC destination is created, the SAP system defaults to Non-Unicode even though the database is Unicode. The port type has to reflect the same type as the database.

Why does the adapter fail to respond to a request?

The subject name to which the adapter listens is different from the subject name of the client.

Why does the adapter fail to respond to a request after successfully receiving it?

Why does the adapter startup fail?

Ensure that the RepoUrl syntax has been specified accurately in the TRA file, and that the path specified for the TRA file is correct.

Why does the adapter startup fail, and the error, 'Failed to enable CM transport', occurs?

The error occurs in one of the following situations:

• Another service is running under the same CM session.
• Permission to create the ledger file in the specified directory is denied.
• The ledger file to be created for the CM session is corrupted.

Check all these before you re-start the adapter. If you find a corrupted ledger file, and then delete the file, you can lost some messages.

What do the following console messages mean when I start an adapter?

Processing
/tibco/private/adapter/R3AdapterConfiguration/SAPAdapter ... 
		

80 [main] INFO com.tibco.security.impl.np.SecurityVendor - Initializing JSSE's crypto provider class com.sun.net.ssl.internal.ssl.Provider in default mode 
		

This message is informational only and its display based on the class path specified in the TRA file and the platform where you start the adapter.

These messages are displayed on all platforms when you start an adapter from the command line or the adapter launcher of TIBCO Business Studio. Because they are console messages, they cannot be displayed in the TIBCO Administrator logs.