Once you have the IDOC in the routed flowservice pipeline then parse the IDOC (transformFlatToHierarchy)gives output IDOC structure then map the data to EDIFACT ORDERS individual Segments (UNH child segments)based on the mapping specifications and create UNH structure.
Finally invoke WmEDI services (convertToString)pass the input FFSChema (EDIFACT ORDERS schema)this will create EDI String.Final steps will be invoking (wm.b2b.edi.util:addICEnvelopeEDIFACT)and pass the above created EDI String to (parameter “documents”)along with other inputs this will adds EDIFACT Envelope segments(UNB/UNG/UNZ).Bottom line is these steps will accomplish to EDIFACT ORDERS format.
For validating the ORDERS envelope (UNB)segments you can use the envelopeProcess service before routing to external world.
If you feel this not elaborate info,regarding mapping EDI segments
please look into WmEDISamples package sample flows to get an overview.
check this site www.unedifact.org for understanding EDIFACT ORDERS segments.
HTH,
#edi#Integration-Server-and-ESB#webMethods