I would argue that perhaps you need to learn to instruct the translator to think as you do, since most likely you're the one doing the actual thinking (in most cases). Leah
________________________________ From: Brandon Bee <[email protected]> To: [email protected] Sent: Thu, March 31, 2011 6:55:22 PM Subject: RE: [EDI-L] EDI mapping basics Your question is actually a very good one. In order to professionally support EDI translation on a particular EDI translator platform, you do need to understand how it is processing the data. You literally need to learn to think like the translator, and each translator thinks differently. *Most* translators are designed to process in the order of the source document. They start from the first record of the source (or segment of EDI data) and process all the instructions in that record/segment. Once they move on to the next record, they literally forget everything they ever knew about the previous record. They have extremely bad short term memory. The good news is, the translator will do exactly what you tell it. Unfortunately, that’s also the bad news. And, if you forget to connect your command to some kind of event in the source document, then you only thought you told it to do something. EDI is very much an acquired skill. Becoming an expert at a particular translator software package is even more of an acquired skill. Finding resources on the web, in print, etc. is a great idea, but there is no substitute for learning by doing when it comes to EDI. So, dig in. Write some maps, and expect to fail a lot in the beginning. Learn what you can from the failures, and get better. That’s pretty much how every EDI professional I know got to be one. From: [email protected] [mailto:[email protected]] On Behalf Of DINAKAR Sent: Thursday, March 31, 2011 1:15 PM To: [email protected] Subject: Re: [EDI-L] EDI mapping basics Hi, I know some of the basics like standards (X12,EDIFACT),VAN,implementation guides. But my problem is that in my company i am just doing support like whenever a doc gets rejected by translator, i will analyse the error and notify the TP about the same.Exactly my problem is i don't know how the docs are being translated by translator(internally). what conditions should we give translator for this task.....and so on....I searches a lot in web and everywhere i can see only basics like what is a tranlator,VAN, implementation guides....but i want to learn what exactly is happening inside???? Thanks for the help in advance On Thu, Mar 31, 2011 at 10:31 PM, Emmanuel Hadzipetros < [email protected] <mailto:ehadzipetros%40hotmail.com> > wrote: > > > No, but you did. Dinakar is clearly not there yet. So there’s no point. > > From: [email protected] <mailto:EDI-L%40yahoogroups.com> >[mailto:[email protected] <mailto:EDI-L%40yahoogroups.com> ] On Behalf Of > > Lowell Porter > Sent: Thursday, March 31, 2011 9:54 AM > > To: [email protected] <mailto:EDI-L%40yahoogroups.com> > Subject: RE: [EDI-L] EDI mapping basics > > >His question really should have been . I want to learn. Can you recommend > >sites, articles, books, anything that'll help me help myself get started. > > You didn't even recommend your own book ;-) > > Lowell Porter > EDI Analyst > > From: Emmanuel Hadzipetros <[email protected] ><mailto:ehadzipetros%40hotmail.com> <mailto: > > ehadzipetros%40hotmail.com> > > To: "'Art Douglas'" <[email protected] <mailto:adouglasedi%40gmail.com> ><mailto:adouglasedi%40gmail.com> > > >, "'DINAKAR'" > <[email protected] <mailto:sarbadadinu%40gmail.com> ><mailto:sarbadadinu%40gmail.com> >, < > > [email protected] <mailto:EDI-L%40yahoogroups.com> ><mailto:EDI-L%40yahoogroups.com> > > > Date: 03/31/2011 11:31 AM > Subject: RE: [EDI-L] EDI mapping basics > Sent by: [email protected] <mailto:EDI-L%40yahoogroups.com> ><mailto:EDI-L%40yahoogroups.com> > > > A good basic description. Putting on my Canadian hat, however, I'd point > out > that X12 is a North American standard as it is also the most widely used > standard in Canada and has been for decades. At least as far as EDI is > concerned, Canada and the US are a single territory. > > And as for EDIFACT, it's a United Nations standard and widely used beyond > Europe, including by the US government, in such departments as Homeland > Security, the global auto industry, which has committed to eventually > moving > entirely to EDIFACT, and in Asia, where a number of very large projects > have > been recently completed and are underway, including India's harbors. > > However you cut it, it's difficult to sum everything up in a few words or > a > few paragraphs. It's not rocket science but there's no denying that there > is > a learning curve to mapping or any other skill required to do EDI. My > advice > to Dinakar would be to begin by reading . search the web . there's a ton > of > stuff out there that'll give him a good introduction to EDI and what he > needs to know to succeed. > > His question really should have been . I want to learn. Can you recommend > sites, articles, books, anything that'll help me help myself get started. > > From: [email protected] <mailto:EDI-L%40yahoogroups.com> ><mailto:EDI-L%40yahoogroups.com> [mailto: > > [email protected] <mailto:EDI-L%40yahoogroups.com> ><mailto:EDI-L%40yahoogroups.com> ] On Behalf Of > > Art > Douglas > Sent: Thursday, March 31, 2011 8:51 AM > To: 'DINAKAR'; [email protected] <mailto:EDI-L%40yahoogroups.com> ><mailto:EDI-L%40yahoogroups.com> > > Subject: RE: [EDI-L] EDI mapping basics > > Dinakar, > > While Smanatha's response is technically correct, it may be a little more > terse than you desired. > > Mapping EDI is not all that much different than mapping terrain - or > rather > using a map to go from where you are to where you wish to be. > > There are generally two kinds of EDI maps: inbound and outbound. The > inbound map is used to take information sent to you by another entity (we > call other entities "Trading Partners"), and transform it in to a form > useable by your organization. The outbound map takes information generated > by your organization and formats it for your Trading Partner. The formats > most often used are X12 in the USA, and variations of EDIFACT in Europe. > Both X12 and EDIFACT, as well as other standard formats are used outside > and > across the named regions as well. Another format some people class with > EDI > is XML. XML is quite useful, especially if you are selling a product > designed to use it. In the EDI community we are often reserved in our > enthusiasm of XML, for reasons you don't need to know in a "Basic" > discussion. > > Each standard has various versions, older, newer and newest. The standards > undergo change, and each batch of changes warrant a new version. > > Before you create a map, you must establish between you and your trading > partner, which standard and version you will use. Then you must establish > the document, aka Transaction Set. For example, if you are mapping for a > manufacturer, and your trading partner is a wholesale distribution > company, > and your client of employer is in the U.S., you may wish to use the X12 > 850 > Purchase order, or the 875 Grocery Purchase Order. Or you may select the > EDIFACT ORDERS transaction set. I'm going to continue this discussion > assuming you have selected the 850. > > Next, you must determine where you wish to go - the target of the EDI map, > if you will. What information do you want. Let's say your client or > employer is using Oracle EBS. In all likelihood, you will want to map to > the POI file, which Oracle's EC Gateway will suck in and make into a Sales > Order. (Assuming the data is correct, your map is correct, and the setup > is > correct in Oracle,) > > You must determine what data your Trading Partner (TP) is sending in the > 850, and if it is adequate. If not, you will have to negotiate with your > TP, or your Oracle developers to fill in the gaps. > > Once all that is done, comes the simple part - building the map. From > here, > you use the tool provided to build a set of instructions that will > transform > the inbound data into the outbound data. > > Next comes testing of the map, doing the Oracle setup for the Trading > Partner/Customer and testing of the results in a test Oracle instance. > Once > you and your internal customer (customer service?) are happy with the > results, you move or replicate the Oracle setup to production, redirect > your > map's output to production, notify your TP that you are in production. If > you use SAP, JDE, PeopleSoft or any of hundreds of others of back-end > systems, the steps are similar. > > Somewhere along the line you should have also tested the 997 > acknowledgement > which tells your TP that you have received his EDI transactions, and that > they did or did not pass a syntax test. > > Now, you sit back and monitor the results, making corrections as > necessary. > > Good luck, > > Art > > EDI Guy > > From: [email protected] <mailto:EDI-L%40yahoogroups.com> ><mailto:EDI-L%40yahoogroups.com> <mailto: > > EDI-L%40yahoogroups.com> > [mailto:[email protected] <mailto:EDI-L%40yahoogroups.com> ><mailto:EDI-L%40yahoogroups.com> <mailto: > > EDI-L%40yahoogroups.com> ] On Behalf > Of > DINAKAR > Sent: Thursday, March 31, 2011 7:22 AM > To: [email protected] <mailto:EDI-L%40yahoogroups.com> ><mailto:EDI-L%40yahoogroups.com> <mailto: > > EDI-L%40yahoogroups.com> > Subject: [EDI-L] EDI mapping basics > > Hi, > > Kindly someone post the basics of mapping. I am a starter. > > -- > WITH WARM REGARDS! > > DINAKAR > > [Non-text portions of this message have been removed] > > [Non-text portions of this message have been removed] > > [Non-text portions of this message have been removed] > > ------------------- > This transmission may contain information that is privileged, confidential > and/or exempt from disclosure under applicable law. If you are not the > intended recipient, you are hereby notified that any disclosure, copying, > distribution, or use of the information contained herein (including any > reliance thereon) is STRICTLY PROHIBITED. If you received this > transmission in error, please immediately contact the sender and destroy > the material in its entirety, whether in electronic or hard copy format. > Thank you. > > [Non-text portions of this message have been removed] > > [Non-text portions of this message have been removed] > > > -- WITH WARM REGARDS! DINU [Non-text portions of this message have been removed] [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/
