Hi Samantha, I've done this numerious different ways. And yes if you want you can increment a code list via SQL through the light weight JDBC adapter, or better yet just create your own table and use the JDBC adapter to do so. If you do not wish to go the database route you can just read a file for the number, increment it, write the file out again. You can prob also use the transaction register to do what you wish to do as well. So many ways to accomplish this rather then double mapping or doing any other crazy stuff.
Question - does it HAVE to be a sequenced number? For example for some non-edi quasi 810 customers I just use the invoice number (or any other incremented number that comes out with your data), its an ever increasing number out of our system. - John On Wed, Aug 3, 2011 at 9:51 AM, Samantha Scott <[email protected]>wrote: > ** > > > I am looking for suggestions from GIS/Sterling integrator folks here who > may > have a suggestion what I can use to solve this problem. > > I have a partner who wants to trade non-EDI data. I agreed and have been > kicking myself since then because I have to code and code and code in an > inverse proportion to the sales potential of this dinky customer. > > Anyway, the latest PITA is they want me to serialize the files I send them. > 1, 2, 3, etc. Like a control number, not unreasonable one would think, but > I can't find anything that would serve as a control number in SI if you are > not using EDI envelopes. Codelists can be queried but not updated. I do > not want to create a database table for the sole use of this customer and I > have no intention of ever agreeing to this again. My last resort idea is a > control file that I collect, read the last number, increase and use it and > then write a new one for next time. Does anyone have a better idea? Is it > possible to use EDI envelopes and their controls without actually wrapping > the data in envelopes? > > [Non-text portions of this message have been removed] > > > [Non-text portions of this message have been removed] ------------------------------------ ... 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/
