Mapping:
1. While integrating with F&O try to utilize the Existing/standard Maps. And add your own custom fields and customization in the same map.
2. Prefer using only required fields and avoid using unnecessary fields.
3. Maintain proper versioning of the map.
Integration Keys:
1. Integration keys are one of the fundamental and most important concepts in Dual write. To maintain the uniqueness of the records these keys play vital role.
2. It’s always the best practice to Check the Keys at both system where the integration is happening.
3. You can create your own keys based on requirements.
Legal Entities:
1. Maintain only required Legal entities. Unnecessary Legal entities will push unnecessary data and that would impact your storage.
2. For example:
Initial sync up:
1. Initial sync up is required to migrate the existing data from system to another.
2. It’s always the best practice to check the legal entities for whom you want to migrate the data, and this is only required for Company specific entities.
3. Make sure if initial sync up is really needed as once you started with it you cannot roll back.
4. If you have data discrepancies in one system, it’s always the best practice to clean the data from that system and run the initial sync up to bring back the data.
5. While cleaning the data make sure to Turn off the required maps as this would impact another system.
Changing/Updating the map:
1. Whenever you update the map first stop the map and then perform the Update action.
2. After you are done with the update processing, save and refresh the map to reflect the changes.
3. Always maintain the versions of map. This would help you to use the same map for different purpose.
Solution updates:
Always make sure to check whether the solutions related to Dual write are updated.
Error handling:
1. During integration errors can occur. Some can be common errors. You can get the error details in error log accordingly you can resolve it.
2. It’s always the best practice to check the error details in trace log and analyze it.
3. Sometimes errors do not have specific details so you can enable the error log table in F&O and try to analyze the error log.
4. When nothing works try to reset the link between the two systems