Try it now Login

Message type

UN/EDIFACT JUPREQ

JUPREQ is a UN/EDIFACT message published in 50 directory versions of the standard. A written summary of its purpose has not been added to this library yet; the segment structure for each version is complete and linked below.

Open the D24A JUPREQ specification
Message
JUPREQ
Directory versions
50
Latest
D24A

Sending and receiving

Exchange JUPREQ with your trading partners

The specification tells you what a valid JUPREQ 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 JUPREQ to your ERP, WMS or accounting system Find your trading partner Document requirements by partner Talk to an EDI specialist Scope a JUPREQ flow with us

Specifications

JUPREQ in every directory version

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

50 directory versions

Frequently asked questions

Which directory version of JUPREQ do I need?

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