Upgrading Older Configuration Files

www.altova.com Print this Topic Previous Page Up One Level Next page

Home >  Data Sources and Targets > EDI > Customizing EDI Structure >

Upgrading Older Configuration Files

EDI configuration files contain a reference to (and are validated against) one of the XML schemas available in the MapForceEDI directory (see EDI Configuration Schemas). To view the schema and version of a configuration file, open the file in a text editor and check the following line at the beginning:

 

<?xml version="1.0" encoding="UTF-8"?>

<Config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../EDIConfig5.xsd" Version="5">

 

MapForce 2019 recognizes custom EDI configurations that are based on EDIConfig.xsd schema version 3 or later, introduced in MapForce 2011, Release 3. Compared to previous version, this schema adds the ability to map data to or from multiple message types in the same EDI component. If you were using custom EDI configuration files that point to a schema version prior to version 3, then your configuration files must be upgraded. Otherwise, when you attempt to add the custom EDI collection to the mapping, the following message appears on the "Browse EDI Collections" dialog box:

 

"The selected EDI collection uses an old configuration file version that supports only a single message type per component."

 

The following instructions show you how to upgrade the schema of an EDI configuration file from EDIConfig.xsd version 2, to EDIConfig.xsd version 3.

 

 

To upgrade the configuration files:

1.Copy Envelope.Config from the original configuration folder (for example, "EDIFACT") to the folder containing you customized EDI collection (for example, "EDIFACT.Custom").
2.Edit EDI.Collection, and change the root element's Version attribute from "2" to "3".
3.Add <Root File="Envelope.Config"/> after the </Meta> tag:

<?xml version="1.0" encoding="UTF-8"?>
<Messages xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" Version="3">
 <Meta>
   <Version>D</Version>
  <Release>04B</Release>
  <Agency>UN</Agency>
  </Meta>
  <Root File="Envelope.Config"/>
  <Message Type="ORDERS" File="ORDERS.Config" Description="Purchase order message"/>
</Messages>

4.Edit ORDERS.Config, and change the root element's Version attribute from "2" to "3".
5.Add <Format standard="EDIFACT"/> (or, depending on the case, X12, or HL7) after the </Meta> tag.
6.Rename <Group name="Message"...> to <Group name="Message_ORDERS"...> (or whatever the custom message type is), and remove the outer group levels ("Envelope", "Interchange", and their segments) as shown below:

<?xml version="1.0" encoding="UTF-8"?>
<Config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" Version="3">
  <Meta>
    <Version>D</Version>
    <Release>04B</Release>
    <Agency>UN</Agency>
  </Meta>
  <Format standard="EDIFACT"/>
  <Include href="Admin.Segment"/>
  <Include href="EDSD.Segment"/>
  <Include href="UNCL.Codelist"/>
  <Message>
    <MessageType>ORDERS</MessageType>
    <Description>Purchase order message</Description>
    <Revision>14</Revision>
    <Date>2004-11-23</Date>
     <Group name="Envelope">
        <Group name="Interchange" maxOccurs="unbounded">
           <Segment ref="UNA" minOccurs="0"/>
           <Segment ref="UNB" minOccurs="0"/>
           <Group name="Group" maxOccurs="unbounded">
              <Segment ref="UNG" minOccurs="0"/>
              <Group name="Message_ORDERS" maxOccurs="unbounded" info="UNH - Message header">
                <Segment ref="UNH"/>
                <Segment ref="BGM"/>
                      <Segment ref="UNT"/>
              </Group>
              <Segment ref="UNE" minOccurs="0"/>
           </Group>
           <Segment ref="UNZ" minOccurs="0"/>
        </Group>
     </Group>
  </Message>
</Config>

If a mapping was open while you were editing the configuration file, it should be reloaded. The connections will be automatically remapped from "Message" to "Message_ORDERS" item.


© 2019 Altova GmbH