In this article
Oracle Fusion EDI integration moves established trading partner workflows to a new ERP by retaining useful partner mapping rules and rebuilding the handoff to Oracle Fusion. You should inventory each partner's documents, confirm its current EDI guide, test the new ERP flow and reconcile transactions before changing production routing. An existing map is a starting point, not a finished Fusion integration.
BOLD VAN helps manage that separation through BOLD Integration, which maps EDI data into and out of Oracle ERP and other business systems. The central decision is which rules still describe the trading partner and which rules were written solely for the old ERP. Keeping those decisions separate makes testing more useful and gives your team a clearer cutover plan.
What moves when the ERP changes
An EDI map translates a partner's document into information your business system can use, or turns business-system output into a partner's required document. Legacy maps often contain partner identifiers, code conversions and business decisions accumulated through years of testing. Replacing the ERP does not automatically invalidate those rules, but the old map's output may no longer match the new system's process.
For example, an X12 850 purchase order can still represent the same customer order after your ERP changes. The destination structure, customer matching and handling of exceptions may need redesign. Oracle's B2B messaging documentation describes Oracle messaging configuration, while the integration method you use depends on your Fusion implementation. Check the relevant Oracle documentation and each partner's published EDI implementation guide before settling the design.
How the data flows between a partner and Oracle Fusion
Think of the migration as three connected layers. The external layer is the partner's EDI standard, version, document and connection. The mapping layer interprets the partner's data and applies agreed business rules. The ERP layer delivers the resulting information to the appropriate Oracle Fusion workflow, then handles outbound data on the return path.
| Layer | What to preserve | What to validate |
|---|---|---|
| Trading partner | Identifiers, document scope and agreed connection | Current guide, version and test expectations |
| Mapping | Useful conversions and partner-specific rules | Codes, exceptions and ownership of changes |
| Oracle Fusion handoff | Business intent of each transaction | Supported interface, processing result and error path |
Typical order workflows involve an 850 purchase order, an 855 purchase order acknowledgment, an 856 advance ship notice and an 810 invoice. A 997 functional acknowledgment addresses syntax checking. Which documents you exchange, and how each must be formatted, depend on the partner and the X12 version. Do not infer a retailer's requirements from the transaction number alone. BOLD VAN maps data to and from ERP, WMS, TMS and e-commerce platforms, including Oracle ERP, ShipHero, Oracle TMS, Shopify and others. Where a platform uses an API, the connection can translate EDI to that platform's API and back, with implementation details governed by that platform's documentation.
Cutover warning: A successful 997 does not mean an order was accepted or posted in Oracle Fusion. It tells the sender whether the document passed the receiver's syntax check and can report acceptance or rejection. Check the business result separately, and make sure only one production route sends each outbound document during cutover.
A controlled process for moving legacy maps
- Inventory active flows. Record the partner, document, direction, EDI version, connection, map owner and ERP destination. Include infrequent documents and exception handling, not just daily purchase orders.
- Review the partner rules. Compare existing maps with each partner's published implementation guide. Separate current requirements from old workarounds and confirm ambiguous decisions with the business owner.
- Design the Fusion handoff. Work with your Oracle team to identify the supported integration path for each business process. Define what success, rejection and retry mean without assuming the old ERP's structure carries over.
- Test both directions. Use representative orders, acknowledgments, shipment notices and invoices where applicable. Compare identifiers, quantities, totals and processing results, then exercise a rejected transaction and its correction path.
- Reconcile and cut over. Compare legacy and new outcomes during parallel tests. Assign one production sender per partner and document type, set a rollback decision point and verify the first production transactions against the ERP records.
BOLD VAN's new maps are typically ready to test in about two days. That is a map testing milestone, not an Oracle Fusion project timeline. Partner testing, ERP readiness and approvals still govern the cutover. For a closer look at matching transactions across both paths, see our parallel EDI reconciliation guide.
Common pitfalls and best practices
Keep an auditable decision record for every reused rule. A map can pass a syntax test while routing an order to the wrong business process or applying an obsolete code conversion. Give finance and operations a role in checking business outcomes, rather than leaving signoff entirely to the integration team.
- Check source material. Use the current partner guide and actual document examples. A legacy map may reflect an older version or a rule that has changed.
- Test negative cases. Confirm where failed translation, ERP rejection and corrected documents go. Define who investigates each type of failure.
- Control duplicate sends. Parallel tests can compare results without letting both ERP routes transmit production invoices or shipment notices.
- Plan ongoing maintenance. When a trading partner changes its requirements, BOLD VAN updates the map, and minor changes are typically handled at no cost.
Every document is tracked in the BOLD VAN portal, where customers can search, requeue and report, with notifications when something needs their attention. For teams leaving an on-premise translator, managed cloud mapping also reduces dependence on one employee who knows the old configuration and removes the in-house map maintenance burden.
Choosing the right integration ownership
If your team already maintains partner maps, it may keep that responsibility and focus on connecting the new ERP handoff. If you need managed mapping as well, BOLD Integration covers EDI translation and integration into the ERP, WMS or another system, including connections to a platform's API. Compare approaches against your internal capacity, partner testing workload and the process for handling changed specifications. BOLD VAN offers one predictable per-trading-partner price.
The practical goal is to preserve partner relationships while proving that orders, shipments and invoices reach the right business process in Fusion. Treat map reuse as a tested decision, not an assumption.
Frequently asked questions
Can you reuse legacy EDI maps with Oracle Fusion?
You can often reuse partner rules as a starting point, but you must review the current partner guide and redesign or validate the ERP handoff. Test each map against the Fusion business process before cutover.
Which EDI documents should you test during an Oracle Fusion migration?
Test every document your partners actually exchange. Common X12 examples are the 850 purchase order, 855 purchase order acknowledgment, 856 advance ship notice and 810 invoice. Confirm versions and requirements in each partner's published guide.
Does an accepted 997 mean the order reached Oracle Fusion?
No. A 997 reports whether the document passed the receiver's syntax check and can indicate acceptance or rejection. It does not confirm that the order or its content was accepted or posted in Oracle Fusion.
How do you avoid duplicate EDI documents at cutover?
Use parallel testing to compare results, but designate one production sender for each partner and document type. Reconcile the first live transactions and keep a defined rollback decision point.
If you are planning an Oracle Fusion transition, explore BOLD Integration to discuss partner map review, ERP handoffs and a testable cutover plan with our team.
