Infor LN API Development: REST, SOAP, and BOD Integration Guide
Infor LN exposes integration capabilities through multiple API layers: the traditional BAAN/LN session-based interface, the Infor ION BOD messaging framework, and modern web service endpoints published through the LN Integration Framework. Senior developers must understand which API layer fits each integration scenario to avoid performance bottlenecks and data integrity issues.
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
Building LN integrations? Netray's AI agents generate API mappings and BOD configurations from your LN data model—see a live demo.
Related Resources
Infor LN Third-Party Integration Connector Guide
Build and configure third-party integration connectors for Infor LN. ION Connect, middleware patterns, and connector development for CRM, WMS, and e-commerce systems.
Infor LNInfor LN Cloud Migration Strategy Guide
Plan your Infor LN cloud migration with assessment frameworks, architecture decisions, and phased migration strategies for moving LN to Infor Cloud or hybrid hosting.
Infor LNInfor LN BAAN Backward Compatibility Layer
Navigate BAAN backward compatibility in Infor LN. Legacy 4GL code migration, session mapping, table structure changes, and BaanIV to LN transition strategies.