webMethods Rocky Mountain User Group-EDI for TN

1
EDI and Trading Networks Concepts Document
Setup Mapping Enveloping Functional Acks
2
We apply a knowledgeable and disciplined approach
to integration projects. With a focus on
business benefit, rather than on technical
coolness, we partner with our customers to
leverage webMethods products and our insight to
create robust, powerful integration solutions.
webMethods platform solutions

• 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
Trading Networks provides services for the
management of partners and the exchange of
documents. You define partners, document types
and processing rules that manage the flow of
documents in and out of your environment. Based
on this configuration information, Trading
Networks processes each document by passing the
document to a service, delivering it to a partner
or sending an alert e-mail to an administrator.
Trading Networks
4
The EDI modules work with the TN framework to
extend the benefits of TN to EDI document
exchange. The EDI Module Core Component
provides services for mapping, enveloping,
flat-file support, etc. while the EDI Module
Trading Networks component supplements the TN
environment to support processing EDI. EDI for TN
provides de-enveloping so your services can
work with one transaction set at a time.

• 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

EDI and TN
EDI for TN
5
1
Download schemas and templates.
Install the template.
2
These are the high-level steps to configure your
TN install- ation for specific transaction sets.
You should read both the EDI Core and EDI TN
component manuals before starting.
Setup
Create namespace record and schema.
Define validation record reference.
3
4
Install EDI document type.
5
6
Configure TN profiles and rules.
6
consider mapping a segment/section of the
document at a time, especially when those
segments have multiple occurrences.
Segment Mapping
7
ISA00 00 0100001
011234598 GSRC0000112345987620010926103000
000000 ST861000000001 BRABRAReferenceId2001092
600107 REFSIShipper Id DTM05020011026 PRF
Purchase Order 20010909 TD1CTN500G600LB TD
5M TD3TLInitEquipment Number . . SE200000
00001 GE2000000009 IEA1123456789
Various elements of an EDI document need to vary
by trading partner. This includes delimiters,
identification qualifiers and identifiers.
Instead of hard-coding these into a mapping
service, thereby making the mapping service
partner specific, we can look up these values
from extended fields in the TN profiles.
Enveloping
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 If idTypeForSender is DUNS, ISA05 is set to 01. If idTypeForSender is Mutually Defined, 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 If idTypeForReceiver is DUNS, ISA07 is set to 01. If idTypeForReceiver is Mutually Defined, 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
Use a custom service to lookup values from TN
profile extended fields and establish defaults.
Place these values in a custom envelope record.
9
For outbound EDI documents, the same steps for
converting a record to an EDI string and adding
the group and interchange envelopes can be used
for any transaction set. A utility service
simplifies the work.
Simple changes to the service presented here can
be made to support multiple transaction sets per
group and multiple groups per interchange.
10
A functional acknowledgement (FA) indicates the
results of a syntactical analysis of the
electronically encoded documents. In other
words, did the document(s) being acknowledged
conform to the format we agreed upon? Were all
the data elements in the right order? Were the
codes values used correct?
An FA only indicates that the indicated
interchange was accepted or rejected
syntactically. It does not indicate the
acceptance of the document by the system that
performs the ultimate processing. For example, an
FA does not say we accept your purchase order.
Rather, it says we received your purchase order
and are processing it.
Functional Acks (997s)
Heres my purchase order.
Heres my purchase order.
I dont understand XYZ.
Got it.
Heres a corrected one.
Got it.
11
The EDI Core Component service,
wm.b2b.edi.util.generateFA, performs group-level
validation and an envelope-level compliance
check. It acknow-ledges interchange and
group-level validation status only. Custom work
is need-ed to create FAs at the transaction set
level.
TSet FAs
12

• Service Highlights
• Duplicates TN validation using wm.b2b.ediconvertT
  oValues and pub.schemavalidate
• 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

The EDI Core Component service,
wm.b2b.edi.util.generateFA, performs group-level
validation and an envelope-level compliance
check. It acknow-ledges interchange and
group-level validation status only. Custom work
is need-ed to create FAs at the transaction set
level.
TSet FAs
ISA00 00 0112 GSFA123459
876000012002071818151 ST997181815103 AK1RC
000000009 AK2861000000001 AK3TD388 AK4035
Equipment Number AK3RCD118 AK408700
13
Why SBI?
Contact For more information please contact Rob
Eamon at 208-890-2255 email reamon_at_sbiandcompany.
com www.sbiandcompany.com