EDI ASN Integration
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-14-2015 08:37 AM
Hi techno experts,
we have a requirement to Integrate EDI ASN data across ServiceNow and a third party application ePlus. This is about procuring an Asset when order is placed. We wanted to track down order, processing, shipment of an Asset completely automated. Here typical steps.
Here is a typical EDI transaction using Integration:
- A Retail trading partner places an order with customer. They issue an EDI 850 Purchase Order (PO), and that order is then sent electronically to the EDI provider.
- The EDI provider translates the document using their maps and sends to the customer.
- The purchase order is picked up electronically by the customer and brought into ServiceNow using one of the methods provided by EDI providers (ePlus) . That PO is brought into ServiceNow and processed. A Sales Order or Invoice is issued and the product is shipped to the retail trading partner.
- An EDI 856 Advance Shipping Notice is then sent to the trading partner by way of the EDI provider to inform them of the shipping information.
- An EDI 810 is sent to the trading partner (again by way of the EDI provider) for payment.
I have reviewed EDI data format, and it looks like below. That formats makes me to go with Email Integration to get it translated to ServiceNow or a SFTP; thats what I could think off for now. Not sure, if EDI has a WebServices Integration. Yet to figure it out. Anyone implemented in the past, if yes share best practices
EDI 856 Format:
ISA*01*0000000000*01*ABCCO *12*4405197800 *01*999999999 *111206*1719*-*00406*000000049*0*P*>
GS*SH*4405197800*999999999*20111206*1045*49*X*004060
ST*856*0008
BSN*14*829716*20111206*142428*0002
HL*1**S
TD1*PCS*2****A3*60.310*LB
TD5**2*XXXX**XXXX
REF*BM*999999-001
REF*CN*5787970539
DTM*011*20111206
N1*SH*1 EDI SOURCE
N3*31875 SOLON RD
N4*SOLON*OH*44139
N1*OB*XYZ RETAIL
N3*P O BOX 9999999
N4*ATLANTA*GA*31139-0020**SN*9999
N1*SF*1 EDI SOURCE
N3*31875 SOLON ROAD
N4*SOLON*OH*44139
HL*2*1*O
PRF*99999817***20111205
HL*3*2*I
LIN*1*VP*87787D*UP*999999310145
SN1*1*24*EA
PO4*1*24*EA
PID*F****BLUE WIDGET
HL*4*2*I
- Labels:
-
Integrations
-
Scripting and Coding
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-02-2017 09:16 PM
HI Ajay ,
Thanks for the reply!
Could you please let me know how the EDI format data was converted to native formats /Supported format of servicenow to import into the table?
A fair idea about it would be very much help me.
Best Regards
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-22-2017 09:12 AM
If folks could share some insight and pointers on how the EDI integration was achieved that would be very helpful. Thanks in advance.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-19-2018 02:07 AM
Hi All,
Has anyone on this thread finished the implementation ? We have a similar requirement using EDI and could really use some high level guidelines on how this was performed.
Thanks
Aswini Kuppam
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-07-2025 12:21 PM
I know this is an older thread, but did you implement EDI 856 ASN or a variation of it. Any feedback you can share?