Connect Oracle Fusion to EDI instantly

• Fusion environment access and Collaboration Messaging setup rights
• Business unit, inventory organisation and supplier or customer records
• The trading partners you deal with, or plan to
• Item, pack and price data aligned to what partners order in
• How we should reach Fusion, and who owns that access

Only the things we cannot hold for you. What each trading partner requires is already on our side, so there is no specification to go and obtain.

Collaboration Messaging access

Rights to configure collaboration documents, partner setup and delivery methods, plus visibility of the message history when a document has to be traced.

Business unit and organisation structure

Which business units and inventory organisations each partner trades against, since document routing and defaulting follow that structure.

Customer and location records

Each partner mapped to a Fusion customer or supplier, with their delivery points mapped to GLNs so ship-to references resolve without manual matching.

Item and pack data

GTINs at each packaging level, the unit of measure the partner orders in, and the conversion to how the item is held in Fusion.

Which partners you trade with

The partners in scope, now and next. We already hold what each of them requires, so there is no specification for you to obtain.

• Outbound B2B setup is not in one place. Collaboration Messaging needs the service provider and trading partner configured, and B2B Configuration separately needs the host, the trading partner and an agreement. Miss the agreement and the document fails on send rather than queueing, while the partner record itself looks correctly set up.

  XEDI holds the partner relationship, so Fusion emits its collaboration document to one destination instead of carrying an agreement per retailer. Adding a trading partner is something we configure in XEDI, not another set of B2B records for your team to keep in step.

• Messages are not sent or received for documents that have not been explicitly enabled for that trading partner. Nothing errors in the application that raised the event, so the first sign is a retailer asking where an order acknowledgement went.

  XEDI validates the expected document set per partner and surfaces a missing or unacknowledged flow as an exception, so a document that never left is visible rather than silent.

• Each delivery method has a maximum message size covering the payload and any attachments, and Collaboration Messaging will not process a message that exceeds it. Large catalogue or inventory files are the usual casualty.

  XEDI schedules large data flows such as catalogue and stock updates separately from transactional documents, so a bulk file is not competing with orders for the same delivery route.

• Override message definitions configured per trading partner while a service provider is in use, where no override was actually needed. The partner then receives a document shaped differently from every other partner on the same service.

  Partner-specific shaping happens once, in XEDI's mapping, rather than as overrides scattered across Fusion setup. One definition per document type serves every partner, with differences applied at the boundary.

• Partners are generally connected already, so trading starts without waiting for Collaboration Messaging to be finished.
• Partner-specific message rules live with us rather than in Fusion configuration, so a new retailer is neither an ERP change nor a task for your team.
• Documents are validated against the partner's rules before they are sent, so rejections surface while someone can still act on the order.
• One connection covers the partners you trade with now and every one you take on later, each built and verified by us rather than set up per retailer.
• Every message is traceable end to end, which is what finance needs when an invoice is queried weeks after despatch.
• Partners raise problems with us rather than with you. We are notified on your behalf and rectify them, so a rejected document does not become your team's investigation.

Yes. XEDI maps trading partner EDI documents to the collaboration documents Oracle Fusion already produces and consumes, so orders arrive in Fusion order management and acknowledgements, despatch advice and invoices go back out in the format each partner requires.

Fusion exchanges its own collaboration documents, and the EDIFACT, TRADACOMS or X12 translation happens in the messaging layer. Routing partners through XEDI means each dialect, and the validation that goes with it, is handled outside your Fusion configuration.

Not when the translation and partner connection sit with XEDI. Fusion raises its collaboration document and XEDI handles the partner's message standard, identifiers and transport, which keeps the partner-specific detail out of the ERP.

Most of the elapsed time is your own data rather than the integration. We already hold what the partner requires, so where identifiers and item data are ready at the start, connections are normally measured in weeks rather than months.