Four EDI files for a single order line

Goal Merge the four flows to know whether each line is ordered, confirmed or delivered, and be alerted when a confirmed date passes without delivery.

A manufacturer and its logistics partner exchange four flat files around one order line: the order, the acknowledgement, the confirmed date, the delivery note. Sales administration asks, line by line:

never acknowledged?
confirmed but not delivered?
delivered in another quantity?

lumnik Open
Logistics
EDI
Sales admin
Connector
Entity
Workflow

ZINT_CC_42100001.txt

SAPPRD           NPEC      
SAPPRD           NPEC      EC100001  M. DURAND                               12 RUE DES LILAS                                  69003   FR 42100001    KIT0012     Couverture à barres automatique 8x4 coul30.000    M2  6880001   
SAPPRD           NPEC      EC100001  M. DURAND                               12 RUE DES LILAS                                  69003   FR 42100001    KIT0031     Kit anti-soulèvement sur tube pour couve1.000     U   6880002   
SAPPRD           NPEC      EC100001  M. DURAND                               12 RUE DES LILAS                                  69003   FR 42100001    LIV0000     Livraison couverture à barres France mét1.000     U   6880003   
SAPPRD           NPEC      EC100245  MME FAURE                               LIEU-DIT LES ÉPINETTES - 4 CHEMIN DU MOULIN       84120   FR 42100002    BAC0450     Bâche hiver opaque 10x5                 50.000    M2  6880011   
SAPPRD           NPEC      EC100245  MME FAURE                               LIEU-DIT LES ÉPINETTES - 4 CHEMIN DU MOULIN       84120   FR 42100002    ENR0002     Enrouleur télescopique                  2.000     U   6880012   
SAPPRD           NPEC      EC100245  MME FAURE                               LIEU-DIT LES ÉPINETTES - 4 CHEMIN DU MOULIN       84120   FR 42100002    LIV0000     Livraison bâche France métropole        1.000     U   6880013

ZINT_CA_0000060001.txt

450017000142100001

ZINT_C1_4500170001.txt

SAPPRD           NPEC      
4500170001  6880001          KIT0012           20261020
4500170001  6880002          KIT0031           20261020
4500170001  6880003          LIV0000           20261021

ZINT_BL_63170001.txt

SAPPRD           NPHC      
63170001        4500170001KIT0012           30.000    6880001
63170001        4500170001KIT0031           1.000     6880002
63170001        4500170001LIV0000           1.000     6880003

manifests/10-cc.yaml

apiVersion: connectors.lumnik.io/v1kind: Connectormetadata:  name: scenario-cycle-cc-b  connector_type: csv-file  scopes: [logistics-b]spec:  transport:    kind: local    path: /tmp/lumnik-scenario/edi-order-cycle/b/ZINT_CC_*.txt   # order lines, ERP → partner  parser:    lines: true  after_process: none  mapping:    dataset:      - filter-where: { column: line, regex: ".{27}EC.*" }   # the header carries no customer code      - enrich-context: { stage: ORDERED }    cell:      - regex-extract:          column: line          required: true          pattern: "^(.{17})(.{10})(.{10})(.{40})(.{50})(.{8})(.{3})(.{12})(.{12})(.{40})(.{10})(.{4})(.*)$"          groups: { 4: customer_name, 8: order_no, 9: article, 10: label, 11: ordered_qty, 12: unit, 13: line_id }      - clean: { columns: [customer_name, order_no, article, label, ordered_qty, unit, line_id], strip: true }      - parse-number: { column: ordered_qty, decimal-separator: "." }

manifests/20-ca.yaml

apiVersion: connectors.lumnik.io/v1kind: Connectormetadata:  name: scenario-cycle-ca-b  connector_type: csv-file  scopes: [logistics-b]spec:  transport:    kind: local    path: /tmp/lumnik-scenario/edi-order-cycle/b/ZINT_CA_*.txt   # acknowledgements, partner → ERP  parser:    lines: true  after_process: none  mapping:    cell:      - regex-extract:                 # the purchase order and the order it acknowledges, glued          column: line          required: true          pattern: "^(\\d{10})(\\d{8})$"          groups: { 1: po, 2: order_no }

manifests/30-c1.yaml

apiVersion: connectors.lumnik.io/v1kind: Connectormetadata:  name: scenario-cycle-c1-b  connector_type: csv-file  scopes: [logistics-b]spec:  transport:    kind: local    path: /tmp/lumnik-scenario/edi-order-cycle/b/ZINT_C1_*.txt   # confirmed dates, partner → ERP  parser:    lines: true  after_process: none  mapping:    dataset:      - filter-where: { column: line, regex: "\\d.*" }        # data lines start with the purchase order      - enrich-context: { stage: CONFIRMED }    cell:      - regex-extract:          column: line          required: true          pattern: "^(.{12})(.{17})(.{18})(.{8})$"          groups: { 1: po, 2: line_id, 3: article, 4: confirmed_date }      - clean: { columns: [po, line_id, article], strip: true }      - parse-date: { column: confirmed_date, formats: ["yyyyMMdd"] }

manifests/40-bl.yaml

apiVersion: connectors.lumnik.io/v1kind: Connectormetadata:  name: scenario-cycle-bl-b  connector_type: csv-file  scopes: [logistics-b]spec:  transport:    kind: local    path: /tmp/lumnik-scenario/edi-order-cycle/b/ZINT_BL_*.txt   # delivery notes, partner → ERP  parser:    lines: true  after_process: none  mapping:    dataset:      - filter-where: { column: line, regex: "\\d.*" }      - enrich-context: { stage: DELIVERED }    cell:      - regex-extract:          column: line          required: true          pattern: "^(.{16})(.{10})(.{18})(.{10})(.*)$"          groups: { 1: bl_no, 2: po, 3: article, 4: delivered_qty, 5: line_id }      - clean: { columns: [bl_no, po, article, delivered_qty, line_id], strip: true }      - parse-number: { column: delivered_qty, decimal-separator: "." }

$ lm apply -f 10-cc.yaml
Applied connector "scenario-cycle-cc-f" — 1 endpoint

$ lm connector run scenario-cycle-cc-f
run scheduled: fc199b0c-eed7-4182-8370-67c5c2f7a2eb

$ lm run get fc199b0c-eed7-4182-8370-67c5c2f7a2eb
ID        CONNECTOR            ENDPOINT  STATUS     IN  OUT  SKIPPED  DEAD-LETTERS  STARTED           ENDED             EVALUATED
fc199b0c  scenario-cycle-cc-f  default   Completed  9   7    2        0             2026-10-28 22:46  2026-10-28 22:46  no

$ lm apply -f 20-ca.yaml
Applied connector "scenario-cycle-ca-f" — 1 endpoint

$ lm connector run scenario-cycle-ca-f
run scheduled: 02c58c7a-e71f-449e-96c6-cbf6a090ae8d

$ lm run get 02c58c7a-e71f-449e-96c6-cbf6a090ae8d
ID        CONNECTOR            ENDPOINT  STATUS     IN  OUT  SKIPPED  DEAD-LETTERS  STARTED           ENDED             EVALUATED
02c58c7a  scenario-cycle-ca-f  default   Completed  2   2    0        0             2026-10-28 22:46  2026-10-28 22:46  no

$ lm apply -f 30-c1.yaml
Applied connector "scenario-cycle-c1-f" — 1 endpoint

$ lm connector run scenario-cycle-c1-f
run scheduled: 43a7be9a-cf6d-430b-ba5d-a59356180a5e

$ lm run get 43a7be9a-cf6d-430b-ba5d-a59356180a5e
ID        CONNECTOR            ENDPOINT  STATUS     IN  OUT  SKIPPED  DEAD-LETTERS  STARTED           ENDED             EVALUATED
43a7be9a  scenario-cycle-c1-f  default   Completed  8   6    2        0             2026-10-28 22:46  2026-10-28 22:46  no

$ lm apply -f 40-bl.yaml
Applied connector "scenario-cycle-bl-f" — 1 endpoint

$ lm connector run scenario-cycle-bl-f
run scheduled: e2be5ad3-24a7-44a6-a154-0278e60f244c

$ lm run get e2be5ad3-24a7-44a6-a154-0278e60f244c
ID        CONNECTOR            ENDPOINT  STATUS     IN  OUT  SKIPPED  DEAD-LETTERS  STARTED           ENDED             EVALUATED
e2be5ad3  scenario-cycle-bl-f  default   Completed  7   5    2        0             2026-10-28 22:46  2026-10-28 22:46  no

manifests/50-order-line-cycle.yaml

kind: Entityname: order_line_cycle_blabel: Cycle d'une ligne de commandedescription: "One order line across the four flows: ordered, acknowledged, confirmed, delivered — the stage is the most advanced flow that names the line."match: [line_id]scopes: [logistics-b]columns:  line_id: { label: "Ligne" }  order_no: { label: "Commande" }  customer_name: { label: "Client" }  article: { label: "Article", prefer: t_scenario_cycle_cc_b }  ordered_qty: { label: "Commandé" }  confirmed_date: { label: "Livraison confirmée" }  delivered_qty: { label: "Livré" }  bl_no: { label: "Bon de livraison" }  stage: { label: "Étape", conflicts: false }   # the flows progress, they do not disagreesources:                                 # the order is the priority: the furthest flow names the stage  - table: t_scenario_cycle_bl_b    map: { line_id: line_id, article: article, delivered_qty: delivered_qty, bl_no: bl_no, stage: stage }  - table: t_scenario_cycle_c1_b    map: { line_id: line_id, article: article, confirmed_date: confirmed_date, stage: stage }  - table: t_scenario_cycle_cc_b    map: { line_id: line_id, order_no: order_no, customer_name: customer_name, article: article,           ordered_qty: ordered_qty, stage: stage }joins:  - table: t_scenario_cycle_ca_b           # the acknowledgement is per order, not per line    from: order_no    to: order_no    map: { po: acknowledged_po }

$ lm entity apply -f 50-order-line-cycle.yaml
Applied entity "order_line_cycle_f" → connector."v_order_line_cycle_f"

$ lm entity get order_line_cycle_f
LINE_ID  ARTICLE  DELIVERED_QTY  BL_NO     STAGE      CONFIRMED_DATE  ORDER_NO  CUSTOMER_NAME  ORDERED_QTY  ACKNOWLEDGED_PO  _CONFLICTS
6880001  KIT0012  30             63170001  DELIVERED  2026-10-20      42100001  M. DURAND      30           4500170001       {}
6880002  KIT0031  1              63170001  DELIVERED  2026-10-20      42100001  M. DURAND      1            4500170001       {}
6880003  LIV0000  1              63170001  DELIVERED  2026-10-21      42100001  M. DURAND      1            4500170001       {}
6880011  BAC0450  45             63170002  DELIVERED  2026-10-22      42100002  MME FAURE      50           4500170002       {}
6880012  ENR0002                           CONFIRMED  2026-10-22      42100002  MME FAURE      2            4500170002       {}
6880013  LIV0000  1              63170002  DELIVERED  2026-10-23      42100002  MME FAURE      1            4500170002       {}
6880021  ENR0002                           ORDERED                    42100003  M. NGUYEN      1                             {}

manifests/60-line-lifecycle.yaml

apiVersion: apps.lumnik.io/v1kind: Workflowmetadata:  name: order-line-cycle-bspec:  scope: logistics-b  provenance: declared  on:    table: connector.v_order_line_cycle_b   # the fused view: the stage only exists there    column: stage    key: line_id                            # one document per order line  states:    - { code: ORDERED, label: "Commandée", initial: true }    - { code: CONFIRMED, label: "Date confirmée" }    - { code: DELIVERED, label: "Livrée", terminal: true }  due:                                      # the deadline is a date the data carries, not a first sighting    column: confirmed_date    states: [CONFIRMED]    zone: Europe/Paris                      # a date-only column: due at the end of that day in Paris    message: "Ligne {doc_key}: livraison confirmée pour le {due}, toujours pas livrée"

$ lm workflow apply -f 60-line-lifecycle.yaml -o json
{
  "name": "order-line-cycle-f",
  "scope": "logistics-f",
  "table": "connector.v_order_line_cycle_f",
  "column": "stage",
  "dataTruth": {
    "undeclared": [],
    "unobserved": [],
    "nullOrBlank": 0,
    "tableMissing": false,
    "keyColumnMissing": false,
    "keyNullOrBlank": 0,
    "checkUnavailable": false,
    "unavailableReason": null,
    "dueProblem": null,
    "invalidOrderValues": null,
    "keysWithSeveralRows": 0,
    "columnsUnverified": []
  }
}

$ lm entity get order_line_cycle_f --filter stage=CONFIRMED
LINE_ID  ARTICLE  DELIVERED_QTY  BL_NO  STAGE      CONFIRMED_DATE  ORDER_NO  CUSTOMER_NAME  ORDERED_QTY  ACKNOWLEDGED_PO  _CONFLICTS
6880012  ENR0002                        CONFIRMED  2026-10-22      42100002  MME FAURE      2            4500170002       {}

$ lm entity get order_line_cycle_f --filter stage=ORDERED
LINE_ID  ARTICLE  DELIVERED_QTY  BL_NO  STAGE    CONFIRMED_DATE  ORDER_NO  CUSTOMER_NAME  ORDERED_QTY  ACKNOWLEDGED_PO  _CONFLICTS
6880021  ENR0002                        ORDERED                  42100003  M. NGUYEN      1                             {}

$ lm inbox --type decision.overdue.order-line-cycle-f
ID     WHEN      PROCESS                      MESSAGE                                                                     ENTITY_KEY
20367  just now  workflow:order-line-cycle-f  Ligne 6880012: livraison confirmée pour le 2026-10-22, toujours pas livrée  6880012

Limits

The date reads at the end of the day, Paris time. A confirmed date moved to another past day raises a new alert. A date already reported, no.
A different delivered quantity shows side by side. No filter compares two columns.
Synthetic files, on the template of a real exchange.

Sales admin · EDI

Where does this order line stand?

Four files, one logistics partner, no overall view.

Order, acknowledgement, confirmed date, delivery note: each in its own format.

Synthetic files, on the template of a real exchange

The problem

Sales admin opens four files for one answer.

Never acknowledged?
Confirmed but not delivered?
Delivered in another quantity?

Nothing is changed

The files stay as they are.

lumnik reads the four flows.
It matches them line by line.
Each line takes its furthest stage.

What had to be written

due:
  column: confirmed_date
  states: [CONFIRMED]

The confirmed date becomes a deadline.

The whole scenario fits in 6 declaration files, 144 lines.

The answers

Each line, its stage.

6880012: confirmed date, not delivered.
6880021: never acknowledged.
6880011: delivered 45 for 50.

The delay

The date has passed. The line is not delivered.

Decision inbox

Ligne 6880012: livraison confirmée pour le 2026-10-22, toujours pas livrée

Real message, replay of 28 October 2026.

The limit

lumnik shows the gap. Sales admin judges it.

45 for 50 reads side by side.
No filter compares two columns.

Try it

The scenario replays end to end.

Four flows, one fusion, one lifecycle, one alert: each step is published with its output.

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

Try lumnik Open →