Transcript OAGI Briefing - UN/CEFACT Forum

Open Applications Group
Lunch and Learn
UN/CEFACT Meeting March 16, 2006
OAGIS implementation of Core Components
David Connelly
http://www.openapplications.org
1
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
Open Applications Group
• Introduction
• How the OAGIS standard
implemented Core Components
• How people are using OAGIS
• OAGIS Adoption
2
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
Open Applications Group
Who we are
The Open Applications Group is a notfor-profit, open, and fully independent
Open Standards Organization.
3
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
OAGi Genesis
• Founded in November, 1994
• Originally by ERP Vendors
• Focused on how they can
integrate together better
• Identified common content as
biggest missing piece
4
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
Original OAGi Scope
from 1995
A. To Extra-Enterprise
Systems
E
N
T
E
R
P
R
I
S
E
B. Between ERP
Applications
C. To Special Purpose
Applications
5
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
What is OAGIS?
6
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
OAGIS® is Payloads and
Business Processes
CustomerParty
• Scenario is the process
definition
• Business Object Documents
(BOD) are the messages in
the Scenario
SupplierParty
ProcessPurchaseOrder
AcknowledgePurchaseOrder
ShowDeliveryReceipt
ProcessInvoice
ConfirmBOD
7
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
OAGIS® 9 - Current Version
•
•
•
•
•
•
•
•
Released April 5, 2005
Over 10 total years in the field
70 Business Scenarios
434 Messages (BODs)
77 Nouns (Common Objects) defined
12 Verbs Defined
More localization for more International support
UN/CEFACT/ISO compliant
– ISO 11179
– CCTS 2.01/ISO 15000-5
– TBG17 BIE/ABIE
8
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
Current Scope of
OAGIS® 9.0 Content
•
•
9
eCommerce
–
–
–
–
–
–
–
e-Catalog
Price Lists
RFQ and Quote
Order Management
Purchasing
Invoice
Payments
–
–
–
–
–
–
MES
Shop Floor
Plant Data Collection
Engineering
Warehouse Management
Enterprise Asset Mgmt.
Manufacturing
•
Logistics
•
CRM
•
ERP
– Orders
– Shipments
– Routings
–
–
–
–
Opportunities
Sales Leads
Customer
Sales Force Automation
–
–
–
–
–
Financials
Human Resources
Manufacturing
Credit Management
Sarbanes/Oxley & Control
Value Chain Collaboration
Applications
Enterprise
Management
Applications
Enterprise
Execution
Applications
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
OAGIS BODs are a Language
• BODs are comprised of
- Nouns
- Verbs
• Nouns contain the business
content
• Verbs describe the action
10
BOD
ProcessPurchaseOrder
Verb
Noun
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
BOD History
• BOD and Meta Data Invented
– June 1995
• XML DTDs Shipped
– February 1998
• XML XDR Shipped
– December 1999
• XML Next Gen XSD Shipped
– March 2002
• UN/CEFACT CC XML Shipped
– May 2005
11
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
BOD History
• 5 generations of technology already
• Reinforces the importance of syntax neutrality
12
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
The BOD Architecture
13
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
BOD Architecture
•
•
•
•
•
•
•
14
BOD is technical architecture
Provides a message container
Enables the meta model
Common look, feel, and behavior
Enables a high level of re-use
Enables the extensibility mechanisms
Provides a faster learning curve for the user
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
OAGIS Nouns
•
•
•
•
•
•
•
15
Nouns are consistent like Common Objects
78 in OAGIS 9
Can be Documents
Can be Control Data
Can be any content needed in a message
Behavior is affected by Verbs
Verbs are described in next section
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
OAGIS Noun Examples
•
•
•
•
•
•
•
16
PurchaseOrder
Invoice
Shipment
Quote
RequestForQuote
ProductionOrder
MaintenanceOrder
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
OAGIS Verbs
BOD
ProcessPurchaseOrder
Verb
17
Noun
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
OAGIS® Verbs?
• Nouns may need to be different at execution
• The Verbs help drive these constraints
• Example
– SyncPurchaseOrder
– CancelPurchaseOrder
• OAGIS constrains the Nouns with XPath
portion of XSL (Not XSLT portion)
18
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
Verb Example
CustomerParty
SupplierParty
ProcessPurchaseOrder
AcknowledgePurchaseOrder
ShowShipment
ShowDeliveryReceipt
ProcessInvoice
ConfirmBOD
19
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
A Constraint Rule
Rule
Context
Test
20
Message
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
Using Constraints to
Add Context
BOD Instance
21
XSL Processor
Validating Parser
BOD XML Schema
Application
BOD Constraints
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
OAGIS Extensibility
• OAGIS® provides the user a unique
form of extensibility to stretch the
standard without breaking it.
22
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
Overlay Extensibility
• OAGIS® uses three technologies to
enable Overlay extensibility
– Global Elements
– Namespaces
– Substitution Groups
23
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
Overlay Example
Overlay
OAGIS®
Your BOD
24
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
Lite BODs for Specific Use Cases
• OAGIS® also enables you to
“extrude” Lightweight BODs
• Canonical stays in place
• Extrude from the class libraries
• Maintain at the library level
• Use lightweight BODs for
lightweight services
Lite BODS
OAGIS® CANONICAL BODS
25
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
OAGIS Components
•
•
•
•
26
Started with this concept in 1995
OAGIS Building Blocks
Nouns Comprised of Components
Used to “Assemble” the BODs
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
OAGIS®
Component
Example
27
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
Header
Party
Address
Contact
PO BOD
Assembled
using
Components
Terms
Charge
Distribution
Line
Party
Address
Contact
Terms
Distribution
Diagram Note:
- Required = Solid boxes
- Optional = Dashed boxes
Charge
Distribution
POSubLine
POLineSchedule
28
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
OAGIS Architecture
Resources
Meta Model
Content
29
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
BOD Assembly Example
OAGIS® BOD
Noun
Verb
Component
Component
Compound
Field
Field
30
Field
Component
Field
Compound
Field
Component Compound
Field
Field
Compound
Field
Field
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
Open Applications Group
OAGIS® 9
Implementation of
UN/CEFACT
Core Components
31
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
Early OAGi UN/CEFACT Efforts
• Involved with ebXML Since inception in
November 1999
• Participated in most of meetings
• Focused on Business Process and Core
Components
• Part of ebXML Proof of Concept in Vienna
• OAGIS Contribution to CC in 2001
32
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
UN/CEFACT Endorsement
33
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
UN/CEFACT Standards
Implemented in OAGIS® 9
34
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
UN/CEFACT Standards
Implemented in OAGIS® 9
• Conformance to UN/CEFACT ATG2 Naming
and Design Rules.
– Where we deviate it is to meet the functional
needs of OAGIS and OAGi member requirements.
• ISO 15000-5 – CCTS 2.01
• UN/CEFACT TBG17 – ACCs and BIE/ABIEs
as defined to this point.
35
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
Why did OAGIS implement CC?
• Business Decision
• Technical Decision
36
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
Why did OAGIS implement CC?
• OAGIS® Users asked for it
– Automotive Supply Chain
– Aerospace Supply Chain
– Defense Industry
• Two largest software vendors have adopted it
– SAP
– Oracle
• OAGIS® convergence initiatives
– ISA SP95
– HR-XML
– UN/CEFACT
37
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
Why did OAGIS implement CC?
• Will increase interoperability for enterprises
– Encourages all business languages to be based on
same concepts.
– Defines grammar rules
– Defines key naming conventions
– Defines key common content (Components)
38
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
Why did OAGIS implement CC?
• The right thing to do
– OAGIS® participation in MoU MG asks for it
– Good citizen in standards world
39
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
Building Bridges
40
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
UN/CEFACT Standards
implemented in OAGIS 9
• Strategy
– All TBG17 Approved ACCs (as of 02/05) available
– Subset of TBG17 Approved ACCs implemented in
Components.xsd
– Most stable ACCs identified for implementation
– ACCs also evaluated for compatibility with OAGIS
design rules
• 19 ABIEs in OAGIS 9
– Based on 18 TBG17 Approved ACCs
41
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
UN/CEFACT Standards
implemented in OAGIS 9
ABIEs Implemented Included
•
•
•
•
•
•
•
•
•
•
42
Project
AllowanceCharge
Calculation
Tax
Authorization
Payment Authorization
Term
Person
Status
Dimension
•
•
•
•
•
•
•
•
•
HazardousMaterial
Location
Communication
Preference
Contact
TimePeriod
TemperatureRange
CurrencyExchange
Price
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
OAGIS
Component
Libraries
• OAGIS
• UN/CEFACT
• IST/ISO
43
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
OAGIS UN/CC Implementation
Let’s Go Look
44
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
OAGi Participation in UN/CEFACT
• TMG – Techniques and Methodology Group
– CCTS: Core Component Technical Specification
– BCSS: Business Collaboration Schema
Specification
– CCMA: Core Component Message Assembly
• TBG – International Trade and Business
Process Group
– TBG17: Core Component Harmonization
• ATG – Applied Technologies Group
– ATG2: XML Naming and Design Rules Technical
Specification
45
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
Special Thanks
• Initiated the move for OAGi to adopt the UN/CEFACT Core
Components efforts.
• Created the OAGi CC Workgroup, leading it to ensure that
OAGIS is compliant with UN/CEFACT.
• Initiated the role and represents OAGi on UN/CEFACT
TBG17.
• Worked with UBL and UN/CEFACT ATG2 to establish a
common set of schema modules for CCTS; the basis for
building Core Components.
• Initiated the task and became OAGi ISO TC 154
Liaison. This is the E-Commerce Group at ISO.
Garret Minakawa,
Oracle Corporation
46
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
Standards within the
OAGIS® Standard
W3C - URI/URL
W3C - XML Schema 1.0 Part 1
W3C - XSL Schema 1.0 Part 2.0
W3C - XML Style Language
W3C - XML Path Language (XPath) Version 1.0
ISO - ISO11179
ISO - ISO1500-5 Core Components Type Specification
ISO - ISO20022 (UNIFI Financial Standard)
ISO - ISO4217 - Currency Codes
ISO - ISO639 - Language Codes
UN/CEFACT ATG2 Naming and Design Rules - NDR
UN/CEFACT Harmonized Core Components – TBG17
MIME Media Type Code
UNECE Unit Code
OMG UML 2.0
47
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
Open Applications Group
Questions?
48
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
Knowledge of OAGIS® Adoption
• Difficult to know full adoption number
• OAGIS® is free and the download only
requires a registration
• We learn from
• Word of mouth
• Emails
• Surveys
• Luck
• We count downloads
• We track emails
• Probably know 10% of user base
49
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
OAGIS Downloads
• 100,000+ downloads
over last 8 years
• Representing over 60
countries
50
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
Drivers for OAGIS®
Implementations
• B2B beyond traditional EDI
– Supply Chain Management
– Supply Chain Visibility
– Collaborative Engineering and Manufacturing
• Increasing demand to connect internal
processes to external processes
• Service Oriented Architecture
– Requires Business Service Definitions
• Emerging understanding of the benefit of a
Canonical ModelTM
51
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
The Business Environment
Business
Unit 1
Business
Unit 2
Business
Unit n
Customer
Supplier
Enterprise
Integration Back Bone
52
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
A Case for a Canonical
Model
From <many to many> to <many to one>
53
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
The mathematics of
scaling up
For traditional point to point or
<many to many> integration:
The number of possible connections
among any number of items is n(n-1)
for two way connections.
Number of
components
to integrate
54
Apply traditional
formula
Cost of traditional
integration @ 0.1 FTE
n=5
5(4)
=
20
2 FTEs
n = 10
10(9)
=
90
9 FTEs
n = 15
15(14) = 210
21 FTEs
n = 20
20(19) = 380
38 FTEs
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
The mathematics of
scaling up
For best practices integration:
The number of possible connections
among any number is n * 2.0
Number of
components
to integrate
55
Best practices
formula
Cost of best practices
integration @ 0.1 FTE
n=5
5 * 2.0 = 10
1 FTE
n = 10
10 * 2.0 = 20
2 FTEs
n = 15
15 * 2.0 = 30
3 FTEs
n = 20
20 * 2.0 = 40
4 FTEs
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
Sample of Customers using
the OAGIS Canonical Model
•
•
•
•
•
•
•
•
•
•
•
56
TeliaSonera
SKF
Amersham Health
Goodrich Aerospace
Goodyear Tire
Cisco
IBM
Boeing
Ford
General Electric
Lucent
Solution
Provider
specific
Overlay
Company
Specific
Overlay
Vertical
Content
Overlay
Vertical
Content
Overlay
Vertical
Content
Overlay
OAGIS Canonical Business Language
Supplier
ERP
CRM
Customer
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
Industry Collaborations
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
57
UN/CEFACT – United Nations
ISO- International Standards Organization
MoU MG – Memorandum of Understanding Management Group
IEC TC57 WG14 – Electric Utility Standards
KIEC – Korean e-Commerce Consortium
NIST – National Institute of Standards & Technology
AIAG – Auto Supply Chain North America
Odette – Auto in Europe
ITA – Information Technology in Germany
STAR – Auto Retail North America
AAIA – Auto Aftermarket North America
RV Industry – North America
AIA – Aerospace North America
AECMA – Aerospace Europe
OSCRE – Facilities Management
VISION Industry
HR-XML – HR Content, world-wide
SP95 – Enterprise Controls
ARTS (Retail)
STEP – Engineering world-wide
IFX – Interactive Financial Exchange
SWIFT
TWIST
Comptia/EIDX – Electronics and Computer Industry
WS-I
OASIS
Tax-XML
UBL
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
OAGIS live users in
41 known countries
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
58
Australia
Austria
Bahrain
Belgium
Brazil
Canada
Chile
China
Croatia
Czech Republic
Denmark
Ireland
Finland
France
Germany
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Holland
Hungary
India
Israel
Italy
Japan
Korea (South)
Lithuania
Mexico
Netherlands (Holland)
Norway
Oman
Papua New Guinea
Poland
•
•
•
•
•
•
•
•
•
•
•
•
•
Russia
Saudi Arabia
Singapore
Slovenia
Slovakia
South Africa
Spain
Sweden
Switzerland
Turkey
United Arab Emirates
United Kingdom
United States
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
OAGIS live users in
over 40 industries
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
59
Aerospace
Agri-Business
Automotive Manufacturing
Automotive Retail
Automotive Aftermarket
Banking
Brewing
CPG
Chemical
Computer Hardware
Computer Software
Consumer Goods – Electronics
Defense
Distributors
Federal Government
Food Manufacturing
Furniture Manufacturing
Medical Device Manufacturing
Mortgage
Pharmaceutical
Insurance
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Industrial Goods Manufacturing
Logistics
Medical Device Manufacturing
Mining
Oil
Natural Gas
Paint
Paper
Publishing
Retail
Shipping
Software
State Government
Local Government
Telecommunications
Tire Manufacturing
Tobacco
Trucking
Universities
Electric Utilities
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
Some eGovernment
Implementations
•
•
•
•
•
•
•
•
•
60
Dutch Ministry of Finance
UK Ministry of Defense for Logistics
UK Post (Mail)
UK Network Rail
KIEC (Korea)
Dubai eGovt
Govt. of Oman
USAF
US DLA
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
Some Automotive Adoption
•
•
•
•
•
•
•
•
61
General Motors
Ford Motor Company
Volvo
Volkswagon
Toyota
Honda
Nissan
Covisint
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
Some Hi-Tech and
Telecom Adoption
•
•
•
•
•
•
•
•
•
•
•
•
•
62
Microsoft
IBM
Cisco
Texas Instruments
Motorola
Qualcomm
Intuit
Lucent
Slovak Telecom
TeliaSonera
British Telecom
MCI
Verizon
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
Some Retail Adoption
•
•
•
•
•
•
•
•
•
•
63
Staples
Best Buy
Microage
Nordstrom
Lowes
Coles-Meyers Australia
Saks
Home Depot
Woolworths Australia
Canadian Tire
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
Some General
Manufacturing Adoption
•
•
•
•
•
•
•
•
•
•
•
•
•
64
Ingersol Rand (Ireland)
General Electric
SKF (Sweden)
Black and Decker
Campbells Soup (Australia)
British and American Tobacco
Siemans
Johnson and Johnson
Engelhard
Cargill
Emerson
AAC Comos (Netherlands)
Agilent
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
Some Aerospace Adoption
•
•
•
•
65
Boeing
Lockheed Martin
Northrop Grumman
Goodrich Aerospace
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
Some Services Adoption
•
•
•
•
•
•
66
Disney
Ameriquest
The Hartford
Standard and Poors
ADP
Salt River Project (Electricity)
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
Some OAGIS Vendor Adoption
•
•
•
•
•
•
•
•
•
•
•
•
•
67
Oracle
SAP (partial)
IBM
ExpiditeBiz
Microsoft
iBASEt
iConnect
Covisint (Compuware)
HK Systems
Catalyst
Brooks Software
Camstar
Compiere
•
•
•
•
•
•
•
•
•
•
•
•
Tibco
Scala
QAD
iWay
webMethods
Websphere
Camstar
Kaba Benzing
Wonderware
Baan
WiPro
EDS
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
End User Example
68
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
Lucent and OAGIS®
OAGIS®
69
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
Lucent and OAGIS®
70
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
US DOD
71
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
Community of
OAGIS® Users Group
72
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
Campbells and OAGIS®
From: [email protected]
Sent: Wednesday, June 04, 2003 11:41 PM
To: Dave Chambless
Cc: David Connelly; [email protected];
[email protected]
Subject: RE: Campbell Soup and the Open Applications Group
Hello Dave,
Thanks for the invitation to join OAG. At Campbells Asia Pacific (I am
based in Sydney, Australia) we have already adopted OAGIS as our message
content schema (canonical form) in our EAI projects. We are a Tibco shop,
and leverage the toolset for both B2B and A2A integrations. We reviewed
ebXML for the initial B2B integration with a 3PL that was our first EAI
project, but since the particular trading partner in question did not have
a messaging framework in place enabling the infrastructure level
interoperability, we leveraged the default Tibco framework (tibXML) as the
most appropriate alternative because it is simpler to implement and to
deploy and was sufficient for the 3PL integration.
The principle we've adopted is that all messages hitting the Tibco message
"bus" will be mapped into a standard "canonical" XML content schema - OAGIS
- to ensure future reuse of any data published on the bus.
We found OAGIS supported most of the B2B transactions we needed for 3PL . . .
73
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
UK Ministry of Defense
74
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
Dubai eGovt.
75
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
SKF and OAGIS®
From: [email protected]
Sent: Thursday, July 29, 2004 7:20 AM
To: [email protected]
Subject: An XML question
Dear Sir,
Good afternoon!
I am trying to learn as much as I can about XML.
The company I work for have chosen OAGIS 8 as the XML standard.
I am not an IT programmer - I am a 'user'
Please could you just help me to understand the basic differences difference between XML and EDIFACT ?
Thank you very much in advance
Kind regards, Chris
-----------------------------------------------Chris McCulloch
SKF Logistics Services
AB SKF Gothenburg//Sweden
(Tel: +46 99 9999999)
(Email: [email protected])
------------------------------------------------
76
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved
Thanks and
Questions?
77
Copyright © 1995 - 2006 Open Applications Group, Inc. All rights reserved