Skip to Content
Product Information
Author's profile photo Rahul Kapoor

SAP Intelligent Asset Management supports integration with multiple SAP ERP

SAP Intelligent Asset Management  lets you track the entire asset lifecycle. The solution is designed to enable faster decisions, reduce maintenance costs, and optimize asset performance.

Below infographic highlights the business objects supported with out of the box integration, following either replication or synchronisation integration pattern.

 

SAP%20Intelligent%20Asset%20Management%20-%20SAP%20EAM%20Integration

SAP Intelligent Asset Management – SAP EAM Integration

 

Currently upto 4 SAP ERP systems can be connected per SAP Intelligent Asset Management, Business Technology Platform (BTP) subaccount. In order to ensure data sanity & consistency with out of the box integration, we highly recommend customers/partners to connect respective SAP Intelligent Asset Management BTP subaccount (Dev/Test/Prod) with corresponding ERP (Dev/QA/Prod) systems respectively.

The visualisation below can be used as a reference. It highlights recommendation with respect to multiple ERP Integration setup in your SAP Intelligent Asset Management landscape.

Multiple%20ERP%20Integration%20setup%20recommendation

 

Use Cases supported with Multiple ERP integration

 

Data Consolidation

Asset data can be replicated from multiple ERP systems to a single SAP Intelligent Asset Management BTP subaccount

Technical objects having the same external number range in different ERP system(s) can be easily synchronised with the same object ID. However, to ensure data consistency, changes from one connected ERP will not be routed to other connected ERPs via SAP Intelligent Asset Management BTP subaccount.

 

Example: Equipment in different industrial sites (plants) can be visualised within one SAP Intelligent Asset Management BTP subaccount for collaboration purposes or to perform assessments on a group of similar equipment.

Data Distribution

When asset data (e.g., supported objects) on BTP is linked to technical objects in ERP, asset data changes will be automatically synchronised to relevant connected ERP systems.

 

Example: New equipment onboarded in SAP Intelligent Asset Management can be synchronised with any one of the connected SAP ERP system. Later any subsequent updates like the Risk score derived as part of Risk & Criticality assessment can be synchronised with ABC indicator on the equipment in the relevant SAP ERP.

 

Handling of duplicates with Multiple ERP Integration

 

Integration depends on the quality of the master data that already exists in the SAP ERP systems/clients. SAP highly recommends reviewing the quality of master data in ERP before connecting/synchronising it with SAP Intelligent Asset Management.  This would really eases integration implementation and help resolves data issues like duplicate equipment maintained in different maintenance plant within different SAP ERP clients.

The Data Quality vs Data Integrity scale below depicts that if the quality of the master data is good, out of the box integration will be able to maintain data integrity. Though if data quality is low, then master data clean-up & governance is recommended and should be separately taken up as a consulting solution.

 

 

Handling of shared data with Multiple ERP Integration

 

Equipment structure, and corresponding documents can be shared over the SAP Asset Intelligence Network (AIN) and these shared data can also be synchronised in the SAP ERP system. To replicate/share the equipment structure to the ERP system, user need to share the parent object along with its components.

Based on the configuration, ERP user may receive a work item on the parent object for approval and on approving the parent object all the shared child objects of the parent get synchronised automatically and the hierarchy is built accordingly.

For multiple ERP setup, SAP recommends maintaining ‘Review’ configuration in the Mobile Add-on to ensure the ERP workflow could be leveraged to review the shared data before synchronising it in ERP. Refer to integration guide , for more details.

A shared object should be synchronised with only one connected SAP ERP system and in all other connected SAP ERP systems the workflow item should be rejected manually. Though synchronisation will fail if the shared equipment is already linked to a piece of equipment connected to any other SAP ERP system.

 

 

Refer to integration guide for more details on the pre-requisites and minimum ERP release version required to maximise your asset productivity & performance with SAP Intelligent Asset Management leveraging out of the box SAP ERP (On-Premise) integration capabilities.

 

Follow us via @SAP or myself via LinkedIn

Assigned tags

      2 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Fabian Sommer
      Fabian Sommer

      Hi Rahul, thanks for this informations. Question: FL to FL synchronisation will be possible with the 2111 release? BR Fabian

      Author's profile photo Rahul Kapoor
      Rahul Kapoor
      Blog Post Author

      Hi Fabian,

       

      Thats right, FLOC to FLOC outbound (ERP - > IAM) will be feasible with 2111. For now, its recommended for new customers or the existing one's those who have not implemented FLOC -> Location integration already.

      Regards,

      Rahul Kapoor