Try it now Login

Message type

UN/EDIFACT RECADV

Receiving advice message. It is published in 57 directory versions of the UN/EDIFACT standard, each defining its own segment structure.

Open the D24A RECADV specification
Message
RECADV
Directory versions
57
Latest
D24A

Sending and receiving

Exchange RECADV with your trading partners

The specification tells you what a valid RECADV 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.

6 integrations on this site document RECADV handling:

Blue Yonder RECADV mapping and transport Mintsoft RECADV mapping and transport Procure Wizard RECADV mapping and transport ProSKU RECADV mapping and transport SnapFulfil RECADV mapping and transport Workday RECADV mapping and transport

Specifications

RECADV in every directory version

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

57 directory versions

Related messages

Messages in the REC set

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

RECALC UN/EDIFACT message. RECECO Receiving completion message. RECLAM Claim message. RECORD UN/EDIFACT message.

Frequently asked questions

What is the RECADV message?

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

Which directory version of RECADV do I need?

The one your trading partner specifies. RECADV is published in 57 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 RECADV 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