How to Handle Inbound EDI 830 Forecasts in SAP

The Problem: Your customer sends a single 830 forecast containing multiple materials — but in SAP, your scheduling agreements (SAs) only support one material per agreement. What do you do?

This is a common issue when implementing inbound EDI 830s in SAP. Many customers send forecast and JIT data for multiple materials in a single EDI transmission. But SAP requires you to split that data — one DELINS IDoc per material, and often even more than that.

The Solution: Split and Map the 830

When processing an 830 inbound into SAP, you'll need to:

• Split the EDI message by material so each one maps to its own IDoc
• Further split each material into firm and forecast data if both are present
• Ensure each IDoc lines up with a valid scheduling agreement (SA) for that material

This can result in multiple IDocs per material, per 830, such as:

• One DELINS for firm data (e.g., committed shipments)
• One DELINS for forecast data (e.g., planning signals)

Here is a breakdown of the data:

Understanding the Segments on the 830

Yellow (LIN Segment): This represents each material on the 830.

Blue (FST Segment with FST/02 = C): This represents the firm data, denoted by the FST/02 = C (firm). The quantity and date are also included in this segment.

Green (FST Segment with FST/02 = D): These are the forecast segments, as denoted by FST/02 = D (Forecast). The quantity and date are also present in this segment.

How the Segments Map to the DELINS IDoc

Here’s how EDI segments map to SAP IDoc segments:

• LIN creates the E2EDP10 (material/item line)
• FST creates the E2EDP16 (forecast schedule line with date + quantity)

Key data points to watch:

• FST/02 = Requirement type
    • C = Firm
    • D = Forecast
    • A = Immediate (often treated as firm)
    • H = First-time reported firm

• FST/03 = Timing qualifier
    • D = Discrete (daily bucket, common with firm requirements)
    • W = Weekly bucket (often used for forecast data)

Don’t Forget Partner-Specific Variations

Always validate against your customer’s EDI spec. Some will use unique combinations of qualifiers or expect logic that doesn’t match standard SAP processing. In those cases, you’ll need to build a robust and flexible mapping

Watch for CUMs and EDI 862s

Some partners also send EDI 862 messages (for daily JIT deliveries), and may use cumulative quantities (CUMs) to reconcile delivered vs. planned quantities. Handling these adds another layer of complexity — and one we’ll cover in a future post.

In Summary:

When your customer sends one EDI 830 with many materials, but SAP SAs are material-specific, you’ll need to split that message and generate multiple IDocs. It’s not just about data conversion — it’s about understanding how each segment maps and managing firm vs. forecast demand in SAP appropriately.

If you're dealing with 830/862 complexity, we're always happy to talk strategy or tools to simplify your inbound processing landscape.