# Migrating TN EDI docs to new environment

**URL:** <https://techcommunity.softwareag.com/t/migrating-tn-edi-docs-to-new-environment/107334>\
**Category:** Forum\
**Tags:** EDI\
**Created:** [June 4, 2004, 1:31am UTC](https://techcommunity.softwareag.com/t/migrating-tn-edi-docs-to-new-environment/107334 "2004-06-04T01:31:20Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![Guest](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/guest/32/75_2.png) [@Guest](https://techcommunity.softwareag.com/u/Guest)\
**Post date:** [June 4, 2004, 1:31am UTC](https://techcommunity.softwareag.com/t/migrating-tn-edi-docs-to-new-environment/107334/1 "2004-06-04T01:31:20Z")

</div>

We are using webMethods 6.0.1 for EDI X12 integrations.

We are ready to move to our test environment, but need some advice on the proper procedure. Our main question is how to move the EDI schemas to the new environment. For example, in our Development environment, we have several EDI schemas underneath here:

WmEDIforTN.EDIFFSchema.X12.V4010

These were created when we added EDI doctypes to TN via the WmEDIforTN homepage. When we move to our Test environment, do we need to re-add these EDI doctypes to recreate the webMethods schemas?

Please advise.

---

<div class="post-metadata">

**Author:** ![gupta\_r.17495](https://avatars.discourse-cdn.com/v4/letter/g/9fc348/32.png) [@gupta\_r.17495](https://techcommunity.softwareag.com/u/gupta_r.17495)\
**Post date:** [June 4, 2004, 1:36am UTC](https://techcommunity.softwareag.com/t/migrating-tn-edi-docs-to-new-environment/107334/2 "2004-06-04T01:36:30Z")

</div>

yes,you need to re-add the EDI doctypes and it will create Schemas like you did in the DEV.This is the normal way of migrating.

HTH,

---

<div class="post-metadata">

**Author:** ![dave05](https://avatars.discourse-cdn.com/v4/letter/d/ed655f/32.png) [@dave05](https://techcommunity.softwareag.com/u/dave05)\
**Post date:** [June 4, 2004, 2:00am UTC](https://techcommunity.softwareag.com/t/migrating-tn-edi-docs-to-new-environment/107334/3 "2004-06-04T02:00:31Z")

</div>

Joan,

There’s another way. Our production environment is restricted and we try to avoid making browser-based changes. You can promote the schemas by creating a release from the WmEDIforTN package and installing it in your other environment.

HTHT (hope this helps, too),  
Dave

---

<div class="post-metadata">

**Author:** ![gupta\_r.17495](https://avatars.discourse-cdn.com/v4/letter/g/9fc348/32.png) [@gupta\_r.17495](https://techcommunity.softwareag.com/u/gupta_r.17495)\
**Post date:** [June 4, 2004, 2:14am UTC](https://techcommunity.softwareag.com/t/migrating-tn-edi-docs-to-new-environment/107334/4 "2004-06-04T02:14:07Z")

</div>

But using this way will EDI Doc types get installed in TN?Since we always tried to use from browser.

---

<div class="post-metadata">

**Author:** ![Chris\_L](https://avatars.discourse-cdn.com/v4/letter/c/ba9def/32.png) [@Chris\_L](https://techcommunity.softwareag.com/u/Chris_L)\
**Post date:** [June 4, 2004, 2:31am UTC](https://techcommunity.softwareag.com/t/migrating-tn-edi-docs-to-new-environment/107334/5 "2004-06-04T02:31:42Z")

</div>

My practice is to always migrate the wmEDIForTN package by creating a release and we also migrate the doctypes from one environment to the next.  
This holds true especially if you have modified the Dictionary for formatting reasons.

HTH

---

<div class="post-metadata">

**Author:** ![gupta\_r.17495](https://avatars.discourse-cdn.com/v4/letter/g/9fc348/32.png) [@gupta\_r.17495](https://techcommunity.softwareag.com/u/gupta_r.17495)\
**Post date:** [June 4, 2004, 2:53am UTC](https://techcommunity.softwareag.com/t/migrating-tn-edi-docs-to-new-environment/107334/6 "2004-06-04T02:53:04Z")

</div>

If there are any manual modifications in the Dictionary then we might follow the way as chris mentioned.But better way for this scenario is get a FIX from Support if there are any changes or bugs in the dictionary (example EDI 4060 have some space problem in the GS envelope of EDI version field) and install the EDI types from browser.

just my thoughts,

---

<div class="post-metadata">

**Author:** ![Chris\_L](https://avatars.discourse-cdn.com/v4/letter/c/ba9def/32.png) [@Chris\_L](https://techcommunity.softwareag.com/u/Chris_L)\
**Post date:** [June 4, 2004, 6:37am UTC](https://techcommunity.softwareag.com/t/migrating-tn-edi-docs-to-new-environment/107334/7 "2004-06-04T06:37:43Z")

</div>

RMG,

There are a number of times that I found it necessary to modify the dictionary for the EDI Schemas. How do you handle numeric formatting issues within your EDI implementations. How do you solve missing codes? I have found repeated issues with this. What is your suggested solution?

Looking for alternate method.

---

<div class="post-metadata">

**Author:** ![gupta\_r.17495](https://avatars.discourse-cdn.com/v4/letter/g/9fc348/32.png) [@gupta\_r.17495](https://techcommunity.softwareag.com/u/gupta_r.17495)\
**Post date:** [June 4, 2004, 6:36pm UTC](https://techcommunity.softwareag.com/t/migrating-tn-edi-docs-to-new-environment/107334/8 "2004-06-04T18:36:20Z")

</div>

Chris,

I didnt get a chance to anytime to modify numeric formatting services in the Dictionary except some bugs in the dictionary which i stated in the my earlier post.

May be i agree with your method above as a temporary resolution.We have to ask tech support for alternate method for a flexible method.

Regards,

---

<div class="post-metadata">

**Author:** ![bsbabu81](https://avatars.discourse-cdn.com/v4/letter/b/dc4da7/32.png) [@bsbabu81](https://techcommunity.softwareag.com/u/bsbabu81)\
**Post date:** [May 16, 2005, 10:17am UTC](https://techcommunity.softwareag.com/t/migrating-tn-edi-docs-to-new-environment/107334/9 "2005-05-16T10:17:25Z")

</div>

Hi Guys,

I need to install one fix for flatfile dictionary. But, I could not get fix files at any where to install in my IS. Please let me know how to get fix files and where we have to install those files.

Thanks & Regards  
babu

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/techcommunity/original/3X/c/d/cd19967bb605d28a72d77eb83a1cae22f3df2eb8.svg) [@system](https://techcommunity.softwareag.com/u/system)\
**Post date:** [April 2, 2021, 3:04pm UTC](https://techcommunity.softwareag.com/t/migrating-tn-edi-docs-to-new-environment/107334/10 "2021-04-02T15:04:45Z")

</div>


