Integrating ENOVIA and SAP is not an easy task, in particular if there is data that may be changed on both systems and must be synchronized between them. While The ENOVIA Event Bus, together with the xPDM adapters, provides the technical solution to do this, the different data models and process paradigms present a challenge of their own. Knowledge of both sides of the gap and experience in transforming the data from far over 50 customer projects give T-Systems a unique position to satisfy customer needs. Functions The ENOVIA "Send to xPDM", used either from the VPM product structure or an engineering BOM, sends the data to SAP to create or update the corresponding items. Optionally, it provides an interactive SAP function for the reverse transfer. BOMs are transferred as single- or multi-level, depending on your company’s preferred settings. Event-triggered operation is possible as a project-implemented feature. Characteristics The ENOVIA-side business logic is provided by the ENOVIA components involved and can be customized to the level they allow. The SAP-side business logic is provided by the SAP adapter that is the main component of the integration. It can be customized to a high degree, including scripted attribute mapping. The SAP adapter, core component of the integration, runs as an independent web application. To use the standard functionality, no installation in either ENOVIA or SAP is necessary. All transfers are done via a system of gateways and adapters that provide message and file exchange via web services. Data transfer and synchronization are asynchronous.Note: As of V6R2014, ENOVIA does not offer to transfer change objects (ECR/ECO). This function can be provided on a project basis.