Integrations / ERP / Infor LN
Infor LN Integration Guide for Production Scheduling with SkyPlanner APS
This Infor LN integration guide shows partners and IT teams how to connect Infor LN to SkyPlanner APS. SkyPlanner integrates with Infor LN in both directions:
- Production orders, routing operations, work centers, machines, items, stock and purchase orders flow in.
- Planned start and finish dates per operation go back to the LN production orders.
- Operator timelogs come back as machine hours, labor hours and completed quantities.
- SkyPlanner webhooks push schedule changes as they happen.
The SkyPlanner team configures the integration to your LN setup during onboarding and supports it after go-live. Partners and developers can take part, or build on SkyPlanner’s documented REST API (API reference) themselves.
Cloud or on-premises: what shapes every LN integration
LN runs on two release tracks, and they connect differently. SkyPlanner runs in the cloud in both cases, so nothing is installed inside LN.
| LN in the cloud (2022.x to 2026.x, CloudSuites) | LN 10.x on-premises | |
|---|---|---|
| Main interface | LN REST API (service group LN/lnapi) through the ION API Gateway | ION with BODs |
| Authentication | OAuth 2.0, .ionapi backend service credentials | ION connection points |
| Change signal | BODs published to ION, or scheduled polling | BODs published to ION |
| Bulk extract | ION Data Lake or exports | Exchange schemas, database views or session exports |
LN interfaces for scheduling
1. LN REST API. Infor publishes LN services in the ION API Gateway: “You can review the available documentation for the public services that are part of LN API.” For scheduling, the key service is tiapi.sfcProductionOrder. It covers production orders and machine operations with the actions Get Machine Operations, Register machine quantities, Register machine hours and Finish Machine Operations. Further tiapi and tcapi services are listed per tenant in the gateway.
Each service must be entitled and activated. Infor notes that “Try it out” “only works if you are entitled for the service and the service has been activated.” Put this on the project checklist on day one.
2. ION BODs. “Business object documents (BODs) are XML messages used to exchange data between enterprises or enterprise applications.” LN sends them to Infor ION, which routes them to subscribers. Process.ItemMaster and Process.BillOfMaterials are named in the LN 10.8 documentation, which also covers BOD-based integration with LN on premises. The full BOD list for your release sits in your tenant.
3. File exports. On-premises LN can export tables through exchange schemas or database views. This suits the initial load and plants that prefer a scheduled file exchange.
Authentication
On LN in the cloud, use the ION API Gateway with OAuth 2.0:
- Create an ION API authorized app of type Backend Service and download its
.ionapifile. - The file holds the client ID (
ci), client secret (cs), gateway URL (iu), auth server (pu), token path (ot) and tenant (ti). - Request tokens with the client credentials grant. Calls run as a service account.
- Give the service account only the LN roles the integration needs.
On the SkyPlanner side, the REST API authenticates with an API token (SkyPlanner Settings > API) and is documented in Swagger/OpenAPI. The integration tutorial walks through the first calls. An API token is enough to start.
Events, webhooks and polling
LN publishes BODs to Infor ION on business events, and ION routes them to subscribers. A subscriber syncs the changed item or order. Where no BOD fits, the integration polls the LN REST services on a schedule, filtered to open orders.
SkyPlanner sends webhooks when state or the schedule changes, so the write-back side is event-driven.
Data mapping
| Infor LN object (session or service) | SkyPlanner object | Direction | Frequency |
|---|---|---|---|
Items – General (tcibd0501m000), Items – Planning (cprpd1100m000), Process.ItemMaster | Products and materials | LN → SkyPlanner | Initial load, then on change |
Bill of Material (tibom1110m000), production BOMs, material-routing links, Process.BillOfMaterials | Product structure, subproducts, materials per operation | LN → SkyPlanner | Initial load, then on change |
| Routing Operations (tirou1102m000), Tasks (tirou0103m000) | Process steps with setup and run times | LN → SkyPlanner | Initial load, then on change |
| Work Centers (tirou0101m000), Machines (tirou0102m000) | Workstations, workstation groups, efficiencies | LN → SkyPlanner | Initial load, rarely after |
| Calendars, Working Time Schedule (tcppl1100m000) | Shifts and working time | LN → SkyPlanner | Daily, or shifts kept in SkyPlanner |
Production Orders (tisfc0501m000), machine operations (tiapi.sfcProductionOrder) | Orders and jobs with due dates and material needs | LN → SkyPlanner | BOD event or polling every few minutes |
| Inventory on hand | Stock balances | LN → SkyPlanner | Hourly or before each schedule run |
| Purchase order lines with expected receipt dates | Incoming material; stock updates when the PO is marked Delivered | LN → SkyPlanner | Hourly or before each schedule run |
| Production order operations: planned start, finish, machine | Scheduled operations | SkyPlanner → LN | On schedule change, via SkyPlanner webhook |
| Register machine hours and quantities, Finish Machine Operations; Production Order Hours (bptmm1120m000), Report Operations Completed (tisfc0130m000) | Timelogs, quantities, completed operations | SkyPlanner → LN | Per confirmation or per shift |
| Not in LN | Setting time matrix, tools as finite resources, operator counts, alternative workstations | Maintained in SkyPlanner | Set up during onboarding |
Integration patterns
1. Initial master data load. Load items, BOMs, routing operations, tasks, work centers, machines and calendars. Decide how LN’s work center and machine levels map to SkyPlanner: a work center with four machines can become one workstation group with four workstations.
2. Order sync. Read production orders with their operations and material lines, plus stock and open purchase order lines. SkyPlanner treats ordered material as available on the PO delivery date, so the schedule checks stock and incoming supply.
3. Schedule write-back. For each operation the engine placed or moved, SkyPlanner sends the planned start, finish and machine back to the LN production order operation. LN keeps quantities, status and costing.
4. Shop-floor confirmations. Operators log work with Mobile Confirmations, the Production Timer or Quick Log Mode. Timelogs keep the schedule current and go back to LN as machine hours, quantities and finished operations. Pick one posting channel, SkyPlanner or LN sessions, so hours are never booked twice.
5. Ownership and conflict rules. Agree them before go-live:
| Data | Owner |
|---|---|
| Items, BOMs, routings, order quantities and status, stock, postings | Infor LN |
| Operation sequence, planned start and finish, machine assignment | SkyPlanner |
| Setting time matrix, tools, operator counts, alternative workstations | SkyPlanner |
| Shifts and absences | One system, chosen in scoping |
6. Living next to Infor’s own planners. Enterprise Planning keeps proposing supply, and SkyPlanner schedules the production orders against real capacity. On LN 2026 releases, LN’s External Planner setting exists so “The organization can integrate an external planning solution with Infor LN.” If Scheduler+ is active, fix date ownership first: it adds a Scheduled status and requires scheduling before release.
Typical project steps
Implementation is normally completed within weeks after onboarding starts. Before that, the 30-day free trial runs on your own data. Export work centers, machines, routing operations and open production orders from LN sessions to Excel, import them and validate the schedule.
The project itself contains:
- Scoping. Release track, interface route, mapping table, ownership rules and posting channel.
- Access. Entitle and activate the LN REST services, create the
.ionapibackend service and service account, or set up the BOD subscriptions in ION. Sandbox tenant first. - Initial load. Items, BOMs, routing operations, work centers, machines and calendars.
- Order sync. Production orders, stock and purchase order lines by BOD event or polling.
- Constraint setup in SkyPlanner. Setting time matrix, tools, operator counts and alternative workstations.
- Write-back. Planned operation dates, then hours and quantities.
- Parallel run. Run SkyPlanner beside the current plan, compare dates and fix master data.
- Go-live. Switch on write-back once the data matches.
What to plan for in an Infor LN integration
- Wrong documentation set. LN 10.x and the yearly cloud releases differ. Planner+ and Scheduler+ are documented only in the 2026 doc sets, and the Job Shop Scheduler starts in 10.8. Check every page against your release.
- Wrong Infor product. Infor LN is not CloudSuite Industrial (SyteLine) or M3. Their BODs and APIs differ, so use LN documentation only.
- Service not activated. LN REST calls fail until the service is entitled and activated in the tenant.
- Enum filters. OrderStatus is an enumeration, so an OData
$filteron status needs the enum syntax, as Infor community users report. - Lead time versus routing. The Operations Horizon in Items – Planning decides whether planned orders use routing data or a fixed Order Lead Time. Read durations from routing operations, not from order lead times.
- Work center sessions. With Job Shop by Site active, LN uses the Work Center session (tirou0601m000) instead of Work Centers (tirou0101m000). Map from the one your company uses.
- Machine hours versus labor hours. In Production Order Hours, machine hours carry a blank Employee field. Map SkyPlanner machine time and operator time to the right lines.
- Calendars per enterprise unit. Load the calendar that belongs to each work center’s enterprise unit, not one plant calendar.
Who configures the Infor LN integration
- The SkyPlanner team configures it during onboarding and supports it after go-live. Every plant runs LN differently: plan units, work center structures, release flow and posting habits. Mapping those is where the know-how goes.
- Your Infor LN partner can take part. The partner knows your tenant, entitlements and ION setup, and can own the LN side while SkyPlanner provides the REST API, Swagger/OpenAPI documentation and webhooks.
- Your own developers can build it on the same documented REST API with an API token. An API token is enough to start, and the SkyPlanner team assists when needed. Product documentation is public at SkyPlanner docs.
SkyPlanner starts from 199 € per month with 5 workstations included, billed monthly. The integration is quoted up front for your process and needs, together with your plan, so you see the full cost before you start. See how LN’s own planning compares in Infor LN finite capacity scheduling, the overview on the Infor LN page, and other systems in the ERP integrations hub.
SkyPlanner reviews from manufacturers
2 hsaved every week
“SkyPlanner has taken our production planning from Excel spreadsheets to real-time production optimization.”
Kalle Kalliomäki, Supply Chain Specialist
UTU · Electrical switchboards and switchgear
Production planning saves 2 hours of working time every week, and a new work queue reaches the line in seconds.
+90%production efficiency
“Efficiency has gone up 90% in production.”
Abdul Rucyinga, Head of IT
Laboratory & Allied · Pharmaceutical manufacturing
Production efficiency is up 90%, and a three-month optimized plan across all workstations takes under 30 minutes.
99.2%delivery reliability
“SkyPlanner has brought visibility to identifying bottlenecks and clarified production management.”
Toni Tuori, Production Manager
Piristeel · Roof safety and rainwater systems
Delivery reliability reached 99.2% this year, and scheduling saves up to four hours of working time per day.
Fewerstoppages from material shortages
“The value SkyPlanner brings us is that it is a tool that works in daily use, especially for setting delivery dates.”
Tommi Männistö, Production Planning Manager
Eskomatic · Contract machining
Automatic load scheduling gives more accurate delivery dates, and production stoppages caused by material shortages have fallen sharply.
FAQ
How do you connect an APS to Infor LN?
On LN in the cloud, through the LN REST API in the ION API Gateway with OAuth 2.0, plus ION BODs as change events. On LN 10.x on-premises, through ION BODs or file exports. SkyPlanner integrates with Infor LN in both directions on either track.
Which LN API covers production orders?
The tiapi.sfcProductionOrder service in the LN REST API. It reads production orders and machine operations and registers machine hours, quantities and finished operations. Other services are listed per tenant in the ION API Gateway.
Who builds the Infor LN integration?
The SkyPlanner team configures the two-way integration to your LN setup during onboarding and supports it after go-live. Your Infor LN partner or your own developers can also build on SkyPlanner’s documented REST API, and an API token is enough to start.
Do we need Scheduler+ or Planner+ to use SkyPlanner?
No. SkyPlanner schedules LN production orders on its own engine, on any LN release. On LN 2026 releases, LN’s External Planner setting is the documented way to run an external planning solution next to LN.
Why connect SkyPlanner instead of rolling out Scheduler+?
Scheduler+ is an add-on module that “may require a commercial component” (source), documented from the LN 2026 releases, and its schedule is loaded, run and then accepted by the planner (source). SkyPlanner connects to the LN you run today, is live within weeks after onboarding starts, and Autopilot replans automatically on every meaningful change. The SkyPlanner team configures and supports the two-way integration, and your LN partner can own the LN side.
Can we test SkyPlanner before building the integration?
Yes. The 30-day free trial supports up to 20 workstations with CSV or Excel exports from LN, no credit card needed. Start the trial, or talk to sales to scope the integration.
