As you know, a Tradacoms document is made up from multiple transaction sets. For example, the ORDERS map is created from the ORDERS transaction and then the ORDHDR is inserted from Standards and the ORDTLR may be needed and inserted from Standards also. The Tradacoms Tutorial discusses the map creation in more detail.
In Gentran:Server for Microsoft Windows, when processing inbound Tradacoms data, you may be left with extra 'documents' in the Red/?In Document Summary. While these are extraneous documents that are not needed, since the entire document was processed and is in the Green/In Documents Summary, they can be deleted. There is no Translation Report for these and they are just left sitting in the ?In Documents. You can manually delete these, which could get tedious, or possibly archive and purge them.
A much easier and cleaner way to do this would be to create two additional Export maps - one for the ORDHDR transaction and the other for the ORDTLR transaction. The ORDTLR must be created as ORDTLR and after the map is created you will need to highlight the ORDTLR root tag, right-click, Create Sub, Transaction Set from Standards, and select the ORDHDR. The reason the ORDHDR is needed in the ORDTLR map is due to the break maps and splitter process.
For the output of both maps you can just copy and paste the Header record from your original Export map into each of the new Export maps (there should be nothing linked in these maps). You will save, compile, register the new maps and go to the Partner Editor and create an Inbound relation for the ORDHDR and ORDTLR (for this example) and specify the appropriate map under the Translation option. You will use/Select the same Group and Interchange that was created for the original Export map.
If you use the Auto Export and specify an Export File Name, it will be the same for the ORDHDR and ORDTLR as well.
While it may seem like a lot of work, it is quick and easy... and sure beats the alternative...