EDI and Trading Networks

7/29/2019 EDI and Trading Networks

1/13

EDI and Trading Networks

Concepts

Document Setup

Mapping

Enveloping

Functional Acks


2/13

We apply a knowledgeable and disciplinedapproach to integration projects. With a focus

on business benefit,

rather than on technicalcoolness, we partnerwith our customers toleverage webMethods

products and our insight to create robust,powerful integration solutions.

webMethodsplatformsolutions

The Fundamentals

700 technology and marketing professionals

Offices in Portland, Seattle, Salt Lake City, Denver, San

Francisco, Los Angeles, Dallas, Houston, Chicago, New

York, Boston

The Offerings

Assessment

Integration architecture

Design, development and implementation Education and knowledge transfer


3/13

Document

Integration Server

Trading Networks

HTTP

FTP

HTTPS

Built-in Services

Adapters

OnRamps

Packages

Partners

Marketplaces

Applications

Web Services

XML

Trading Networks

Perform

Processing

Actions

Processing

Rule

Recognize

Document Type and

Extract Attributes

Document

Types

Determine How to

Process the

Document

Processing

Rules

Perform

Pre-processing

Actions

-Verify

-Validate

-Check uniqueness-Save

Trading Networks provides services forthemanagement of partners and the exchangeof documents.

You definepartners, document types and processingrules that manage the flow of documents inand out of your environment. Based on thisconfiguration information, Trading Networksprocesses each document by passing thedocument to a service, delivering it to apartner or sending an alert e-mail to anadministrator.

Trading Networks

Document

Attributes


4/13

Document

Trading Networks

Perform

Processing

Actions

Processing

Rule

Recognize

Document Type and

Extract Attributes

Document

Types

Determine How to

Process the

Document

Processing

Rules

Perform

Pre-processing

Actions

-Verify

-Validate

-Check uniqueness-Save

The EDI modules work with the TN frameworkto extend the benefits of TN to EDI document

exchange. The EDIModule: Core Component

provides services for mapping, enveloping, flat-file support, etc. while the EDI Module: TradingNetworks component supplements the TNenvironment to support processing EDI. EDI forTN provides de-enveloping so your servicescan work with one transaction set at a time.

EDI and TN

What Youll See Today:

Integration Server 4.6

Trading Networks 4.5.1

EDI Module: Core Component 4.5

EDI Module: Trading Networks Component 4.5

EDIforTN

Document(env)

Document(TS1)

Document(TS2)

Document

Attributes


5/13

These are the high-levelsteps to configure your

TN install-ation for

specific transaction sets.You should read boththe EDI Core and EDITN component manualsbefore starting.

Setup

1 Download schemas and templates.

Create namespace record and schema.

Install the template.

Define validation record reference.

Install EDI document type.

3

2

4

5 6 Configure TN profiles and rules.


6/13

consider mapping a segment/section of the document ata time, especially when those segments have multipleoccurrences.

Segment Mapping

X12 Custom Record X12Custom Record


7/13

Various elements of an EDI document need tovary by trading partner. This includes

delimiters, identificationqualifiers and identifiers.

Instead of hard-coding these into a mappingservice, thereby making the mapping servicepartner specific, we can look up these valuesfrom extended fields in the TN profiles.

Enveloping

ISA*00* *00* *01*00001 *01*1234598

GS*RC*00001*123459876*20010926*1030*00000000

ST*861*000000001

BRA*BRAReferenceId*20010926*00*1**07

REF*SI*Shipper Id

DTM*050*20011026

PRF*Purchase Order #**20010909

TD1*CTN*500*G*600*LB

TD5****M

TD3*TL*Init*Equipment Number

.

.

SE*20*000000001

GE*2*000000009IEA*1*123456789

EDI Field Extended Field Description

ISA14 ackRequested Indicates whether or not an ack is requested.

ISA15 testIndicator Indicates whether or not this interchange is a test.

ISA16 subFieldDelimiter The character used as the subfield delimiter.

(n/a) fieldDelimiter The character used as the field delimiter.

(n/a) recordDelimiter The character used as the record delimiter (segment terminator).

ISA05 idTypeForSender

senderQualifier

IfidTypeForSenderis DUNS, ISA05 is set to 01. IfidTypeForSenderis MutuallyDefined, ISA05 is set to ZZ. Otherwise, ISA05 is set to the value in senderQualifier.

ISA06, GS02 idTypeForSender Specifies the external ID to use as the sender identifier.

ISA07 idTypeForReceiver

receiverQualifier

IfidTypeForReceiveris DUNS, ISA07 is set to 01. IfidTypeForReceiveris MutuallyDefined, ISA07 is set to ZZ. Otherwise, ISA07 is set to the value in receiverQualifier.

ISA08, GS03 idTypeForReceiver Specifies the external ID to use as the receiver identifier.


8/13

Use a custom service to lookup values from TNprofile extended fields and establish defaults.Place these values in a custom envelope record.


9/13

For outbound EDIdocuments, the same

steps for converting arecord to an EDI stringand adding the groupand interchangeenvelopes can be usedfor any transaction set.A utility servicesimplifies the work.

Simple changes to theservice presented herecan be made to support

multiple transactionsets per group andmultiple groups perinterchange.


10/13

A functional acknowledgement (FA) indicatesthe results of a syntactical analysis of the

electronically encodeddocuments. In otherwords, did the document(s)

being acknowledged conform to the format weagreed upon? Were all the data elements in theright order? Were the codes values used correct?

FunctionalAcks (997s)

An FA only indicates that the indicatedinterchange was accepted or rejected

syntactically. It does not indicate theacceptance of the document by the system thatperforms the ultimate processing. Forexample, an FA does not say we accept yourpurchase order. Rather, it says we receivedyour purchase order and are processing it.

Heres my purchase order.

Got it.

Heres my purchase order.

I dont understand XYZ.

Heres a corrected one.

Got it.


11/13

The EDI CoreComponent service,wm.b2b.edi.util.generateFA,performs group-level

validationand an

envelope-level compliancecheck. It acknow-ledges interchangeand group-levelvalidation status only.Custom work is need-ed to create FAs at the

transaction set level.

TSet

FAs


12/13

The EDI CoreComponent service,wm.b2b.edi.util.generateFA,performs group-level

validationand an

envelope-level compliancecheck. It acknow-ledges interchangeand group-levelvalidation status only.Custom work is need-ed to create FAs at the

transaction set level.

TSet

FAs

Service Highlights Duplicates TN validation using wm.b2b.edi:convertToValues andpub.schema:validate

Validates at envelope level first

Verifies counts and control numbers If no errors, validates transaction sets

Uses error array from validate service to determine error codes and

segment location

AK3/AK4 segments require special handling to determine position of

the offending segment

997s within input document are ignored for validation but included in

acknowledgement counts

ISA*00* *00* *01*12

GS*FA*123459876*00001*20020718*1815*1

ST*997*181815103

AK1*RC*000000009

AK2*861*000000001AK3*TD3*8**8

AK4*03**5*Equipment Number

AK3*RCD*11**8

AK4*08**7*00


13/13

Why SBI?

ContactFor more information please contact

Rob Eamon at 208-890-2255

email: [email protected]

www.sbiandcompany.com

Documents

EDI and Trading Networks