A failed order or shipment in Infor CloudSuite can leave several teams with different versions of the same event. EDI may show a delivered file, the ERP may show no order and the warehouse may already have released a shipment. The safest response is to trace the document across those boundaries before correcting or resending it.
Quick Answer
Infor CloudSuite EDI error handling means locating where a failed order or shipment stopped, checking whether a business record already exists and correcting the responsible data, map or connection before a controlled retry. For orders, verify that the purchase order posted once. For shipments, reconcile the physical shipment, ERP record and advance ship notice. Then check the trading partner's acknowledgment and business response separately.
In This Article
Where orders and shipments fail
Electronic data interchange, or EDI, moves standardized business documents between companies. In a typical order flow, a trading partner sends an 850 purchase order, your integration processes it into Infor CloudSuite and your team may send an 855 purchase order acknowledgment. Later, an 856 advance ship notice, or ASN, describes a shipment. Each handoff has its own status, so a successful transmission does not establish that the ERP posted an order or that the partner accepted an ASN.
Our working definition of an EDI exception is a transaction whose technical state and business state do not yet agree. Focused E-Commerce recommends finding the last confirmed milestone before changing data. This keeps a mapping problem from being treated as a warehouse correction, or a partner rejection from being mistaken for an Infor posting failure.
| Where it stopped | What to check | Who usually investigates first |
|---|---|---|
| Receipt or transmission | Was the file sent, received and associated with the right partner? | EDI or communications owner |
| Translation or validation | Did the document meet the expected format and mapping rules? | EDI mapping owner |
| ERP integration | Did the translated transaction reach the intended Infor workflow? | Integration and ERP owners |
| Business posting | Does an order or shipment record exist, and is it complete? | ERP and operations owners |
| Partner processing | Did the partner acknowledge syntax and then accept the business content? | EDI owner with the trading partner |
The screens, logs and recovery actions vary by CloudSuite application and integration design. If your flow uses Infor ION, the integration layer may sit between the EDI system and the application. Use your application documentation and actual process design to identify the handoff. For more context, see our article on Infor ION and EDI data flows across CloudSuite applications.
A controlled process for failed orders
Identify the original transaction
Start with the partner, document type, order reference, receipt time and available EDI tracking information. Locate the inbound 850 and follow it through receipt, translation, integration and posting. If the transaction is absent at one stage, investigate that boundary rather than changing the purchase order. If it appears at multiple stages, establish whether one copy already produced an ERP order.
Check business state before retrying
Search Infor for the order and review its current status with customer service or order management. A transaction can appear to fail after a business record has been created. Blindly loading the same file again risks a duplicate order or a conflicting update. Hold automated retries while the team establishes whether the original attempt posted fully, posted partially or did not post.
Correct the source of the error
Compare the error with the trading partner's published EDI implementation guide and your approved mapping. If the sender supplied incorrect business data, agree on a corrected source document or another partner-approved procedure. If valid partner data fails because of a translation or integration rule, update and test that rule. If an ERP business value needs attention, involve its owner rather than silently altering the EDI file. Consult the relevant Infor documentation for the applicable recovery action.
After a controlled reprocess, confirm the order exists once, its business details match the intended transaction and any expected 855 reflects the actual order decision. An 855 is a purchase order acknowledgment, but whether your partner expects one, and what it must contain, depends on that partner's guide.
Recovery when an ASN fails
An outbound 856 ASN is especially time-sensitive because the physical shipment may have left before anyone notices the EDI error. Establish three facts: what shipped, what Infor recorded and what the partner received. If those do not match, fix the underlying shipment or mapping issue before resending anything.
- Confirm the physical event. Ask the warehouse to verify the shipment and its package or pallet details against the system record. Do not infer shipped quantities from the original order.
- Inspect the outbound history. Determine whether an 856 was generated, translated, transmitted and acknowledged. A failed generation step calls for a different fix than a partner rejection.
- Review labels where relevant. Compare GS1-128 label information with the shipment and ASN when the partner's guide calls for those labels. A corrected ASN cannot repair a mismatched physical label after dispatch.
- Agree on the correction path. Check the partner's published guide and contact the partner when needed to establish whether it expects a corrected document, another transmission or a separate exception process.
- Verify the result. Record what was resent, what was received and whether the business issue remains open.
Do not resend by default. An already received ASN may be treated differently from an ASN the partner never received. Establish the first transmission's outcome and the partner's correction procedure before generating another 856.
If shipping labels are part of your workflow, our UCC Label App handles UCC-128 and GS1-128 labels. The operational check still belongs to the warehouse and EDI teams: the label, shipment record and transmitted ASN should describe the same shipment.
Common recovery mistakes
The most costly mistakes tend to come from treating one status as the entire transaction outcome. A sent file can fail translation at the receiver. An order can post even if a later response fails. A syntactically accepted ASN can still raise a business issue.
- Reading a 997 as business approval. A 997 functional acknowledgment tells the sender whether a document passed the receiver's syntax check. It can report acceptance or rejection, but it does not mean the order or its content was accepted.
- Fixing the symptom in the wrong system. A recurring mapping failure needs a mapping review. A wrong shipped quantity requires a business and warehouse investigation.
- Retrying without duplicate controls. Check both ERP records and transmission history before reprocessing or retransmitting.
- Closing the ticket at transmission. For outbound documents, track the partner response and resolve any remaining business rejection.
- Using an old partner guide. Confirm the current published implementation guide when onboarding or changing transaction flows.
An 824 application advice, when used by a partner, can convey application-level issues after the document reaches that stage. It serves a different purpose from a 997. Our article on using EDI 824 application advice to diagnose rejected transactions explains how to investigate that response.
Best practices for ongoing operations
Build an exception record that connects technical evidence to a business owner. For each failed order or shipment, capture the partner, document reference, last confirmed milestone, current ERP state, correction owner and next expected response. Agree in advance who can approve a business-data correction and who can authorize a resend.
Test failures as part of partner onboarding, an Infor integration change or a Sterling upgrade. Include an order that fails before posting, one that posts before a response fails and a shipment whose ASN cannot be sent. Confirm that staff can find the original transaction, avoid duplicates and explain the business status without relying on one administrator's memory.
Keep maps and partner rules under change control. The EDI Map Library contains 850+ pre-built EDI maps, but a map still needs testing against your ERP workflow and each partner's published guide. Review exceptions after resolution to see whether a map, validation step, operating procedure or training exercise should change. The aim is a repeatable decision, not simply a cleared queue.
Where an experienced partner helps
Complex exceptions often cross ownership lines: the EDI translator shows one result, Infor shows another and operations needs an answer before shipping. Focused E-Commerce brings 20+ years of EDI expertise and has delivered 500+ EDI implementations. Its Infor ERP integration, IBM Sterling implementation, managed services and EDI training work can help teams trace those handoffs and establish a recovery procedure that fits their environment.
That experience matters most during a migration or rollout. Before changing a map or replacing an integration component, document what counts as successful order posting, successful shipment transmission and confirmed partner processing. Then test failure recovery alongside the normal transaction path. A reliable response to exceptions is part of the integration design, not a task to postpone until the first rejected shipment.
Frequently Asked Questions
How do I troubleshoot a failed 850 order in Infor CloudSuite?
Trace the 850 from receipt through translation and ERP posting. Check whether an order already exists before retrying. Correct the responsible partner data, map or ERP issue, then verify that the intended order posted once.
What should I check before resending an 856 ASN?
Confirm what physically shipped, what Infor recorded and whether the partner received the first 856. Check the partner's published implementation guide for its correction procedure, then reconcile the new transmission with the shipment and any required labels.
Does an accepted 997 mean my CloudSuite order was accepted?
No. A 997 reports whether a document passed the receiver's syntax check. It can report acceptance or rejection, but it does not confirm that the order or its business content was accepted or posted.
How can we prevent duplicate orders during EDI retries?
Pause automatic reprocessing while you compare the original EDI transaction with the ERP order and transmission history. Retry only after you know whether the first attempt posted, and verify the resulting order count and status.
Plan a safer recovery process
If failed orders or ASNs are exposing gaps between your EDI system and Infor, talk with Focused E-Commerce about tracing the workflow and testing a controlled recovery process for your project.
Contact Us



