ECC CS/S4HANA CS integration Overview The following link provides different resources for integrating ECC CS/S4HANA CS with SAP Field Service Management: ECC CS/S4HANA CS Integration Notice Regarding TLS Version Support for SAP ECC Connector / SAP S4 Connector SAP Field Service Management is requiring an upgrade to TLS 1.2 in order to align with industry best practices for security and data integrity. Beginning 1 January 2021, we will disable TLS 1.0/1.1 encryption protocol in SAP Field Service Management Cloud Backend. Action is required prior to this date to prevent any disruption to your production instance of SAP ECC Connector / SAP S4 Connector using TLS 1.0/1.1 connecting to SAP Field Service Management Cloud Backend. The preferable solution is to either upgrade the Message Broker to the newest available version (available in SAP Software Download Center. It is also highly recommended to use latest available version of Microsoft .NET. Or, ensure the Message Broker DLL file’s version is at least the following version: and that you have Windows Server 2012 R2 installed. You can enforce the use of correct TLS version by adding following entry in the Message Broker configuration file: <AppContextSwitchOverrides value="Switch.System.Net.DontEnableSystemDefaultTlsVersions=false" /> in the <runtime> section as shown in the screenshot below: In addition, the following line should be removed from the configuration (if present): <supportedRuntime version=”v4.0” sku=”.NETFramework,Version=v4.5.1” />` Detailed information on Message Broker installation can be found here. In case of any related issue you may contact either SAP Field Service Management support or Proaxia Consulting support. Tips and Tricks Handling of UDFs (User Defined Fields) for a FSM Person Object In ECC CS, S/4HANA CS Connector a UDF for a Person can be created with a subtype attribute set to: “no subtype” ERPUser Employee “no subtype” Not setting a subtype should be avoided, as on the FSM side it unclear for which type of person a UDF should be created. In this case a UDF is sync and in FSM a UDFMeta for a Person object with a subtype=null is created. The UDF will be visible in MDM and it is possible to set a value for a UDF. The Value will be only updated for Unified Person Object. ERPUser In this case a UDF is sync and in FSM a UDFMeta for a Person object with a subtype=ERPUser is created. The UDF will be visible in MDM and it is possible to set a value for a UDF. The Value will be updated for Unified Person Object and for a Person of type ERPUser. Employee In this case a UDF is sync and in FSM a UDFMeta for a Person object with a subtype=EMPLOYEE is created. The UDF will be visible in MDM and it is possible to set a value for a UDF. The Value will be updated for Unified Person Object and for a Person of type EMPLOYEE. Please note that, in FSM there is no need to create a separate UDFMeta for a UnifiedPerson or Person. One UDFMeta for a Person object with subtype ERPUser/EMPLOEE is valid for both objects.