Setting Up EDI Trading Partners in SyteLine
Every EDI relationship in SyteLine begins with a properly configured trading partner profile. The EDITradingPartner IDO stores ISA qualifiers, GS identifiers, communication settings, and transaction set agreements that determine how documents are enveloped, routed, and acknowledged. A single misconfigured qualifier can cause every outbound document to be rejected by the VAN or trading partner.
ISA and GS Envelope Configuration
The ISA (Interchange Control Header) and GS (Functional Group Header) segments define the identity of both sender and receiver. SyteLine's EDITradingPartner form stores these values and injects them into every outbound envelope. The ISA05/ISA07 qualifier codes (ZZ, 01, 08, 12) must match exactly what the trading partner expects, and the ISA06/ISA08 identifiers are padded to fixed lengths per the X12 standard.
- Set ISA05 sender qualifier to match your assigned code type (ZZ for mutually defined, 01 for DUNS)
- Configure ISA06 with your organization ID padded to exactly 15 characters in EDITradingPartner
- Map ISA07/ISA08 to the trading partner's qualifier and ID from their onboarding documentation
- Define GS02 (Application Sender) and GS03 (Application Receiver) codes for functional group routing
- Enable ISA14 acknowledgment flag to request 997/999 functional acknowledgments automatically
Communication Protocol and VAN Settings
SyteLine supports AS2, SFTP, and VAN-based communication for EDI document exchange. The communication profile linked to each trading partner in the EDICommProfile table defines connection parameters, encryption requirements, and retry policies. AS2 connections require MDN (Message Disposition Notification) configuration for delivery confirmation.
- Configure AS2 URL, certificate, and MDN settings in EDICommProfile for direct connections
- Set SFTP host, port, directory paths, and SSH key for file-based exchange partners
- Define VAN mailbox routing with sender/receiver IDs matching ISA envelope qualifiers
- Enable automatic retry with exponential backoff for failed transmission attempts
- Set up communication logging in SLEDILog table for audit trail and troubleshooting
Transaction Set Agreements and Mapping Profiles
Each trading partner requires explicit transaction set agreements that define which document types (850, 810, 856, 855, etc.) are exchanged, their direction, and which mapping profile to use. The EDITSAgreement IDO links a trading partner to specific inbound and outbound maps stored in EDIMap, ensuring the correct field transformations are applied per partner.
- Create transaction set agreements for each document type and direction in EDITSAgreement
- Link inbound 850 maps to the partner-specific mapping profile in EDIMap IDO
- Configure outbound 856 and 810 maps with partner-specific segment requirements
- Set processing priority and batch schedule per transaction set agreement
- Define error handling rules: reject, hold for review, or auto-correct per agreement
Automate trading partner onboarding in SyteLine with Netray's AI-powered EDI configuration agents—get started today.
Related Resources
SyteLine EDI Transaction Sets: 850, 810, 856 Setup Guide
Configure EDI transaction sets 850, 810, and 856 in Infor SyteLine. Step-by-step guide for purchase orders, invoices, and ASN documents with IDO mapping.
Infor SyteLineSyteLine EDI Field Mapping & Data Transformation Guide
Configure EDI field mappings in Infor SyteLine. Map X12 segments to IDO properties, set up data transformations, and handle cross-reference lookups.
Infor SyteLineSyteLine Middleware Integration: Architecture & Platform Selection
Design middleware architectures for Infor SyteLine integration. Compare MuleSoft, Dell Boomi, and Jitterbit for ERP middleware with IDO connectivity patterns.