An EDIFACT ORDERS message read again order line by order line

Goal Read an EDIFACT order segment by segment, then line by line, with no EDI tool.

The buyer sends an ORDERS message on a single line. Segments end with an apostrophe. An apostrophe in a label is written ?'.

fourteen segments, in order;
« Bâche d'hiver » whole;
two order lines, each with its order and its EAN.

lumnik Open
Purchasing
EDI
Connector
Entity

ORDERS_PO-7001.edi

UNA:+.? 'UNB+UNOC:3+3012345000004:14+3098765000002:14+261020:0930+42'UNH+1+ORDERS:D:96A:UN'BGM+220+PO-7001+9'DTM+137:20261020:102'NAD+BY+3012345000004::9'LIN+1++3012345000110:EN'IMD+F++:::Bâche d?'hiver 10x5'QTY+21:12'LIN+2++3012345000127:EN'QTY+21:6'UNS+S'UNT+10+1'UNZ+1+42'

manifests/10-orders.yaml

apiVersion: connectors.lumnik.io/v1kind: Connectormetadata:  name: scenario-edifact-b  connector_type: csv-file  scopes: [purchasing-b]spec:  transport:    kind: local    path: /tmp/lumnik-scenario/edifact-orders/b/*.edi   # one ORDERS message per file  parser:    lines: true                    # the message is one line  after_process: none  mapping:    row:      - split-row: { by: line, sep: "'", escape: "?", position: seg_no }   # one row per segment; ?' is an apostrophe    cell:      - regex-extract:             # the tag, then the segment's elements          column: line          required: true          pattern: "^([A-Z]{3})\\+?(.*)$"          groups: { 1: tag, 2: elements }      - regex-extract: { column: elements, pattern: "^\\d+\\+([^+]+)\\+", groups: { 1: order_no } }   # BGM: the order number      - regex-extract: { column: elements, pattern: "^\\d+\\+\\+(\\d+):EN$", groups: { 1: ean } }    # LIN: the article's EAN      - regex-extract: { column: elements, pattern: "^21:(\\d+)$", groups: { 1: quantity } }        # QTY 21: the ordered quantity      - fill-down: { columns: [order_no], reset-when: { column: tag, in: [UNH] } }      # the order, on every segment of its message      - fill-down: { columns: [ean], reset-when: { column: tag, in: [LIN, UNT] } }      # the EAN, on the segments of its line

$ lm apply -f 10-orders.yaml
Applied connector "scenario-edifact-b" — 1 endpoint

$ lm connector run scenario-edifact-b
run scheduled: 9c9e245e-89f9-49ca-8b3c-54360263bfa4

$ lm run get 9c9e245e-89f9-49ca-8b3c-54360263bfa4
ID        CONNECTOR           ENDPOINT  STATUS     IN  OUT  SKIPPED  DEAD-LETTERS  STARTED           ENDED
9c9e245e  scenario-edifact-b  default   Completed  1   1    0        0             2026-11-03 16:10  2026-11-03 16:10

manifests/20-segment.yaml

kind: Entityname: edifact_segment_blabel: Segment EDIFACTdescription: "One segment of an ORDERS message, in message order: its tag, its elements, and the order and article it belongs to."match: [seg_no]scopes: [purchasing-b]columns:  seg_no: { label: "N°" }  tag: { label: "Segment" }  elements: { label: "Éléments" }  order_no: { label: "Commande" }  ean: { label: "EAN" }  quantity: { label: "Quantité" }sources:  - table: t_scenario_edifact_b    map: { seg_no: seg_no, tag: tag, elements: elements, order_no: order_no, ean: ean, quantity: quantity }

$ lm entity apply -f 20-segment.yaml
Applied entity "edifact_segment_b" → connector."v_edifact_segment_b"

$ lm entity get edifact_segment_b
SEG_NO  TAG  ELEMENTS                                                 ORDER_NO  EAN            QUANTITY  _CONFLICTS
1       UNA  :+.                                                                                         {}
2       UNB  UNOC:3+3012345000004:14+3098765000002:14+261020:0930+42                                     {}
3       UNH  1+ORDERS:D:96A:UN                                                                           {}
4       BGM  220+PO-7001+9                                            PO-7001                            {}
5       DTM  137:20261020:102                                         PO-7001                            {}
6       NAD  BY+3012345000004::9                                      PO-7001                            {}
7       LIN  1++3012345000110:EN                                      PO-7001   3012345000110            {}
8       IMD  F++:::Bâche d'hiver 10x5                                 PO-7001   3012345000110            {}
9       QTY  21:12                                                    PO-7001   3012345000110  12        {}
10      LIN  2++3012345000127:EN                                      PO-7001   3012345000127            {}
11      QTY  21:6                                                     PO-7001   3012345000127  6         {}
12      UNS  S                                                        PO-7001   3012345000127            {}
13      UNT  10+1                                                     PO-7001                            {}
14      UNZ  1+42                                                     PO-7001                            {}

$ lm entity get edifact_segment_b --filter tag=QTY
SEG_NO  TAG  ELEMENTS  ORDER_NO  EAN            QUANTITY  _CONFLICTS
9       QTY  21:12     PO-7001   3012345000110  12        {}
11      QTY  21:6      PO-7001   3012345000127  6         {}

Limits

The order lines are a filtered reading of the segments (--filter tag=QTY): nothing filters after the cell tier.
The UNA segment, which declares the separators, goes through the same escape: it reads ":+.".
One message per file; fictitious GLN and EAN numbers.

Purchasing · EDIFACT

Orders arrive as EDIFACT.

One message on a single line.

ORDERS, one message, two lines

The problem

Everything fits on one line.

An apostrophe ends a segment.
The order is up front, the article further on.

What is not changed

The message stays as it is.

No EDI translator.
No conversion first.

The trap

An apostrophe in a label.

« Bâche d'hiver » is written Bâche d?'hiver.
Misread, it cuts the segment in two.

What had to be written

split-row: { sep: "'", escape: "?" }

One line.

One segment per row, in order.
?' stays an apostrophe.
A 43-line scenario, two manifests.

The result

PO-7001: 12 and 6.

Each quantity carries its order.
And its article's EAN.

The limit

One message per file.

The lines are a filtered read of the segments.

Try it

The scenario replays locally.

Every step is published with its output.

This scenario runs on lumnik Open, free and open source.

Try lumnik Open →