Systems & integrationsSAP integrationOracle Fusion Cloud integrationMicrosoft Dynamics 365 integrationOracle NetSuite integrationSalesforce integrationMicrosoft Azure integrationAS2 integrationConnect Maltexi workflows with the cloud integration layer your organization already operates in Microsoft Azure.
SAME DATA. FURTHER GOOD.Middleware can move messages between applications, but each participant still needs a clear responsibility. Define where files arrive, where documents are interpreted, where business rules run and which team investigates a failed handoff.
Illustrative integration design, adapted to the applications and interfaces available in your environment.
A business event or partner file enters the flow.
Pass the agreed payload and correlation reference.
Interpret, exchange or relate the business information.
Deliver the result and handle its response.
ILLUSTRATIVE WORKFLOW · THE IMPLEMENTATION FOLLOWS YOUR OPERATING REQUIREMENTS
An existing Azure integration workflow receives a partner file. The agreed connection hands document processing to EDI Parser X and routes the resulting business data to its destination. In a pharmaceutical flow, the integration can instead connect an event source with Connect RX. Keep correlation references consistent across the systems involved.
| Business context | Mapping to agree | Why it matters |
|---|---|---|
| Correlation reference | Workflow run → business exchange | Follow a handoff across application boundaries. |
| Payload contract | Incoming file → agreed business data | Separate transport handling from interpretation. |
| Failure ownership | Technical error → responsible team | Avoid an issue moving indefinitely between queues. |
Azure Logic Apps supports enterprise integration workflows and trading-partner concepts. Available connectors and configuration depend on the Azure setup. Maltexi integration work defines the boundary with that environment; it does not imply that Azure is the hosting platform for every Maltexi product.
Use the product that matches the work crossing the boundary. A single integration may combine these tasks, but the data model and acceptance criteria remain specific to each.
Read the structure of partner EDI documents and define the data handoff.
Connect file sources and destinations with their delivery requirements.
Relate serialized pharmaceutical records to operational events and partner information.
Agree on the source of truth for each record, the identifier used to correlate exchanges and the owner of errors. Test a successful transaction, an unknown reference and a repeated request. Record which responses confirm technical delivery and which confirm the intended business result.
This page describes an integration service and use case. The selected interfaces, configuration and implementation scope are agreed for your environment; it does not claim a certified partnership or an out-of-the-box connector.
Yes. Connect RX is the focused product for serialized pharmaceutical records. The integration defines which ERP or partner references must be related to those records, alongside the EPCIS and operational requirements.
Map the data flow between applications and trading partners, then choose the product and integration scope that support it.
Explore systems & integrationsMap trading-partner documents to the information your business system needs, with explicit rules for identifiers, units and required values.
Explore edi mappingPlan a software implementation around the business outcome, the data involved and the people who will run the workflow.
Explore implementationPlan the path between your operational systems, serialized product records and the organizations you exchange data with.
Explore integrationsYour systems. Your partners. The task you need to complete.
Discuss your workflow
