EDIFACT examples

Example maps and schemas install with the Pack for Supply Chain EDI or within the Design Server imported project edifactExamples.zip and edifactExampleBlockChain.zip.

The example map and schema example files install in subdirectories under the following folder:

install_dir\supplychain_edi_vn.n.n\edifact\examples

The examples and example files are defined in the following table:

Example and associated files	Description
examples/arrival Example files: arrival - map source containing arrival_notice executable map simonin - input schema child.txt master.txt arrival.out - expected output	Creates an outbound EDI Arrival notice message (IFTMAN), used for the exchange of cargo and transport related information. A lookup is performed in the master.txt input file using the track number field located in the child.txt input file.
examples/edf2xml Example files: ordersedi_in.txt - input EDIFACT D17A purchase orders orders_in.xml - input XML purchase orders orders_out.xml - results EDI to XML executable map edifact_out.txt - results XML to EDI executable map orders - XML schema that defines the XML purchase order xmlpo - map source containing executable maps edifacttoxml and xmltoedifact	Creates an outbound EDI ORDER message, using XML input and an outbound XML Order using EDI ORDER message input.
examples/ediBlockChain Example files: Multiple maps, schemas, files	Example of using traditional EDI with blockchain.
examples/packages Example files: Input_binPackage.txt - input binary data to attach Input_ediPackage.txt - input edifact message to attach Input_xmlPackage.xml - input non-binary data to attach Output_edipkgAttach.txt - output from map edipkgAttach Input_edipkgDetach1.txt - input for map edipkgDetach1 Input_edipkgDetach2.txt - input for map edipkgDetach2 packagetests - map source containing executable maps edipkgAttach, edipkgDetach1, edipkgDetach2	Example using EDIFACT service segment definitions for packaging and security taking three different inputs to create EDIFACT packages.
examples/security Example files: Input_binPackage.txt - input binary data to attach Input_ediPackage.txt - input edifact message to attach Input_xmlPackage.xml - input non-binary data to attach Output_edisecurity.txt - output from map edisecOut Output_security.txt - output for map edisecIn securitytests - map source containing executable maps edisecIn, edisecOut	Example using EDIFACT service segment definitions for packaging and security taking three different inputs to create EDIFACT packages with security.
examples/vermas Example files: vermas_input.json - input JSON file representing vermas data vermas_d17a.txt - results JSON to vermas executable map vermas_template - JSON schema template for vermas message jsonvermas - map source containing executable map json2vermas	Creates an outbound EDI Verified gross mass message (VERMAS) message, which provides VGM information on transport equipment such as a seagoing container. The executable map issuing JSON as input.