Error notice

nutrab2b.control.error.v2 · Control

Purpose: Report a processing failure that happens after the ACK (e.g. downstream ERP posting failed).
When to send: Asynchronous failure.
Sender → receiver: Receiver → Sender
Expected responses: none
Equivalent standards: EDIFACT: APERAK
Scenarios using it: -

Fields and mappings

Field	Type	Req	Description	Code list / format
ref_event	string	yes	Event id
code	string	yes	Error code	error_code
message	string	yes	Message
retryable	boolean		Can the sender retry?

Business rules

None beyond schema and code lists.

Example

{
  "specversion": "2.0",
  "id": "evt-error_notice-ERROR_NOTICE-1",
  "type": "nutrab2b.control.error.v2",
  "source": "urn:gln:0614141000012:erp",
  "subject": "ERROR_NOTICE",
  "time": "2026-11-02T09:00:00Z",
  "datacontenttype": "application/json",
  "dataschema": "https://nutrab2b.org/schemas/2.0/ERROR_NOTICE.json",
  "sender": {
    "gln": "0614141000012"
  },
  "receiver": {
    "gln": "4012345000009"
  },
  "correlationid": "CONV-RFQ-1001",
  "idempotencykey": "ERROR_NOTICE:ERROR_NOTICE:1",
  "sequence": 1,
  "env": "test",
  "data": {
    "ref_event": "01JBF8K3Q1Z8M4R2T6V9X0YAB1",
    "code": "NB-E009",
    "message": "PO-55012 not found in ERP",
    "retryable": true
  }
}

Mapping checklist

Every required field populated from your system of record
Coded fields mapped to the Bodylia OpenB2B code lists
GLN, GTIN and SSCC check digits validated
Rules above pass in the validator
Idempotency key and per-subject sequence generated
Expected responses, including rejections, handled