Infor LN & BaanFree referencePDF, Excel, Word exportInfor LNAll Infor LN and Baan tools

Infor LN BOD Reference: Outbound Nouns and Initial Publish Sessions

This reference maps the BOD nouns Infor LN 10.x publishes to Infor ION to the initial publish session that sends them and the LN tables behind them. It also lists the BOD Parameters and validation sessions you touch before the first publish.

Download:
BOD noun / setup itemDirectionTypical verbsMain LN source table(s)Initial publish / setup sessionNotes
Setup: BOD Parameters
Setup
-
-
tcbod0100m000 BOD Parameters
Prevent BOD Publishing check box stops all BOD publishing. Select it while configuring, clear it, then run the initial load sessions.
Setup: Validate Publishing Data Setup
Setup
-
-
tcbod0300m000 Validate Publishing Data Setup
Checks ISO codes, blocking reasons, dimension mapping, journal transaction type mapping, tenant / accounting entity / location records and BOD subscriptions. Run before and after configuring.
Setup: Inbound Routing Error Handling
Inbound
-
-
tcbod0100m000 BOD Parameters
Decides what happens to an incoming BOD that does not match a company or an accounting entity and location. Report errors while testing multisite setups.
ItemMaster
Outbound
Sync (Show via Use Verb)
tcibd001 (items)
tcbod0200m000 Publish Logistic Master Data
Tab covers Item and Revision.
PartyMaster
Outbound
Sync (Show via Use Verb)
tccom100 (business partners), tccom110 (sold-to), tccom120 (buy-from)
tcbod0200m000 Publish Logistic Master Data
Tab covers all eight BP roles: sold-to, ship-to, invoice-to, pay-by, buy-from, ship-from, invoice-from, pay-to.
ContactMaster
Outbound
Sync (Show via Use Verb)
tccom140 (contacts)
tcbod0200m000 Publish Logistic Master Data
BillOfResources
Outbound
Sync (Show via Use Verb)
tibom010 (production BOM), tirou102 (routing operations)
tcbod0200m000 Publish Logistic Master Data
Tab covers BOM and Routing.
Location
Outbound
Sync (Show via Use Verb)
tcmcs003 (warehouses) and other enterprise units
tcbod0200m000 Publish Logistic Master Data
Tab covers Office, Warehouse, Project and Site.
WorkCenter
Outbound
Sync (Show via Use Verb)
tirou001 (work centers)
tcbod0200m000 Publish Logistic Master Data
Tab covers Work Center, Work Cell and Station.
Person / UOMGroup / CarrierParty / PriceList
Outbound
Sync (Show via Use Verb)
tccom001 (employees) for Person
tcbod0200m000 Publish Logistic Master Data
Separate tabs. PriceList covers sales and service price lists.
CodeDefinition (logistic code types) and LnMessage
Outbound
Sync
Logistic code tables
tcbod0200m100 Publish Logistic Code Definitions A-L, tcbod0200m200 (M-Z), tcbod0200m300 Publish LnMessage Data
Publish code definitions with the master data so receiving systems get the codes it refers to. LnMessage goes to ION Process for alerts and workflows.
SalesOrder
Outbound
Sync (Show via Use Verb)
tdsls400 (headers), tdsls401 (lines)
tdbod0200m000 Publish Order Management Transactional Data
CustomerReturn
Outbound
Sync (Show via Use Verb)
tdsls400 / tdsls401 (return orders)
tdbod0200m000
Sales order returns tab.
PurchaseOrder
Outbound
Sync (Show via Use Verb)
tdpur400 (headers), tdpur401 (lines)
tdbod0200m000
SupplierRMA
Outbound
Sync (Show via Use Verb)
tdpur400 / tdpur401 (return orders)
tdbod0200m000
Purchase order returns tab.
ReceiveDelivery (Purchase)
Outbound
Sync (Show via Use Verb)
tdpur406 (purchase receipts)
tdbod0200m000
Purchase receipts. The warehouse receipt variant is published from whbod0200m000.
Requisition / RFQ / Quote / SupplierQuote / Contract
Outbound
Sync (Show via Use Verb)
Order Management tables per object
tdbod0200m000
Quote = sales quotations, SupplierQuote = purchase quotations, Contract tab covers supplier and customer contracts.
SupplierSchedule / SupplierPlanningSchedule
Outbound
Sync (Show via Use Verb)
Purchase schedule tables
tdbod0200m000
Purchase releases.
Opportunity / InventoryConsumption
Outbound
Sync (Show via Use Verb)
-
tdbod0200m000
Separate tabs.
ProductionOrder
Outbound
Sync (Show via Use Verb)
tisfc001 (production orders)
tibod0200m000 Publish Manufacturing Transactional Data
ProductionOrder I tab (ShopFloor) publishes production orders, ProductionOrder II (Assembly) publishes assembly orders, LnProductionResult covers repetitive work cells.
Shipment
Both
Sync
Warehousing shipment tables
whbod0200m000 Publish Warehouse Management Transactional Data
Inbound ShipmentBODs from a WMS create shipments, confirmed automatically if Automatic Confirm Shipments from WMS is set in tcbod0100m000.
AdvanceShipNotice
Outbound
Sync
Warehousing tables
whbod0200m000
Customer and receiver variants. WMS Orders check boxes restrict to WMS-controlled warehouses.
ReceiveDelivery (Warehouse)
Outbound
Sync
whinh312 (receipt lines)
whbod0200m000
InventoryAdjustment / CycleCount / InventoryCount / Transfer
Outbound
Sync
Warehousing inventory tables
whbod0200m000
Separate tabs. CarrierRoute is also on this session.
Invoice
Outbound
Sync
cisli305 (sales invoices)
tfbia0210m000 Publish Financial Transactional Data
Publish Proforma Invoice BOD in tcbod0100m000 also sends an InvoiceBOD at shipment confirmation in Warehousing.
SupplierInvoice / PayableTransaction / ReceivableTransaction / AccountsReceivable
Outbound
Sync
tfacp200 (payables open entries), tfacr200 (receivables open entries)
tfbia0210m000
Separate tabs.
SourceSystemJournalEntry
Outbound
Sync
tfgld106 (finalized transactions)
tfbia0210m000
Journal entries for a financial or reporting system.
SourceSystemGLMovement
Outbound
Sync
General ledger history / balances
tfbia8205m000 Publish General Ledger Movement
Check boxes for opening, actual and budget balances. tfbia8211m000 publishes balances by account / dimension combination.
CodeDefinition / Charts / Currency / FinancialCalendar
Outbound
Sync
Financial master tables
tfbia0200m000 Publish Financial Master Data
CodeDefinition II and III need dimensions mapped in tfbia8503m000 first.
Project data (projects, costs, budgets, estimates, progress)
Outbound
Sync
tppdm600 (projects) and project control tables
tpbod0200m000 Publish Project Data
Tabs: Projects, Labor costs, Sundry costs, Project balances, Project period balances, Project costs, Project extensions, Project bids, Project estimates, Project installments, Project budgets, Project progress.

Session codes, names and tab names are taken from the LN 10.x online help. Source tables show where the data lives, not the full BOD mapping: use the BOD mapping and descriptions document for your LN release for field level detail. Publishing to ION cannot be undone, so check the log files after each run.

Get your LN BOD flow list reviewed

Send us the nouns and subscribers you plan to connect and we will check the publish order and setup against your LN release.

Optional. The tool and every export work without this. No spam.

Was this tool useful?

How to use it

Search by noun (SalesOrder, ItemMaster, Shipment) to find the session that does the initial load, or search by session code to see every noun it can send. In LN the tabs of each publish session correspond to BOD nouns, and each tab has check boxes for the data types inside it, for example Item and Revision on the ItemMaster tab of tcbod0200m000. After the initial load, ongoing changes are published by LN itself when records change, as long as Prevent BOD Publishing is cleared. The initial load sessions are normally run once, and again only after a publication error or when a subscribing application needs a fresh data set.

Where this lives in LN

Setup starts in BOD Parameters (tcbod0100m000). Infor's sequence is: select Prevent BOD Publishing, finish the integration configuration (ION connection point, logical IDs, document flows), then clear it and run the initial loads. Validate Publishing Data Setup (tcbod0300m000) checks the data LN needs before it can build valid BODs. Each package has its own publish session: tcbod0200m000 for logistic master data, tdbod0200m000 for Order Management, tibod0200m000 for Manufacturing, whbod0200m000 for Warehousing, tfbia0200m000 and tfbia0210m000 for Financials, tpbod0200m000 for Project. Planning, Quality, Service and People have their own bod0200m000 sessions too.

  • Run master data (tcbod0200m000 and the code definition sessions) before transactional data
  • Use Verb lets you publish Show BODs to named logical IDs instead of Sync to all subscribers
  • Size limits the number of records, 0 means all records in the range
  • Single XML-file per BOD and Logging options help when you need evidence of what was sent

Worked example: first SalesOrder load to a CRM

A plant connects LN to a CRM through ION. The admin selects Prevent BOD Publishing in tcbod0100m000, runs tcbod0300m000 and fixes missing ISO country and currency codes it reports, and sets up the document flow in ION Desk. Then the admin clears Prevent BOD Publishing, runs tcbod0200m000 with the PartyMaster and ItemMaster tabs for company 100, and finally runs tdbod0200m000 with only the SalesOrder check box selected so the CRM receives open orders from tdsls400 and tdsls401. From then on, order changes publish automatically.

Version differences and gotchas

Tab lists change between releases: the 10.7 help for tdbod0200m000 includes tabs such as PlanningSchedule (sales material releases) and LnVendorRating, so compare the session help for your own release before you plan an initial load. Do not use CloudSuite Industrial (SyteLine) BOD lists for LN, the noun coverage and mapping are different. PartyMaster appears as one tab with eight business partner roles, so check which role your subscriber expects. Financial BODs come from tfbia sessions, not a tfbod session, which catches people searching the menu.

Frequently Asked Questions

What is a BOD in Infor LN?

A Business Object Document is an XML message based on the OAGIS standard that LN exchanges with other applications through Infor ION. It has a verb (Sync, Process, Show, Acknowledge) and a noun (SalesOrder, ItemMaster, Shipment). LN publishes outbound BODs when data changes and can process inbound BODs for nouns it supports.

How do I do the initial load of LN data to ION?

Clear Prevent BOD Publishing in BOD Parameters (tcbod0100m000), then run the package publish sessions: tcbod0200m000 and the code definition sessions for master data, then tdbod0200m000, tibod0200m000, whbod0200m000, the tfbia sessions and tpbod0200m000 for the areas you integrate. Check the log after each run.

Where do I find the outbound BOD mapping and descriptions for LN?

Infor publishes a BOD mapping and descriptions document per LN release on docs.infor.com and the Infor support portal, alongside the Infor LN Configuration Guide for Infor ION. Use it for field-level mapping; this page tells you which session and tables are involved.

Why is LN not publishing BODs?

First check Prevent BOD Publishing in tcbod0100m000, then run Validate Publishing Data Setup (tcbod0300m000) for missing setup such as ISO codes, accounting entity and location records or subscriptions. Then check the ION connection point and document flow, and the outbox in ION for errors.

If you want your team to ask LN about orders, items and integration errors in plain English on your own servers, we can set that up next to your ION landscape.

ArchRay builder
Design the on-prem AI stack for Infor LN and Baan: model, GPUs, RAG pipeline, guardrails
See memory, speed and cost as you swap parts, then export the diagram. Free, in your browser.
Open the builder

Keep exploring

Free tools

ERP fixes and how-tos

Runs with your ERP

Guides

AI on your ERP

Integrations

Software