It looks like you are getting the qualifier out of N103 ok.
What do you mean when you say creating a new FFS? Are you referring to the pre-built document types webMethods supplies and that you import with the Install TN Document Types link from the Doc Exchange section of the EDI Module’s administration menu?
When you perform this process, webMethods will create a flat file schema for you. It will be located in the WmEDIforTN package under the EDIFFSchema folder. When you open this flat file schema in the editor, you can generate an Integration Server document type from it. The IS document type will be named T850DT.
This is the IS document type you should be getting when you invoke wm.b2b.edi.convertToValues.
When you examine this document type, you should see a document list named N1. This is the outer list to loop over. Within the N1 document list, you will see N2 and N3 are also document lists, so you will want to loop over those within the N1 loop. N4 is a singe document so you should be able to map values out of it from within the outer N1 loop.
With this as your flow structure, the next thing to do is take a look at EDIValues immediately after stepping past the converToValues service. Is all of the data present in the source EDIValues document?
If this still doesn’t get you to a resolution, we will need to take a closer look at how you are mapping from EDIVallues to the target document type, and how you are converting it to XML.
#webMethods#Flow-and-Java-services#Integration-Server-and-ESB