AWS B2B Data Interchange now supports splitting of inbound X12 EDI documents that contain multiple transactions into individually processed single-transaction documents. Splitting increases the maximum supported file size for multi-transaction EDI documents from 150MB to 5GB and enables independent processing of each transaction, even when trading partners send them batched in a single EDI file.
AWS B2B Data Interchange automates validation, transformation and generation of Electronic Data Interchange (EDI) documents such as ANSI X12 documents to and from JSON and XML data formats. With this launch, you can split incoming multi-transaction X12 documents up to 5GB in size. Each resulting single-transaction document is independently validated and processed, emitting its own set of logs and Amazon EventBridge events, which enables individual post-processing and downstream business-system ingestions. For example, you can use the “Transformation Completed” events to trigger AWS Glue ETL jobs to automatically ingest valid transactions into your purpose-built data lake, while using the “Transformation Failed” events to notify your trading partner of issues with individual transactions of their EDI document.
Support for splitting inbound X12 EDI documents is available in all AWS Regions where the AWS B2B Data Interchange service is available. To get started with building event-driven EDI workloads on AWS B2B Data Interchange, take the self-paced workshop or refer to AWS B2B Data Interchange user guide.
Categories: marketing:marchitecture/application-services,general:products/aws-b2b-data-interchange
Source: Amazon Web Services
Latest Posts
- (Updated) Scoped SharePoint search in Teams (SharePoint app, also called Viva Connections) [MC1332816]
![(Updated) Scoped SharePoint search in Teams (SharePoint app, also called Viva Connections) [MC1332816] 2 snails 2983235 1280](data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==)
- (Updated) Microsoft Teams: Governance for built-in agents in the Teams admin center [MC1387573]
![(Updated) Microsoft Teams: Governance for built-in agents in the Teams admin center [MC1387573] 3 pexels pixabay 208560](data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==)
- Microsoft Viva: New Copilot usage and cost insights [MC1400825]
![Microsoft Viva: New Copilot usage and cost insights [MC1400825] 4 water 6579313 1920](data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==)
- Microsoft Viva: New Copilot usage and cost insights [MC1400825]
![Microsoft Viva: New Copilot usage and cost insights [MC1400825] 5 pxclimateaction 7073104 1920](data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==)

![(Updated) Scoped SharePoint search in Teams (SharePoint app, also called Viva Connections) [MC1332816] 2 snails 2983235 1280](https://mwpro.co.uk/wp-content/uploads/2025/06/snails-2983235_1280-150x150.webp)
![(Updated) Microsoft Teams: Governance for built-in agents in the Teams admin center [MC1387573] 3 pexels pixabay 208560](https://mwpro.co.uk/wp-content/uploads/2024/08/pexels-pixabay-208560-150x150.webp)
![Microsoft Viva: New Copilot usage and cost insights [MC1400825] 4 water 6579313 1920](https://mwpro.co.uk/wp-content/uploads/2025/06/water-6579313_1920-150x150.webp)
![Microsoft Viva: New Copilot usage and cost insights [MC1400825] 5 pxclimateaction 7073104 1920](https://mwpro.co.uk/wp-content/uploads/2025/06/pxclimateaction-7073104_1920-150x150.webp)
