Simple EDI based on ebXML

EDI Today
Legacy EDI
+ Contributing to the productivity of the
present- day economy through the rapid
information exchange among the major
companies, if the exchange is continuance,
frequent and plenty of.
BUT
- Lacking the flexibility and cannot follow the
rapid Business Process Reengineering today.
- Requiring the intricate agreements and the
testing on EDI between the parties by the
person in charge, before starting the business.
- Being difficult to expand EDI world in SME’s
because of the expensive cost and the special
EDI skills.
Web EDI
+ Easy to implement and to access
the electronic datas when you have a
PC with a normal browsing software.
BUT
- Requiring the human operation
always and Inviting the errors
sometimes, because the Web services
don’t provide the automation of the
EDI data handling.
- Being difficult to continue the
rapid and frequent EDI through
Client-Server based system
depending on the human handling.

There is a Solution
95% of FORTUNE 1000 are using EDI
XML/EDI ==> ebXML
BUT
Standardization
Only 2% of Other SME’s are using EDI
 Web EDI

A-Web
Server
HTML on HTTP

B-Web
Server
 XML

XML (Extensible Mark up Language)

offers exciting new opportunities for the
exchange of business data, be that
application-to-application, application-to-
person or person-to-application.
 Standardization is the key to success
Semantics

<DeliveryDate>
g [Goods delivery]?
Receive g [Child birth]?

XML document

Dictionary

IT component
IT service functions

Translate Display
Link
Store
Comm Display
Link

Store
Standardized EC with
Translate Comm
XML technologies
 XML used in e-Business

XML
ebXML Initiative
diffusion

Chaos to
Digital economy realization
Tower of Babel
by standardized IT infrastracture

1998 1999 2000 2001 2002 year

Awareness Proliferation Products Implementation
Standardization
 ebXML Initiative
Purpose : To research and identify the technical basis upon which the global
implementation of XML can be standardized.

Goal : To provide an open technical framework to enable XML to be utilized in a

consistent and uniform manner for the exchange of Electronic Business data in
application to application, application to person and person to application
environments.

Terms : November/1999 – May/2001

Creating a Single Global Electronic Market

Participants :
OASIS,UN/CEFACT,ANSI-X12,DISA,NIST,ISO-TC154,CEN-ISSS,EAN,
DIN,EBES,HL7,SWIFT,OMG,OAG,OTA,CommerceNet,IBM,SUN,
Microsoft,Oracle,RosettaNet,Amazon,AIAG,Boeing,BT,Dun&Bradstreet,
Bank-of-America,JIPDEC,Taipei-III,KIEC…..
 ebXML Requirement
1. Expand the Scope of EC
+ Inter-Company / Industry / Cross-Industry
+ Global companies / SMEs
+ Domestic / International
2. Openness
+ Open access by Human and Maschine
3. Interoperability
+ Business Process and Information Model
Sharing
+ Connectivity in the means of IT
+ Easy migration from Legacy EDI
4. Security
+ Authentication / Integrity / Non-repudiation
& Confidentiality
 ebXML Architecture

Business ContextFor Business Core

Process Document BuiltWith Components
ReferenceTo
Register

Repository Fill other Role

Fill one Role

Profile agree Agreement agree Profile

Business Business
Service
Collaboration Service
Transport
Message
 Business Transaction
Unit of Work
Requesting Responding
Activity Activity
Request Document

SignedReceipt Non-
Non-
Repudi Repudi
ation ation
Response Document

Time-Outs

Success Failure

Legally Binding
Core Component
Core Component(CC)

Party
Party identifier
Context
Name
Address Zip code
State
Internal system
City
Scenario
Building
CC Business Objects

Message exchange Methods

Attributes
CC
 Registry & Repository
Other Registry Other Registry

Company Standard
Profiles Elements

CPA
Negotiation Software
Standard Development
Development
* Standard Elements
Process Paterns Messages
ebXML
Core Component Software Packages
Implementation
Common Business Objects
 Collaboration-Protocol Agreements (CPA)
CPA
CPA ID
CPP negotiate Party’s information negotiate
CPP
For 1 - Party A 2 For
Party A - Party B
Party B
Transport Protocol
Transport Security
DocExchange Protocol
Link to Process-
3 3 Agreed
Agreed Specification Doc.
CPA
CPA Agree- Retry Agree-
ment on -etc. ment on
CPA has CPA has
arrived. arrived.

4 Start Business activities with each other

 Messaging Service
ebXML Applications
Message Service Interface
Based on SOAP
ebXML Message Envelope (MIME)
Message Service

Header Envelope (MIME)

Error Handling
Management

Header Information (XML)

Security
Message Envelope (MIME)

Payload

Communication Interface

HTTP SMTP IIOP FTP Other

 ebXML Specifications
Business Process

Core Component

R&R
R&R : Registry & Repository
CPA : Collaboration Protocol Agreement

CPA

Company-A Company-B

ebXML Messaging
 Current status of ebXML

1. Standard Models not completed

+ Problems on the portability of BPM
+ Problems on the language translation of CC
2. No consensus on the XML Instanciation of CC
3. Early for implementing the full specification of ebXML
+ Development stage of Domain Models
+ Full works on Modeling/Design Required in
each Implementation

Modeling/Design Experts with Expensive Cost

 R&R ebXML
CC BP Partner’s Implementation
Library Scenario CPP
Image
Cooperate System(ebXML Interface)

BP CPA
Composer Negotiation CPA Negotiation

Set
Protocol

Collaboration
Engine Transaction
Document
Composer Business
Document
 Requirement for Simplification

1. Plug and Play

+ Non-expensive Packaged Solution
+ No need for the Special Skills
2. Bridge from the Legacy EDI
+ Easy to migrate from the Legacy EDI
+ Cooperation with Legacy EDI

ebXML Requirement Specification

 Simple EDI in Japan

Exchange the pre-defined business documents

on the pre-defined business process.

ebXML Specification Simple EDI

Business Process Can be used for collaboration engine

Core Componjent Pre-defined (XML Instance from CII)

Registry & Repository Repository for the standard elements

Partner Agreement Not used

Messaging ebXML Messaging Service
 EDI Message Format
UN/EDIFACT

DTM+4:20001916:102’LIN+LX254+500’DTM+75:20000925:102’LIN + CT201+100’...

16Sep2001
Order Date Quantity Date Quantity
Order Form Order Date Name Delivery Name
(Qualifier)
of Goods of Goods
To ABC Company Segment ID CCYYMMDD CCYYMMDD
Segment ID
Delivery (Qualifier)

From XYZ Company Date

CII (Syntax rules for Cross-industry Information Interchange)
Name Quantity Delivery
011 8 20000916 022 5 LX254 015 3 500 031 8 20000925 --- ---
LX254 500 9/25
CT201 100 10/10 Order Date Goods Name Quantity Delivery Date
TI115 300 10/12 Length Length Length Length
Tag:Order Date Tag:Name Tag:Quantity Tag:Delivery Date

XML
Paper Form
<Order>
<OrderDate>20000916</OrderDate>
<Name>LX254</Name> <Qty>500</Qty> <DelDate>20000925</DelDate>
<Name>CT201</Name> <Qty>100</Qty> <DelDate>20001010</DelDate>
<Name>TI115 </Name> <Qty>300</Qty> <DelDate>20001012</DelDate>
</Order>
 CII <-> XML Mapping
CII Data Element
Data TAG Length Data Value

</‘JP’
<‘JP’ Copy
+CII_TAG>
+CII_TAG>

Starting TAG Data Value Ending TAG

XML Element
 CII/XML Example
<?xml version="1.0"
encoding="Shift_JIS" ?> <JPC31></JPC31>
<?xml-stylesheet <JPC32></JPC32> <JPM5>
href="HWSWXSL4.xsl" <JPC33></JPC33> <JPM5R>
type="text/xsl" ?> <JPC34></JPC34> <JP27104>50250</JP27104>
<CII-HWSW001A0110-V10> <JPC35></JPC35> <JP27105>40500</JP27105>
<!– HW/SW EDI 001A Product </JPMGH> <JP27106>65125</JP27106>
Information --> <JPTRM SEQ="1"> </JPM5R>
<JPMGH> <JP27001>00001</JP27001> <JPM5R>
<JPC03>0</JPC03> <JP27002>0110</JP27002> <JP27104>39765</JP27104>
<JPC04></JPC04> <JP27003>19990602</JP27003> <JP27105>82233</JP27105>
<JPC05></JPC05> <JP27187>171539</JP27187> <JP27106>45015</JP27106>
<JPC06></JPC06> <JP27004>506022000001</JP27004> </JPM5R>
<JPC07></JPC07> <JP27005>506022000002</JP27005> </JPM5>
<JPC08></JPC08> <JP27008>1</JP27008> <JP27109>CM</JP27109>
<JPC09></JPC09> <JP27082>1</JP27082> <JP27113>1</JP27113>
<JPC10>HWSW</JPC10> <JP27035>490000000000</JP27035> <JP27114>1</JP27114>
<JPC11>00</JPC11> <JP27040>PC</JP27040> <JP27134>0</JP27134>
<JPC12>1A</JPC12> <JP27083>Personal <JP27135>0</JP27135>
<JPC14>0110</JPC14> Computer</JP27083> <JP27044>298000025</JP27044>
<JPC18>00001</JPC18> <JP27036>JIPDEC-CII-00001-abc- <JP27138>1</JP27138>
<JPC19>990602135843</JPC19> 4567</JP27036> </JPTRM>
<JPC21>CII300</JPC21> <JP27091>0</JP27091> </CII-HWSW001A0110-V10>
<JPC29>I</JPC29> <JP27092>1</JP27092>
<JPC30></JPC30> <JP27103>2</JP27103>

Message Group Header Message Body

 Simple EDI System Configuration
(without Collaboration Engine)

Repository

+Predefined Message
+Stile Sheet
Business

Document
Composing
Applications

CII/XML

ebXML
Messaging SOAP
 EDI Status in Japan

Standard EDI Portion (%)

100%

27%
80%

23%
60%
nXML/EDI

23% nStandard EDI

40%
nIndustry EDI
20% oProprietary EDI
28%

0%
1997 1998 1999 2000 2001 2002 2003
 EDI Road Map
Proprietary EDI
Hi-speed
Standard EDI Hi-volume

CII, UN/EDIFACT Continuance

Open Electronic
OO-edi Market
XML/EDI

Simple EDI EDI in

each group
XML/EDI

Internet
EDI

EDI non-
Installed