Fragments: Split transactions into smaller chunks

Large files are often the result of transaction sets containing many repeated loops or segments. For example, a healthcare provider may send an 837 Health Care Claim containing many individual claims, or a brand may send an 846 Inventory Inquiry/Advice file containing millions of SKUs.

The translation ratio of an EDI file to JSON typically approaches 1:10, so a translated JSON artifact will be multiple times the size of the original EDI file. To avoid overwhelming downstream systems, you can use fragments to split translated inbound transactions from Stedi into smaller, more manageable chunks.

You can also use fragments when generating large outbound EDI files. You send transaction data to Stedi in chunks over time, and Stedi stiches the chunks together to generate a complete EDI file for your trading partner.

​

Configure fragments

You need to configure your Stedi guide to use fragments and then create an inbound or outbound transaction setting using that guide.

​

Stedi guide

You can enable fragments for one repeated EDI segment in each transaction set. To enable fragments within a Stedi guide:

1. Go to the Guides page and edit the guide you want to update.
2. Click the node (segment) in the guide that you want to use to split the file. The node must be a looping data structure, such as an HL loop containing inventory items.
3. Toggle Set as fragment to ON.
4. Publish the changes to your guide.

​

Transaction setting

Once you have enabled fragments on the Stedi guide, create a transaction setting with the guide.

• Inbound transaction settings: You must explicitly toggle Enable fragments to ON. You can use the default batch size (800 segments) or set a custom batch size (up to 50,000 segments).
• Outbound transaction settings: No additional configuration is required.

You can now use fragments to split large inbound transactions or generate large outbound transactions.