Typical EDI Errors
1. Unable to identify the Document
Make sure the document protocol parameters defined in the document definition matches the corresponding data in the inbound document.
2. Agreement Identification which involves Document Identification and TP Identification
For e.g. trading partner agreement not found for the given input values: From party [NAME-ROLE] "GlobalChips-Seller", To party [NAME-ROLE] "GlobalChips-Buyer", Collaboration name "3A4"; also verify agreement effectiveToDate
Check: Make sure to verify Trading Partner Name, Trading Partner Parameters (Optional), Document Type Name, Document Type Revision ,Trading Partner Id, Delivery Channel
3. Document Validation Error
Check: 1. Make sure Document Revision Protocol Parameters i.e Transaction Envelope has valid values.
Proper ECS file is used for Validation. Make sure you have not used xsd instead of ecs file.
4. Connection Issues
Transport error: [IPT_HttpSendConnectionRefused] HTTP connection is refused. Connection refused: connect
Check : Make sure the information about delivery channel is correct and also the end point is active. This can be done by pinging the end points.
5. Duplicate Delivery channel
Check : Make sure you have not used the host ip address for configuring the Trading partner Delivery channel.
Wednesday, August 29, 2007
Typical EDI Errors and Solutions
Posted by Ramesh Nittur at 7:19 AM
Labels: B2B Document Editor, ERROR/Exception
Subscribe to:
Post Comments (Atom)
1 comment:
Hi,
And for Business action name "null" ?
Trading partner agreement not found for the given input values: From party[NAME] "out", To party[NAME] "BAS", Business action name "null"; also verify agreement effectiveToDate
Post a Comment