Large EDI files are often the result of transaction sets containing many repeated loops or segments. For example, a company may receive an 837 Health Care Claim file containing many insurance claims, or a retailer may receive an 846 Inventory Inquiry/Advice file containing millions of SKUs. To avoid overloading downstream systems, you can enable fragments on the repeated EDI segment.
Once enabled, Stedi splits the transaction payload into chunks based on that segment.For example, you might enable fragments on the LIN loop (list of inventory items) in an 846 Inventory Inquiry/Advice. For each processed 846, Stedi will emit fragment.processed.v2 events that each contain a chunk of LIN loop iterations.