Well, now, that's an actual question. One answer is this: somebody needs to speed up their "batch" process. That somebody being the person who's sending you multiple changes to a single order in a single file. This is a business process issue and not a technical issue. How often do you receive this data? Is it pushed to you or do you pull it?
Of course, if this is happening many times per day/hour then someone needs to determine why these are changing so quickly. If there's a flaw in the process then that needs to be fixed. If the orders truly do change this often for some reason, then the orders need to be created and sent much more frequently. You've got some research and back tracking to do. If you can't fix this by addressing the process or by using MCM's suggestion (perhaps the sender is an 800lb gorilla), then you're going to have to figure out a way for TLi and your ERP to work together to indicate which came "first", hopefully there's a time stamp in the data, if not, you could try using the ST control number in some field that can be used by the ERP to sort, check and "order" the changes. To do this, you'll also need to include the ISA or GS control number so the ERP can tell the difference between files sent at different times of day. i.e. the same order may be sent with ST control number 17 at 9am but then be sent with ST control number of 20 at 10am and, according to what you're saying 20 would then overwrite 17 because it arrived "later". You see this can of worms, you don't want it. Fix the process. Good Luck, Leah ________________________________ From: David <[email protected]> To: [email protected] Sent: Monday, March 18, 2013 2:17 PM Subject: [EDI-L] Re: Document order I am processing 940 change orders and in the example both documents are for the same order. I need to make sure that I have the most recent change order. I am using Trustedlink i translator and it is processing the higher number last, but the TP says that the lowest number document should be processed last. I don't know how to change the order of processing in the translator. --- In [email protected], Mike Rawlins <mcr2@...> wrote: > > Well, no, not actually. Usually true in practice though. The X12 > standard is silent on your question - it only says that the transaction > set control numbers should be unique within the functional group. I > don't have the ISO 9735 spec in front of me, but I'm pretty sure EDIFACT > is the same. > > That begs a question though - why do you care which is the most recent? > > Mike > > ----------------------------------------- > Michael C. Rawlins, Senior Software Engineer, GXS > Sent from personal account > > On 3/18/2013 11:10 AM, David wrote: > > > > I have a question on the order of documents. I believe that the higher > > numbered document is the most recent am I correct. In the example > > below Document reference number 0003 should be newer than Document > > reference number 0001. > > > > Interchange reference number . . . . . : 000022778 > > Group reference number . . . . . . . . : 9575 > > Document reference number . . . . . . : 0001 > > > > Interchange reference number . . . . . : 000022778 > > Group reference number . . . . . . . . : 9575 > > Document reference number . . . . . . : 0003 > > > > > [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/
