.png)
Infor LN Integration Guide
Connect Infor LN with enterprise applications through Infor OS ION API REST services, applicable SOAP services, BOD-based messaging, and controlled synchronization workflows.
Infor LN integration options at a glance
Infor LN integrations are commonly implemented through Infor OS, especially the ION API Gateway, ION workflows, and business object documents (BODs), rather than direct database access. REST APIs are the primary option for querying and updating supported LN objects. Applicable LN web services can provide SOAP and WSDL-based compatibility for legacy or function-specific interfaces. ION and BOD processing support asynchronous document and event-oriented flows, although direct webhook coverage varies by object and tenant. Martini can authenticate with OAuth 2.0, orchestrate scheduled or event-driven workflows, transform payloads, enforce business rules, and route failures for retry or reconciliation.
| Integration point | Supported by Infor LN? | Common use cases | How Martini supports it |
|---|---|---|---|
| REST APIs through Infor ION API Gateway | Yes | Query and update supported LN Business Partners, Items, Sales Orders, Purchase Orders, Projects, and other tenant-published resources. Exact operations depend on the LN release, modules, and API catalog. | Martini can consume the ION API REST endpoints, configure OAuth 2.0 credentials, map request and response payloads, apply business rules, and expose APIs for other applications. |
| Authentication | Yes | Infor ION API commonly uses OAuth 2.0 application registration, client credentials, access tokens, permissions, and scopes. Other connection-point authentication methods may depend on the configured interface. | Martini can keep client secrets and environment-specific endpoints outside workflow definitions and use authenticated API workflows with controlled permissions. |
| ION and BOD messaging | Yes | BODs support asynchronous, document-oriented exchanges such as customer, supplier, item, order, invoice, and shipment propagation where the relevant content is enabled. | Martini can receive supported messages through an exposed endpoint or intermediary, validate identifiers and versions, transform BOD-derived payloads, and route duplicates or failures for reconciliation. |
| Webhooks and outbound callbacks | Limited | ION can coordinate event and message processing, but direct webhook coverage is not universal for every LN object or operation. The actual callback or delivery mechanism must be verified in the tenant. | Martini can receive supported callback or message notifications through an API or workflow trigger and can fall back to scheduled incremental polling when event coverage is insufficient. |
| SOAP APIs and LN web services | Limited | Applicable LN releases and components may expose WSDL-based web services for functionality not available through a current REST API or for retained legacy interfaces. | Martini can consume an available WSDL and endpoint, transform SOAP request and response structures, and handle transport and application errors. REST through ION API should generally be evaluated first for new work. |
| Bulk, asynchronous, and batch processing | Limited | Asynchronous BOD and ION processing are available for applicable integrations, while batch behavior varies by selected LN API and integration flow. A universal bulk API for all objects was not confirmed. | Martini can orchestrate paged, scheduled, queued, or bounded-concurrency processing and can separate accepted, rejected, and retryable results. |
| File and attachment APIs | Limited | Document and content capabilities may be available through related Infor products or configured APIs, but file and attachment operations are not universal across LN REST resources. | Martini can process confirmed file or document endpoints and transform file metadata or content where the selected Infor interface supports it. |
| Database and analytics access | Not confirmed | Direct database integration is not the preferred LN application-integration interface because it can bypass application rules, security, validations, and transaction behavior. | Martini can use approved APIs, web services, ION, or BODs. Database connectivity should be limited to explicitly approved reporting or extraction architectures. |
How Infor LN exposes data and business events
Infor LN REST APIs
Infor LN REST APIs are exposed through the Infor OS ION API Gateway. They provide the primary current mechanism for querying and modifying supported business objects, although endpoint names, fields, operations, and permissions depend on the tenant and LN release.
Martini implementation pattern
Martini implementation pattern: configure the tenant-specific ION API endpoint and OAuth 2.0 credentials, invoke the selected resource from a workflow, handle pagination and response status, map the payload to a canonical model, and write the result to the target application or expose it through a Martini API.
Implementation sequence
Infor ION and BOD messages
Infor ION supports asynchronous, document-oriented integration using business object documents. BODs can represent customer, supplier, item, order, invoice, and shipment exchanges where the required content is enabled, but they are not a universal event stream for every LN transaction.
Martini implementation pattern
Martini implementation pattern: receive a supported BOD-derived message through an exposed endpoint or intermediary, validate message and business-object identifiers, check version or current state, map the document to the target system, and route duplicates, ordering conflicts, and failures for controlled processing.
Implementation sequence
Infor LN SOAP web services
Applicable LN releases and components may expose WSDL-based web services. SOAP is a secondary or compatibility option when required functionality is unavailable through a current ION API REST resource or when an existing legacy service must be retained.
Martini implementation pattern
Martini implementation pattern: configure the available WSDL endpoint and authentication, construct the SOAP request from canonical data, invoke the service, parse the response or fault, and route business and transport errors separately. The specific WSDL and Enterprise Server configuration must be confirmed before implementation.
Implementation sequence
Scheduled incremental synchronization
When direct event or callback coverage is unavailable, Martini can poll supported LN REST resources using a timestamp, sequence, status, posting date, or other incremental field. The selected change-tracking field must be verified for each resource.
Martini implementation pattern
Martini implementation pattern: schedule a workflow, retrieve pages using a durable checkpoint, transform and upsert each object, advance the checkpoint only after successful processing, and use bounded concurrency and backoff to respect tenant capacity.
Implementation sequence
Common Infor LN integration patterns
Pattern 1: Sync Business Partners to enterprise applications
When to use this pattern
Use this pattern when customer, supplier, address, or payment information in LN must be kept aligned with a CRM, service platform, procurement application, or analytical store. Event-driven processing can be used where supported; otherwise, schedule incremental retrieval.
Integration direction
Example Mapping
| Infor LN Field | Canonical Field | Target Field |
|---|---|---|
| BusinessPartner.businessPartnerId | party.externalId | Account.externalId |
| BusinessPartner.name | party.name | Account.name |
| BusinessPartner.addresses | party.addresses | Account.billingAddress |
| BusinessPartner.paymentTerms | party.paymentTerms | Account.paymentTerms |
Martini implementation pattern
Martini retrieves or receives Business Partners, validates required identifiers and addresses, maps the payload to a canonical party model, and upserts the target using an external identifier. Invalid master data is routed to an exception path, while transient API failures use bounded retries and the workflow stores a checkpoint for replay.
Martini capabilities used
- workflows
- API consumption
- OAuth 2.0 configuration
- data mapping
- business rules
- idempotency
- error handling
Pattern 2: Process Sales Orders from a commerce or CRM application
When to use this pattern
Use this pattern when an external application creates customer orders that must become LN Sales Orders and receive order, shipment, or fulfillment status in return.
Integration direction
Example Mapping
| Infor LN Field | Canonical Field | Target Field |
|---|---|---|
| order.id | salesOrder.externalReference | SalesOrder.externalReference |
| order.customer | salesOrder.businessPartner | SalesOrder.businessPartner |
| order.lineItems | salesOrder.lines | SalesOrder.lines |
| order.totalPrice | salesOrder.amount | SalesOrder.amount |
Martini implementation pattern
Martini exposes or consumes the source order API, validates customer and item references, transforms line and pricing structures into the LN Sales Order model, and submits supported operations through ION API. The workflow records the LN order number, prevents duplicate creation using the source order reference, and publishes status back to the source after successful processing.
Martini capabilities used
- APIs
- workflows
- data mapping
- validation
- business rules
- correlation IDs
- retry handling
Pattern 3: Synchronize Purchase Orders and supplier status
When to use this pattern
Use this pattern when Coupa, SAP S/4HANA, or another procurement application creates approved purchasing transactions that must be submitted to LN and reconciled with supplier or receipt status.
Integration direction
Example Mapping
| Infor LN Field | Canonical Field | Target Field |
|---|---|---|
| supplier.id | supplier.externalId | PurchaseOrder.supplier |
| purchaseOrder.number | purchaseOrder.externalReference | PurchaseOrder.externalReference |
| purchaseOrder.lines | purchaseOrder.lines | PurchaseOrder.lines |
| purchaseOrder.status | purchaseOrder.status | PurchaseOrder.status |
Martini implementation pattern
Martini receives approved purchase data, validates supplier and item identifiers, maps line quantities and dates, and submits the supported LN Purchase Order operation. It returns the LN document number and status, distinguishes business validation from transient failures, and reconciles partial line or receipt results rather than treating the entire multi-system process as atomic.
Martini capabilities used
- workflow orchestration
- API consumption
- mapping and transformation
- validation
- conditional routing
- reconciliation
- error handling
Pattern 4: Load incremental Items and inventory data into analytics
When to use this pattern
Use this pattern for high-volume synchronization of Items, inventory balances, or Warehousing Orders into Snowflake or another approved analytical destination without repeatedly extracting the complete LN dataset.
Integration direction
Example Mapping
| Infor LN Field | Canonical Field | Target Field |
|---|---|---|
| Item.itemCode | item.externalId | ITEM_CODE |
| Item.description | item.description | DESCRIPTION |
| Item.lastModified | item.modifiedAt | MODIFIED_AT |
| InventoryBalance.quantityAvailable | inventory.availableQuantity | AVAILABLE_QUANTITY |
Martini implementation pattern
A scheduled Martini workflow uses a verified incremental filter and pagination, normalizes LN responses, applies bounded concurrency, and writes analytical rows in controlled batches. It advances a durable checkpoint only after successful writes, retries temporary failures with backoff, and sends schema or data-quality exceptions to a review path.
Martini capabilities used
- scheduled workflows
- API consumption
- pagination handling
- data transformation
- batch orchestration
- checkpointing
- monitoring
Applications commonly integrated with Infor LN
Infor LN can exchange operational, commercial, procurement, project, and analytical data with adjacent enterprise applications. The exact scope depends on the LN release, deployed modules, Infor OS tenant configuration, published APIs, and enabled BODs.
| Application | Scenario | Direction | Martini Pattern |
|---|---|---|---|
| Salesforce | Synchronize Business Partners, items, sales orders, order status, and customer-facing fulfillment information. | Salesforce → Martini → Infor LN | Martini can expose an order API for Salesforce, validate and map requests to LN Sales Orders, then run a separate workflow that publishes LN order and fulfillment status back to Salesforce. Stable external references and exception routing help prevent duplicate orders. |
| SAP S/4HANA | Coordinate master data, procurement, logistics, finance, or manufacturing processes when LN and SAP coexist in a wider enterprise landscape. | SAP S/4HANA → Martini → Infor LN | Martini can orchestrate process-specific API exchanges, normalize identifiers and dates, apply routing rules by company or business unit, and persist correlation and reconciliation status across both systems. |
| Microsoft Dynamics 365 | Exchange customer, supplier, item, order, and operational data between overlapping enterprise applications. | Microsoft Dynamics 365 → Martini → Infor LN | A Martini workflow can consume source API data, map it into LN REST payloads exposed through ION API, and return LN identifiers and statuses to Dynamics 365 with retry handling for transient failures. |
| ServiceNow | Use LN operational and customer information to support service, asset, incident, or support-related processes. | Infor LN → Martini → ServiceNow | Martini can retrieve selected LN Business Partners, Items, Projects, or service-related information, transform it into ServiceNow payloads, and process selected updates back to LN where the deployed APIs support them. |
| Workday | Coordinate employee, organization, cost-center, or project-related information with LN processes. | Workday → Martini → Infor LN | Martini can schedule incremental retrieval from Workday, validate organizational identifiers, map them to the applicable LN structures, and route rejected records to an exception workflow rather than partially applying invalid data. |
| Coupa | Synchronize suppliers, purchase orders, requisitions, receipts, and procurement status. | Coupa → Martini → Infor LN | Martini can receive approved procurement transactions, map supplier and line identifiers to LN Purchase Orders, submit supported operations through ION API, and return LN document numbers and statuses to Coupa. |
| Snowflake | Load LN operational data into an analytical warehouse for reporting, planning, and historical analysis. | Infor LN → Martini → Snowflake | A scheduled Martini workflow can page through approved LN API resources using incremental filters, normalize nested payloads, load analytical structures, and record checkpoints so failed pages can be replayed without reloading the full dataset. |
| Shopify | Exchange products, inventory availability, fulfillment status, and orders between LN and a commerce channel. | Shopify → Martini → Infor LN | Martini can receive Shopify orders, validate customer and item references, submit supported Sales Order operations to LN, and publish inventory or fulfillment updates back to Shopify using separate idempotent workflows. |
How to build a Infor LN integration in Martini
Objective
Establish a tenant-specific connection to Infor LN through the ION API Gateway or another confirmed interface without embedding credentials in workflow logic.
Instructions in Martini
- Confirm the LN release, ION tenant, published API catalog, and required operations.
- Register an ION API application and obtain the required OAuth 2.0 scopes.
- Store client credentials, tokens, WSDL details, and environment values in secure Martini configuration.
- Use SOAP or an approved ION mechanism only when the required capability is not available through REST.
Objective
Select an event, callback, API request, or scheduled trigger based on the actual event coverage and change-tracking fields available in the LN tenant.
Instructions in Martini
- Use a supported ION or BOD-derived message when the required business event is available.
- Expose a Martini API or receive a callback only for a confirmed delivery mechanism.
- Use a scheduler for incremental polling when direct event coverage is insufficient.
- Define the checkpoint, status, sequence, or timestamp used to identify changes.
Objective
Read or receive Business Partners, Items, Sales Orders, Purchase Orders, Warehousing Orders, Projects, or other confirmed resources while respecting pagination and tenant capacity.
Instructions in Martini
- Invoke the selected ION API resource or consume the configured message.
- Follow documented continuation or page parameters rather than assuming a fixed page size.
- Persist the last successful page, object key, or checkpoint where appropriate.
- Avoid direct database access for normal application integration.
Objective
Coordinate calls to LN and target systems as a durable business process with explicit branching, correlation, and reconciliation behavior.
Instructions in Martini
- Separate source retrieval, transformation, target write, and status publication into clear workflow stages.
- Use correlation IDs and durable processing status across multi-step exchanges.
- Apply bounded concurrency and asynchronous processing only where the selected interface supports it.
- Define compensation or reconciliation behavior when one system succeeds and another fails.
Objective
Convert LN payloads and external application models into a canonical structure while enforcing required fields, identifiers, and business rules.
Instructions in Martini
- Map LN-specific identifiers, addresses, dates, quantities, statuses, and nested lines explicitly.
- Treat optional fields as optional and avoid undocumented schema assumptions.
- Validate customer, supplier, item, project, and organizational references before writes.
- Use external references or idempotency keys to prevent duplicate business objects.
Objective
Create, update, or publish the transformed result to the target application and return relevant LN identifiers and statuses.
Instructions in Martini
- Use upsert or lookup-before-create behavior where the target supports it.
- Submit supported LN operations through ION API or the confirmed web service.
- Record target responses, LN document numbers, message identifiers, and processing status.
- Do not assume a cross-system transaction is atomic.
Common Infor LN data objects used in integrations
| Object | Typical Use | Common target systems | Martini handling |
|---|---|---|---|
| Business Partners | Synchronize customers, suppliers, addresses, classifications, payment terms, and commercial identifiers. | Salesforce, Microsoft Dynamics 365, ServiceNow, Coupa, Snowflake | Martini retrieves or receives incremental changes, maps identifiers and nested address data, validates required fields, and upserts using a stable external reference. |
| Items | Exchange manufactured items, purchased items, item attributes, and product master data. | Shopify, Salesforce, Microsoft Dynamics 365, Snowflake | Martini pages through supported resources, normalizes units and classifications, applies item eligibility rules, and routes invalid or incomplete items to exception handling. |
| Sales Orders | Create and synchronize customer orders, lines, quantities, prices, fulfillment status, and delivery information. | Salesforce, Shopify, Microsoft Dynamics 365, Snowflake | Martini validates customer and item references, maps order lines, submits supported create or update operations, and uses external references and reconciliation status to make retries idempotent. |
| Purchase Orders | Exchange supplier orders, lines, receipts, confirmations, and procurement status. | Coupa, SAP S/4HANA, Microsoft Dynamics 365, Snowflake | Martini transforms supplier and line structures, applies approval and amount rules, submits supported operations, and separates business validation failures from retryable transport errors. |
| Warehousing Orders | Coordinate warehouse movements, shipments, receipts, and inventory-related execution data. | Shopify, Snowflake, Microsoft Dynamics 365, ServiceNow | Martini uses incremental retrieval or supported messages, maps warehouse and shipment identifiers, validates sequence or status changes, and prevents stale updates from overwriting current state. |
| Projects | Synchronize project structures, activities, budgets, costs, and project transactions. | Workday, SAP S/4HANA, Microsoft Dynamics 365, Snowflake | Martini maps project and organizational keys, applies scope and status rules, loads analytical or operational targets, and records correlation data for reconciliation. |
Authentication and security considerations
OAuth 2.0 for ION API
Infor LN APIs exposed through the ION API Gateway commonly use OAuth 2.0 with an application registration, client ID, client secret, access tokens, permissions, and scopes. Authorization URLs and scopes are tenant-specific.
Credential management
Store client credentials, tokens, endpoint values, and any SOAP or connection-point credentials in Martini environment configuration or secrets rather than embedding them in workflows.
Least privilege and transport security
- Request only the LN API permissions required by the integration.
- Use the tenant's approved secure endpoints and transport settings.
- Consider Basic Authentication, API keys, or client certificates only where the selected Infor interface explicitly supports them.
- Avoid direct database credentials for normal LN application integration.
Operational considerations for Infor LN integrations
Tenant and release differences
API resources, fields, BODs, connection points, and permissions vary by LN release, installed modules, and Infor OS configuration. Obtain the target tenant's API catalog or OpenAPI definitions before finalizing mappings.
Pagination and incremental processing
Large collections such as Business Partners, Items, Sales Orders, and inventory data may require pagination. Use documented continuation controls and a verified timestamp, sequence, status, or other incremental filter instead of repeatedly extracting complete datasets.
Rate limits and concurrency
ION API capacity and request limits depend on the tenant and endpoint. Use bounded concurrency, backoff for transient failures, batching only where supported, and scheduled workloads for large synchronizations.
Idempotency and message ordering
Use stable external references, message identifiers, object versions, and correlation IDs to prevent duplicate orders or BOD effects. Validate current LN state when messages can be delayed or delivered out of order.
Schema and testing
Treat optional fields as optional, avoid undocumented attributes, version mappings when contracts change, and test after LN or ION upgrades. Reconcile cases where one system succeeds and the other fails because cross-system workflows are not automatically atomic.
Why use Martini instead of scripts or point-to-point integrations?
Orchestrate more than an API call
Infor LN integrations often combine API calls, BOD-derived messages, scheduled retrieval, target-system writes, validation, and reconciliation. Martini represents that behavior as maintainable workflows rather than isolated scripts.
Separate business rules from transport logic
Martini can map and transform LN payloads, apply validation and routing rules, and expose APIs for upstream or downstream applications while keeping environment-specific credentials and endpoints configurable.
Improve reliability and reuse
- Use shared workflows and reusable integration services across LN objects and applications.
- Handle pagination, retries, idempotency, checkpoints, and exception paths explicitly.
- Support REST, applicable SOAP, callbacks, files, and other confirmed enterprise endpoints within a coordinated process.
- Monitor workflow execution and preserve correlation data for operational troubleshooting.
Frequently asked questions
Infor LN is commonly integrated through Infor OS, especially the ION API Gateway for REST APIs, ION workflows, and BOD-based asynchronous messaging. Applicable LN web services can provide SOAP interfaces, while scheduled incremental synchronization can cover processes where direct event delivery is unavailable. Direct database integration is generally not the preferred application-integration method.
Yes. Martini can integrate with Infor LN by consuming REST APIs exposed through the ION API Gateway, consuming applicable SOAP services, receiving supported ION or BOD-derived messages, and orchestrating scheduled synchronization workflows. The exact resources and operations depend on the LN release and tenant configuration.
No. A dedicated Infor LN connector is not required. Martini can use Infor LN's confirmed native integration mechanisms, principally ION API REST services, applicable SOAP services, and supported ION or BOD-based messages, together with OAuth 2.0 and workflow orchestration.
Lonti does not charge an additional per-connector or per-vendor fee to integrate Infor LN. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from Infor, infrastructure providers, or other third-party systems based on subscriptions, usage, and deployment model.
REST APIs exposed through the Infor OS ION API Gateway should generally be evaluated first for new integrations. ION and BODs are relevant for asynchronous document-oriented flows, while SOAP may be appropriate for a required capability available only through an existing WSDL-based service or a retained legacy interface.
ION supports event and message orchestration, including BOD-based processing, but this does not mean every LN object or operation exposes a direct webhook. The specific event, message, callback, and delivery mechanism must be confirmed for the customer's tenant. Martini can receive supported notifications or use scheduled incremental polling as a fallback.
Martini can retrieve or receive LN objects, follow pagination, map LN-specific fields into a canonical model, apply validation and business rules, and write to a target application. Incremental synchronization can use a verified modification timestamp, sequence, status, posting date, or other change field for the selected resource.
Martini workflows can distinguish temporary transport or capacity failures from authentication, validation, authorization, and business-rule errors. Bounded retries with backoff can be used for retryable failures, while stable external references, message identifiers, object versions, and durable processing status help make order and message handling idempotent. Failed items can be routed to controlled exception and reconciliation processes.
Related Martini documentation
APIs
Operations
Integrate Infor LN with confidence
Use Martini to connect Infor LN with enterprise applications through governed APIs, workflows, transformations, and reliable synchronization patterns.