In this blog post, we will run through 5 steps to help with maintenance and troubleshooting of your interCompany integration solution for SAP Business One. 

We want to start off with some maintenance tips to keep your system running efficiently. 

1. Handling Failed Messages in the SAP Intercompany Message Log

 Monitor the Intercompany failed message logs regularly. Navigate to the Message log Failed Messages in the Intercompany Admin Console using the following path:  

Intercompany Admin Console → Monitoring → Message log → failure 

Review the logs and delete any messages which are no longer required.  

For the remaining failed messages, use the retry link to retry the failed transaction or choose the Retry All Errors link to retry all failed transactions in one click.  

Some messages may fail again. Review the error and if the root cause is clear address the issue and retry again.
Example: To generate this document, first define the numbering series in the management module. For this error, please check the default manual series for the document in the receiving company. 

If you cannot resolve a failed message after reviewing existing notes or documentation, please create a Support Incident with component SBO-ICO. 

2. Configuring scheduled tasks 

In step one we talked about retrying failed messages. Did you know you can schedule the system to automatically retry failed errors, in addition to other scheduled tasks? Auto Retry on Errors  

This feature allows to automatically retry failed transactions after a specified time interval. 

Navigate to the Auto retry on Errors configuration in the Intercompany Admin Console using the following path:  

Intercompany admin console → Preferences → Auto Retry errors 

You can also configure the number of times a failed message is re-tried. See the next section, Manage Logs for more detail and the impact this can have on the system. 

Manage Logs  

The manage logs feature allows you to set the frequency of automatic deletion for the following logs.  Navigate to the Manage logs configuration in the Intercompany Admin Console using the following path: Intercompany admin console → Preferences → Manage Logs 

The recommended setting is 30 days, which will result in the system automatically deleting logs older than 30 days.  

We can also see a configuration for Failed Messages Retry Count. This is directly related to the Auto Retry configuration above. To prevent the system continuously retrying a failed message you can set a limit on the number of times a failed message will be retried.

Note: It is notrecommended to set the value of Auto Retry Failed Messages greater than 5. Each time a failed message is retried, logs are generated for that retry.With an increased number oflogs, you may encounter significant DB growth resulting in performance issues. 

In the first two steps we covered some general maintenance. Now we would like to go through some troubleshooting steps that can help resolve Master Data Replication or Document Exchange issues. 

3. SAP Intercompany test connection

  The companies defined for Intercompany transactions need to have correctly configured  connection data in their respective SLD entries. You can easily confirm the connection status  by opening each required SLD entry and running the DI and JDBC tests. For any DI test  connection failures refer to SAP Note 2029714. For JDBC test connection failures, verify the  username and password are valid. Please also ensure the SQL server and database names  are correct. 

4. Event Sender Troubleshooting 

In this section, we will look at some troubleshooting tips for events involved in Master Data Replication or Document Exchange. 

Check if theEvent Sender is working as expected by enabling (Log = On) the B1 Event Monitor log in the Integration Framework using the following path: 

Integration Framework → Monitoring → B1 Event Monitor  

Perform a test and verify the data in the B1 Event Monitor log. If you see the expected data, you can disable this log and likely rule out the Event Sender as a source of your issue. 

Example: I see data with Statusas Success in the B1Event Monitorlog, for one global item which I updated: 

This indicates that there is no issue with the Event Sender configuration. 

If the results are not as expected, for example: 

Here I updated one global item, however the event for this is filtered (not successful).  

To troubleshoot this, you should run the EventSender Setup and Event Sender Troubleshooting Toolby following below mentioned paths: 

Integration framework→Tools → Event Sender 

Integration framework →Tools → Troubleshooting 

If this does not resolve the issue, please review SAP Note 1882000. After the issue is resolved, please disable the B1 Event Monitorlog. 

5. Queue monitor status 

In some cases, you can see transactions in the queue are not being processed. Depending on the Integration Framework version, you can check this in the queue monitor: 

– Integration framework 1.0→ Monitoring→ Queue monitor 

–Integration framework 2.0 → Monitoring → TechnicalQueue monitor 

Please review SAP Note 2173439 to troubleshoot the queue issue.

If you still have an issue with SAP Intercompany object replication, please create an incident with component SBO-ICO.

Summary

In this blog, we explained few points to work smoothly with InterCompany Integration Solution for SAP Business One and also troubleshoot general issues.

Support Spotlight Series 

We hope this read has been informative and beneficial. For more blogs and tips from the SAP Business One Support team, please visit our space on the communities: https://blogs.sap.com/tag/b1-support-spotlight/

For questions about SAP Business One, please submit your question here.

Author: Nidhi Singh

Nidhi is Support Engineer at SAP Labs India, for 6 years. As a technical support specialist in SAP Business One Integration, she provides support in technical issues faced by users. She is graduate in commuter science and Engineering also have software development & designing experience in past.  

• Alert Moderator