How Infor VISUAL EDI Integration connects to Infor VISUAL
Infor ION connectors
Documents flow between 1 EDI Source and VISUAL as ION BODs. This suits sites that already run ION for other integrations and want one messaging layer.
Point-to-point through Infor APIs
The vendor also describes a direct integration through Infor APIs. This avoids an ION dependency, but you need to agree on which APIs, credentials and error handling are used.
What data moves
| From | To | Data | When |
|---|---|---|---|
| Trading partner via 1 EDI Source | Infor VISUAL | Purchase orders and changes | Partner transmits the document |
| Infor VISUAL | 1 EDI Source | Advance ship notices | Shipment released or confirmed |
| Infor VISUAL | 1 EDI Source | Invoices | Invoice posted to the customer |
Setting it up
- 1Choose ION or APIDecide whether to use ION connectors or direct API integration, based on what your team already maintains.
- 2List partners and documentsDocument each trading partner, their document types and any special rules.
- 3Prepare master dataLoad customer ship-to codes and partner part cross-references into VISUAL.
- 4Build the mappingsAgree with 1 EDI Source how EDI fields map to VISUAL order and invoice fields.
- 5Test end to endRun test orders through to shipment and invoice for each partner.
- 6Go live with monitoringAssign daily review of failed and held documents.
What usually breaks
- !Choosing ION without existing ION expertise adds an unplanned project.
- !Direct API integration needs credential and version management that is often forgotten at upgrade time.
- !Partner-specific requirements get added late and break generic mappings.
- !Price, quantity and unit of measure differences between PO and VISUAL order lead to invoice disputes.
- !Items with lot or serial tracking need careful ASN design.
A private AI layer across both systems
Mapping exception review
A private assistant compares incoming EDI with VISUAL customer and part data and lists orders that cannot map, with suggested cross-reference entries for approval.
Price and quantity mismatch checks
Flag orders where PO price or unit differs from the VISUAL price list before they are released.
Daily EDI summary
Summarize overnight documents, failures and held items in plain language for the customer service lead.
Try it here, free
Infor VISUAL Engineering Change Notice Template
A fill-in ECN form covering part revision, engineering master and BOM changes, open work order impact and approvals, ready to export.
When something else fits better
- SPS Commerce is another provider that integrates with VISUAL, using ION BOD XML.
- A few partners can sometimes be handled through their web portals without EDI.
- Use VISUAL's own import tools with flat files for low-volume, simple documents.
Frequently asked questions
How does 1 EDI Source connect to VISUAL?
Their integration page says they use Infor ION connectors or point-to-point integration through Infor APIs. Which one fits depends on your ION footprint and IT preferences.
Which documents are covered?
The page mentions EDI orders, invoices and ship notices between VISUAL and trading partners. Ask the vendor about other document types you need.
Is it suitable for on-prem VISUAL?
VISUAL is commonly on-prem, and the vendor lists direct API as an option, so network access and security need to be designed with them.
What would a private AI layer add?
It can triage failed EDI documents and check mappings against VISUAL data on your own servers. Any change to orders or master data stays behind human approval.
Pairing documented at www.1edisource.com/integrations/infor-visual-erp/ . Infor VISUAL EDI Integration is a product of 1 EDI Source; Netray is independent and not affiliated with either vendor.