1. 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.
   

2. Please ensure that the appropriate replication method is selected in the Replication Method setting within the Intercompany Administration Console. Replication via the Service Layer should only be configured after confirming that the B1SL test connection is successfully working in the SLD.
   

3. 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:
   

4. 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 that all participating companies in the landscape are selected in the Event Sender Setup. Please refer to the screenshot below:
     

   • 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.

5. 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. Suppose the events do not appear in the SEVT table. In that case, 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.

6. Verify SLD Test Connections:

   • Test the SLD B1DI and JDBC connections for all participating companies.
   • Ensure the correct credentials and server details are configured. This includes the SBO-COMMON, IC_Landscape, and the root level (B1i Server) SLDs.

1. If the framework has become corrupted or partially installed, repairing or reinstalling it ensures that all essential components and services are restored. 
   
2. Navigate to the SAP setup files and choose the Repair option. If issues persist, perform a clean reinstall of B1if.
   

2. Re-execute the SAP Business One Event Sender Setup

1. The Event Sender is responsible for capturing and transmitting events from SAP Business One databases to B1if.
2. Re-run the setup wizard and ensure you provide accurate configuration details (database credentials, server name, and connection details). Any incorrect information will prevent events from being delivered to B1if.
   
3. Please note that the server details (either the server name or the server IP address) defined in the SLD configuration and the Event Sender setup must remain consistent across the entire landscape.
   

3. Deploy the Intercompany Solution

After ensuring that SAP B1if and Event Sender are running correctly, redeploy the Intercompany solution package.

4. Verify the Key Mapping Configuration

1. Key Mapping is essential for synchronizing the master data and transactions across the companies.
   
2. Open the Key Mapping module in the Intercompany solution and confirm that the mappings are set correctly for Business Partners, Items, and other relevant objects.
3. Incorrect or missing key mappings can result in replication failures even if B1if is functioning.