Message type
UN/EDIFACT KEYMAN
KEYMAN is a UN/EDIFACT message published in 1 directory version 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 SERVICE_V4 KEYMAN specification- Message
- KEYMAN
- Directory versions
- 1
- Latest
- SERVICE_V4
Sending and receiving
Exchange KEYMAN with your trading partners
The specification tells you what a valid KEYMAN 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.
Specifications
KEYMAN in every directory version
A trading partner names both the message and the directory, for example SERVICE_V4 KEYMAN, because the segments differ between versions. Open the one your partner specified.
1 directory version
Frequently asked questions
Which directory version of KEYMAN do I need?
The one your trading partner specifies. KEYMAN is published in 1 directory version 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 KEYMAN 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
- GS1 EDI standards GS1 guidance on EDI standards used for supply-chain document exchange.
- UNECE introduction to UN/EDIFACT United Nations guidance on UN/EDIFACT for structured business data exchange.
- X12 EDI standards Official X12 standards body for North American EDI transaction standards.
- OpenPeppol post-award specifications OpenPeppol documentation for e-procurement and e-invoicing specifications.