Adding New Versions of EDI Standards

You can configure Module for EDI to support a new version of any EDI standard that Module for EDI supports, except VDA and TRADACOMS.

1. Obtain the appropriate SEF file for the new version of the EDI standard. The SEF file's .INI section must specify the EDI standard and version. The file must contain all the transaction sets that the version supports.

2. In Designer's navigation panel, run the following built-in service located in the WmEDIforTN package: wm.b2b.editn.util.VersionSupport:addNewEDIVersion. This service creates a new TN document type file in the config directory of the WmEDIforTN package. The new version will be available when defining TN document types. Specify the following input parameters for the service:

Input Parameter	Description
SEF fileName	The fully qualified path of the SEF file.
Replace?	Whether to overwrite an existing SEF file of the same name and its associated TN document type file. yes—Overwrite an existing SEF file of the same name and its associated TN document type file. no—Do not overwrite an existing SEF file of the same name and its associated TN document type file. This is the default.

Note:
The service does not update the envelope segments structure or the validation for individual fields. However, the service does update the following fields in the IS document type wm.b2b.editn.rec:EDIHEADERS so that Trading Networks recognizes the new version during validation:

Standard	Code list for field	Description
ANSI X12, VICS, UCS	ISA/ISA12	Version in the Interchange header.
	ISA/GS/GS08	Version in the Group header.

Note:
If the new version of the EDI standard introduces changes to the structure of the 997 transaction set, these changes will not be reflected in the functional acknowledgments created by the wm.b2b.edi:generateFA service.

For complete information about the wm.b2b.editn.util.VersionSupport:addNewEDIVersion service, see webMethods Module for EDI Built-In Services Reference .

4. Install the new TN EDI document type for the transaction set, as described in Defining TN EDI Document Types. Module for EDI creates the TN EDI document type and the SEF files.

Module for EDI creates...	In the following directory...
TN EDI document type	WmEDIforTN\config\EDI_Standard\docType.xml where EDI_Standard is X12, UNEDIFACT, ODETTE, EANCOM, VICS, or UCS.
SEF file	Integration Server_directory \instances\$instance_name\packagesWmEDI\pub\SEFS\EDI_Standard\version.sef Note: Integration Server_directory \instances\$instance_name\packagesWmEDI\pub\SEFS\EDI_Standard_SefDesc\version.sef. When InstallSEFSchemaWithDescription is set to true. Note: For UN/EDIFACT, ODETTE, and EANCOM, the system adds a CONTRL message in the .SETS section of the SEF file.

Important:
After you install a new version of an EDI standard and the corresponding TN EDI document type, do not re-install that version of the EDI standard. If you re-install it, the internal ID of the document type will change, and any references to that ID will be incorrect. In addition, any Trading Networks processing rules that refer to the document type will also be incorrect.