Infor ERP Integration

Infor's portfolio reality

Infor isn't a single ERP — it's a portfolio of industry-specific ERPs Infor acquired and modernized. The three most common in manufacturing are CloudSuite Industrial (formerly SyteLine, also called CSI), CloudSuite LN (formerly BaaN, then Infor ERP LN), and CloudSuite M3 (originally from Lawson). Each has a distinct data model and history.

What unifies them is Infor's ION (Intelligent Open Network) — the integration platform Infor built specifically to connect its portfolio products and external systems. Horizon's connector uses ION as the primary integration path, with IDO (Intelligent Data Object) and BOD (Business Object Document) protocols for the actual data exchange.

Which Infor products Horizon connects to

• Infor CloudSuite Industrial (SyteLine / CSI) — the most common Infor ERP among mid-market discrete manufacturers. Horizon integration uses ION and IDOs. Production-deployed at multiple manufacturers.
• Infor CloudSuite LN — used by larger discrete and process manufacturers, particularly in aerospace, automotive, and industrial equipment. Integration through ION with LN's specific business objects.
• Infor CloudSuite M3 — used in food and beverage, fashion, and chemicals. Integration through ION and M3's API gateway.
• Infor VISUAL — for smaller manufacturers running this older Infor product, integration is through direct database access since ION coverage is limited.

ION as the integration backbone

Infor ION is more than a middleware layer — it's a data normalization layer that translates between Infor's various ERPs and external systems. The advantage for Horizon integration: ION provides a consistent integration target regardless of which Infor ERP the customer runs.

ION exposes data through BODs (standardized business object messages — GetItem, SyncItem, GetSalesOrder, etc.) and supports both REST and messaging-based exchanges. Horizon uses BOD-based exchange for the standardized objects and falls back to ERP-specific IDOs or APIs for objects ION doesn't natively cover.

SyteLine/CSI specific objects Horizon reads

• Items with their item types (Phantom, Family, Standard) and planning attributes
• Item Warehouse records for per-warehouse inventory parameters
• Current stock by warehouse, location, lot
• Customer orders and order line history
• Purchase orders and vendor data
• BOMs (Current/Engineering/Production) — SyteLine's distinction between BOM types is preserved
• Job routings and work centers
• MRP planning parameters (Order Policy, Lot Size, Yield, Lead Time)

LN-specific objects Horizon reads

• Items with item planning parameters at the cluster and warehouse level
• Inventory positions including project-pegged inventory (LN's project pegging is distinctive)
• Bills of material with phantom and reference designators
• Routings with operations, machines, and tasks
• Sales order history with sales offices and customer hierarchies
• Purchase order history with supplier rankings

M3-specific objects Horizon reads

• Items with M3's product structure and configurator attributes
• Inventory at warehouse and stock zone level
• Customer orders with M3's distinctive multi-line, multi-delivery structure
• Production orders with M3's order type variations

What Horizon writes back to Infor

• Planned purchase orders through PO BODs
• Planned production orders or job recommendations
• Item planning parameter updates — written back through SyncItem BODs or ERP-specific IDOs
• Forecast values consumed by Infor's own planning processes where customers use them

Alternative integration path

Infor's ION platform supports scheduled flat-file delivery (CSV, XML) over SFTP for environments where event-based or API integration isn't preferred. Many Infor customers running mixed on-premise and cloud landscapes use this pattern.

Authentication and connection

• Infor CloudSuite (cloud-hosted): OAuth 2.0 with service account, configured in Infor OS (Operating Service). The customer's Infor administrator provisions the integration.
• Infor on-premise: ION-mediated connection with service account credentials. Network connectivity through customer-managed VPN or Infor-recommended secure tunneling.
• Direct database (older versions like VISUAL): Read-only schema access provisioned by the customer's DBA team.

A representative reference deployment

An anonymized $250M industrial parts manufacturer running Infor CloudSuite Industrial (SyteLine) across 2 plants deployed Horizon for demand planning, inventory optimization, and finite capacity scheduling in 10 weeks. The Infor integration completed in week 5 of the project. The customer's IT team worked with Infor's professional services briefly to confirm ION configuration for the BODs Horizon needed; most of the integration work happened on the Horizon side.

The interesting result: this customer had previously evaluated Infor's own integrated planning module (CloudSuite Industrial Planning) and concluded it wasn't sufficient for their demand variability and finite capacity needs. Horizon co-existing with SyteLine gave them better planning capability without re-platforming the ERP. The integration through ION made this practical.

Mongoose framework (SyteLine specific)

SyteLine's Mongoose framework provides additional extensibility for customer-specific data and processes. Horizon's connector respects Mongoose customizations — custom IDOs, custom forms — by working with what the customer's developers have already built rather than requiring rework.

Infor + non-Infor mixed environments

Many Infor customers run Infor as the ERP backbone with non-Infor systems for adjacent functions (CRM, e-commerce, WMS). Horizon can pull from Infor and supplementary systems simultaneously, presenting a unified planning view. The integration approach treats each source according to its own access pattern; Horizon's data model normalizes across them.

Common Infor-specific considerations

• BOD coverage gaps — Not every Infor data object is exposed through a standardized BOD. For objects where BOD coverage is missing, the connector falls back to direct IDO access (SyteLine) or ERP-specific APIs.
• Customer-specific BOD enhancements — Some customers have extended standard BODs with custom fields. The connector captures these explicitly during configuration.
• Multi-environment patterns — Customers running CloudSuite Industrial at some plants and LN at others (a result of acquisitions) need explicit mapping at integration time. Horizon supports this multi-Infor pattern, with the unified ION layer making it easier than connecting to two unrelated ERPs.