Baan Purchase Order Template and Print Layout Guide for Infor LN
This Baan purchase order template shows a clean PO layout with the fields Baan and Infor LN purchase orders normally print: header, supplier and ship-to, terms of payment and delivery, and a line table with delivery dates. Fill the fields, export to PDF or Word, and use it as a spec when you rebuild or tidy the PO report.
Fill in
Baan Purchase Order Template
Purchase Order 400123
Buyer: Northfield Components Inc. 1200 Industrial Parkway Columbus, OH 43215, USA
Order date: 2026-10-20 Revision: 0 Purchase office / buyer: J. Morgan, Central Purchasing
Supplier
Apex Precision Castings Ltd. 45 Foundry Road Birmingham B9 4AA, UK
Ship to
Northfield Components Inc. Receiving Dock 3 1200 Industrial Parkway, Columbus, OH 43215
Commercial terms
Currency: USD Terms of payment: Net 45 days from invoice date Terms of delivery: DAP Carrier: Supplier arranges, DAP Columbus
Order lines
| Pos | Item / supplier item | Description | Qty | Unit | Unit price | Delivery date | Line amount |
|---|---|---|---|---|---|---|---|
| 1 | CST-20418 | Housing, cast iron, per drawing rev C | 120 | EA | 38.50 | 2026-11-17 | 4,620.00 |
| 2 | CST-20419 | Cover, cast iron, per drawing rev B | 120 | EA | 12.75 | 2026-11-17 | 1,530.00 |
| 3 |
Remarks and conditions
Material certificates and first article report to accompany first shipment. Reference PO number on all packing slips and invoices.
The supplier is asked to confirm this order in writing within 3 working days. Delivery dates are the dates goods must arrive at the ship-to address.
Authorization
This is a generic layout for reference, not an export of any specific Baan report. Match it to your own print session and report layout. Terms and conditions text is a starting point, not legal advice; have your legal team approve it.
Baan purchasing data, searchable on-prem
Ask us how a private AI layer can answer purchasing questions from Baan or LN data without leaving your network. Optional.
Optional. The tool and every export work without this. No spam.
How to use the template
Enter the header and terms in the form, replace the example lines with your own, and export. You can send the result as a manual PO when the ERP is unavailable, or give it to a report developer as the target layout. The fields mirror what Baan holds on the purchase order header (order number, order date, buyer, supplier, payment terms, delivery terms) and on each line (position, item, quantity, unit, price, delivery date).
Where the data comes from in Baan and LN
Purchase orders live in the purchase order header and line tables, tdpur400 and tdpur401 in Infor LN (tdpur040 and tdpur041 in Baan IV). The supplier or business partner details come from the common tables, and terms of payment and delivery come from the common terms tables. The order is normally printed from the purchase order print session in the Purchase Control module, which calls a report whose layout you maintain in the Tools report editor. Check the exact session codes and table names in your own version before you build.
- Header fields: order, order date, buyer, supplier, currency
- Line fields: position, item, description, quantity, unit, price, delivery date
- Terms: payment terms, delivery terms, carrier
- Texts: header and line texts print as remarks
Changing the PO print layout
Report layouts in Baan and LN are edited in the Tools module report editor, usually on a copy of the standard report assigned to your package VRC, so upgrades do not overwrite your work. Typical changes are adding a logo, moving the delivery date next to quantity, printing the supplier item number, adding a supplier acknowledgment request and showing the order revision. Change one thing at a time, test with a draft order, and keep the customized report in version control.
Common mistakes
Frequent problems are printing the internal item number when the supplier needs its own part number, leaving out the revision after a change order, mixing up order date and requested delivery date, and printing long line texts that push the totals onto a second page. If you send POs by EDI or email, confirm that the layout and the electronic message carry the same data.
Frequently Asked Questions
What does a Baan purchase order contain?
A header with order number, date, buyer, supplier, currency, payment and delivery terms, and one or more lines with item, description, quantity, unit, price and delivery date. Header and line texts print as remarks. Totals and tax come from the order and tax setup.
Can I edit the Baan purchase order report layout?
Yes. Reports are maintained in the Tools report editor. Copy the standard report, change the copy, and assign it to the print session or print group so it survives upgrades. Test on a draft order before releasing it to buyers.
Is this the same as the Infor LN purchase order?
The structure is the same idea in Baan IV, Baan V and Infor LN, but session names, tables and report objects differ by version. Treat the template as a layout reference and confirm field names in your own system.
Can I use this as a purchase order when the ERP is down?
Yes, as a stopgap. Use your normal PO number range, enter the order in Baan afterwards, and mark the document as a manual order so the two records match. Do not issue duplicate numbers from the template.
If you are moving off Baan or want your purchasing data searchable by a private AI on your own servers, Netray can help with both. The template is free either way.
Related Tools
Purchase Order Terms and Conditions Checklist
A 30-point checklist of the clauses a manufacturing purchase order should cover: price, delivery, quality, flow-downs and legal terms.
Supply Chain & InventoryPurchase Order Acknowledgement Review Checklist
A checklist for reviewing a supplier's order acknowledgement before you accept differences in price, dates, terms or quality requirements.
Infor LN & BaanInfor LN and Baan ERP Table List by Package
Filterable list of commonly used Infor LN and Baan tables by package, with the naming convention, key fields and where a Baan IV table differs from LN.
Infor LN & BaanInfor LN and Baan Integration Interface Specification Template
Fill-in functional and technical specification for an LN or Baan interface, including data flow, error handling and volumes.
More Infor LN & Baan tools
See all- Baan to Infor LN Migration Readiness Assessment
- Baan IV End-of-Life Risk Cost Calculator
- Infor LN Upgrade Cost Estimator
- Infor LN vs SyteLine Selector
- Baan Data Migration Effort Calculator
- Infor LN Multi-Site Rollout Planner
- Infor LN Customization Complexity Scorer
- Baan Modernization ROI Calculator
- Infor LN Performance Tuning Checklist
Keep exploring
Free tools
- Infor LN and Baan Customization Inventory WorksheetEditable worksheet to list every Baan or LN customization with type, owner, effort and a retire, keep or replace decision.
- Infor LN and Baan ERP Table List by PackageFilterable list of commonly used Infor LN and Baan tables by package, with the naming convention, key fields and where a Baan IV table differs from LN.
- Baan to Infor LN Data Conversion Mapping WorksheetField-level mapping sheet for Baan or legacy data moving into Infor LN, with transform rules, owners and load status.
ERP fixes and how-tos
- Baan Open Order Report: Sales and Purchase Sessions, Filters and TablesHow to get a Baan open order report for sales and purchase orders: which sessions to use, how to filter open lines, and which tables to query or export.
- Private AI Layer for Baan On-Prem: Reference ArchitectureReference architecture to add a private AI assistant to Baan on-prem: data access paths, retrieval, permissions, sizing and rollout, no cloud needed.
- Infor LN Reports Stuck in the Print Queue: Device and Spooler FixInfor LN reports sit in the print queue and never print when a device goes offline. Check the device definition, the spooler, and fix the queue fast.
Guides
- BAAN 5 to Infor LN Complete Migration GuideMigrate from BAAN 5 to Infor LN comprehensively. 4GL analysis, data transformation, business process mapping, and organizational change management.
- Baan to SAP Migration vs Infor LN: Baan ERP vs SAP S/4HANABaan to SAP migration versus Infor LN: compare functional fit, the 12-18 vs 18-30 month timelines, customization rework and cost for Baan ERP manufacturers.
- AI Integration with Infor LN and Baan: A Technical GuideIntegrate AI with Infor LN or Baan: ION API patterns, business object documents, session versus web service access, and where AI agents should not write.
AI on your ERP
- AI for Legacy Baan IV/V: Capture the Knowledge Before It Walks Out the DoorUse AI to capture knowledge from ageing Baan IV/V systems, document undocumented customisations, and de-risk a future migration to LN or CloudSuite.
- AI for Infor LN Purchasing: Faster Exception Handling on Orders, Schedules and SuppliersAI for Infor LN purchasing: triage late orders and schedules, answer supplier performance questions, and draft POs with buyer approval. On-prem option.
Integrations
- How to add WhatsApp to Baan IV / Baan VHow to send order, shipment and approval messages from Baan IV or Baan V over WhatsApp Business Platform, using exports, a staging table and a small relay.
- How to add AI agents to Baan IV and Baan VHow to add AI agents to Baan IV or Baan V: tool layer over read-only database access and AFS, human approval on writes, and an on-prem model. A practical guide.