Verify SAP B1if Services: Ensure all services are running smoothly. If they are already running, we recommend restarting all services, including the SAP B1 Integration Framework, Event Sender, and DI Proxy services.
Check Failure Messages:
Review the failure section of the intercompany message log to identify any failure messages. If you encounter any, click on the message icon to retrieve the failure XML payload and share the relevant screenshots with Walldorf Support for further assistance. Refer to the screenshot below:
Check Events in the SEVT Table: Verify if any events are stuck in the SEVT table in the SBO-COMMON database and whether they are failing in the SAP B1 Event Monitor (SAP B1if 2.0 --> Monitoring --> SAP B1 Event Monitor).
If events are stuck or failing in the Event Monitor, rerun the SAP B1 Event Sender Setup. Once the setup completes successfully, restart the SAP B1 Event Sender service.
Ensure the server name, IP address, and port in the Event Sender Setup are consistent with the details provided in the SLDs.
If the test connection in the Event Sender setup fails, check if the B1if Runtime User is active. For guidance on troubleshooting Runtime User activation, refer to the Troubleshooting B1if Runtime User Activation article.
Verify Event Initiation: If no events appear in the steps above, stop the SAP B1 Event Sender service temporarily. Then, update any global master data or intercompany branch document to verify whether the Event Sender is functioning correctly. If the events do not appear in the SEVT table, you can either review the configuration of the Event Sender Setup and rerun it, or contact SAP Support for further assistance with the SAP Business One Event Sender.
Verify SLD Test Connections:
If the SAP B1if is functioning properly but the issue persists while replicating intercompany master data or transactions, please collect detailed error payloads, screenshots, and configuration details. Raise the issue to Walldorf Support for further investigation.