Thanks to all your suggestions.  I got it to work (finally!) through some kind 
of funky extended rule, but it's a temporary fix so I'm not too worried about 
it.  At least I got it to work!

Thank you all again


--- In [email protected], "tbergmann1" <tbergmann1@...> wrote:
>
> Happy Friday, everyone.
> 
> I am using Gentran Server for Windows, version 5.1.  I am working on an 
> outbound 856 map where I have to look at a particular app field (store 
> number) and tell the map if it's equal to 15 different values, then write a 
> specific code to the EDI data (i.e. if = to "000015" then (write) "KN") and 
> if it isn't equal then give it another code (i.e. if != to "000015" then 
> (write) "DS").  I have not been able to figure out how to write the extended 
> rule for all 15 values so I thought I'd use a lookup table to tell the 
> translator if the value is in the table, give it the KN code and if not give 
> it the DS code.
> 
> If the lookup table is the best way to go, how would I write the extended 
> rule to use it?  And if the lookup table is not the best way, what would be?
> 
> Thanks for all your help!  I've tried to get this to work so many different 
> ways that my eyes are starting to bug out of my head!
>




------------------------------------

...
Please use the following Message Identifiers as your subject prefix: <SALES>, 
<JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC>

Job postings are welcome, but for job postings or requests for work: <JOBS> IS 
REQUIRED in the subject line as a prefix.Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/EDI-L/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/EDI-L/join
    (Yahoo! ID required)

<*> To change settings via email:
    [email protected] 
    [email protected]

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/

Reply via email to