Electronic Data Interchange - from Legacy System to JDE

Wheeler

Active Member
I would really appreciate whatever information I can get.
We are switching over to JD Edwards Enterprise One 9.2 from a homegrown system. I have reviewed the JDE EDI Implementation Guide but I just would really like to get an idea some sample data for the 850 document for starters.

For example, for the F47011 the minimum required fields are:
EDOC - EDI document number (I know this comes from Next Number)
EDCT - EDI Document Type
EKCO - EDI Document Key Company
EDST - EDI Transaction Set
EDER - Send/Receive Flag (self explanatory)
TPUR - Transaction Set Purpose
AN8 or SHAN - Address number or Ship to Address (know what this is - but would still like to see example)
SYMCU - Business Unit (I know this is the JDE Business Unit

for example in the EDI 850 below - what would be the Document Type? What would be the Transaction Set? What would be the Send/Receive Flag?

1 ISA*00* *00* *01*001753755KRES *12*3106614111 *160126*1535*U*00401*000001152*0*P*>GS*PO*00175375
2 4111*20160126*1535*588*X*004010ST*850*0001BEG*00*NE*TESTPO**20160126PER*BD*S*TE*FOB*PPDTM
3 6TD5*****BWYMAN*PB*P211019272N9*L1*TEXTMSG*.....ALL CONDUIT MUST BE USA MADE..... ..... SHIP TO ..... KIRBY RISK 181
4 RE PKY N LAFAYETTE, IN 47904N1*BY*KIRBY RISK 1 ELECTRICAL SUPPLY*1*0017537550001N1*BT*KIRBY RISK 1 ELECTRICAL SUPPLY*1
5 1*ST*KIRBY RISK 1 ELECTRICAL SUPPLY*9*0017537550001N3*18 SAGAMORE PKY NN4*LAFAYETT*IN*47904PO1*000001*5000*FT*
*BP*561101***VP*E034 10FTPID*F****COND E034 EMT 3/4" 10 FTPO1*000002*3000*FT**PF***UI*78339202003*BP*561
7 0PID*F****COND E100 EMT 1" CONDUITPO1*000003*1200*FT**PF***UI*78339202006*BP*561109***VP*E200PID*F****COND E200
8 UITPO1*000004*2000*FT**PF***UI*98001000102*BP*560928***VP*R034PID*F****COND R034 RIGID 3/4" CONDUITCTT*4SE*25*0
9 002BEG*00*NE*P211019273**20160126PER*BD*Steve Kaduk*TE*765-448-4567FOB*PPDTM*002*20160126TD5*****BWYMAN*PB*P211019
10 XTMSG*.....ALL CONDUIT MUST BE USA MADE..... ..... SHIP TO ..... KIRBY RISK 835 REPPMSG*DR COLUMBUS, IN 47201N1*BY*KI
11 LECTRICAL SUPPLY*1*0017537550002N1*BT*KIRBY RISK 2 ELECTRICAL SUPPLY*1*001753755N1*ST*KIRBY RISK 2 ELECTRICAL SUPPLY*9
12 02N3*835 REPP DRN4*COLUMBUS*IN*472017475PO1*000001*5000*FT**PF***UI*78339202002*BP*561101***VP*E034 10FTPID*F**
13 EMT 3/4" 10 FTPO1*000002*1500*FT**PF***UI*98001002005*BP*561107***VP*E112PID*F****COND E112 EMT 1-1/2" CONDUITP
14 0*FT**PF***UI*78669200001*BP*580362***VP*I012PID*F****COND I012 IMC 1/2" CONDUITPO1*000004*2500*FT**PF***UI*
15 BP*560903***VP*I034PID*F****COND I034 IMC 3/4" CONDUITPO1*000005*250*FT**PF***UI*98001000003*BP*560905***VP*I100
indicates non-displayable character.

Thank you
 
Last edited:

JMast

Reputable Poster
Hello,

Your sample looks like typical PO from a trading partner, so none of the fields you list would be there except EDST which would be the 850. Those fields are all specific to JDE used to create the Sales Order. We have our translation software set up to pass them all as constants except for EDOC/AN8/SHAN. EDOC is a simple next number that our EDI software assigns to each incoming document. AN8/SHAN would be lookups based on the trading partner and store/location values provided in the PO. You can do that lookup in your EDI software or in JDE.

As for sample data, remember that these fields can be configured differently by different JDE users, so it may be better for you to create your own sample data and discover what works best for you. One way to do this is to use P47010 and key in a sample PO. You can see how it populates the F47 tables and test and edit until you get R47011 to create the sales order you are expecting.
 

Wheeler

Active Member
Thank you so much JMast!!! I have mapped and written programs for EDI for many years but I have never worked with JD Edwards. Thank you - this makes sense. I will create the sample data and see how it populates the F47 tables and go from there.
 

JMast

Reputable Poster
You are welcome. JDE can be a little confusing. Way back when, JDE was actually tightly integrated with an EDI software. They realized that customers were going to use a variety of connectors, so they ended that integration. So, you will see some fields in applications and tables that look/sound important, but may not be. With your prior experience, work through the EDI guide, but put your focus on starting there and exploring/testing on your own with simple documents so you uncover what is vital and not. Also, if you have time constraints, I have heard good things about JDETips EDI training. You may be able to get a few hours with them to cut through the processes quickly.
 

Wheeler

Active Member
I have another question:
Is anyone actually using TrustedLink i? If so, can you tell me what field you are using for the Set_ID field in the translation mapper for the header record (H01)?
(from OpenText, aka GXS aka Inovis)

Thank you so much in advance :)
 
Top