Articles in this section

EDI generator helper FAQs – generating import files

Anitha Abraham
Updated

What is the EDI generator helper and when should I use it?

The EDI generator helper is a validation and preview tool in B2B Manager that allows you to generate and review outbound EDI files before they are sent to a trading partner.

You should use it when:

  • Building a new outbound EDI transaction (850, 856, 810, or the like.)
  • Troubleshooting missing segments or loops
  • Testing changes to mappings or FDR configurationsIt helps you confirm that your JSON source data
  • Investigating trading partner rejections

It helps you confirm that your JSON source data and FDR structure will produce a properly formatted EDI file.
Where can I access the generator helper in B2B Manager?
You can launch it directly from the Celigo EDI import in your integrator.io flow.
How does the EDI generator helper highlight errors and where?
Errors are flagged in red with counts and exact error locations, helping you quickly locate and fix non-conformities with the parsing rules.
What should I check when an EDI file has errors?

You could check the following items:

  1. Ensure the file conforms to the expected EDI standard (X12/EDIFACT).
  2. Compare your data and the parser rules in the helper.
  3. Make edits in the FDRs or source data and preview again.
Can I test changes before running my flow?
Yes — the EDI generator helper lets you preview and validate how your changes affect output before running the flow.
What’s the recommended workflow for using the EDI generator helper?
  1. After entering initial details in the import form, launch and preview the data in the EDI generator helper. If there are any errors, check and troubleshoot errors.
  2. After entering all configurations, preview the import data & confirm that the generated output has no errors. If there are errors, launch the EDI generator helper to check and troubleshoot errors.
  3. After running the flow, troubleshoot errors that occur by launching and using the EDI generator helper.
What’s the difference between EDI generator helper validation errors and trading partner rejections?

EDI generator helper validation errors:

  • Occur inside Celigo before sending the file.
  • Indicate structural issues (missing required segments, element length violations, incorrect loop placement).
  • Are based on the configured FDR.

Trading partner rejections:

  • Occur after the file is sent.
  • May be due to partner-specific implementation rules not enforced in your FDR.
  • Can include code value restrictions, business rule validations, or partner-specific requirements.

Important distinction: The EDI generator helper validates EDI structure — not always partner-specific business rules.
How does the EDI generator helper use the FDR (File Definition Rules)?

The FDR defines:

  • Segment order
  • Loop structure
  • Required vs optional segments
  • Maximum repetitions
  • Element formatting rules
  • Data type constraints

Your JSON data must align with this hierarchy. If the JSON structure doesn’t match the FDR’s loop structure, the generated EDI will be incomplete or incorrect.

Think of the FDR as the “blueprint” and your JSON as the “input data.” The EDI generator helper builds the file exactly according to that blueprint.
Does the EDI generator helper validate against trading partner implementation guides or only EDI structure?
  • The configured FDR
  • EDI standard structural rules (X12/EDIFACT)

It does not automatically enforce every partner-specific rule unless those rules are explicitly configured in your FDR.

For example:

  • It may validate that BEG is required in an 850.
  • It may not automatically enforce a partner-specific qualifier restriction unless configured.

Best practice:

Always cross-check outbound EDI against the trading partner’s implementation guide — not just the EDI generator helper output.
Why is my EDI file not generating even though the mapping completed successfully?

The issue perhaps could perhaps be because of the following reasons:

  • Missing required segments (for example, BEG for 850, BIG for 810)
  • Required elements left blank
  • Loop trigger segments not generated
  • Envelope configuration issues (ISA/GS/ST)
  • Conditional rules not met

The EDi generator helper shows which required segments or elements were not created. Always verify required flags in the FDR.
Why are some segments missing from my generated EDI file?

Few common causes for this issue are:

  • The segment is conditionally generated and its condition was not met.
  • Required data field was empty in the source record.
  • Loop trigger segment did not generate, preventing the loop from forming.
  • Incorrect mapping path.

Check the following items:

  • Source/export preview data
  • Loop trigger segment presence
  • Conditional generation rules
  • Min/max use settings
Why are loops not repeating correctly in the generated file?

You could check:

  • Source array structure
  • Proper mapping into repeating group nodes
  • Correct loop definition in the FDR
  • Max use constraints

If multiple records exist but only one loop generates:

  • Confirm mapping is at the correct loop level.
  • Ensure the source data is structured as an array.
  • Verify no max-use restriction is limiting output.

If a PO1 loop should repeat, your source must provide multiple line objects — not flattened fields.
Why am I getting “Missing required element” errors in the EDI generator helper?

The issue could be because:

  • A required element in the FDR does not have mapped data.
  • A required element is conditionally required based on a qualifier.
  • The value provided does not meet length or format constraints.

You could check:

  • Required flags in FDR
  • Conditional rules
  • Data type (numeric, alphanumeric)
  • Min/max length
Why is the segment order incorrect in the generated EDI?

If segments appear out of order:

  • Review loop hierarchy in FDR.
  • Ensure segments are mapped under the correct parent loop.
  • Avoid creating parallel loop structures unintentionally.

The EDI generator helper strictly follows the FDR tree structure.
Why are envelope segments (ISA/GS/ST) incorrect?

The issue could be because:

  • Control numbers not incrementing correctly
  • Sender/Receiver IDs misconfigured
  • Version mismatch (4010 vs 5010)
  • Incorrect date/time formats

You could check:

  • Trading partner configuration
  • Control number settings
  • ISA/GS version alignment
  • Qualifier codes

Envelope errors often cause trading partner rejection even when transaction data is correct.
Why does my generated EDI fail trading partner validation but passes EDI generator helper?

The issue could be because:

  • Partner-specific implementation rules not reflected in FDR
  • Code value restrictions
  • Custom segment requirements
  • Different interpretation of optional vs required fields

Always validate against:

  • Trading partner implementation guide
  • Required qualifiers
  • Segment usage rules

The EDI generator helper validates structure — not partner-specific compliance unless configured.
Why are numeric values formatted incorrectly (decimals, padding, or the like)?

The issue could be because of :

  • Decimal precision mismatch
  • Missing implied decimals
  • Incorrect numeric type mapping
  • Leading zero trimming

You could check the following items:

  • Element type in FDR (N0, N2, R, etc.)
  • Decimal handling in mapping
  • Transformation logic applied before generation

Some numeric elements require implied decimals (for example, 1000 = 10.00).
Why is my EDI file generating extra segments?

Extra segments could be because:

  • Default values are applied unintentionally
  • Mapping exists at multiple levels
  • Loop repetition not properly constrained
  • Conditional logic always evaluates as true

You could check the following items:

  • Conditional rules
  • Default value fields
  • Loop structure placement
What are best practices when using the EDI generator helper?

Given below are some steps you could follow for successful EDI flows.

  • Start validation with a single transaction sample.
  • Validate required segments first.
  • Confirm loop repetition with 2–3 line items.
  • Test envelope configuration separately.
  • Cross-check against trading partner guide.

Use structured source JSON that mirrors EDI hierarchy.
What are a few advanced generator troubleshooting scenarios?

  • “My PO1 lines are generating but CTT count is wrong”

    → Ensure CTT01 is mapped to the total number of line items.

  • “My REF segments repeat incorrectly”

    → Confirm REF is inside the correct loop and not defined at header level.

  • “Dates are rejected by partner”

    → Check format (CCYYMMDD vs YYMMDD).