Any format, any transaction
X12, EDIFACT, and HIPAA using XML, JSON and file formats. Every transaction set your partners use, built to their documentation. Uses AI to Auto-Map the partner's specifications to build a map in minutes.
Framework Interchange
Connect your external supply chain to Microsoft Dynamics 365.
Framework Interchange is Framework Systems' trading-partner integration product for Microsoft Dynamics 365 Finance & Supply Chain Management. It sends, receives, translates, maps, validates and processes electronic business transactions between Dynamics 365 and your customers, suppliers, carriers, 3PLs, banks and marketplaces, and it supports onboarding those partners.
Trading-partner integration, not just data movement
The integration processing itself, translation, mapping, validation and transaction processing, is a core part of the product, not simply the movement of data.
More than EDI
EDI is a major capability of Framework Interchange, but the product is not limited to traditional EDI. It supports trading-partner exchanges involving EDI, APIs and other supported methods of electronic business exchange.
Inside Microsoft Dynamics 365
The business context already lives inside Microsoft Dynamics 365, and the integration should too. Framework Interchange performs trading-partner integration in the environment where customer, supplier, inventory, fulfillment, production and other ERP information already exists, rather than on a separate hosted platform.
Six things Framework Interchange does
Generated inside F&O
Processes using X++ with the Data Management Framework. EDI Envelopes, partner-specific maps and any business logic you want applied all run in your Dynamics 365 instance. Works with all your customizations.
Validated before it leaves
X12 and EDIFACT compliance checks, 997 and 999 acknowledgements handled automatically, and a test workbench where you paste raw EDI and watch it parse, never touching production data.
Sent directly to your partner
The built-in transport sends from your environment straight to the partner's, over SFTP, FTPS, AS2 or API, and writes a backup copy of every transaction to your Azure storage.
EDI Map Actions built-in
Over 100 pre-built actions to transform any data from any entity or custom data, so most maps need no custom code.
Yours to extend
X++ extension points at Map, Load, Parse, Stage and Process. One error center brings file, validation, Data Management and mapping issues into a single screen.
Nothing between you and your trading partner
Generated, validated and sent from your environment. Your Azure holds the inbound landing folder and a backup of every transaction.
What changes when EDI lives inside your ERP
No external data store
The transaction and its EDI live in one database: yours. No vendor copy of your orders, prices or customers, no vendor portal, nothing to reconcile, and nothing for someone else's model to learn from.
Controlled by you
You decide who maps, who fixes and who approves. Run it in-house, or have your partner or Framework Systems run it for you. The software works the same either way.
Your production data stays in Dynamics
Built, validated and sent from your environment straight to your partner's. No vendor copy, no third party in the path. Standard Azure security, role-based access and audit apply, because it is your Azure.
No lock-in
Maps, connections and history are yours, in your tenant. Change partners, change providers, or change nothing, on your schedule.
What Framework Interchange supports
Confirm the specific standards, documents, interfaces and connectivity required for your trading partners with Framework Systems.
| EDI standards and document structures | Supported EDI standards and document structures define the trading-partner transaction documents being exchanged, including X12 and EDIFACT transaction sets built to each partner's implementation guide. |
|---|---|
| APIs and interfaces | APIs and interfaces are a distinct category from EDI standards and document structures. Framework Interchange interfaces, processes and records API transactions inside Dynamics 365. |
| Electronic data structures | Data structures describe how exchanged information is represented: X12, EDIFACT, XML, JSON and flat files. |
| Connectivity | Connectivity carries the transactions and is selected by the customer: SFTP, FTPS, AS2 and API, direct to the partner. Framework Interchange does not require a VAN; a VAN is used only when a trading partner requires one. |
| Your configurations | Trading-partner configurations, mappings and your accumulated integration work remain within your Microsoft Dynamics 365 environment. Key proprietary Framework Systems source code is encrypted to protect intellectual property and only show extensions; Actions and transaction portions of the code remain available for full view. |
| Included Framework Advisor capabilities | Framework Interchange includes Interchange-specific Framework Advisor capabilities: mapping assistance, interpretation of trading-partner specifications, validation assistance, exception analysis and troubleshooting, where currently supported. It does not include every Framework Advisor capability. |
See Auto-Map build a partner map from your own specification
Bring a trading partner's implementation guide or an example file. We will show you how long the first map takes.