Liaison presented a case study of how their software helped Antigua Group become compliant with a new requirement from one of their customers, Kohls.com. Antigua needed to include invoice numbers on Advance Ship Notices, but the invoices were created after the notices. Liaison's Delta and ECS products allowed Antigua to map XML documents between their ERP and trading partners, and automate processes so the ECS system could retrieve an invoice number and include it on the notice. This integration helped Antigua streamline their EDI operations and meet their customer's needs.

1. @LiaisonTech
Easy EDI: It Does Exist
Featuring valued customer

2. @LiaisonTech
Reasons to Watch This Presentation
• A major client or supplier is asking you to exchange EDI
or XML
• You are upgrading your ERP system and need to
rewrite all of your data translation maps
• Your current data integration solution is out of date and
is no longer supported
• Resources are tight. You need every tool you bring into
IT to do more than just satisfy one project
Image courtesy of Wildbeast1 on Flickr

3. @LiaisonTech
Benefits of Data Integration
SAVE MONEY
– Eliminate paper
• eliminate lost mail or garbled faxes
• reduce paper, printing and postage costs
• reduce paper document processing and filing costs
SAVE TIME
– Eliminate document re-keying
• eliminate human re-keying errors (1% to 3%)
• faster document processing means faster capture of
sales recognition and payments
INCREASE COMPETITIVE ADVANTAGE
– Better visibility
• electronic data can be processed at any time
• data lets you know, plan and respond to market
conditions
– Higher score-carding
• Streamline supply chain processes
• Provide clients with higher system visibility
– Use the software for A2A and B2B
2008 Aberdeen report
“A Comparison of Supplier
Enablement Around the World”
showing savings of EDI in average
PO requisition processing costs
Paper EDI
North
America
$37.45 $23.83
EMEA $42.90 $34.05
APAC $23.90 $14.78

4. @LiaisonTech
On-Premise Software Used at Antigua
4
Communications server software. Provides AS2 connection.
Access to data repository. Proactive alert notifications.
Universal data translator. Supports EDI, XML, data file,
database and custom report view formats.
Stores all documents sent and received through system.
Archive. Used to store all data translation maps and versions.

5. @LiaisonTech
Integration Solution Offerings – ECS and Delta
• Delta is an any-to-any mapping and data translation tool.
• ECS is a communication server supporting a wide variety of data
transfer protocols and standards.
• Delta and ECS combined provide an enterprise application
integration (EAI) solution capable of coordinating the many diverse
applications, databases and e-commerce formats found across the
enterprise.
• Delta and ECS combined provide a business to business (B2B)
solution capable of coordinating all trading partner requirements as
an extension of the enterprise.

6. @LiaisonTech 6
Types of Business Object ModelsTypes of Business Object Models
Model Type Source Target
EDI (ANSI X12, EDIFACT, TRADACOMS) √ √
XML √ √
Data file (flat and formatted files such as comma
delimited or SAP IDOC)
√ √
Database (OLE DB or ODBC access) √ √
Text (plain text or HTML) √

7. @LiaisonTech
Delta Modeling
7
Creating an XML Model
Creating an XML ModelCreating an XML Model
Creating an EDI ModelCreating an EDI Model

8. @LiaisonTech
The Antigua Group
8
• One of the nation’s leading designers and
marketers of men’s, women's and
children's lifestyle apparel and sportswear
Golf
Licensed Sports
Corporate
Specialty Retail
• 30+ years serving
• Founded on 1979; based in Peoria, AZ
NBA
MBL
Arena Football
NHL
hundreds of colleges and universities
NFL
• Holds licenses with major professional sports
leagues:
• 9500 customers
• 258 Employees, 55 sales Representatives

9. @LiaisonTech
Antigua’s Situation
9
• In 2006 Antigua began the process of migrating from BPCS to Lawson’s M3
• Lawson’s EDI module which is the Movex Enterprise Collaborator
(M.E.C) transacts with XML documents

10. @LiaisonTech
• 30 active trading partners with 6 maps each that needed to be translated
from EDI to XML and back
Antigua’s Situation

11. @LiaisonTech
• Existing EDI systems were outdated and consisted of custom made
applications developed in house to support the exchange of information
Antigua’s Situation

12. @LiaisonTech
• The processing of these transactions was manual and very tedious.
Antigua’s Situation
• 275 average daily inbound transactions and 539 average daily utbound
transactions
• Common EDI: 812 Debit/Credit Adjustment,820 Remittance Advice,850 Purchase Orders,860
PO changes, 810 Invoices,856 Advance Ship Notice’s, 753 Request for Routing Instructions,754
Routing Instructions

13. @LiaisonTech 13
• It is an application that can easily integrate with our ERP’s EDI module.
EDI softwareEDI software
Movex Enterprise
Collaborator M.E.C.
Movex
?
• It is a system that fit the budget allocated for our EDI implementation.
• It is an EDI system, NOT another ERP.
Solution = Liaison’s Delta/ECS

14. @LiaisonTech
• It is a user friendly system that is easy to learn and maintain.
• It is a system that helped us automate the manual process involved in
receiving, translating, generating and sending EDI transactions.
Solution = Liaison’s Delta/ECS
• It is an adaptable system that included all the functionality we needed and
more.
• It is system that has a modeling tool that allowed us to create all the maps
needed to go live in a very short amount of time.

15. @LiaisonTech
Using Liaison’s Delta and ECS
• 2008 – Antigua goes live on M3, 30 active trading partners are set up in
Delta and MEC. 170 maps were created, generated, translated and tested
within 4 months. EDI goes live and is stable on day 1.
• 2009 – ALL inbound transactions are placed on automatic processing thru
Delta/ECS. These included the translation of payment remittances and
Debit/Credit Adjustments to reports that automatically forwarded to our
credit department.
• 2009 – Integrated Delta with our Universal Product Code generator to
create the 832 Price/Sales Catalog.

16. @LiaisonTech
• 2010 – Outbound transactions for Invoices are automatically processed
using Delta/ECS. We started transitioning all trading partner’s Advance
Ship Notices to automatic processing by putting them on a schedule where
ECS picks up the documents to be sent at certain times of the day.
• 2010 – Kohls.com becomes a trading partner and requires that their
invoice number is sent with the Advance Ship Notice. Delta/ECS makes
this possible.
• November 2010 – Kohls Retail becomes a trading partner.
• 2011 – Antigua used Delta and ECS to integrate the online ordering
system with MEC to bring in orders from our sales force in to the ERP.
• 2011 – Antigua used Delta and ECS to create and deliver order
confirmations from the ERP to our sales force.
• 2009 – Alerts and watch dogs are put into place to inform our EDI
coordinator that there are transactions that need attention both in the
inbound and outbound processes.
Using Liaison’s Delta and ECS

17. @LiaisonTech
How Delta/ECS help us be Compliant with
Kohls.com
When Kohls.com became a trading partner in 2010 they required Antigua to
include their Invoice number on the Advance Ship Notices they receive.
Problem 2. Billing Records that create the Invoice are created after
Shipment confirmation. Confirmation creates the ASN. How can you
include information in the ASN that is not yet created.
Problem 3. MEC does not communicate back to Movex after it has
received the XML to update the files
Problem 1. This is a Mandatory Data segment and we need to be
compliant

18. @LiaisonTech
MEC receives and
translates the MBM and
creates an Advance ship
notice in the form of an
xml document
A Movex Business
Message is created
and sent to MEC to
generate an ASN
Customer Orders
are confirmed for
shipment in
Movex
A Movex creates
billing records
Movex
Business
Message in
.xml
Advance Ship
Notice in .xml
ECS receives the
.XML through an
input channel
ECS send the .edi to
the VAN
M3
A
A Delta Map
translates the .XML to
an .edi
Advance Ship
Notice in .edi
Movex is updated
after the MBM has
been generated
Advance Ship Notice Process Flow

19. @LiaisonTech
Invoice Process Flow
An Invoice is created
from Billing records
created during
confirmation
M3
A Movex Business
Message is created
Movex
business
message in
.xml
MEC receives and
translates MBM and
creates an invoice in
the form of an xml
document
Invoice in .xmlECS send the .edi to
the VAN
B
Invoice in .edi
The MBM is sent to
MEC to generate an
INVOICE in XML
format
Movex is updated
after the MBM has
been generated
ECS receives the
.XML through an
input channel
A Delta Map
translates the .XML to
an .edi

20. @LiaisonTech
MEC receives and
translates the MBM and
creates an Advance ship
notice in the form of an
xml document
A Movex Business
Message is created
and sent to MEC to
generate an ASN
Customer Orders
are confirmed for
shipment in
Movex
A Movex creates
billing records
Movex
Business
Message in
.xml
Advance Ship
Notice in .xml
ECS receives the
.XML through an
input channel
ECS send the .edi to
the VAN
M3
A
A Delta Map
translates the .XML to
an .edi
Advance Ship
Notice in .edi
Movex is updated
after the MBM has
been generated
INVOICE NUMBER
What needs to happen for Kohls ASN’s

21. @LiaisonTech
How we became compliant
MEC receives and
translates the MBM and
creates an Advance ship
notice in the form of an
xml document
A Movex Business
Message is created
and sent to MEC to
generate an ASN
Customer Orders
are confirmed for
shipment in
Movex
A Movex creates
billing records
Movex
Business
Message in
.xml
Advance Ship
Notice in .xml
ECS receives the
.XML through an
input channel
ECS send the .edi to
the VAN
M3
A
A Delta Map
translates the .XML to
an .edi
Advance Ship
Notice in .edi
Movex is updated
after the MBM has
been generated
We configured Movex not to send an MBM to generate the ASN.

22. @LiaisonTech
Invoice Process Flow
Create Invoice from
Billing records
created during
confirmation
A Movex Business
Message is created
and sent to MEC to
generate an Invoice
Movex
business
message in
.xml
MEC receives and
translates MBM and
creates an invoice in
the form of an xml
document
Invoice.xml
How we became compliant
We invoiced the customer order, that created a Movex Business Message that is sent to the
MEC

23. @LiaisonTech
We created a Delta Map to translate the XML invoice to a XML Movex Business Message. We
then had ECS forward that XML document to MEC to create the ASN.
How we became compliant

24. @LiaisonTech
How we became compliant
We created a Delta Map to translate the XML invoice to a XML Movex Business Message. ECS
forward’s that XML document to MEC to create the ASN.
An Invoice is created
from Billing records
created during
confirmation
M3
A Movex Business
Message is created
Movex
business
message in
.xml
MEC receives and
translates MBM and
creates an invoice in
the form of an xml
document
Invoice in .xml
B
The MBM is sent to
MEC to generate an
INVOICE in XML
format
Movex is updated
after the MBM has
been generated
ECS receives the
.XML through an
input channel
A Delta Map
translates the .XML to
a Movex Business
Message
Movex
business
message in
.xml
ECS forwards the
MBM .xml to MEC

25. @LiaisonTech
MEC receives the MBM and generates an Advance Ship Notice that contains the Invoice
number.
How we became compliant

26. @LiaisonTech
An Invoice is created
from Billing records
created during
confirmationM3
A Movex Business
Message is created
Movex
business
message
in .xml
MEC receives and
translates MBM and
creates an invoice in
the form of an xml
document
Invoice
in .xml
The MBM is sent to
MEC to generate an
INVOICE in XML
format
Movex is updated
after the MBM has
been generated
ECS receives the
Invoice.XML through
an input channel
A Delta Map
translates the
Invoice.XML to a
Movex Business
Message
Movex
business
message
in .xml
ECS forwards the
MBM .xml to MEC
 ECS receives the ASN that contains the Invoice number. A Delta Map translates it to an .EDI and executes another
Delta Map that updates the files in Moves to indicate that the ASN has been generated. ECS then sends the .EDI to the
van.
MEC receives and
translates MBM and
creates an Advance ship
notice in the form of an
xml document
Advance
Ship
Notice
in .xml
ECS send the .edi
to the VAN
ECS receives the
ASN.XML through an
input channel
A Delta Map
translates the ASN
.XML to an ASN.EDI
A Delta Map runs to
update the files in
Movex to indicate that
the ASN has been
generated
How we became compliant

27. @LiaisonTech
Benefits of Using Liaison Delta/ECS
27
• Streamlined transaction processing
• Faster trading partner setup time
• Smoother integration with the ERP
• Improved retailer relationships
• Reduced labor requirements

28. @LiaisonTech 28

29. @LiaisonTech
Solutions
•Data Integration
•Data Management
•Data Security
Multinational
•Global headquarters in Atlanta
•European offices in Finland,
Netherlands, Sweden, UK
•More than 7000 customers
worldwide in over 46 countries
Visit Antigua here
For more
presentations:
Liaison Webinars
ABOUTLIAISON
29
Additional Resources