I was able to get the document type defined in Trading Networks.
There are assumptions taking into effect:
- You have X12 v6040 available.
These are the steps used:
A. Go to IS folder (IntegrationServer\packages\WmEDIforTN\config).
B. Copy file (X12_6040_DocTypes.xml) to (X12_6042_DocTypes.xml).
C. Edit file (X12_6042_DocTypes.xml) and keep only references to X12 6040 867.
D. Change all references of 6040 to 6042.
E. Go to IS folder (IntegrationServer\packages\WmEDI\pub\SEFS\X12).
F. Copy file (6040.SEF) to (6042.SEF).
G. Edit file (6042.SEF). At the top of the file, change 6040 to 6042. Should be two places. Make sure.
H. Later in the file is another reference to 6040. Since you’re adding 6042, you will also need to place 6041 in the sequence. (NOTE: Looking at other SEF files, it’s assumed you need to have 6041 in the sequence.)
I. Start Designer and connect to the IS that you’re modifying.
J. Go to package (WmEDIforTN) and run service (wm.b2b.editn:installEDITypes) with the following inputs (X12 6042 867).
K. Go into Trading Networks console and verify that the document is present and enabled in the list of valid documents.
Now that I’ve been able to define the document into Trading Networks, the issue I’m currently having is parsing the incoming v6042 document from our pipeline partner. Being that this is actually a version of the v6040 document I’m having parsing issues. The file schema & dictionary complexity has made modifying the parse process my next hurdle.