Infor ION as the Integration Backbone
Infor ION is the native middleware for Infor LN and serves as the most natural integration point for Salesforce connectivity. ION Connect handles message routing, transformation, and monitoring between LN and external systems. Salesforce connects to ION via its REST API or through an ION API Gateway endpoint that exposes LN BODs as consumable services.
- ION BODs such as Sync.CustomerPartyMaster and Process.SalesOrder carry structured LN data in XML format
- ION Connect document flows map LN outbound BODs to Salesforce REST API calls for record creation
- ION API Gateway exposes LN business functions as REST endpoints consumable from Salesforce Apex callouts
- Infor Data Lake stores BOD history and provides an alternative query path for Salesforce reporting integrations
- ION Workflow triggers can conditionally route messages based on LN company, order type, or customer group
Key Data Flows Between Salesforce and LN
The primary integration scenarios between Salesforce and LN center on customer master synchronization, order lifecycle management, and pricing consistency. Customer data typically flows from Salesforce to LN when new Accounts are qualified, while order status and shipment data flow from LN back to Salesforce to keep sales reps informed.
- Account-to-Business Partner sync pushes Salesforce Account data to LN Business Partner master via Sync.CustomerPartyMaster BOD
- Opportunity-to-Sales Order conversion triggers Process.SalesOrder BOD creation in LN when Opportunity reaches Closed Won
- LN shipment confirmations flow back to Salesforce via Confirm.Shipment BOD updating custom Shipment__c records
- Price list synchronization publishes LN sales price books to Salesforce PricebookEntry records on schedule
- LN project milestones sync to Salesforce for project-based manufacturers tracking delivery against commitments
Handling Multi-Company and Multi-Currency in LN
Infor LN's multi-company architecture means a single LN environment may contain dozens of financial companies, each with different currencies, tax rules, and chart of accounts. Salesforce integrations must route data to the correct LN company based on the originating Salesforce Account or Opportunity. Currency conversion and tax handling add additional complexity.
- Salesforce Account custom field stores the mapped LN Company number for correct order routing
- Multi-currency Salesforce orgs require exchange rate alignment with LN currency tables during order sync
- Tax code mapping between Salesforce tax fields and LN tax schedules prevents tax calculation discrepancies
- Intercompany orders in LN require special handling when the Salesforce selling entity differs from the fulfilling entity
- ION workflow rules inspect LN Company on inbound BODs to route responses to the correct Salesforce business unit
Try it here, free
CRM Implementation Cost Calculator
Model total first-year CRM cost, subscription, data migration, integrations, customization, and training, so the budget request is accurate before the project starts.
Planning a Salesforce-to-Infor LN integration? Let our LN specialists design a BOD-based architecture that fits your environment.