Infor LN API Development: REST, SOAP, and BOD Integration Guide

LN API Architecture and Endpoint Types

LN's API surface is layered across three generations of integration technology. The legacy BaanIV/LN session API uses bshell-based calls into LN business functions. The ION BOD layer publishes and consumes standardized XML Business Object Documents through Infor ION.

The newest LN Integration Framework exposes RESTful web services mapped to LN sessions and tables.

• Session API: direct invocation of LN 4GL business functions via bshell sessions and BDE connectors
• ION BOD layer: publish Sync, Process, and Acknowledge BODs from LN sessions via ttstpbodpub (ttiop4100m000)
• LN Web Services: SOAP endpoints generated from LN sessions using the Web Service Wizard (ttstpws series)
• REST API via Infor OS: ION API Gateway routes authenticated REST calls to LN backend services
• Infor Data Lake integration: LN publishes BODs to Data Lake for analytics and cross-application reporting

Building Outbound Integrations from LN

Outbound integrations push LN data to external systems. The preferred pattern uses ION BODs published from LN sessions that trigger on business events like order creation or shipment confirmation. For real-time requirements, the LN Web Service framework publishes synchronous SOAP endpoints.

Each approach has distinct session management and transaction control implications.

• Configure BOD publishing in LN session ttiop4100m000 mapping LN tables to OAGIS BOD structures
• Use ION Connect data flows to route published BODs to target systems with transformation and filtering
• Implement LN Web Services using ttstpws sessions for synchronous request-response integration patterns
• Handle LN session state management: each web service call opens a bshell session with associated resources
• Implement error handling via ION BOD acknowledgment patterns using ConfirmBOD and fault messages

Inbound Integration and Data Consumption

Inbound integrations consume external data into LN tables and business processes. The ION BOD subscription mechanism in LN processes incoming BODs through mapping sessions that validate and insert data. For bulk data loads, the LN Data Migration Framework (DMF) provides templated import sessions that enforce LN business rules during ingestion.

• Subscribe to inbound BODs using LN session ttiop4500m000 with field-level mapping to LN table columns
• Validate inbound data against LN business rules by routing BOD processing through standard LN sessions
• Use DMF import sessions (ttdmf series) for bulk data loads with built-in validation and error logging
• Implement idempotency checks using BOD document IDs to prevent duplicate processing of replayed messages
• Monitor integration health via ION OneView dashboards tracking BOD volumes, failures, and latency