Dynamic mapping of 3rd party applications with SAP Business One

[Mari_Ma]

Hello Experts ;

I want to do a dynamic mapping between whatever 3rd party application and my backend SAP Business one and this dynamic mapping will map the fields of the 3rd party application (like Shopify,Magento ...) with the appropriate fields in SAP Business one.

I have to mention that whenever i want to change the third party application from one to another i don't have to create another mapping for it here is the dynamic aspect will reveal. I want to use SAP CPI for the integration process.

Any suggestion please ?

[bdBais13]

To achive a dynamic mapping between 3rd part application you must to use XSLT or Groovy Script, not Message Mapping, the xsd dynamic is not supported and probably is not enougth. About your requirements you must to understand the fragility of this implementation, if you doesn't recognize the field (with different name, structure, format) and you put value dynamically on other field you will be in trouble. If you want to add "any structure" to a destination that accept "any structure" and create new fields when they are not present (I doubt this kind of approach exist in your architecture) you can try to use a normal xslt or groovy script.

[Sonali_Gogu]

To enable dynamic mapping between any third-party application (Shopify, Magento, etc.) and SAP Business One using SAP CPI, these steps can help - 

1. Use a metadata-driven mapping approach stored externally (e.g., JSON or database) that defines how fields from each third-party application's data structure map to SAP Business One fields. This metadata can be updated or switched when changing the third party without needing to recreate mappings in CPI.

2. SAP CPI supports integration flows where you can invoke dynamic message transformation using external scripts or lookups against a central mapping repository (JSON files or records) to apply the appropriate mapping based on the source system.

3. Use SAP CPI to connect to various 3rd party systems (Shopify via GraphQL, Magento via APIs) and use integration processes that retrieve data from these systems, apply the dynamic mapping based on the metadata for the current 3rd party, and push into SAP Business One.

4. Staging tables or intermediate steps can be used for complex transformations, allowing you to manipulate and validate data once fetched before final persistence.

5. The JSON file or mapping repository holds mapping rules (field mappings, transformations, conversions) for each 3rd party source. When switching from Shopify to Magento, you update the mapping metadata file rather than changing CPI integration code.

6. Integration platforms like appseconnect or celigo, and approaches recommended in SAP forums align with this pattern, promoting reusable, flexible integration logic with externalized mappings for multiple eCommerce and ERP systems.

This approach minimizes redundant work and enhances integration flexibility and maintainability and the design provides a scalable, low-maintenance dynamic mapping solution for integrating various third-party apps with SAP Business One via SAP CPI.

[rasjoshi]

Hi @Mari_Ma,

Is your source structure same irrespective of application? Also do you have any message transformation logic to apply?

BR,

RJ

[Mari_Ma]

Hi @rasjoshi;

No, they're not the same. For example, integrating Magento with SAP Business One is different from integrating Shopify with SAP Business One. I need to create a dynamic mapping using a JSON file for this requirement.

Do you have any idea please