Last week I was asked to do something I personally have never done before, create 721 copies of a trading partner with a different EDI and App code and a unique partner id for each for a project needing divisional lookups. Now having suffered through the 30+ partners needed to make Ford happy I had no intentions of copying and pasting 721 DUNs numbers: so I quit the job and am now happily flipping burgers at BK. Just kidding; however, it made me wonder who is actually luckier, oh and by the way "the first 855s will be going out tomorrow morning".
Ok so here is what I did utilizing a little ingenuity and a quick VBScript.
1) Created a template trading partner with Gentran's Trading Partner manager and export the partner to the partners directory. Being sure to use Tag words.
2)Create a text file list of all my divisional lookup values.
3) Ok Next I created my vbscript. Your lucky I'm sharing the one I created right here.
' Example: cscript GenerateGentranPartners.vbs "C:\GENSRVNT\Partners\GHX - REPVAL.par" C:\PartnerList.txt C:\GENSRVNT\Partners\ ProfileID
' ******************************************************************************
' ******************************************************************************
' ** Create Gentran Partners Script **
' ** Version 0.0.1 **
' ** **
' ** Stephen Case **
' ** http://www.ediassociates.com **
' ** **
' ** Usage: **
' ** cscript.exe GenerateGentranPartners.vbs **
' **
4) Here is the command line for useing the script.
cscript C:\pathto\GenerateGentranPartners.vbs
[template file] [partner list file] [output dir] [Gentran Profile ID prefix]
Example: cscript C:\pathto\GenerateGentranPartners.vbs"C:\GENSRVNT\Partners\GHX - REPVAL.par" C:\PartnerList.txt C:\GENSRVNT\Partners\ GHX
5) Once the partner files have been created you can schedule a GDW_Partner_Import through Gentrans Process Controller to import all the partners in one sweep. Just a note to import my 721 partner took close to 45 minutes.
Happy Gentraning...