Try it now Login

Message type

UN/EDIFACT DOCAMA

Document amendment message. It is published in 59 directory versions of the UN/EDIFACT standard, each defining its own segment structure.

Open the D24A DOCAMA specification
Message
DOCAMA
Directory versions
59
Latest
D24A

Sending and receiving

Exchange DOCAMA with your trading partners

The specification tells you what a valid DOCAMA looks like. Sending and receiving one means mapping it to the system that holds the data, agreeing the format with each partner, and handling the messages that come back when something is rejected. XEDI does the mapping, validation and transport.

Browse integrations Connect DOCAMA to your ERP, WMS or accounting system Find your trading partner Document requirements by partner Talk to an EDI specialist Scope a DOCAMA flow with us

Specifications

DOCAMA in every directory version

A trading partner names both the message and the directory, for example D00A DOCAMA, because the segments differ between versions. Open the one your partner specified.

59 directory versions

Related messages

Messages in the DOC set

UN/EDIFACT groups related documents under a shared three-letter stem. These usually appear together in one trading flow.

DOCADV Document advice message (document status). DOCAMI Document amendment instruction. DOCAMR Document amendment request. DOCAPP Document application message. DOCARE Document arrival advice. DOCINF Document information message.

Frequently asked questions

What is the DOCAMA message?

Document amendment message. It is one of the UN/EDIFACT message types, identified by the six-letter name DOCAMA in every directory version that publishes it.

Which directory version of DOCAMA do I need?

The one your trading partner specifies. DOCAMA is published in 59 directory versions and the segment detail differs between them, so a mapping built for one version is not automatically valid for another.

How do I send a DOCAMA message?

Map the data from the system that holds it into the segment structure the agreed directory version defines, then transport it by the route the partner uses, commonly AS2 or SFTP. XEDI handles the mapping, validation and transport, and surfaces the acknowledgements and errors that come back.

Sources and further reading