I personally am fond of the Joey Tribiani version from "Friends" He would say the point is "moo" Its like a cow's opinion...it doesn't matter.
On Jul 25, 2012, at 2:32 PM, <[email protected]> <[email protected]> wrote: > Regarding native English speakers ... > > Their in lies the problem, there not getting taught proper English in > they're schools. > > -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf Of > Samantha Scott > Sent: 07/25/2012 12:52 PM > To: Mukundaraj Munisamy > Cc: [email protected] > Subject: Re: [EDI-L] Sterling VAN sFTP > > No problem. I wish more native english speakers understood that difference, > you have an excuse! > > AS2 is much less problematic than FTP. I switch every partner I can and I > will only use that with the VAN these days. > > We use the 997's for reconciliation. If you set up the system to 1) do the > work 2) if it can't send an error reliably then you can manage exceptions > rather than touch every transaction. > > I commented to my admin that I noticed a $10million order last wednesday > when I was looking in the archive for something else. He asked if I should > have been notified. I said no, that is exactly how it should be. I should > only hear about it when there is a problem. A $10million order that is a > non-event is a marvelous thing. > > On Jul 25, 2012, at 12:09 PM, Mukundaraj Munisamy wrote: > > > Thanks for the correction. Well, that is the disadvantage of English as a > Second Language -:) > > > > We use direct AS2 with some TPs but afraid of switching the VAN (where > bulk of my TPs are) connection to AS2 thinking what will happen if something > goes wrong in the firewall!! > > The corporate standard mandates using a secure protocol. So I left with > only sFTP. > > > > VAN reports will be used for status re-conciliation in the ERP system and > also fed into a reporting system for the support team. > > > > Thanks, > > Mukund > > > > > > From: Samantha Scott <[email protected]> > > To: Mukundaraj Munisamy <[email protected]> > > Cc: "[email protected]" <[email protected]> > > Sent: Wednesday, July 25, 2012 11:26 AM > > Subject: Re: [EDI-L] Sterling VAN sFTP > > > > The point is not "mute", it may be "moot"...check your dictionary. > > > > I do not use FTP to connect from SI 5.2 to Sterling VAN, I use AS2 so I am > of limited detailed assistance here. I recommend AS2, if you have that > option. > > > > Your second concern about the files being deleted is not that tragic. You > have the ability to re-queue files to be resent from the Sterling > mailbox...they will never be lost. Have no fears here. > > > > As for the report, what do you use them for? If you send something to the > VAN they don't like their 030 error report will be in your e-mailbox > practically before the connection is finished. > > > > On Jul 25, 2012, at 10:57 AM, Mukundaraj Munisamy wrote: > > > >> Hi, > >> > >> We are currently on Mainframe connecting to Sterling VAN using FTP to > transmit data. In the new Sterling B2B Integrator 5.2.3 platform that is > being built we are required to use sFTP to connect to the VAN. When we > explored the opportunities the following challenges are going to be a mute > point using sFTP: > >> > >> - Files/Interchanges are not batched. Every connection "downloads" one > file at a time which will be a performance issue as we get many interchanges > from our Trading Partners. > >> > >> - After each download, files are automatically deleted from the VAN which > may result in lost interchanges. We would like to download the file and have > the control of deleting the files not auto delete by the system. > >> > >> - VAN reports are available only by email not available in a directory as > with regular FTP.. > >> > >> Are there any work around for the above issues using sFTP with Sterling > VAN? > >> > >> > >> Thanks, > >> Mukund > >> > >> [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 > > [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/
