# Infor LN integration document types and integration rules with ION

> Source: https://netray.co/erp-help/infor-ln-integration-document-types-and-rules
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: ERP Help

## Short answer

In LN, an integration document type ties an LN business object to a BOD noun and direction so ION can send or receive it. Rules and mappings then decide which LN data populates the BOD, which events trigger publication and how incoming BODs are converted into LN transactions. Set up the document type first, then the mapping, then test in ION Desk.

## Kind

how-to

## System

infor-ln

## Erp

Infor LN

## Module

Integration / ION

## Query

infor ln integration document type

## Alternate Queries

- integration rules for ln
- infor ln ion bod document
- infor ln integration mapping setup

## Applies To

Infor LN 10.x with Infor OS / ION (on-prem or cloud). Session names vary by version.

## Steps

### Set up an integration document

**Items:**

- Confirm the ION connection point (the LN application ID) and logical ID are configured and active.
- Define or enable the integration document type for the BOD noun, with direction (outbound publish or inbound consume).
- Configure the data mapping from LN fields to BOD elements, including code translations (units, currencies, business partners).
- Configure the triggering rule: which LN event or status change publishes the BOD, and any filter conditions.
- Register the document flow in ION Desk with the connection points and a routing rule.
- Test with one record and inspect the BOD in ION monitoring. Fix mapping errors before enabling at volume.

## Sections

### What the document type controls

**Body:**

The document type is the contract. It says which LN entity maps to which BOD noun, in which direction, and with which verbs (Sync, Process, Get). Without it enabled, ION sees nothing from LN or LN rejects what ION sends.

Custom fields need DAL extensions and an extended mapping. Out-of-sync customization shows as missing elements in the BOD or inbound validation failures.

### Rules, mapping and translation

**Body:**

Most production issues sit in code translation: a unit of measure, an item or a business partner code that exists in LN but has no cross-reference in the other system. Maintain cross-reference tables intentionally and monitor for unmapped values.

Inbound BODs run through DAL, so business rules apply. A BOD that breaks a rule is rejected with a message you can read in the integration monitor.

### Where to debug

**Body:**

Use the LN integration monitor for outbound status, ION Desk for message flow and the BOD content, and the LN log for DAL errors. Compare a good and a bad BOD side by side.

## Pitfalls

- Enabling publication before translation tables are populated.
- Testing only with a toy record that skips optional elements.
- Custom fields not reflected in the mapping.
- No monitoring for rejected inbound BODs.
- Changing mapping in production without versioning.

## Ai Angle

An assistant that reads ION message logs and LN mapping tables can say why a BOD failed and which cross-reference is missing. Netray builds integrations and private AI over them; inbound writes stay behind human approval.

## Faq

### What is an integration document type in LN?

**Answer:** It is the definition that links an LN business entity to a BOD noun and direction, so LN can publish or consume that document through ION.

### Do I need a rule for every BOD?

**Answer:** You need a trigger for outbound documents and a mapping for both directions. Exact configuration depends on the noun and version.

### Why is my BOD rejected on inbound?

**Answer:** Most often an unmapped code or a DAL validation failure. The integration monitor and LN log show which.

### Can I use REST instead of BODs?

**Answer:** For many scenarios, yes. See the LN REST API page; BODs remain the standard for event-driven document exchange.

## Search terms

infor ln integration document type, integration rules for ln, infor ln bod, infor ln ion, infor ln ion desk, infor ln integration mapping, infor ln document flow, infor ln connection point

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json