Softshare Delta and ECS Training Binder - … Delta/ECS Training Introduction to ANSI X12 2 equivalent EDI format. • Trading Partner A person or organization that has agreed to exchange

Softshare Delta & ECS Training

Table of ContentsPowerPoint PresentationsHands-On Projects

Introduction to ANSI X12

Common EDI Terminology

ANSI American National Standards Institute is a private non-profit coordinator and clearing house on national and international standards including X12.

ANSI X12 The standard adopted by the U.S. Federal Government and most U.S. industries for the exchange of EDI documents.

EDIFACT (Electronic Data Interchange for Administration, Commerce, and Transport) The standard used internationally for the exchange of EDI documents.

Transaction Sets Business documents that have been converted to an equivalent EDI format

Softshare Delta/ECS Training Introduction to ANSI X12 2

equivalent EDI format.

Trading Partner A person or organization that has agreed to exchange EDI business documents electronically. The sending or receiving party involved in the exchange of EDI transmissions.

ANSI X12 Terms Applying to X12

X12 Standard The actual language that is agreed upon for use in the EDI system.

X12 V i T ll h t X12 l f ll i X12 i d t d X12 Version Tells us what X12 rules we are following. X12 is updated on an annual basis.

X12 Implementation Conventions User-defined refinements to the version. ICs should never include anything that is not in the version; however, they could exclude options in order to simplify transactions.


ANSI X12 Terminology

SegmentST*850*0006

Element

Delimiters

Qualifiers

Naming Conventions for Data Element (BEG01)

ST 850 0006

BEG*00*SA*19358**20070827

PER*BD*The Sports Place*TE*(213) 555-7890

PO1*1*300*EA*2.25******VP*4894F

PID*F****Golf Ball

CTT*1

AMT*TT*675

SE*8*0006


(BEG01)

Basic Components of an X12 EDI Document

Interchange EnvelopeISA/IEA Segments

Detail Segments(e g Purchase Order)

Transaction Set Header

Functional Group Header

Interchange Control Header

Functional GroupGS/GE Segments

Transaction SetST/SE Segments

(e.g. Purchase Order)

Detail Segments(e.g. Purchase Order)

Transaction Set Trailer


Functional Group Trailer

Functional Group Header




Transaction SegmentsData Elements

Detail Segments(e.g. Receiving Advice)


Functional Group Trailer

Interchange Control Trailer

ANSI X12 Interchange Envelope

ISA*00* *00* *ZZ*ASPI *ZZ*TSP *070827*1110*X*00501*000000004*0*T*~

GS*PO*ASPI*TSP*20070827*111010*18*X*005010

ST*850*0006

BEG*00*SA*19358**20070827BEG 00 SA 19358 20070827


PO1*1*300*EA*2.25******VP*4894F

PID*F****Golf Ball

CTT*1

AMT*TT*675

SE*8*0006

GE*1*18

IEA*1*000000004


Contains information on the date and time of creation, who the transaction is from, and to whom it is directed. The number of transmitted functional groups is also included in this envelope.

ANSI X12 Functional Group Header/Trailer


GS*PO*ASPI*TSP*20070827*111010*18*X*005010

ST*850*0006

BEG*00*SA*19358**20070827BEG 00 SA 19358 20070827


PO1*1*300*EA*2.25******VP*4894F

PID*F****Golf Ball

CTT*1

AMT*TT*675

SE*8*0006

GE*1*18

IEA*1*000000004


Contains information such as the type of transactions enclosed, the sender and receiver IDs, creation date, and control number.

ANSI X12 Transaction Set Header/Trailer


GS*PO*ASPI*TSP*20070827*111010*18*X*005010

ST*850*0006

BEG*00*SA*19358**20070827BEG 00 SA 19358 20070827


PO1*1*300*EA*2.25******VP*4894F

PID*F****Golf Ball

CTT*1

AMT*TT*675

SE*8*0006

GE*1*18

IEA*1*000000004


Indicates the beginning and ending segments of a singular transaction. These segments include the number of segments included in the transaction set (to ensure complete transmission).

ANSI X12 Control Numbers


GS*PO*ASPI*TSP*20070827*111010*18*X*005010

ST*850*0006

BEG*00*SA*19358**20070827BEG 00 SA 19358 20070827


PO1*1*300*EA*2.25******VP*4894F

PID*F****Golf Ball

CTT*1

AMT*TT*675

SE*8*0006

GE*1*18

IEA*1*000000004


All header and trailer segments must be present and have matching control numbers in order for the data to be accepted as a valid X12 transmission.

ANSI X12 Transaction Segments


GS*PO*ASPI*TSP*20070827*111010*18*X*005010

ST*850*0006

BEG*00*SA*19358**20070827BEG*00*SA*19358**20070827


PO1*1*300*EA*2.25******VP*4894F

PID*F****Golf Ball

CTT*1

AMT*TT*675

SE*8*0006

GE*1*18

IEA*1*000000004


Transaction segments fall between the ST and the SE segments. These segments contain data specific to this single transaction. The segments are organized in a uniform manner based on the X12 guidelines.

ANSI X12 Data Elements


GS*PO*ASPI*TSP*20070827*111010*18*X*005010

ST*850*0006

BEG*00*SA*12348**20070827BEG 00 SA 12348 20070827


PO1*1*1*EA*1.25******VP*4894F

PID*F****Golf Ball

CTT*1

AMT*TT*1.25

SE*8*0006

GE*1*18

IEA*1*000000004


These are the actual data elements of the transaction. They hold the useful information that the business document is intended to communicate. Each element is separated by a pre-arranged character (in this case, an asterisk (*)).

997 Functional Acknowledgment

ISA*00* *00* *ZZ*TSP *ZZ*ASPI *070827*1115*X*00501*000000007*0*T*~

GS*FA*TSP*ASPI*20070827*1115*1001*X*005010

ST*997*0009

AK1*PO*4

AK1 Functional Group Response Header Used to respond to the functional group header and to start the ackno ledgment for a f nctional gro p

AK1 PO 4

AK2*850*0006

AK5*A

AK9*A*1*1*1

SE*5*0009

GE*1*1001

IEA*1*000000007


header and to start the acknowledgment for a functional group.

AK2/AK5 Transaction Set Response Header/Trailer The transaction set control number found in the ST segment in the transaction set being acknowledged.

AK9 Functional Group Response Trailer Acknowledges acceptance or rejection of a functional group and reports the number of included transaction sets from the original.

Exercise: Interpreting Implementation Conventions


ANSI X12 Data Types

Data types define the data which may be included in an element:

AN Alphanumeric String

B Binary Data

DT Date (YYMMDD or CCYYMMDD)

FS Fixed-Length String

ID Identifier, from a pre-defined list of applicable code values

Nn Numeric, with (n) implied decimal places


R Decimal Number (Real Number)

TM Time (HHMMSS), 24-hour clock

Exercise: Building EDI


Hierarchical Looping (HL Loops)

Hierarchical Loop (HL Loop) An EDI data structure which allows a set of segments to be used repeatedly, but with each loop reflecting a different "level" of informationreflecting a different level of information.

Used in transaction sets such as 856 Advance Ship Notice

Not the same as repeating segments

Example: HL #1 uses an N1 segment to reflect the ship-to information for the entire shipment, while HL #2 uses an N1 segment to reflect the buyer information for a particular order


within that shipment.

Hierarchical Looping Example (856)

Shipment Level

ST*856*0015BSN*00*11*20070827*141032

HL*1**STD1*CTN25*2****G*75*LBDTM*011*20070827 DTM*017*20070912

Order Level

Pack Level

Item Level

DTM*017*20070912 N1*ST*Denver DC*92*020

HL*2*1*OPRF*19358N1*BY*Store 093*92*093

HL*3*2*PMAN*GM*00000049000000000931

HL*4*3*ILIN**VP*4894FSN1**15*EA

HL*5*1*OPRF*19392N1*BY*Store 294*92*294

HL*6*5*P


HL 6 5 PMAN*GM*00000049000000000942

HL*7*6*ILIN**VP*4894FSN1**25*EA

SE*23*0015

Softshare EDI Dictionary Viewer


Common EDI Transmission Methods

Value-Added Network (VAN) An electronic service provider that transmits, receives, and stores EDI and other electronic messages for trading partners. Traditionally, data may be sent to a VAN via FTP, g p y, y ,SMTP, HTTP, or modem.

Interconnect A VAN to VAN connection that assists trading partners in transmitting data when the sender and receiver subscribe to different electronic service providers.

EDIINT (AS1, AS2, AS3) A set of protocols that allows partners to transmit data securely (encrypted), and receive an immediate


y yresponse (called an MDN) to let the sender know the data was received.

VAN Interconnect Flowchart

Your Company Your Trading Partner

Interconnect


SoftshareYour TradingPartners VAN

Interconnect

EDIINT Terminology & Features

AS1/AS2/AS3 EDIINT process by SMTP, HTTP, or FTP respectively (AS2 is the most commonly used)

Features/Benefits of EDIINT

Security Security options include encryption of the message, signing of the message, and sending via secure transmission method (such as HTTPS or FTP/S).

Non-repudiation When a message is transmitted, the receiver sends back a message disposition notice (MDN) to let the user know h h h d d d d bl


that either the message was received and was understandable, or that there was an error. If the message and reply are both signed, neither party is able to refute when the message was sent/received, or that the content received was the same as the message sent.

EDIINT Security Terminology

Certificate An electronic document which incorporates a digital signature to bind together a public key with an identity (such as an email or AS2 ID). The certificate can be used to verify that a public ) y pkey belongs to an individual or company. Certificates can be self-signed or signed by a certificate authority.

Certificate Authority (CA) An entity which issues digital certificates for use by other parties (examples: Verisign, Thawte).

Public & Private Keys A user has a pair of cryptographic keys a public key and a private key. The private key is kept secret, while the


y y ypublic key may be widely distributed. Messages are encrypted with the recipient's public key and can only be decrypted with the corresponding private key.

Questions?


Softshare Delta/ECSComponents & Concepts

Softshare Product Overview

Product Edition Overview

Athena Forms-based Web-EDI for low volume

Delta Any to any data translatorDelta Any-to-any data translator

Run-Time For integration with 3rd party software

Standard Development and execution of translation maps

Enterprise All features of standard edition + Solution Manager

ECS Communications server

Lite Maximum of 10 trading partners. No security.

Standard Unlimited trading partners, SFTP, FTPS, EDIINT

Softshare Delta/ECS Training Softshare Delta/ECS Components & Concepts

g p , , ,

Enterprise All features of standard edition + failover and scaling

2

Delta Key Components

Trading Partner Manager (TPM)

Log Viewer

EDI Notepad

EDI Dictionary Viewer

Data Link Manager

Solution Manager (Delta Enterprise only)

Softshare Delta/ECS Training Softshare Delta/ECS Components & Concepts 3

Exercise: Creating TPM Entries


Steps for Creating a Data Translation Map

1. Create a Source Model

2. Create a Target Model

3. Create a Data Translation Map

4. Validate the Data Translation Map

5. Test the Data Translation Map

6. Install the Data Translation Map


Types of Business Object Models

EDI (source or target): ANSI X12, EDIFACT, TRADACOMS

XML (source or target)

Data file (source or target): flat and formatted files such as comma delimited or SAP IDOC

Database (source or target): OLE DB or ODBC access

Text (target only): plain text or HTML


Methods for Creating Business Object Models

From scratch

From a definition file

Delta template

SEF (for EDI)

DTD or Schema (for XML)

SAP IDOC (for data files)

From a sample file or transaction


From a sample file or transaction

Accurate Modeling = Trouble-Free Mapping

Accurate field lengths

Accurate data types

Proper data constraints

Code lists and defaults

Hierarchy (parent-child relationships)


Objects & Elements

Object: A container for fields, elements, etc. An object is not a data element and cannot be mapped directly.

Element: A data object (e.g. field, EDI element, XML cdata, etc.). Elements contain data and can be mapped directly.


Exercises:Creating a Data Translation Map

Exploring Softshare Delta Menu Options


Source-Driven Mapping Definition

Source-driven map execution process:

1. Validation: Delta validates the file (EDI or XML) for syntax

2. Delta reads in each data object for processing, one at a time:

EDI segment or composite

Data file record type

XML tag

3. Delta executes any rules that have that data object as the


y jsource node for the rule

Source Firing Concepts


Source Firing Overview

Execution order for map rules is determined by:

1. Source node

2. Rule timing

3. Numerical order

When Delta reaches a source object, it reads all the data elements associated with that object, and then executes rules associated with that source object

Child bj t ( h it hild l t ) t


Child objects (such as composites or child elements) are not read until after all rules associated with the parent node have been executed

Source Fire Mapping Tip #1

The source node for a rule must be at or after the data

ST*850*0001element that you are trying to map.

If you are mapping N102, then the source node for the rule can be N1 or N3, but not BEG.

ST*850*0001

BEG*00*SA*SS9901**990129

N1*BY*Buyer Name*93*12346

N3*123 Main St.

N4*AnyTown*CA*99999

PO1*A*39*EA*5.77**BP*309034483-00

PID*F****WIDGETS

CTT*1


Source Firing Mapping Tip #2

A target data element cant be mapped until after the parent object p jis created.

This means that the source node of the rule that creates the parent object must be the same or prior to the source node of the rule


source node of the rule that maps the data element.

Troubleshooting Source Firing Issues

Errors that indicate a possible source node problem are:

The variable is undefined or has gone out of scope.

Target object was not found, it either went out of scope, or was not created yet. Target node=

Other possible symptoms of source node problems are:

Looping issues (e.g. either not enough or too many of a target node)


node)

Rules execute out of order, creating map errors

Changing Source Nodes

Changing a source node:

1. Right-click the rule and select Change Source Node.

2. Highlight new source node and click OK (or double-click source node).

3. Review your rule. Delta may have changed the data elements to full path notation. Double-check to make sure syntax is still


make sure syntax is still correct, especially for database queries.

IntelliMap

For any map that has EDI or XML as a target, you can create target elements out of order. IntelliMap will help put them into correct ordercorrect order.

Limitations:

Minor performance hit

Ambiguous cases may not produce desired results


Target-Driven Mapping

For any map that has EDI, XML, or a structured data file (i.e. a data file with multiple record types) as a source, target-driven mapping allows the map to determine the processing order formapping allows the map to determine the processing order for source nodes to accommodate target ordering requirements.

Limitations:

Map will run slower, due to need for data caching

One source order per source model


Conditional Logic

Condition tab: Perform this rule when:

General tab: assign target elements a value based on conditional logic

Decision procedure

Logical operators: and, or, not

IIF(): function used to evaluate an expression

Case logic:


Copy/paste rule groups

Use condition bar to apply logic to multiple rules

Variables

1. Declare the variable

Assign name

Initialize to a value

2. Assign the variable a value

Index variable

Mathematical variable

Stored value variable


3. Retrieve the variables value and write to target data

Example: need to track the number of line items being mapped to an EDI purchase order

Arrays

One-dimensional and multi-dimensional arrays supported

Use variables or data elements as array indexes

Index management is key

Store a series of related data elements

Must be triggered by looping source object for multiple values of like kind (e.g. line items)

Enable rule Repeat column for data retrieval


Static or variable can be used as repeat value

Initialize and clear arrays with Deltas built in InitArray() and ClearArray() functions

Testing/Debugging Advanced Diagnostics

Available from a maps properties

Log details of rule execution shows the results of the execution of each rule

Log each node visited in the source datashows each piece of


shows each piece of source data that is read by Delta

Testing/Debugging - Breakpoints

Breakpoints pause map testing at strategic locations

There are three types of breakpoints:

Fixed breakpoint: assigned to a rule and triggered whenever the rule is Fixed breakpoint: assigned to a rule and triggered whenever the rule is evaluated

Conditional fixed breakpoint: assigned to a rule, but only triggered when the rule is executed (i.e. its condition evaluates to TRUE)

Global breakpoint: triggered when a designated expression evaluates to TRUE

When a breakpoint is hit, testing pauses so that you may:


View mapping that has occurred up to breakpoint

Step through rules one at a time

Inspect source data

Map Organizer

Installed maps can be managed through Deltas Map Organizer:

Associate with partners

Retrieve from installed location

Revoke (i.e. take out of production)

P k f di t ib ti Retrieve from installed location

View maps installation history

Package for distribution


For Delta Enterprise users, many of Map Organizers functions are replaced by Solution Manager

Solution Manager (Delta Enterprise)

Store version information for maps, d l d th

Management of Delta maps, models, and other translation resources:

models, and other resources

Deploy solutions to connected ECS servers

Receive alerts if there are issues deploying solutions (such as missing data links)

Easily roll back solutions to


Easily roll back solutions to previous versions

Export solution resources for use on other servers

Delivery

For EDI, XML, and text output, delivery is configured in the maps properties (Delivery tab)

Trading Partner Manager

Delivery method

Specialized variables can override interchange values

_isa_sender_qual, _isa_sender_id, _gs_sender_id

_isa_receiver_qual, _isa_receiver_id, _gs_receiver_id

For data file output delivery is configured in:


For data file output, delivery is configured in:

Target model

Maps properties

ECS Key Components

Management Console

Data Administrator

Trading Partner Manager (TPM)

Log Viewer

Status Monitor


Other ECS Components and Features

SSL Certificate Generator

Certificate Manager

ECS Archive Features

ECSInfo Diagnostic

WebECS


Introduction to EDIFACT

What is EDIFACT?

An EDI standard

Electronic Data Interchange For Administration, Commerce, gand Transport

A collection of syntax rules, message elements and messages

Maintained by UN/CEFACT, the United Nations Centre for Electronic commerce For Administration, Commerce, and Transport under the UN Committee on Trade, Economic and S i l C il

Softshare Delta/ECS Training Introduction to EDIFACT 2

Social Council

Common EDI Terminology

ANSI American National Standards Institute is a private non-profit coordinator and clearing house on national and international standards including X12.

EDIFACT (Electronic Data Interchange for Administration, Commerce, and Transport) The standard used internationally for the exchange of EDI documents.

Implementation Conventions User-defined refinements to the Version. IC's can never add anything that is not in the Version; however, they could choose to exclude options in order to simplify their messages.

Message Business document that has been converted to an equivalent


g qEDIFACT format.

Trading Partner A person or organization that has agreed to exchange EDI business documents electronically. The sending or receiving party involved in the exchange of EDI transmissions.

Requirement of an EDI Standard

Provide addressing capabilities for delivery of messages through a network and for automatic recognition of sender and receiverand receiver

Provide possibilities for low-level message validation

Provide possibilities for high-level message validation

Provide flexibility in its application

Minimize message size


Minimize processing power needed to validate and process messages

Addressing

EDIFACT wraps messages in Interchange Segment Envelopes. An Interchange Segment contains the sender and receiver address.

Sender Address

Receiver Address

Interchange Segment En elopes (UNB/UNZ)

UNB+UNOA:4+WONKY:ZZ+GLOOP:ZZ+040801:0913+1'

UNH+0001+ORDERS:D:01A:UN'

BGM+105+D654321987+9'

.

.

CNT+12:1033.55'

UNT+33+0001'


BGM+105+E321654987+9'

.

.


Envelopes (UNB/UNZ) .UNS+S'

CNT+2:4'

CNT+12:1082.83'

UNT+18+0002

UNZ+2+1'

Low-Level Message Validation

EDIFACT uses pre-defined service segments

By reading and interpreting the service segments, a computer y g p g g papplication can do a first, low-level validation

EDIFACT service segments all start with UN



Service SegmentsUNB+UNOA:4+WONKY:ZZ+GLOOP:ZZ+040801:0913+1'UNH+0001+ORDERS:D:01A:UN'

Syntax IdentificationUNB

UNOA = Character set used4 = Syntax version

Message IdentificationUNH

ORDERS = Message type

UNH+0001+ORDERS:D:01A:UN

BGM+105+D654321987+9'

.

.

CNT+12:1033.55'

UNT+33+0001'


BGM+105+E321654987+9'

.

.

.

UNS+S'

CNT+2:4'


ORDERS Message typeD = Message version01A = Message releaseUN = Controlling agency

CNT+12:1082.83'

UNT+18+0002

UNZ+2+1'


Unique Reference UNB+UNOA:4+WONKY:ZZ+GLOOP:ZZ+040801:0913+1'UNH+0001+ORDERS:D:01A:UN'References must match

Segment Count

Message Count in Interchange

BGM+105+D654321987+9'

.

.

CNT+12:1033.55'

UNT+33+0001'


BGM+105+E321654987+9'

.

.

.

UNS+S'

CNT+2:4'

CNT+12:1082 83'


CNT+12:1082.83

UNT+18+0002

UNZ+2+1'

The Birth of an EDIFACT Message

EDIFACT message are pre-defined and composed from elementary building y gblocks. These building blocks are stored in electronic dictionaries so computer applications can use them.

Message dictionary


Segment dictionary Composite dictionary Element dictionary

EDIFACT Elements

Elements are the smallest and most fundamental building blocks

Elements are defined in element dictionaries

El t h ti Elements have properties: Data type (such as text or numeric)

Length (minimum and maximum length or fixed length)

A number to identify them in the dictionary

BGM+105+D654321987+9'

------------------------------------------

1000 Document name

Desc: Name of a document.

Simple Elements


Repr: an..35

-----------------------------------------

1001 Document name code

Desc: Code specifying the document name.

Repr: an..3

Data Element Representationa = Alphabeticn = Numerican = Alphanumeric

EDIFACT Composite Elements

Elements that have data which should be interpreted together are grouped in composite elements

C it l t d fi d i it l t di ti i Composite elements are defined in composite element dictionaries

Composite elements define a list of elements they contain and per element if it is mandatory or conditional with this composite

C001 TRANSPORT MEANSDesc: Code and/or name identifying the type of CNT+12:1033.55


means of transport.

8179 Transport means description code C an..81131 Code list identification code C an..173055 Code list responsible agency code C an..38178 Transport means description C an..17

1 composite element consisting of 2 simple elements

EDIFACT Segments

A segment is a collection of elements and composite elements with a specific meaning

S t d fi d i t di ti i Segments are defined in segment dictionaries

Segments define a list of composite and simple elements they contain and if they are mandatory or conditional

DTM DATE/TIME/PERIODFunction: To specify date, and/or time, or period.


C507 DATE/TIME/PERIOD M 12005 Date or time or period function code

qualifier M an..32380 Date or time or period text C an..352379 Date or time or period format code C an..3

DTM+10:20040214:102

EDIFACT Messages

A message is a collection of segments in a specific order and with a specific structure

A i ll h d f ifi f i ( h A message contains all the data for a specific function (such as a purchase order, invoice, etc.)

Messages are defined in message dictionaries

A message dictionary defines the structure of the segments it can contain and the rules to use the message

Every EDIFACT message is preceded by a UNH service


segment and followed by a UNT service segment

Message dictionaries are lengthy documents

EDIFACT Interchanges

An EDIFACT interchange is a collection of one or more EDIFACT messages



BGM+105+D654321987+9'

destined for a single receiver

An interchange is preceded by a UNB segment and followed by a UNZ segment

Only interchanges are sent over a network, as

.

.

CNT+12:1033.55'

UNT+33+0001'


BGM+105+E321654987+9'

.

.

.

UNS+S'

CNT+2:4'

CNT+12:1082.83'

UNT+18+0002


,they contain the addressing information

UNZ+2+1'

Interchange Messages

How to Keep Things Apart


UNH 0001 ORDERS D 01A UN'

By using separator characters.

By default, a quotation mark () separates segments, a plus sign


BGM+105+D654321987+9'

.

.

CNT+12:1033.55'

UNT+33+0001'


BGM+105+E321654987+9'

.

.

.

UNS+S'

CNT+2:4'

separates segments, a plus sign (+) separates composites, and a colon (:) separates elements within a composite.

Both comma and period (.) are accepted as decimal separators.

Separator characters can be changed by using the UNA ser ice segment The UNA if


CNT 2:4

CNT+12:1082.83'

UNT+18+0002

UNZ+2+1'

service segment. The UNA, if used, is always the first segment in an interchange and does not use any separators itself. UNA is fixed length.

Giving Meaning to Data

EDIFACT messages are built from elementary and quite generic building blocks.

S h d i i h i bl k ?So how do we give meaning to those generic blocks?

By using qualifiers.


Giving Meaning to Data


UNH 0001 ORDERS D 01A UN'

An EDIFACT qualifier is just another EDIFACT element. Most qualifier elements have an associated code list.


BGM+105+D654321987+9'

.

.

CNT+12:1033.55'

UNT+33+0001'


BGM+105+E321654987+9'

.

.

.

UNS+S'

CNT+2:4'

Some code lists are part of the EDIFACT standard, but they can also be supplied by ISO, GS1/EAN, industry organizations or any other institute that trading partners agree on.

Qualifiers as part of a composite mostly qualify other elements within that composite (for example, KGM qualifies the amount in an MEA segment).


CNT 2:4

CNT+12:1082.83'

UNT+18+0002

UNZ+2+1'

amount in an MEA segment).

Sometimes a qualifier qualifies a segment or a whole message (like BGM document message name, coded, qualifies the meaning of the whole message). Qualifiers

For More Information

www.unuece.org

United Nations Web site United Nations Web site

Where the EDIFACT standard is maintained

UN documentation and specs are freely available


Common EDI Transmission Methods

Value-Added Network (VAN) An electronic service provider that transmits, receives, and stores EDI and other electronic messages for trading partners. Traditionally, data may be sent to a VAN via FTP, g p y, y ,SMTP, HTTP, or modem.

Interconnect A VAN to VAN connection that assists trading partners in transmitting data when the sender and receiver subscribe to different electronic service providers.

EDIINT (AS1, AS2, AS3) A set of protocols that allows partners to transmit data securely (encrypted), and receive an immediate

( ll d MDN) t l t th d k th d t


response (called an MDN) to let the sender know the data was received.

VAN Interconnect Flowchart

Your Company Your Trading Partner

Interconnect


SoftshareYour TradingPartners VAN

Interconnect

EDIINT Terminology & Features

AS1/AS2/AS3 EDIINT process by SMTP, HTTP, or FTP respectively (AS2 is the most commonly used)

Features/Benefits of EDIINT

Security Security options include encryption of the message, signing of the message, and sending via secure transmission method (such as HTTPS or FTP/S).

Non-repudiation When a message is transmitted, the receiver sends back a message disposition notice (MDN) to let the user know h h h d d d d bl


that either the message was received and was understandable, or that there was an error. If the message and reply are both signed, neither party is able to refute when the message was sent/received, or that the content received was the same as the message sent.

EDIINT Security Terminology

Certificate An electronic document which incorporates a digital signature to bind together a public key with an identity (such as an email or AS2 ID). The certificate can be used to verify that a public ) y pkey belongs to an individual or company. Certificates can be self-signed or signed by a certificate authority.

Certificate Authority (CA) An entity which issues digital certificates for use by other parties (examples: Verisign, Thawte).

Public & Private Keys A user has a pair of cryptographic keys a public key and a private key. The private key is kept secret, while the


y y ypublic key may be widely distributed. Messages are encrypted with the recipient's public key and can only be decrypted with the corresponding private key.

Introduction to XML

XML Concepts Overview

XML data structures and naming Tags Elements and Attributes XPath

XML specifications Document Type Definitions (DTDs) W3C XML Schema Namespace

Softshare Delta/ECS Training Introduction to XML 2

XML business structures Business frameworks Examples: SOAP, ebXML

XML Tags, Elements & Attributes

TagIdentifies open and close points of an XML

close points of an XML element.

ElementIdentified by its tag. Can contain data or other objects.

A123456789

05/24/2004 09:21:48 AM

1-23456-78901-2

22

7

Basketballs


AttributeChild of element. Defined within tag.

XPath

XPath is a way to name the XML elements and data so they can be identified and used by processes like XSLT (display stylesheets) and XML queries. It can use language such as child, sibling, descendant, etc.

XPath for Basketballs OrdersBatch/Order/OrderLine/Description

A123456789

05/24/2004 09:21:48 AM

1-23456-78901-2

22

XPath for Basketballs = OrdersBatch/Order/OrderLine/Description


7

Basketballs

Document Type Definitions (DTDs)

A DTD provides a standard for exchanging data via XML

(CompanyName*|Address1*|Address2*|City*|Province*|PostalCode*|Country*)*>

XML.

A DTD specifies the tags, elements, and attributes of a compliant XML document. It may also restrict the value of an element or attribute.


BatchID CDATA #IMPLIED >

OrderID CDATA #REQUIRED >

LineNumber CDATA #IMPLIED >

A DTD is analogous to an EDI implementation convention (IC).

XML Schemas

An XML schema is a specification used to describe the structure of

Fault reporting structure

XML documents

An XML schema is more specific than a DTD in that it includes ways to specify the data type of elements (e.g. Booleans, numbers, dates and times, currencies) and it is based on XML


is based on XML

It is defined in the W3C's XML Schema Working Group

Namespaces

A namespace is identified via a Uniform Resource Identifier (a URL or URN)

12345


A namespace is identified via a Uniform Resource Identifier (a URL or URN).

This XML syntax prevents name conflicts in documents (e.g. the same element name in two sections of a document) by qualifying the name of an element or attribute with a namespace URI and prefix. The prefix xmlns is a reference to the term XML namespaces.

XML Business Frameworks

An XML business framework is a specification that defines:

The structure of business data, usually described using XML

The structure of messaging components using XML

The rules for communications, routing and handling of the messages

Transport, routing, and packaging

May also define security, discovery, error handling, etc.

Examples: ebXML, ACORD w/SOAP, BizTalk, RosettaNet


Examples: ebXML, ACORD w/SOAP, BizTalk, RosettaNet

SOAP

SOAP = Simple Object Access Protocol (originally)

Originally developed as a way to connect to applications over the Internet using an XML messaging structure

SOAP 1.0 introduced in 1999

SOAP 1.1 = SOAP with attachments approved by W3C in May, 2000

SOAP 1.2 = Current W3C recommendation approved in June 2003


in June, 2003

Sample SOAP Message

Header info such as routing may appear here

Manifest or payload data typically appears here


Sample SOAP with Attachments

[MIME Headers/Boundary]

Header info such as routing can optionally appear here

Manifest/payload data typically appears here

CID used when referencing an attachment

ebXML

ebXML is a set of specifications that together enable a modular electronic business framework. The vision of ebXML is to enable a global electronic marketplace where enterprisesis to enable a global electronic marketplace where enterprises of any size and in any geographic location can meet and conduct business with each other through the exchange of XML-based messages. (From www.ebxml.org.)

Exchange data securely and reliably.

Formalize relationships with trading partners.


Provide means to discover trading partners.

Use a common vocabulary to exchange data.

ebXML Components

ebXML Collaborative Partner Profile Agreement (CPPA):Exchange of TP data

ebXML Messaging Service Specification (MS):Messaging service (to, from, purpose, security, etc.)

ebXML Registry Information Model (RIM):Creates a repository for business schemas, rules, standards, etc.

ebXML Registry Services Specification (RSS):Specifications to provide access to the ebXML registry


Specifications to provide access to the ebXML registry

ebXML Sample Message (SOAP)

(this area omitted..)

Money Transfer


Business Scenario & Projects

Business Scenario

Active Sports Products, Inc. (ASPI) is a manufacturer of sporting goods including uniforms, sportswear, and supplies

for baseball, football, soccer, and water sports. ASPI is a major supplier to Global Enterprises and Wiki Toys. ASPI

has been conducting business with Global Enterprises and Wiki Toys using traditional paper documents.

Recently, Global Enterprises and Wiki Toys have contacted ASPI and asked that ASPI begin conducting business

with them via EDI. To accommodate these two customers, ASPI purchased Softshare Delta Enterprise and Softshare

ECS as its EDI solution.

Youve been put in charge of ASPI's EDI program. Its your responsibility to use these Softshare integration products

to create a solution that processes, produces, and integrates the EDI documents required by Global Enterprises and

Wiki Toys.

Project Overviews

EDI Purchase Order to Data File Youll translate the purchase orders received by ASPI into a data file that can be

read by ASPIs internal systems, while also returning acknowledgments to

Global Enterprises and Wiki Toys.

Data File to EDI Invoice Youll translate the invoice data produced by ASPIs accounting system into

outgoing EDI invoices destined for Global Enterprises and Wiki Toys.

Database to EDI Ship Notice Youll translate the shipment information that ASPI stores in a SQL Server

database into outgoing EDI ship notices destined for Global Enterprises and

Wiki Toys.

Database Shipment Reports Youll use the shipment information that ASPI stores in a SQL Server database

to generate an HTML report that summarizes all items shipped to Wiki Toys and

Global Enterprises in a one-day period.

Handling Data Errors with Softshare ECS Youll use ECS and Deltas various tools and utilities to handle two common

types of errors found in arriving EDI data.

Sample Entries for Trading Partner Manager

Active Sports Products, Inc (ASPI)

Vendor ID: Self

Accounting ID: Self

EDI Coordinator: Phone: +1 805-555-1234

E-mail: [email protected] Fax: +1 805-555-1235

Administrative Contact: George Thompson Phone: +1 805-555-1234


Address: 911 Olive Street

City: Santa Barbara

Province: CA

Postal Code: 93101-3242 Country: United States (US)

EDI Routing Information:

ANSI X12 Qualifier: ZZ Identifier: ASPI

UN/EDIFACT Qualifier: ZZ Identifier: UNASPI

AS2 Identifier: AS2ASPI

Note: Set the Type for this entry to "Self" on the General tab of the Properties page in Trading Partner Manager.

Global Enterprises

Vendor ID: 002

Accounting ID: GE123

EDI Coordinator: John Williams Phone: +31 (0)20 6388077

E-mail: [email protected] Fax: +31 (0)20 3306478

Administrative Contact: Susan Meyer Phone: +31 (0)20 6388077

E-mail: [email protected] Fax: +31 (0)20 3306478

Address: Brouwersgracht 136

City: Amsterdam

Province: NH

Postal Code: 1013 HA Country: Netherlands (NL)


ANSI X12 Qualifier: ZZ Identifier: GLE

UN/EDIFACT Qualifier: ZZ Identifier: UNGLE

AS2 Identifier: AS2GLE

Wiki Toys

Vendor ID: 003

Accounting ID: WT123

EDI Coordinator: Brenda Mikals Phone: +1 808-555-7890


Administrative Contact: Harold Shaw Phone: +1 808-555-7890


Address: 2123 Terrace Dr.

City: Hilo

Province: HI

Postal Code: 96720-2411 Country: United States (US)


ANSI X12 Qualifier: ZZ Identifier: WIKI

UN/EDIFACT Qualifier: ZZ Identifier: UNWIKI

AS2 Identifier: AS2WIKI

Project Blue:EDI Purchase Order to Data File

Receive Order from Trading Partner (FTP Pull)

Submit Document to Delta for mapping

Direct Data File Output to C:\ECS_Inbox\POTest.txt

END

Send Acknowledgment to Trading Partner via FTP

Project Blue: EDI Purchase Order to Data File

For this project, ASPI needs to:

Translate the EDI purchase orders that Wiki Toys and Global Enterprises are sending into a format that can be read by its internal systems

Return functional acknowledgments to Wiki Toys and Global Enterprises whenever purchase orders are received

Dynamically deliver those outgoing functional acknowledgments based on information stored in Trading Partner Manager

Project Blue Steps

Delta Manual "EDI Models" chapter

1. Create a source EDI purchase order business object model in Delta. When creating this model, import the POEDISample.edi file to use as a basis, which can be found in the "X12" or "EDIFACT" subfolder (depending on which standard you're working in) of the "EDI Purchase Order to Data File (Project Blue)" folder. Once the source model is created, refine its properties using the printed X12 or EDIFACT EDI purchase order specifications that are provided in the "Project Resources" area of your training binder (blue folder).

Delta Manual "Data File Models" chapter

2. Create a target data file business object model in Delta. When creating this model, import the POFileSampleData.txt file to use as a basis, which can also be found in the project folder. Set the file delivery to "C:\ECS_Inbox\POTest.txt." Printed specifications for this data file are provided in your training binder (blue folder).

Hint: The POFileSampleData.txt is a data file with multiple record types.

Delta Manual "Setting Map Parameters" & "Mapping Overview" chapters

3. Using the source and target models you created in steps 1 and 2, create a data translation map in Delta.

Hint: Use the same data file specifications referenced in the previous step to assist with mapping. There is a column in these specifications that indicates how the EDI elements in the source model should be mapped to the fields in the target model.

Delta Manual "Testing Your Map" chapter

4. Validate the map (Map|Validate).

5. Test the map (Map|Test). Delta will prompt you to select the source file. Test the POEDITestBatch.edi file which can be found in the project folder.

6. Verify that the map's data file output is correct. You can use the purchase order audit document that is provided in your training binder (blue folder) to verify the accuracy of the output.

Delta Manual "Putting Maps Into Production" chapter

7. Once your map is producing reliable results in all situations, install it (Map|Install).

Trading Partner Manager Guide "Property Pages" chapter

8. In Trading Partner Manager, associate your newly installed map with the Global Enterprises and Wiki Toys trading partner entries. This is done from the Documents page of the trading partner entry's properties.

ECS Management Console Guide "Input Channels" chapter

9. Open Softshare ECS's Management Console. Create a new FTP input channel with the parameters listed in the following table (leave the default values in place for all parameters not listed here). This input channel is responsible for retrieving EDI purchase orders from Global Enterprises and Wiki Toys.

Tab Setting Value

General

Name FTP Input for EDI Purchase Orders

Host Name uspub1.softshare.com

User Name (e.g. "student1")

Password (e.g. "student1")

Directory //inbox (e.g. "/student1/inbox")

File *.edi

ECS Management Console Guide "Event Rules " chapter

10. Also in Management Console, create a "Translate using Softshare Delta" event rule with the following parameters (leave the default values in place for all parameters not listed here). This event rule is responsible for sending data that arrives on the FTP input channel to Delta.

Tab Setting Value

Translate Using

Event Name Auto Translate EDI Purchase Orders

Source FTP Input for EDI Purchase Orders

ECS Management Console Guide "Output Channels" chapter

11. Still in Management Console, create a new FTP output channel with the parameters listed in the following table (leave the default values in place for all parameters not listed here). This output channel is responsible for delivering functional acknowledgments to Global Enterprises and Wiki Toys.

Tab Setting Value

General

Name FTP Output to Training Server

Host Name uspub1.softshare.com

User Name student (e.g. "student1")

Password student (e.g. "student1")

Base Path //outbox (e.g. "/student1/outbox")


12. Go back into Trading Partner Manager and from both the Global Enterprises and Wiki Toys trading partner entries, set default delivery to the FTP output channel. Set the To field's value to "EDIData.edi." This is done from the Delivery page of a trading partner entry's properties.

13. The instructor will queue source EDI data for you to retrieve and translate. Retrieve it by right-clicking your FTP input channel and selecting "Run Now." This should trigger the "Auto Translate EDI Purchase Orders" event rule you just wrote.

Note: Using ECS' Data Administrator, verify that the map's output was routed to the location designated in the target model and that functional acknowledgments were generated and delivered in response.

Take the Challenge Once you've successfully created and run your basic map, see if you can incorporate these more advanced concepts into your map rules.

Delta Manual "Data File Models" & "Working with Maps" chapters

1. Currently, every EDI purchase order is being mapped to the same data file. Instead, map each purchase order to an individual data file with a unique name based on today's date and time, and a numerical sequence.

Hint: From the data file object's General property page, select the The actual filename will be determined at translation/delivery time option. Then, go into the Delivery page of the map's properties, set the delivery method to file delivery, and establish the file naming conventions using the insertable functions available.

Delta Manual "Working with Maps" chapter

2. Set the map to deliver each data file to an ECS output channel. You can deliver to the same FTP output channel that you created for delivering functional acknowledgments.

Delta Manual "Mapping Overview" chapter

3. The "LineShipDate" field, which currently carries the ship date from the line item (detail) section of each line item, should use the ship date from the EDI header section when no ship date is available for the line item.

Hint: Use a variable to store the header ship date.

4. Only create POAddressInfo record types (record identifier #110) for ship-to addresses. Ignore all other address types.

Hint: Use a condition to differentiate between address types.

5. Test the edits you have made. When the map is producing reliable results, reinstall it and perform step 13 from the original set of blue project steps to run the map.

Purchase OrderEDI Implementation Conventions

ANSI X12

850 Purchase Order Dictionary: 4030

Header Usage Pos. No. Seg. ID Name Max. UseMandatory 10 BEG Beginning Segment for Purchase Order 1 Optional 20 CUR Currency 1 Optional 30 REF Reference Identification >1 Optional 40 FOB F.O.B. Related Instructions >1 Optional 50 DTM Date/Time Reference >1

LOOP ID N1Optional 60 N1 Name >1 Optional 70 N3 Address Information >1 Optional 80 N4 Geographic Location >1 Optional 90 PER Administrative Communications Contact >1

Detail Usage Pos. No. Seg. ID Name Max. Use

LOOP ID PO1Mandatory 100 PO1 Baseline Item Data Optional 110 PID Product/Item Description >1 Optional 120 DTM Date/Time Reference >1

Summary Usage Pos. No. Seg. ID Name Max. Use

LOOP ID - CTTOptional 130 CTT Transaction Totals >1 Optional 140 AMT Monetary Amount 1

SEGMENT: BEG - Beginning Segment for Purchase OrderLoop: 850.BEG Usage: Mandatory Data Element Summary

Usage Ref. Des. Name AttributesMandatory BEG01 353 - Transaction Set Purpose Code

00 Original 01 Cancellation

ID 2/2

Mandatory BEG02 92 - Purchase Order Type Code SA Stand-alone Order

ID 2/2

Mandatory BEG03 324 - Purchase Order Number AN 1/22 Mandatory BEG05 373 - Date DT 8/8

SEGMENT: CUR - CurrencyLoop: 850.CUR Usage: Optional Data Element Summary Usage Ref. Des. Name AttributesMandatory CUR01 98 - Entity Identifier Code

BY Buying Party (Purchaser)ID 2/3

Mandatory CUR02 100 - Currency Code ID 3/3

SEGMENT: REF - Reference IdentificationLoop: 850.REF Usage: Optional Data Element Summary Usage Ref. Des. Name AttributesMandatory REF01 128 - Reference Identification Qualifier

IA Internal Vendor Number VN Vendor Order Number

ID 2/3

Optional REF02 127 - Reference Identification AN 1/50

SEGMENT: FOB - F.O.B. Related InstructionsLoop: 850.FOB Usage: Optional Data Element Summary Usage Ref. Des. Name AttributesMandatory FOB01 146 - Shipment Method of Payment

CC Collect PP Prepaid (by Seller)

ID 2/2

SEGMENT: DTM - Date/Time ReferenceLoop: 850.DTM Usage: Optional Data Element Summary Usage Ref. Des. Name AttributesMandatory DTM01 374 - Date/Time Qualifier

010 Requested Ship 002 Requested Delivery

ID 3/3

Optional DTM02 373 - Date DT 8/8

SEGMENT: N1 - NameLoop: 850.N1 Usage: Optional Data Element Summary Usage Ref. Des. Name AttributesMandatory N101 98 - Entity Identifier Code

BY Buying Party (Purchaser) ST Ship To

ID 2/3

Optional N102 93 - Name AN 1/60 Optional N103 66 - Identification Code Qualifier

92 Assigned by Buyer or Buyer's Agent ID 1/2

Optional N104 67 - Identification Code AN 2/80

SEGMENT: N3 - Address InformationLoop: 850.N1.N3 Usage: Optional Data Element Summary Usage Ref. Des. Name AttributesMandatory N301 166 - Address Information AN 1/35 Optional N302 166 - Address Information AN 1/35

SEGMENT: N4 - Geographic LocationLoop: 850.N1.N4 Usage: Optional Data Element Summary Usage Ref. Des. Name AttributesOptional N401 19 - City Name AN 2/30 Optional N402 156 - State or Province Code ID 2/2 Optional N403 116 - Postal Code ID 3/15 Optional N404 26 - Country Code ID 2/3

SEGMENT: PER - Administrative Communications ContactLoop: 850.N1.PER Usage: Optional Data Element Summary Usage Ref. Des. Name AttributesMandatory PER01 366 - Contact Function Code

BD Buyer Name or DepartmentID 2/2

Optional PER02 93 - Name AN 1/60 Optional PER03 365 - Communication Number Qualifier

TE TelephoneID 2/2

Optional PER04 364 - Communication Number AN 1/256 Optional PER05 365 - Communication Number Qualifier

EM Electronic MailID 2/2

Optional PER06 364 - Communication Number AN 1/256

SEGMENT: PO1 - Baseline Item DataLoop: 850.PO1 Usage: Mandatory Data Element Summary Usage Ref. Des. Name AttributesOptional PO101 350 - Assigned Identification AN 1/20 Optional PO102 330 - Quantity Ordered R 1/15 Optional PO103 355 - Unit or Basis for Measurement Code

DZ Dozen EA Each PC Piece PR Pair

ID 2/2

Optional PO104 212 - Unit Price R 1/17 Optional PO106 235 - Product/Service ID Qualifier

UK EAN/UCC - 14ID 2/2

Optional PO107 234 - Product/Service ID AN 1/48 Optional PO108 235 - Product/Service ID Qualifier

VN Vendor's (Seller's) Item Number ZZ Mutually Defined

ID 2/2

Optional PO109 234 - Product/Service ID AN 1/48

SEGMENT: PID - Product/Item DescriptionLoop: 850.PO1.PID Usage: Optional Data Element Summary Usage Ref. Des. Name AttributesMandatory PID01 349 - Item Description Type

F Free-formID 1/1

Optional PID05 352 - Description AN 1/80

SEGMENT: DTM - Date/Time ReferenceLoop: 850.PO1.DTM Usage: Optional Data Element Summary Usage Ref. Des. Name AttributesMandatory DTM01 374 - Date/Time Qualifier

002 Delivery Requested 010 Requested Ship

ID 3/3

Optional DTM02 373 - Date DT 8/8

SEGMENT: CTT - Transaction TotalsLoop: 850.CTT Usage: Optional Data Element Summary Usage Ref. Des. Name AttributesMandatory CTT01 354 - Number of Line Items N0 1/6

SEGMENT: AMT - Monetary AmountLoop: 850.CTT.AMT Usage: Optional Data Element Summary Usage Ref. Des. Name AttributesMandatory AMT01 522 - Amount Qualifier Code

TT Total Transaction AmountID 1/3

Mandatory AMT02 782 - Monetary Amount R 1/18

Sample EDI Purchase Order

ST*850*0002 BEG*00*SA*1234564**20070208 CUR*BY*USD REF*IA*003 REF*VN*1024846 FOB*PP DTM*010*20070308 DTM*002*20070315 N1*ST*Wiki Warehouse 1*92*003 N3*2123 Terrace Dr. N4*Hilo*HI*96720-2411*USA PER*BD*Harold Shaw*TE*(808) 555-7890 N1*BY*Wiki Toys PO1*1*10*EA*19.99**UK*00004900000010*VN*98765 PID*F****Basketballs NBA Leather PO1*2*16*EA*2.25**UP*000049000001300*VN*98775 PID*F****Basketball Net Cotton CTT*2 AMT*TT*235.9 SE*20*0002

Purchase OrderTarget File Specifications

Data File Structure

Data file: POFileSampleData.txt Character Set: ASCII End of Record Delimiter: CRLF Field Delimiter: , Quote Character: Record Structure: - Purchase Order Header Record - Purchase Order Address Record - Purchase Order Line Item Record - Purchase Order Line Item Description Record

Purchase Order Header Record

Description: Purchase Order Header Information

Record Identifier: 100

Elements

Maps From

Name Type Required Format Description ANSI X12 EDIFACT

PONumber string No n/a Purchase Order Number BEG03 BGM02

PODate date No yyyyMMdd Purchase Order Date BEG05 DTM0102, when DTM0101 is 137

ShipDate date No yyyyMMdd Shipment Date (default for all items) DTM02, when DTM01 is 010

DTM0102, when DTM0101 is "010"

VendorID string No n/a Vendor's ID REF02, when REF01 is IA RFF0102, when RFF0101 is "IA"

DeliveryTerms string No n/a Delivery Terms of Payment FOB01 TOD02

Currency string No n/a Currency CUR02 CUX0102

Purchase Order Address Record

Description: Name, address, and contact information


Elements

Maps From


AddressType string No n/a Entity Type (e.g. Bill-To, Ship-To) N101 NAD01

Name string No n/a Entity Name N102 NAD0401

IDCode string No n/a Entity Code (such as Shipment Location Code or Vendor ID) N104 NAD0201

Address1 string No n/a Address Line 1 N301 NAD0501

Address2 string No n/a Address Line 2 N302 NAD0502

City string No n/a City Name N401 NAD06

Province string No n/a State or Province N402 N/A

PostalCode string No n/a Postal Code N403 NAD08

Country string No n/a Country N404 NAD09

ContactName string No n/a Contact Name PER02 CTA0202

ContactPhone string No n/a Contact Phone Number PER04, when PER03 is TE COM0101, when COM0102 is "TE"

Purchase Order Line Item Record

Description: Line Item Details


Elements

Maps From


PONumber string No n/a Purchase Order Number BEG03 BGM02

LineNum integer No n/a Order Line Number PO101 LIN01

Quantity integer No n/a Quantity Ordered PO102 QTY0102

UnitOfMeasure string No n/a Unit of Measure PO103 QTY0103

Price float No n/a Unit Price PO104 PRI0102

VendorPartNum string No n/a Vendor Part Number PO109 PIA0201

GTIN string No n/a Global Trade Identification Number PO107 LIN0301

LineShipDate date No yyyyMMdd Line Item Shipment Date

DTM02, when DTM01 is 010 (if a DTM segment exists in the PO1 loop)

DTM0102, when DTM0101 is "010" (if a DTM segment exists in the LIN loop)

Purchase Order Line Item Description Record

Description: Line Item Description (may repeat)


Elements

Maps From


Description string No n/a Product Description PID05 IMD0304

Sample Data File Layout

"100","A123456789","20040210","20040214","0001","CC","USD" "110","ST","Global Store #1","","1234 Main St.","WHSE A25","Johnson","CT","06549","USA","JOHN DAVIDSON","(123)4567890" "150","A123456789",1,22,"EA",7,"BA001","00123456789012","20040214" "160","Basketballs NBA Leather" "150","A123456789",2,15,"EA",9,"FB001","00123456789013","20040215" "160","Footballs NFL Leather" "150","A123456789",3,12,"EA",6.3,"SC001","00123456789014","20040216" "160","Soccer Balls AYSO Leather" "100","B987654321","20040211","20040215","0001","CC","USD" "110","ST","Global Store #2","","7019 Franklin Blvd.","","Albany","NY","12201","USA","","" "150","B987654321",1,44,"EA",2.2,"BB001","00123456789015","20040217" "160","Baseballs MLB Vinyl" "150","B987654321",2,4,"EA",1390.37,"WS001","00123456789016","20040218" "160","Windsurfing Board Blue Fiberglass" "150","B987654321",3,4,"EA",525.25,"WS002","00123456789017","20040219" "160","Sails for Windsurfing Boards Red Nylon" "100","C894561237","20040212","20040215","0001","PP","USD" "110","ST","Global Store #3","","45789 Crestview","WHSE 45C","Cherry Hill","NJ","08002","USA","JOHN DAVIDSON","(123)4567890" "150","C894561237",1,15,"EA",53.45,"FS035","00123456789018","20040220" "160","Rod/Reel Combos Shimano " "150","C894561237",2,22,"EA",2.24,"FS914","00123456789019","20040221" "160","Fishing Sinker Assortment Lead"

Purchase Order Audit

Purchase Order Audit

After mapping the test file titled POEDITestBatch.edi, your data file output should match the following descriptions:

The mapping of purchase order A123456789 should produce the following records:

One header record (record 100)

One address record (record 110)

Three line item records (record 150), each with three line item description records (record 160)

The mapping of purchase order B987654321 should produce the following records:


One address record (record 110)

Three line item records (record 150), each with three line item description records (record 160)

The mapping of purchase order C894561237 should produce the following records:


Two address records (record 110)

Two line item records (record 150), each with two line item description records (record 160)

The data file output should look like this (an electronic copy of this data is available in the project folder under the file name Project Blue Comparison File.txt):

"100","A123456789","20040731","20040731","0001","PP","USD" "110","ST","GLOBAL Store #2","549857","4366 Jamestown Way","","Tampa","FL","16549","USA","John Davidson","(123)4567890" "150","A123456789",1,22,"EA",7,"BA001","00123456789012","20040731" "160","Basketballs" "160","NBA" "160","Leather" "150","A123456789",2,15,"EA",9,"FB001","00123456789013","20040731" "160","Footballs" "160","NFL" "160","Leather" "150","A123456789",3,12,"EA",6.3,"SC001","00123456789014","20040731" "160","Soccer Balls" "160","AYSO" "160","Leather" "100","B987654321","20040731","20040731","0001","PP","USD" "110","ST","GLOBAL Store #2","16516519","4366 Jamestown Way","","Tampa","FL","16549","USA", "John Davidson","(123)4567890" "150","B987654321",1,44,"EA",2.2,"BB001","00123456789015","20040731" "160","Baseballs" "160","MLB" "160","Vinyl" "150","B987654321",2,4,"EA",1390.37,"WS001","00123456789016","20040731" "160","Windsurfing Board" "160","Blue" "160","Fiberglass" "150","B987654321",3,4,"EA",525.25,"WS002","00123456789017","20040731" "160","Sails for Windsurfing Boards" "160","Red" "160","Nylon" "100","C894561237","20040731","20040731","0001","CC","USD" "110","ST","GLOBAL Dist Center","81916551","4366 Jamestown Way","","Tampa","FL","16549","USA", "John Davidson","(123)4567890" "150","C894561237",1,15,"EA",53.45,"FS035","00123456789018","20040731" "160","Rod/Reel Combos" "160","Shimano" "150","C894561237",2,22,"BG",2.24,"FISHSNKASSRT","00123456789019","20040802" "160","Fishing Sinker Assortment" "160","Lead"

Purchase OrderEDI Implementation Conventions

EDIFACT

ORDERS Purchase Order Dictionary: D:96A

Header Usage Pos. No. Seg. ID Name Max. UseMandatory 10 BGM Beginning of message 1 Mandatory 20 DTM Date/time/period >1 Optional 30 RFF Reference >1

LOOP ID - NADOptional 40 NAD Name and address >1

LOOP ID CTA Optional 50 CTA Contact information >1 Optional 60 COM Communication contact >1

Optional 70 CUX Currencies >1 Optional 80 TOD Terms of delivery or transport >1

Detail Usage Pos. No. Seg. ID Name Max. Use

LOOP ID - LINOptional 90 LIN Line item >1 Optional 100 PIA Additional product ID >1 Optional 110 IMD Item description >1 Optional 120 QTY Quantity >1 Optional 130 DTM Date/time/period >1 Optional 140 PRI Price details >1

Summary Usage Pos. No. Seg. ID Name Max. UseMandatory 150 UNS Section control 1 Optional 160 CNT Control total >1

SEGMENT:BGM - BEGINNING OF MESSAGE Loop: ORDERS.BGM Usage: Mandatory COMPOSITE: BGM01 - C002 - DOCUMENT/MESSAGE NAME Loop: ORDERS.BGM.BGM01 Usage: Optional Data Element Summary Usage Ref. Des. Name Attributes Optional BGM0101 1001 - Document/message name, coded

220 Order ID 1/3

Optional BGM02 1004 - Document/message number AN 1/35 Optional BGM03 1225 - Message function, coded

1 Cancellation 9 Original

ID 1/3

SEGMENT:DTM - DATE/TIME/PERIOD Loop: ORDERS.DTM Usage: Mandatory COMPOSITE: DTM01 - C507 - DATE/TIME/PERIOD Loop: ORDERS.DTM.DTM01 Usage: Mandatory Data Element Summary Usage Ref. Des. Name Attributes Mandatory DTM0101 2005 - Date/time/period qualifier

10 Shipment date/time, requested 137 Document/message date/time 2 Delivery date/time, requested

ID 1/3

Optional DTM0102 2380 - Date/time/period AN 1/35 Optional DTM0103 2379 - Date/time/period format qualifier

102 CCYYMMDDID 1/3

SEGMENT:RFF - REFERENCE Loop: ORDERS.RFF Usage: Optional COMPOSITE: RFF01 - C506 - REFERENCE Loop: ORDERS.RFF.RFF01 Usage: Mandatory Data Element Summary Usage Ref. Des. Name Attributes Mandatory RFF0101 1153 - Reference qualifier

IA Internal vendor number VN Order number (vendor)

ID 1/3

Optional RFF0102 1154 - Reference number AN 1/35

SEGMENT:NAD - NAME AND ADDRESS Loop: ORDERS.NAD Usage: Optional Data Element Summary Usage Ref. Des. Name Attributes Mandatory NAD01 3035 - Party qualifier

BY Buyer ST Delivery party

ID 1/3

COMPOSITE:NAD02 - C082 - PARTY IDENTIFICATION DETAILS Loop: ORDERS.NAD.NAD02 Usage: Optional Data Element Summary Usage Ref. Des. Name Attributes Mandatory NAD0201 3039 - Party id. identification AN 1/35 Optional NAD0203 3055 - Code list responsible agency, coded

92 Assigned by buyer or buyer's agent ID 1/3

COMPOSITE:NAD04 - C080 - PARTY NAME Loop: ORDERS.NAD.NAD04 Usage: Optional Data Element Summary Usage Ref. Des. Name Attributes Mandatory NAD0401 3036 - Party name AN 1/35 COMPOSITE:NAD05 - C059 - STREET Loop: ORDERS.NAD.NAD05 Usage: Optional Data Element Summary Usage Ref. Des. Name Attributes Mandatory NAD0501 3042 - Street and number/p.o. box AN 1/35 Optional NAD0502 3042 - Street and number/p.o. box AN 1/35 Optional NAD06 3164 - City name AN 1/35 Optional NAD07 3229 - Country sub-entity identification AN 1/9 Optional NAD08 3251 - Postcode identification AN 1/9 Optional NAD09 3207 - Country, coded AN 1/3

SEGMENT:CTA - CONTACT INFORMATION Loop: ORDERS.NAD.CTA Usage: Optional COMPOSITE: CTA02 - C056 - DEPARTMENT OR EMPLOYEE DETAILS Loop: ORDERS.NAD.CTA.CTA02 Usage: Optional Data Element Summary Usage Ref. Des. Name Attributes Optional CTA0202 3412 - Department or employee AN 1/35

SEGMENT:COM - COMMUNICATION CONTACT Loop: ORDERS.NAD.CTA.COM Usage: Optional COMPOSITE: COM01 - C076 - COMMUNICATION CONTACT Loop: ORDERS.NAD.CTA.COM.COM01 Usage: Mandatory Data Element Summary Usage Ref. Des. Name Attributes Mandatory COM0101 3148 - Communication number AN 1/512 Mandatory COM0102 3155 - Communication channel qualifier

EM Electronic mail TE Telephone

ID 1/3

SEGMENT:CUX - CURRENCIES Loop: ORDERS.CUX Usage: Optional COMPOSITE: CUX01 C504 CURRENCY DETAILS Loop: ORDERS.CUX.CUX01 Usage: Optional Data Element Summary Usage Ref. Des. Name Attributes Mandatory CUX0101 6347 - Currency details qualifier

2 Reference currencyID 1/3

Optional CUX0102 6345 - Currency, coded ID 1/3 Optional CUX0103 6343 - Currency qualifier

9 Order currencyID 1/3

SEGMENT: TOD - TERMS OF DELIVERY OR TRANSPORT Loop: ORDERS.TOD Usage: Optional Data Element Summary Usage Ref. Des. Name Attributes Optional TOD02 4215 - Transport charges method of payment, coded

CC Collect PP Prepaid (by seller)

ID 1/3

SEGMENT:LIN - LINE ITEM Loop: ORDERS.LIN Usage: Optional Data Element Summary Usage Ref. Des. Name Attributes Optional LIN01 1082 - Line item number N 1/6

COMPOSITE:LIN03 - C212 - ITEM NUMBER IDENTIFICATION Loop: ORDERS.LIN.LIN03 Usage: Optional Data Element Summary Usage Ref. Des. Name Attributes Optional LIN0301 7140 - Item number AN 1/35 Optional LIN0302 7143 - Item number type, coded

EN International Article Numbering Association (EAN)ID 1/3

SEGMENT:PIA - ADDITIONAL PRODUCT ID Loop: ORDERS.LIN.PIA Usage: Optional Data Element Summary Usage Ref. Des. Name Attributes Mandatory PIA01 4347 - Product id. function qualifier

5 Product identificationID 1/3

COMPOSITE:PIA02 - C212 - ITEM NUMBER IDENTIFICATION Loop: ORDERS.LIN.PIA.PIA02 Usage: Mandatory Data Element Summary Usage Ref. Des. Name Attributes Optional PIA0201 7140 - Item number AN 1/35 Optional PIA0202 7143 - Item number type, coded

VN Vendor item number ZZZ Mutually defined

ID 1/3

SEGMENT:IMD - ITEM DESCRIPTION Loop: ORDERS.LIN.IMD Usage: Optional Data Element Summary Usage Ref. Des. Name Attributes Optional IMD01 7077 - Item description type, coded

F Free-formID 1/3

COMPOSITE:IMD03 - C273 - ITEM DESCRIPTION Loop: ORDERS.LIN.IMD.IMD03 Usage: Optional Data Element Summary Usage Ref. Des. Name Attributes Optional IMD0304 7008 - Item description AN 1/35 Optional IMD0305 7008 - Item description AN 1/35

SEGMENT:QTY - QUANTITY Loop: ORDERS.LIN.QTY Usage: Optional COMPOSITE: QTY01 - C186 - QUANTITY DETAILS Loop: ORDERS.LIN.QTY.QTY01 Usage: Mandatory Data Element Summary Usage Ref. Des. Name Attributes Mandatory QTY0101 6063 - Quantity qualifier

21 Ordered quantityID 1/3

Mandatory QTY0102 6060 - Quantity N 1/15 Optional QTY0103 6411 - Measure unit qualifier

BG bag C62 piece DZN dozen EA each PR pair

ID 1/3

SEGMENT:DTM - DATE/TIME/PERIOD Loop: ORDERS.LIN.DTM Usage: Optional COMPOSITE: DTM01 - C507 - DATE/TIME/PERIOD Loop: ORDERS.LIN.DTM.DTM01 Usage: Mandatory Data Element Summary Usage Ref. Des. Name Attributes Mandatory DTM0101 2005 - Date/time/period qualifier

10 Shipment date/time, requested 2 Delivery date/time, requested

ID 1/3

Optional DTM0102 2380 - Date/time/period AN 1/35 Optional DTM0103 2379 - Date/time/period format qualifier

102 CCYYMMDDID 1/3

SEGMENT:PRI - PRICE DETAILS Loop: ORDERS.LIN.PRI Usage: Optional COMPOSITE: PRI01 - C509 - PRICE INFORMATION Loop: ORDERS.LIN.PRI.PRI01 Usage: Optional Data Element Summary Usage Ref. Des. Name Attributes Mandatory PRI0101 5125 - Price qualifier

AAA Calculation netID 1/3

Optional PRI0102 5118 - Price N 1/15

SEGMENT:UNS - SECTION CONTROL Loop: ORDERS.UNS Usage: Mandatory Data Element Summary Usage Ref. Des. Name Attributes Mandatory UNS01 0081 - SECTION IDENTIFICATION ID 1/1

SEGMENT:CNT - CONTROL TOTAL Loop: ORDERS.CNT Usage: Optional COMPOSITE: CNT01 - C270 - CONTROL Loop: ORDERS.CNT.CNT01 Usage: Mandatory Data Element Summary Usage Ref. Des. Name Attributes Mandatory CNT0101 6069 - Control qualifier

2 Number of line items in message 23 Total ordered quantity

ID 1/3

Mandatory CNT0102 6066 - Control value N 1/18

Sample EDI Purchase Order

UNH+0034+ORDERS:D:96A:UN' BGM+220+A123456789+9' DTM+137:20040731:102' DTM+10:20040731:102' RFF+IA:0001' RFF+VN:VENDOR5428' NAD+ST+549857::92++GLOBAL Store #2+4366 Jamestown Way+Tampa+FL+16549+USA' CTA++:John Davidson' COM+(123)4567890:TE' CUX+2:USD:9' TOD++PP' LIN+1++00123456789012:EN' PIA+5+BA001:VN' IMD+++:::Basketballs' IMD+++:::NBA' IMD+++:::Leather' QTY+21:22:EA' PRI+AAA:7' LIN+2++00123456789013:EN' PIA+5+FB001:VN' IMD+++:::Footballs' IMD+++:::NFL' IMD+++:::Leather' QTY+21:15:EA' PRI+AAA:9' LIN+3++00123456789014:EN' PIA+5+SC001:VN' IMD+++:::Soccer Balls' IMD+++:::AYSO' IMD+++:::Leather' QTY+21:12:EA' PRI+AAA:6.3' UNS+S' CNT+2:3'

Project Green:Data File to EDI Invoice

Retrieve data file exported by internal systems

Submit data file to appropriate Delta map

During mapping, dynamically assign EDI addressing information

based on intended invoice recipient

END

Deliver EDI invoices to ECS output channel

Project Green: Data File to EDI Invoice

For this project, ASPI needs to:

Translate the invoice data produced by its accounting system into outgoing EDI invoices destined for Global Enterprises and Wiki Toys

Dynamically address those outgoing EDI invoices based on information stored in Trading Partner Manager

Project Green Steps


1. Create a user-defined code table named "Charges" that substitutes the charges/allowances codes found in the source data file for their corresponding EDI codes (Tools|User Defined|Code Tables). The code table should use the values found in the following table. This code table should be referenced (as part of a code lookup rule) by the map you'll create for this project.

Code (Data File Value) SAC02 Code (ANSI X12) C214/7161 Code (EDIFACT)

PR F800 PAD

FR D240 FC

SP H090 SH

Delta Manual "Setting Map Parameters" chapter

2. Using the source model titled InvoiceDataFile.bom and the target model titled ASPI_INVOICE.bom, create the initial parameters of your map. Both of these models can be found in the "X12" or "EDIFACT" subfolder (depending on which standard you're working in) of the "Data File to EDI Invoice (Project Green)" project folder. This step requires additional detail:

2a. During the initial map creation Merlin, set the map's delivery to the ECS output channel titled "FTP Output to Training Server" (you should have already created this output channel for project blue) and set the To field's value to "Invoice.edi."

2b. Also in the Merlin, establish ASPI as the sending trading partner and, for the receiving trading partner, establish a trading partner lookup against the local identifier in Trading Partner Manager that carries the vendor ID.

Hint: Use the printed data file specifications that are provided in the "Project Resources" area of your training binder (green folder) to determine which field in the source file contains the vendor ID value.


3. Once the map's initial parameters are set, write the map's rules.

Hint: Use the printed X12 or EDIFACT EDI specifications that are provided in your training binder (green folder) to assist with mapping. There is a column in these specifications that indicates how the fields in the source model should be mapped to the EDI elements in the target model.

Delta Manual "Testing Your Map" chapter

4. Validate the map.

5. Test the map. Delta will prompt you to select the source data file. Use the InvoiceSourceData.txt file, found in the project folder.

6. Verify that the map's EDI output is correct. You can use the invoice audit document that is provided in your training binder (green folder) to verify the accuracy of the output.

Delta Manual "Putting Maps Into Production" chapter

7. Once your map is producing reliable results, install it.

ECS Management Console Guide "Input Channels" chapter

8. Open Softshare ECS's Management Console. Create a new file input channel with the parameters listed in the following table (leave the default values in place for all parameters not listed here). This input channel will be used to retrieve the source data file.

Tab Setting Value

General

Name File Input for Invoice Data

Directory C:\ECS_Outbox

File Pattern *.txt

ECS Management Console Guide "Event Rules" chapter

9. Also in Management Console, create a "Translate using Softshare Delta" event rule with the following parameters (leave the default values in place for all parameters not listed here). This event rule is responsible for routing data from your file input channel to the appropriate Delta map.

Tab Setting Value

Translate Using

Event Name Translate Invoice Data

Source File Input for Invoice Data

10. Copy the InvoiceSourceData.txt file from the project folder to the C:\ECS_Outbox folder.

11. Right-click your file input channel and select "Run Now." This should retrieve the source data and trigger the "Translate Invoice Data" event rule you just wrote, causing your map to run.

12. Check the directory used by your FTP output channel to verify receipt of the translated EDI invoices.

Hint: The invoices should be located in a file titled "Invoice.edi" because that's the file name you provided when initially setting the map's delivery in step 2.

Take the Challenge

Once you've successfully created and run your basic map, see if you can incorporate these more advanced concepts into your map rules.


1. Only create line item description segments for line items that have no GTIN present in the source data file.

Hint: Use a condition to run the line item description segment object creation rule based on the presence of a GTIN.

2. Calculate net line amount and 15% tax rate for each line item and store these values in their appropriate detail level segments.

Hint: Use the printed EDI specifications that are provided in your training binder (green folder) to assist with this challenge. There is a column in these specifications that indicates what value each element in the EDI invoice should carry and those that relate to this challenge are proceeded with the word "Challenge."

3. Calculate the total of all net line item amounts; allowances and charges; tax; and the resulting total invoice amount (if working with ANSI X12, total invoice amount will have already been mapped since this is mandatory for 810 invoices). Store these values in their appropriate summary level segments.

Hint: Again, refer to the printed EDI specifications for assistance in determining where these calculated values should go in the EDI invoice.


4. Deliver the map's EDI output to different files, depending on each invoice's intended recipient. In other words, all invoices destined for Wiki Toys should go to a different file than those destined for Global Enterprises. To accomplish this:

4a. Change the map's delivery to the Use Trading Partner Manager to determine delivery method option. This is done from Delivery page of the map's properties.

Hint: Don't change the sender/receiver trading partner information. The trading partner lookup you previously configured is still valid for this challenge scenario.

4b. In Trading Partner Manager, adjust the trading partner entries for Wiki Toys and Global Enterprises so that the output from this project's map (and this project's map only) is delivered to trading-partner-specific files (e.g. "Wiki_Invoices.edi" and "Global_Invoices.edi") via the ECS output channel titled "FTP Output to Training Server."

Hint: Set an advanced delivery binding (based on map delivery criterion) from each trading partner entry's Delivery page.

Note: Each time new EDI invoices are generated for Wiki Toys or Global Enterprises, they are appended to the file already present in the FTP directory.

5. Test the edits you have made. When the map is producing reliable results, reinstall it and perform steps 10-12 from the original set of green project steps to run the map.

InvoiceSource File Specifications

Data File Structure

Data file: InvoiceSourceData.txt Character Set: ASCII End of Record Delimiter: CRLF Field Delimiter: , Quote Character: Record Structure: - Invoice Header Record - Invoice Address Record - Invoice Charges and Allowances Record - Invoice Line Item Record - Invoice Line Item Description Record

Invoice Header Record

Description: Invoice Header Information


Elements

Name Type Required Format Description

PONumber string No n/a Purchase Order Number

InvNumber string No n/a Invoice Number

PODate date No yyyyMMdd Purchase Order Date

ShipDate date No yyyyMMdd Shipment Date (default for all items)

VendorID integer No Vendor's ID

DeliveryTerms string No n/a Delivery Terms of Payment PP Pre-paid CC Collect

TermsNetDays integer No Payment Terms - Net Days

TermsDiscDays integer No Payment Terms - Discount Days

TermsDiscPerc float No n/a Payment Terms - Discount Percent

Currency string No n/a Currency

Invoice Address Record

Description: Name, Address, and Contact Information


Elements


AddressType string No n/a Entity Type (such as Bill-To, Ship-To)

Name string No n/a Entity Name

IDCode string No n/a Entity Code (such as Shipment Location code or Vendor ID)

Address1 string No n/a Address Line 1

Address2 string No n/a Address Line 2

City string No n/a City Name

Province string No n/a State or Province

PostalCode string No n/a Postal Code

Country string No n/a Country

ContactName string No n/a Contact Name

ContactNumber string No n/a Contact Phone Number

Invoice Charges and Allowances Record

Description: Invoice Charges and Allowances


Elements


Indicator string No n/a Charge/Allowance Indicator Flag A Allowance C Charge

Code string No n/a

Charge/Allowance Type Code PR Promotional (Allowance) FR Freight (Charge) SP Special Handling (Charge)

Amount float No n/a Charge/Allowance Amount

Description string No n/a Charge/Allowance Description

Invoice Line Item Record

Description: No description


Elements


InvNumber string No n/a Invoice Number

LineNum string No n/a Invoice Line Number

Quantity integer No Quantity Invoiced

UnitofMeasure string No n/a Unit of Measure

Price float No n/a Unit Price

VendorPartNum string No n/a Vendor Part Number

GTIN string No n/a Global Trade Identification Number

LineShipDate date No yyyyMMdd Line Item Shipment Date

Invoice Line Item Description Record

Description: Line Item Description (may repeat)


Elements


Description string No n/a Product Description

Sample Data File Layout

"100","A123456789","INV23457","20040210","20040214","002","CC",30,10,1.5,"USD" "110","ST","Global Store #1","","1234 Main St.","WHSE A25","Johnson","CT","06549","USA","","" "110","SF","ASPI Warehouse","12345","911 Olive St.","","Santa Barbara","CA","