Content Comparison

Enable the integration between Power Platform and SAP to announce changes in SAP to Power Platform asynchronously and so not in realtime, without coupling the both systems. A good design will take in consideration the existing design related to SAP (see image below).

...

Context and Problem

1. Current architecture implying a front door (micro-service) is mandatory. Direct access to SAP is not allowed.

2. No current integration between Power Platform and SAP. Power Platform is a SAAS in the public Internet even if it’s in the backbone of Microsoft.

3. For now, there is only a one-way communication, from SAP to Power Platform. Data transfered from SAP is not considered as confidential.

4. Data volume is not substantial : about 2 thousand records could be affected in Power Platform. Not a case of intensive computing and long-running functions.

5. Hybrid scenario is highly recommended regarding the current architecture related to SAP and the willing to upgrade the latter to Hana.

...

Solutions

Technology choices

Information below is established according the context (data volume, etc.). We know that Azure provides a multitude of services (as IAAS & ad PAAS).

...

Call the processes ProcessContextBuildingObject, ProcessMappingObject, etc.

//ProcessContextBuildingObject
public ResultValidation ProcessContextBuildingObject(ref ResultValidation result, IContextServices contextServices, string key, 
      string dirPath, string file, string FTPUser, string FTPPassword)
{
   var filesFtpInDirectory = dirPath.FtpDirectoryList(FTPUser, FTPPassword);
   if(filesFtpInDirectory == null) { return result; }
   
   var filesKNA1 = filesFtpInDirectory.Where(fileFtpInDirectory => fileFtpInDirectory.Contains(Constantes.KNA1)).ToList();
   if (!filesKNA1.Any()) { return result; }
   //etc..
   result.kNA1s = new List<KNA1>();
   if (dt != null) { result.kNA1s = Util.ConvertDataTableToKNA1(dt); }
   return result;
}

//ProcessMappingObject
public void ProcessMappingObject(IContextServices contextServices, ref ResultValidation result)
{
    result.accountsKNA1 = new List<Account>();
    result.accountsKNA1 = Util.MapKNA1toAccount(contextServices, result.optionSetMetadataBases, result.kNA1s, 
                              result.existingAccounts, result.industryCodes, result.industries, result.shippingTypes, result.customerSectors,
                              result.customerActivities, result.customerProducts, result.transactionCurrencies, result.transportZones);
    //etc...                              
}

Repository Layer

Issues and Considerations