Typical message flow for MRO integration - HxGN EAM - 11.07.01 - Feature Briefs - Hexagon

The following diagram illustrates a typical message flow that facilitates the integration between HxGN EAM and an Infor® ERP system for the MRO materials and services purchasing and inventory.

The following is a sequence of business events facilitated by this message flow.

1. EAM and ERP synchronizes master data used in the MRO operation, including:

   • MRO parts and service records. They are primarily created in the ERP and synchronized into EAM through SyncItemMaster messages. Optionally MRO material and service items can be created in EAM and synchronized into ERP. MRO services are Trades in HxGN EAM.

   • Suppliers are created and maintained outside of HxGN EAM.

   • Cost Codes are carried in the CodeDefinition message. They are also maintained outside HxGN EAM.

   • If the master data is defined on accounting entity level, please make sure the correspond entity has multi-org enabled in EAM. You can go to EAM Multi-Org Security screen and selectively turn on the multi-org flag for the following entities based on the master data setting:

     BOD Name	EAM Entity	Multi-Org
     CodeDefinition for Cost Centers	CSTC	Enabled
     ItemMaster for Parts	PART	Enabled
     ItemMaster for Trades	TRAD	Enabled
     SupplierPartyMaster	COMP	Enabled

   • If the master data is defined on accounting entity level, please also note you cannot use the same id on different account entities for Trades and Cost Codes.

2. When a requisition in HxGN EAM is approved, HxGN EAM sends a ProcessRequisition message to the ERP, where the requisition is processed into purchase orders. These purchase orders are published by the ERP and imported into HxGN EAM through the SyncPurchaseOrder messages. Further updates to purchase orders in the ERP are reflected in HxGN EAM through additional SyncPurchaseOrder messages.

3. MRO part deliveries can be received using either HxGN EAM or the ERP, but they are communicated to the other side using ProcessReceiveDelivery or SyncReceiveDelivery, depending which system performs the receiving transaction. In an implementation, you can enforce a process to allow the receiving to be done only in the ERP, only in HxGN EAM, or in both, depending on your specific situation and what is supported in the ERP product.

4. MRO services are received against HxGN EAM work orders and communicated to the ERP through SyncServiceConsumption messages.

5. When HxGN EAM uses (issues) MRO parts from a warehouse to an HxGN EAM work order, it sends a ProcessShipment for such a transaction. The ERP processes the transaction when receiving that message in order to relieve the item from the warehouse as well as perform GL postings for this transaction.

6. When an HxGN EAM user returns unused MRO parts back to the warehouse, HxGN EAM sends a ProcessReceiveDelivery message (without a reference to any purchase order). The ERP processes the transaction when receiving that message to adjust the item quantity as well as perform GL postings for this transaction.

7. When physical inventory counting takes place in an MRO warehouse, HxGN EAM generates ProcessInventoryAdjustment messages for any quantity adjustments. The ERP processes these transactions when receiving such messages to adjustment the quantity as well as perform GL postings for these transactions.