If you are working with the Business Partner master data objects in SAP S/4HANA Cloud Public Edition, you might have seen the “Relationship Failed” error while replicating the objects from one system to another. Usually, this isn't a data error, but a timing issue — the system tries to link two business partner objects before they are both fully saved in the database. 

Instead of manually restarting these messages every time an error occurs, you can use the Automatic Reprocessing app to let the system fix the issues. Here is how to set it up.

When replicating Business Partners, the Relationship Scenario fails (often with a “Locked” or “Not Found” error). This happens because the relationship record reaches the system faster than the BUSINESS PARTNER master record itself. Manually monitoring and clicking “Restart” for every failure is a waste of resources. 

Follow these three steps to automate the recovery process using the Fiori-native framework. 

Step 1: Open the Automatic Reprocessing App 

1. Log in to your SAP S/4HANA Cloud Public Edition system with the role SAP_BR_CONF_EXPERT_BUS_NET_INT or similar integration roles to access the app. 
   
   
2. Use the App Finder (or the search bar) to locate the app “Automatic Reprocessing”. 
   

Step 2: Maintain Reprocessing Entries 

This is where you define the “Retry Rules.” 

1. Click on Create Entry. 
2. Identify your Interface: Maintain the Namespace and Interface name related to your BUSINESS PARTNER Relationship (e.g., for SOAP APIs). 
3. Define the Error: Enter the specific Message Class and Message Number that is causing the failure (e.g., Message Class R1 or MDG_BS_BUSINESS PARTNER_MS).
       
4. Set the Frequency: 

• Max Retries: How many times should the system try again? (Recommended: 3-5). 

• Waiting Time: How long should the system wait between tries? (Recommended: 60 – 300 seconds). 

Pro Tip: These are autosaved entries. Once you fill in the fields, the system registers them immediately. There is no manual “Save” button to click—your changes are live as soon as they are entered. 

Step 3: Retrigger and Monitor 

After you maintain the configuration:

1. Retrigger the Scenario: Go back to the source system or the Message Monitoring app and retrigger the failed relationship record. 
2. Watch the Status: The message will move from “Error” to “In Process” or “Scheduled for Reprocessing.” 
3. The system will now automatically attempt to create the relationship based on your wait times, giving the Business Partner objects time to be created first. 

By spending a few minutes in the Automatic Reprocessing app, you eliminate hours of manual monitoring. This approach ensures your BUSINESS PARTNER relationships stay consistent without human intervention.