Project funded by the European Community under
the “
Research for the Benefit of Specific Groups (in
particular SMEs)”
A Semantic Service
-
Oriented Private Adaptation
Layer Enabling the Next Generation, Interoperable
and Easy
-
to
-
Integrate Software Products of
European Software SMEs
Project number
232372
Project Acronym
EMPOWER
Project Title
A Semantic Service
-
Oriented Private Adaptation Layer Enabling the
Next Generation, Interoperable and Easy
-
to
-
Integrate Software
Products of European Software SMEs
Thematic Priority
FP7
-
SME
-
200
8
-
1
“Research
for the Benefit of Specific Groups (in particular SMEs)”
Start date of the project
May
1
st
, 200
9
Deliverable number
D
4
.
4
Deliverable name
InfomatiX
Prototype
Version
1
.0
Type (distribution level)
CO
Related
WP
WP
4
–
Enterprise Services and Objects
Semantic Map
Lead contractor
InfomatiX
Author(s)
Ákos Bérczes,
Panagiotis Gouvas
and
Eleni Fotopoulou
Contributing Partners
InfomatiX
,
SingularLogic,
ICCS
Project Name
EMPOWER
Project Number
232372
Document
D4.4 InfomatiX Prototype
Date
28/2/2013
EMPOWER
:
A Semantic
Service
-
Oriented Private Adaptation Layer Enabling the Next Generation, Interoperable and Easy
-
to
-
Integrate Software Products
of European Software SMEs
FP7
-
SME
-
200
8
-
1:
“Research for the Benefit of Specific Groups (in particular SMEs)”
Page
2
of
79
VERSIONING & CONTRIBUTION HISTORY
Version
Date
Modification reason
0.1
1.11.2012
Table Of
Contents
0.2
16.11.2012
Insertion of
Architectural diagram
s for
Distiller and CashTime in Chapter 2
0.3
02.12.2012
List of Figures
0.4
01.01.2013
Appendix
0.5
19.01.2013
Update Use Cases, Chapter 4
1.0
28.2.2013
Final
Version addressing the review
comments
Project Name
EMPOWER
Project Number
232372
Document
D4.4 InfomatiX Prototype
Date
28/2/2013
EMPOWER
:
A Semantic
Service
-
Oriented Private Adaptation Layer Enabling the Next Generation, Interoperable and Easy
-
to
-
Integrate Software Products
of European Software SMEs
FP7
-
SME
-
200
8
-
1:
“Research for the Benefit of Specific Groups (in particular SMEs)”
Page
3
of
79
EXECUTIVE SUMMARY
This document presents the requirement analysis of the pilots of the InfomatiX prototype as these were
specified in the scope and goals of the EMPOWER project. The current document presents an overview
of the XML data transformation problem addressed in EM
POWER, and outlines the solution for
semantic
-
based data mapping. It also revises the InfomatiX requirements and discusses the integration
need, as well as the solution given by the EMPOWER project based on the idea of accomplishing
interoperability scenar
ios amongst registered services provided by discrete vendors. Furthermore, the
use case scenarios as these were determined by the functional requirements of the EMPOWER system
are reported. A representative set of use case scenarios were implemented in ord
er to present the
exposure of web services employed by “CashTime” and “Distiller” systems and the interoperability
獣Vn慲ao猠瑨慴W慲攠慣ai敶eT b整睥敮e瑨敭⸠周TougU 愠獰散楦V挠獥V o映u獥V捡獥V獣敮慲楯猬V瑨攠p敲獰散瑩We
o映瑨W v敮eor 慮T 捵c瑯m敲eo牧慮楺慴a
on 捡c慢楬楴楥猠瑨WougU 瑨W NMP佗䕒Np污瑦lrm 慲e ev慬a慴aT
慮T 捬慲c晩敤⸠周攠To捵men琠捯n捬cT敳e睩瑨w瑨攠慣ai敶em敮瑳eo映瑨攠楮楴楡i goa汳l慮T 瑡牧整猠
牥条牤楮g
瑨攠Wcop攠o映瑨攠䥮景
ma瑩堠p牯瑯瑹p攮
Project Name
EMPOWER
Project Number
232372
Document
D4.4 InfomatiX Prototype
Date
28/2/2013
EMPOWER
:
A Semantic
Service
-
Oriented Private Adaptation Layer Enabling the Next Generation, Interoperable and Easy
-
to
-
Integrate Software Products
of European Software SMEs
FP7
-
SME
-
200
8
-
1:
“Research for the Benefit of Specific Groups (in particular SMEs)”
Page
4
of
79
Table of Contents
VERSIONING & CONTRIBUTION HISTORY
................................
................................
................................
.....
2
EXECUTIVE SUMMARY
................................
................................
................................
................................
..
3
Table of Contents
................................
................................
................................
................................
..........
4
List of Figu
res
................................
................................
................................
................................
................
6
List of Tables
................................
................................
................................
................................
.................
9
Abbreviations
................................
................................
................................
................................
..........
10
1.
Introduction
................................
................................
................................
................................
........
11
1.1.
Deliverable Outline
................................
................................
................................
.....................
13
2.
R
evision of InfomatiX Requirements
................................
................................
................................
..
14
2.1.
Software Product Used in the Pilots
................................
................................
...........................
14
2.1.1.
Company product profile
................................
................................
................................
....
14
2.1.2.
Software product architecture
................................
................................
...........................
15
2.2.
Software developments and maintenance
................................
................................
.................
16
2.2.1.
CashTime
................................
................................
................................
.............................
16
2.2.2.
Distiller
................................
................................
................................
................................
17
2.2.3.
Mobia
ccess
................................
................................
................................
..........................
18
2.3.
Solution map
................................
................................
................................
...............................
19
2.3.1.
CashT
i
me
................................
................................
................................
.............................
19
2.3.2.
Distiller
................................
................................
................................
................................
19
2.3.3.
Correlation and combination
................................
................................
..............................
19
2.4.
Shipment model
................................
................................
................................
..........................
19
2.5.
Data and functional templates
................................
................................
................................
...
20
2.5.1.
CashTime
................................
................................
................................
.............................
20
2.5.2.
Distiller
................................
................................
................................
................................
23
2.6.
Integration need
................................
................................
................................
.........................
29
2.6.1.
CashTime
................................
................................
................................
.............................
29
2.6.2.
Distiller
................................
................................
................................
................................
34
Project Name
EMPOWER
Project Number
232372
Document
D4.4 InfomatiX Prototype
Date
28/2/2013
EMPOWER
:
A Semantic
Service
-
Oriented Private Adaptation Layer Enabling the Next Generation, Interoperable and Easy
-
to
-
Integrate Software Products
of European Software SMEs
FP7
-
SME
-
200
8
-
1:
“Research for the Benefit of Specific Groups (in particular SMEs)”
Page
5
of
79
2.6.3.
Mobiaccess
................................
................................
................................
..........................
34
3.
Exposing web services through SIL
................................
................................
................................
.....
35
3.1.
CashTime, web services exposed, use case scenarios
................................
................................
36
3.1.1.
Use Case #1
–
Create new record for a web service
................................
...........................
37
3.1.2.
Use Case #2
–
Modify a specific record of a web service.
................................
..................
38
3.1.3.
Use Case #3
–
View available operations of a web service
................................
.................
40
3.1.4.
Use Case #4
–
View
the WSDL of a web service
................................
................................
.
41
3.2.
Distiller, web services exposed, use case scenarios
................................
................................
...
42
3.2.1.
Use Case #1
–
Create new record for a web service
................................
...........................
43
3.2.2.
Use Case #2
–
Modify a specific record of a web service.
................................
..................
44
3.2.3.
Use Case #3
–
View
available operations of a web service
................................
.................
46
3.2.4.
Use Case #4
–
View the WSDL of a web service
................................
................................
.
47
4.
Interoperability scenarios through the use of SAL
................................
................................
.............
48
4.1.
System test reports
................................
................................
................................
.....................
48
4.2.
Vendor use case scenarios
................................
................................
................................
..........
48
4.2.1.
Use Case #1
–
Register Software Component(s)
................................
................................
.
49
4.2.2.
Use Case #2
–
Add new service to a current Software Component
................................
...
52
4.2.3.
Use Case #3
–
Edit
Functional Annotations
................................
................................
........
55
4.2.4.
Use Case #4
–
Edit Data Annotations
................................
................................
..................
58
4.3.
Customer use case scenarios
................................
................................
................................
......
62
4.3.1.
Use Case #1
–
Manag
e Installations
................................
................................
....................
63
4.3.2.
Use Case #2
–
Define CPP's (Collaborative Party Profile)
................................
...................
65
4.3.3.
Use Case #3
–
Define CPA (Collaborative Party Agreement)
................................
..............
67
4.3.4.
Use Case #4
–
Show My CPA's (Bridges)
................................
................................
.............
69
5.
Conclusions
................................
................................
................................
................................
.........
79
Project Name
EMPOWER
Project Number
232372
Document
D4.4 InfomatiX Prototype
Date
28/2/2013
EMPOWER
:
A Semantic
Service
-
Oriented Private Adaptation Layer Enabling the Next Generation, Interoperable and Easy
-
to
-
Integrate Software Products
of European Software SMEs
FP7
-
SME
-
200
8
-
1:
“Research for the Benefit of Specific Groups (in particular SMEs)”
Page
6
of
79
List o
f
F
igures
Figure 1: Generic Design
-
and run
-
time XML data transformation.
................................
...........................
11
Figure 2: Generic M
-
N design
-
and run
-
time XML data transformation.
................................
...................
12
Figure 3: Architectural diagram of CashTime.
................................
................................
............................
17
Figure 4: Architectural diagram of Distiller.
................................
................................
................................
17
Figure 5: Architectural diagram of Mobiaccess.
................................
................................
.........................
18
Figure 6: Distiller Ordering module schema.
................................
................................
..............................
23
Figure 7: Distiller invoicing module schema.
................................
................................
..............................
24
Figure 8: Customer Master Schema
................................
................................
................................
............
25
Figure 9: Material master schema.
................................
................................
................................
.............
25
Figure 10: Prices schema.
................................
................................
................................
............................
26
Figure 11: Listing schema.
................................
................................
................................
...........................
26
Figure 12: CashTime
-
SIL subsystem main page.
................................
................................
.........................
36
Figure 13: Create new “Currency” record.
................................
................................
................................
..
37
Figure 14: Vendor completes the required fields.
................................
................................
......................
37
Figure 15: A new record of type "Currency" is created.
................................
................................
.............
38
Figure 16: List all records of the Currency table.
................................
................................
........................
38
Figure 17: Attributes of a Currency record.
................................
................................
................................
39
Figure 18: Modify the Currency name.
................................
................................
................................
.......
39
Figure 19: System presents the modified record.
................................
................................
.......................
39
Figure 20: CashTime web services page.
................................
................................
................................
....
40
Figure 21: XML code of the WDSL file.
................................
................................
................................
........
41
Figure 22: Distiller
-
SIL subsystem main page.
................................
................................
............................
42
Figure 23: Create new “Distiller authentication” record.
................................
................................
...........
43
Figure 24: Vendor completes the requir
ed fields.
................................
................................
......................
43
Figure 25: A new record of type "Distilleruserpdapassword" is created.
................................
...................
44
Figure 26: List all records of the Distilleruserpdapassword table.
................................
..............................
44
Figure 27: Attributes of a Distilleruserpdapassword record.
................................
................................
......
45
Figure 28: Modify the Login name.
................................
................................
................................
.............
45
Figure 29: System presents the modified record.
................................
................................
.......................
45
Project Name
EMPOWER
Project Number
232372
Document
D4.4 InfomatiX Prototype
Date
28/2/2013
EMPOWER
:
A Semantic
Service
-
Oriented Private Adaptation Layer Enabling the Next Generation, Interoperable and Easy
-
to
-
Integrate Software Products
of European Software SMEs
FP7
-
SME
-
200
8
-
1:
“Research for the Benefit of Specific Groups (in particular SMEs)”
Page
7
of
79
Figure 30: Distiller web services page.
................................
................................
................................
........
46
Figure 31: XML code of the WDSL fi
le.
................................
................................
................................
........
47
Figure 31: Mai
n Page of actor: Vendor.
................................
................................
................................
......
48
Figure 32: “Register Software Component” page.
................................
................................
......................
49
Figure 33: User completes the required fields.
................................
................................
..........................
50
Figure 34: “Successful/Information” page.
................................
................................
................................
.
51
Figure 35: “Show S
oftware Components” page.
................................
................................
........................
52
Figure 38: User completes the required fields.
................................
................................
..........................
53
Figure 36: "Register service" page.
................................
................................
................................
.............
53
Figure 39: “Successful/Information” page.
................................
................................
................................
.
54
Figure 40: "Registered Web Services" page.
................................
................................
...............................
55
Figure 41: "Functional Annotation of Web Service" page.
................................
................................
.........
56
Figure 42: “Functional Annotation of Web Service” page.
................................
................................
.........
57
Figure 43: “Successful/Information” page.
................................
................................
................................
.
57
Figure 44: “Data Annotation of Web Service” page.
................................
................................
..................
58
Figure 45 “Search for Matches” page.
................................
................................
................................
........
59
Figure 46: "Successful/Information” page.
................................
................................
................................
.
60
Figure 47: “Annotation Mapping Tool”
................................
................................
................................
.......
61
Figure 49: “Main” page of actor: Customer
................................
................................
................................
62
Figure 50: "Manage installations of Exposed Web Servic
es" page.
................................
............................
63
Figure 51: Exposed Web Services of a specific software component.
................................
........................
64
Figure 52: "Define CPP's" page.
................................
................................
................................
..................
65
Figure 53: "Re
gistered Web Services of a specific Software Component" page.
................................
.......
66
Figure 54: "Create a New CPP" option.
................................
................................
................................
.......
66
Figure 55: "Define CPA(Bridge)
--
WS" page.
................................
................................
..............................
67
Figure 56: Creating a bridge between two web services.
................................
................................
...........
68
Figure 57: "Successful/Information" page.
................................
................................
................................
.
68
Figure 58: "See My Bridges" page.
................................
................................
................................
..............
6
9
Figure 59: Input XML for bridge operation.
................................
................................
................................
70
Figure 60: Bridge process results.
................................
................................
................................
..............
70
Figure 61: First Soap Request/Respond of Bridge process.
................................
................................
........
71
Project Name
EMPOWER
Project Number
232372
Document
D4.4 InfomatiX Prototype
Date
28/2/2013
EMPOWER
:
A Semantic
Service
-
Oriented Private Adaptation Layer Enabling the Next Generation, Interoperable and Easy
-
to
-
Integrate Software Products
of European Software SMEs
FP7
-
SME
-
200
8
-
1:
“Research for the Benefit of Specific Groups (in particular SMEs)”
Page
8
of
79
Figure 62: XML code for XBRL UPCasting and DownCasting.
................................
................................
.....
71
Figure 63: UPCasting and D
owncasting xslt.
................................
................................
...............................
72
Figure 64: Second Soap Request/Respond of Bridge process.
................................
................................
...
72
Figure 65: Target service XML output.
................................
................................
................................
.......
72
Figure 57: Disabled Bridge.
................................
................................
................................
.........................
73
Figure 67: Bridge process results.
................................
................................
................................
...............
74
Figure 68: Bridge process information.
................................
................................
................................
.......
75
Figure 70: Bridge process information.
................................
................................
................................
.......
78
Project Name
EMPOWER
Project Number
232372
Document
D4.4 InfomatiX Prototype
Date
28/2/2013
EMPOWER
:
A Semantic
Service
-
Oriented Private Adaptation Layer Enabling the Next Generation, Interoperable and Easy
-
to
-
Integrate Software Products
of European Software SMEs
FP7
-
SME
-
200
8
-
1:
“Research for the Benefit of Specific Groups (in particular SMEs)”
Page
9
of
79
List of Tables
Table 1: Abbreviations table.
................................
................................
................................
......................
10
Table 2: CashTime data format.
................................
................................
................................
..................
22
Table 3: CashTime types and fields.
................................
................................
................................
............
23
Table 4: Custom master database table.
................................
................................
................................
....
27
Table 5: Product master database table.
................................
................................
................................
...
27
Table 6: Prices database table.
................................
................................
................................
..................
28
Table 7: Order database table.
................................
................................
................................
...................
28
Table 8: Order Details database table.
................................
................................
................................
.......
28
Table 9: Mapping for invoices.
................................
................................
................................
....................
31
Table 10: Mapping for ledgers.
................................
................................
................................
...................
33
Table 11: Semantic conflicts.
................................
................................
................................
......................
33
Table 12: Accounting conflicts.
................................
................................
................................
...................
33
Table 13: Type matching between the two services.
................................
................................
.................
73
Table 14: Type matching between the two services.
................................
................................
.................
76
Table 15: Type matching between the two services.
................................
................................
.................
78
Project Name
EMPOWER
Project Number
232372
Document
D4.4 InfomatiX Prototype
Date
28/2/2013
EMPOWER
:
A Semantic
Service
-
Oriented Private Adaptation Layer Enabling the Next Generation, Interoperable and Easy
-
to
-
Integrate Software Products
of European Software SMEs
FP7
-
SME
-
200
8
-
1:
“Research for the Benefit of Specific Groups (in particular SMEs)”
Page
10
of
79
Abbreviations
Abbreviation
Definition
AJAX
Asyn
chronous Java and XML
API
Application Program Interface
CM
Canonical Model
CPA
Collaborative Party Agreement
CPP
Collaborative Party Profile
CRM
Customer Relationship Management
ERP
Enterprise
Resource P
lanning
IIS
Internet Information Services
IT
Information Technology
PDA
Personal Digital Assistant
RTDI
Research, Technological Development and Innovation
SAL
Semantic Adaptation Layer
SFA
Sales Force Automation
SIL
System Interoperability Layer
SOAP
Simple Object Access Protocol
UI
User Interface
URL
Uniform
Resource Locator
WSDL
Web Service Description Language
XBRL
Extensible Business Reporting Language
XML
Extensible Markup Language
XSD
XML Schema Description
Table
1
: Abbreviations table.
Project Name
EMPOWER
Project Number
232372
Document
D4.4 InfomatiX Prototype
Date
28/2/2013
EMPOWER
:
A Semantic
Service
-
Oriented Private Adaptation Layer Enabling the Next Generation, Interoperable and Easy
-
to
-
Integrate Software Products
of European Software SMEs
FP7
-
SME
-
200
8
-
1:
“Research for the Benefit of Specific Groups (in particular SMEs)”
Page
11
of
79
1.
I
ntroduction
EMPOWER addresses the issue of semantic interoperability of data exchanged by enterprises. Since the
data sent and received is assumed to be in XML, we face the problem of XML data transformation.
Figure
1
provides an overview of the elements involved in XML data transformation and the generic
process by which an XML document is transformed into another document. Company X (depicted on the
left side of the picture) want
s to send the Source XML document (e.g. an invoice) to Company Y. The
Source XML document is compliant with an XSD schema (Source XSD) made available by Company X
such that the receivers of its XML documents can understand the structure and meaning of such
documents. Company Y (on the right side of the figure) processes XML documents (in our case Target
XML) according to its own schema Target XSD. If Target XSD differs from Source XSD, then company X is
faced with the problem of having to process the Source
XML document which it does not understand.
Therefore, the
core challenge
is to generate the Target XML document from the Source XML document,
given the Source XSD schema and the Target XSD schema. A Transformation Layer is usually designed to
address thi
s challenge by providing means to map the Source XSD to the Target XSD at design time, and
by providing an engine that implements the schema mappings at run time when the Target XML needs
to be generated from Source XML.
Figure
1
:
Generic Design
-
and run
-
time XML data transformation.
The above solution does not scale when there are several Source XSDs that need to be mapped to
several Target XSDs (e.g. one compa
ny needs to send an XML document to several other companies
Transformation
Layer
Company X
Company Y
Source
XSD
Target
XSD
Source XML
(Instances)
Target XML
(Instances)
Schema
transformations
Instance
transformations
Design
-
time
Run
-
time
Project Name
EMPOWER
Project Number
232372
Document
D4.4 InfomatiX Prototype
Date
28/2/2013
EMPOWER
:
A Semantic
Service
-
Oriented Private Adaptation Layer Enabling the Next Generation, Interoperable and Easy
-
to
-
Integrate Software Products
of European Software SMEs
FP7
-
SME
-
200
8
-
1:
“Research for the Benefit of Specific Groups (in particular SMEs)”
Page
12
of
79
whose schemas are different from the one of the sender) because each mapping between a Source and
a Target need
s
to be designed, maintained, and implemented individually. This problem is usually
c
ircumvented by using an intermediate schema called
canonical model
(CM)
, which usually is a super set
of all other schemas, and providing mappings from the Source XSDs to the CM, and mappings from the
CM to the Target XSDs. This approach is illustrated in
Figure
2
. This approach implies that at run time the
Source XML document is used to generate a CM XML instance document (based on the mappings
between the Source XSD
and CM XSD), which in turn is used to generate the Target XML document
(based on the mappings between the CM XSD and the Target XSD).
Figure
2
:
Generic M
-
N design
-
and run
-
time XML data transformation.
Source
XSD
1
Source XML
i
(Instances)
Target
XML
j
(Instances)
Canonical Model (CM)
XSD
Source
XSD
2
Source
XSD
n
Target
XSD
1
Target
XSD
2
Target
XSD
m
CM XML
(Instances)
…
…
Design
-
time
Run
-
time
Project Name
EMPOWER
Project Number
232372
Document
D4.4 InfomatiX Prototype
Date
28/2/2013
EMPOWER
:
A Semantic
Service
-
Oriented Private Adaptation Layer Enabling the Next Generation, Interoperable and Easy
-
to
-
Integrate Software Products
of European Software SMEs
FP7
-
SME
-
200
8
-
1:
“Research for the Benefit of Specific Groups (in particular SMEs)”
Page
13
of
79
1.1.
Deliverable
Outline
Thi
s deliverable is divided into a number of chapters, which will be outlined below.
Chapter
2
–
Revision of
InfomatiX Requirements
:
The software
architecture of the
products provided
by InformatiX
and
the
ir
existing
data and functional templates
are
exte
nsively
described
.
In addition the
need for integration
and the solution given by the EMPOWER project based on the idea of
accomplish
ing
interoperability scenarios amongst registered services provided by the
Vendors
are
discussed
.
Chapter
3
–
Exposing web services through SIL:
In
this chapter the use of
the
System Interoperability
Layer
(SIL) subsystem
is
described in detail. Furthermore a representative set of use cases regarding the
set
-
up of
the
SIL subsystem and
the exposure of
web ser
vices employed by “CashTime” and “Distiller”
systems through
Spring
Roo Plug
-
in
are
presented.
Chapter
4
–
Interoperability scenarios through the use of SAL:
In
this section a representative set of
the use cases that will be supported by the EMPOWER p
latform are described in detail. The use case
scenarios which
are
presented are divided into two categories
, with the first
concerning the Vendor
capabilities through the EMPOWER platform and the other one
concerning
the perspective of the
customer/organiz
ation presenting possible interoperability scenarios amongst registered services
provided by the Vendors.
Chapter
5
–
Conclusions: In the final chapter the conclusions of this deliverable are discussed
, along
with
the achievements of
the
initial goals and target regarding the scope of InformatiX prototype.
Project Name
EMPOWER
Project Number
232372
Document
D4.4 InfomatiX Prototype
Date
28/2/2013
EMPOWER
:
A Semantic
Service
-
Oriented Private Adaptation Layer Enabling the Next Generation, Interoperable and Easy
-
to
-
Integrate Software Products
of European Software SMEs
FP7
-
SME
-
200
8
-
1:
“Research for the Benefit of Specific Groups (in particular SMEs)”
Page
14
of
79
2.
Revision
of InfomatiX
Requirements
2.1.
Software Product
Used in the Pilots
2.1.1.
Company product profile
Infomatix Ltd
.
(www.infomatix.hu) is a rapidly growing System Developer and Integrat
or Company
specialized in the fields of developing Mobile Applications, CRM and Workflow management
Applications. The company has more than
2
50 clients with more than 50 000 users. Its products are
acclaimed for their high customizability and user
-
friendly
approach. Infomatix colleagues are technology
professionals, who implement and support world
-
class business solutions. The company believes in
commitment, quality, unquestionable integrity, putting the needs of
its
clients first and honoring the
intellect
ual capital of our employees.
Two of its products (Distiller and CashTime) are market leaders in Hungary, Distiller being a very popular
SFA system in the field of FMCG, whilst CashTime being a workflow, project and time / cost
management system mostly ap
plied in the consultancy sector. Infomatix recently released the 3.
1
version of its mobile development framework product called “MobiAccess” based on the idea of the
creation of an integrated software development tool compatible with different mobile devic
es.
This product is a Mobile framework that can help additional solutions ‘get mobilized’. This
means
that
with the use of
this
framework
,
ERP, CRM, Networking and other kind of applications can get a mobile
interface in a much easier way
than
it was prev
iously possible. Because of this background the solution
is especially focusing on providing fast and easy integration with ERP and CRM systems.
The innovation potential of the company is very strong
;
Infomatix manages several RTDI projects funded
from th
e Hungarian innovation Fund (such as MOBILMED, for example), the Structural Funds and the
Framework Programme (such as
FUSION
and EMPOWER).
In 2009 Infomatix Ltd. was announce
d that it has won the Deloitte T
echnology Fast 50 award. The Fast
50 is awarded b
y market analysis company Deloitte and is based on revenue increase of enterprises in
the Central European region.
Our products are acclaimed for their high customizability and user
-
friendly approach. One of our main
clients, ‘Nestlé Hungary’ has awarded u
s with a Regional Innovation Award 2004 for our Sales Force
Automation System, “Distiller” which was implemented for their Gastronomical sector.
We are proud to say that the innovation potential of our company is very strong. We are very much
interested i
n IT integration research activities as this is of great importance to our medium and long
term perspective in competitiveness.
We have made the research and the implementation of our products without any help from
multinational companies at ‘niche’ segmen
ts of the IT sector. However the company is a late entry in the
Project Name
EMPOWER
Project Number
232372
Document
D4.4 InfomatiX Prototype
Date
28/2/2013
EMPOWER
:
A Semantic
Service
-
Oriented Private Adaptation Layer Enabling the Next Generation, Interoperable and Easy
-
to
-
Integrate Software Products
of European Software SMEs
FP7
-
SME
-
200
8
-
1:
“Research for the Benefit of Specific Groups (in particular SMEs)”
Page
15
of
79
IT business so at any time we implemented a product at a customer we were required to create a
communication link to at least 1 ERP or Financial or CRM product.
Currently we are working on a
s
olution which connects several ERP systems located in Central European countries. In this architecture
the information centre is in Hungary, but the system must be implemented in neighboring countries.
I
n
each country there are different ERP solutions
,
so
a strong communication interface is required. We also
encountered integration problems throughout the development work related to our new version of
“MobiAccess”.
We
have
participate
d
in an FP6 project (FUSION) which is also related to the topic of integr
ation as this
is about the implementation of a communication channel usable for any kind of data exchange.
These experiences led us to the conclusion that
the
IT integration market has further challenges which
we have to overcome to improve our services a
nd keep pace with the market needs.
2.1.2.
Software product architecture
CashTime
CashTime is web
-
based application that can be accessed via users through a web browser but it has also
a web
-
service interface that can be used by other applications to use the services provided by the
system. It provides an export/import capability that i
s used to integrate with third party applications,
mainly accounting applications. This export/import mechanism has to be customized currently to adopt
to
the given accounting software. As the customization must be done every time the system is
integrated
,
it is a main issue to make this process as fluent and easy as possible. Exploiting the benefits
of the EMPOWER project we expect the CashTime product to be far more adaptable and easier to be
integrated with.
Distiller
The Distiller application providing
field/sales force automation is relying heavily on the client
-
server
architecture. It has a client component that is used on handheld devices, a central client component that
is used for administration, reporting and monitoring the work done by the users u
sing the mobile
clients. The central (server) component is responsible for the connection to the central database,
orchestrating the synchronization process that exchanges data between the database and the mobile
clients. The system can be used as
a
standa
lone application but it is more profitable to integrate
it
with
an ERP system. This integration need leads this pilot project to implement an infrastructure that allows a
general easily adaptable interface to connect to and exchange data with ERP applicati
ons.
Mobiaccess
Mobiaccess is a mobile development framework that allows easy creation of mobile applications
without any platform
-
specific development knowledge. It supports both desktop PCs (including
notebook, tablet PCs) and all of the well
-
known mobil
e platforms (Blackberry, Windows Mobile, Java
-
Project Name
EMPOWER
Project Number
232372
Document
D4.4 InfomatiX Prototype
Date
28/2/2013
EMPOWER
:
A Semantic
Service
-
Oriented Private Adaptation Layer Enabling the Next Generation, Interoperable and Easy
-
to
-
Integrate Software Products
of European Software SMEs
FP7
-
SME
-
200
8
-
1:
“Research for the Benefit of Specific Groups (in particular SMEs)”
Page
16
of
79
based phones, Symbian, iPhone, Android). Mobiaccess itself is not a solution but we have implemented
many products based on this framework, and we intend to use it as the integration platform that will
connect
Distiller and CashTime to the semantic web service layer.
Mobiaccess and Distiller are going to converge in the future. As the first step, the central server of
Distiller will be replaced by the Mobiaccess’ Sync Server. The Sync Server will enable
Distiller to connect
to the semantic web service layer using the connector that will be implemented during the Empower
project.
CashTime software product will have its own connector to the semantic web layer. This will enable the
integration between Mobia
ccess enhanced by Distiller and CashTime, exploiting the benefits of the
Empower project.
2.2.
Software developments and maintenance
2.2.1.
CashTime
CashTime is running on
an
IIS application server and
is
deployed as two web application
s
, one for the
core functionali
ties and one for administrative purpos
es
(
Figure
3
)
.
An additional application for finances
is also
d
eployed.
CashTime’s core and administration components are third
generation, web
-
based
solutions using a multi
-
tiered architecture. They are written in ASP.NET and AJAX to create a quickly
responding, functionally rich user interface. The application for finances is derived from a legacy
application and is written in Vi
sual Basic 6.
The web
-
based CashTime application is a successor of the
former Visual Basic 6 implementation. However the finances application comes from this version and
this explains why it is implemented in VB6.
Project Name
EMPOWER
Project Number
232372
Document
D4.4 InfomatiX Prototype
Date
28/2/2013
EMPOWER
:
A Semantic
Service
-
Oriented Private Adaptation Layer Enabling the Next Generation, Interoperable and Easy
-
to
-
Integrate Software Products
of European Software SMEs
FP7
-
SME
-
200
8
-
1:
“Research for the Benefit of Specific Groups (in particular SMEs)”
Page
17
of
79
Application server
CT Admin
CT core
Data
base
Finances
application
Accounting system
Custom export
format
Web browser
Figure
3
: Architectural diagram of CashTime.
2.2.2.
Distiller
Distiller is shipped as one product however the administrative/management component and the mobile
client applications must be deployed on the appropriate devices separately.
The archi
tecture follows the
client
-
server model with fat clients
(
Figure
4
)
(
Error! Reference source not found.
)
.
Distiller server
Synchronization
engine
Data
Mobile
(
PDA
)
client application
Third party ERP system
Administrative
/
Management
application
Figure
4
: Architectural diagram of Distiller.
The central component is written in VB6 and the mobile clients are written in C++, the administration
component is derived from a legacy application and is written in Visual Basic 6, but its functionality is
extended by add
-
ins implemented in C#.
Project Name
EMPOWER
Project Number
232372
Document
D4.4 InfomatiX Prototype
Date
28/2/2013
EMPOWER
:
A Semantic
Service
-
Oriented Private Adaptation Layer Enabling the Next Generation, Interoperable and Easy
-
to
-
Integrate Software Products
of European Software SMEs
FP7
-
SME
-
200
8
-
1:
“Research for the Benefit of Specific Groups (in particular SMEs)”
Page
18
of
79
The mobi
le clients are run on PDAs with Windows Mobile operating system, thus C++ is a natural choice
as implementation language. The central server and the component for administration are legacy
applications and intended to run only on Microsoft Windows, thus Vi
sual Basic was an easy choice for
them. The add
-
ins are implemented in C# as the most popular implementation language used for
Windows
-
based development and is more powerful than VB6.
2.2.3.
Mobiaccess
Mobiaccess consists of many components and there are several
deploying options. The most usual is to
deploy the synchronization server, the central administration application and the database on the same
host. The desktop client application is deployed separately, but the mobile client applications are
deployed usin
g the administration software.
Mobiaccess is based on the client
-
server architecture schema
(
Figure
5
)
. Its central server component is
responsible for data exchange b
etween the client devices and the central database and accessing
remote systems on behalf of the clients if the business logic dictates so.
The server component and the desktop client applications are implemented in Java,
while
the mobile
clients are imple
mented in the given platform native language (Java, C#, C++, Objective
-
C). The central
administrative component is based on a legacy application that is implemented in Visual Basic 6 and
add
-
ins are developed for it in Delphi and C#.
Mobiaccess Sync Server
Remote call
engine
Sync Engine
Data
base
Third party
ERP
/
CRM
/
etc
.
Mobile client
(
PDA
,
BB
,
Symbian
,
laptop
)
Desktop PC client
Administrative
application
Figure
5
: Architectural diagram of Mobiaccess.
The languages are chosen according to the given mobile platform native language, in some cases as the
only option and in other cases as the most efficient solution since effici
ency is essential considering the
limited computational capacity of the mobile devices.
The central administrative component is currently Windows
-
based, but it will be replaced with a new
component written in Java to provide platform independency.
Project Name
EMPOWER
Project Number
232372
Document
D4.4 InfomatiX Prototype
Date
28/2/2013
EMPOWER
:
A Semantic
Service
-
Oriented Private Adaptation Layer Enabling the Next Generation, Interoperable and Easy
-
to
-
Integrate Software Products
of European Software SMEs
FP7
-
SME
-
200
8
-
1:
“Research for the Benefit of Specific Groups (in particular SMEs)”
Page
19
of
79
The SyncServer component is implemented in Java because Mobiaccess
aims for
platform independent
development and deployment in every aspect of the system.
2.3.
Solution map
2.3.1.
CashT
i
me
CashTime is mainly used in consultancy agencies, law firms, marketing agencies
but its services are
mainly domain independent
. Actually
time sheet and task management is also used by our company
internally.
2.3.2.
Distiller
Distiller is a field/sales force automation solution and therefore it is mainly used in market research,
finance, food
industry, healthcare, chemical industry domains.
2.3.3.
Correlation and combination
CashTime and Distiller functionalities can be easily combined as some of the services of CashTime are
domain independent. E.g. the tasks assigned in the Distiller system to the e
mployees using the mobile
devices can be automatically transferred to CashTime and form the base data to calculate the salary of
the given employee who is usually paid for performance.
However this interoperability is not straightforward to
be
implement
ed
currently. A possible solution is
to create a process that polls the Distiller database looking for changes, extract the information that has
to be transferred into CashTime while another process could insert this information to the CashTime
database. Thi
s solution is far from optimal
,
yet
the only possibility currently. This process would be
simplified using the semantic web services giving a direct connection between Distiller and CashTime.
2.4.
Shipment model
Neither CashTime nor Distiller has a reseller/dis
tributor network. They are marketed by the company
and deployed by support or consultant personnel. If the products have to be adjusted and/or integrated
to existing software of the customer, the implementation of these adjustments and integration
requirem
ents are developed by the company’s own development team. The customization usually
means that the codebase is branched and the necessary changes are implemented by the development
team, and a new application is built from the source.
The support of Distil
ler and CashTime customers
are based on their contract.
Mobiaccess is freely available to download from the Internet,
and
customers can use it to create the
applications they need. Another common scenario is when our company creates a solution for the
Project Name
EMPOWER
Project Number
232372
Document
D4.4 InfomatiX Prototype
Date
28/2/2013
EMPOWER
:
A Semantic
Service
-
Oriented Private Adaptation Layer Enabling the Next Generation, Interoperable and Easy
-
to
-
Integrate Software Products
of European Software SMEs
FP7
-
SME
-
200
8
-
1:
“Research for the Benefit of Specific Groups (in particular SMEs)”
Page
20
of
79
cust
omer based on the framework. These customers contract for support
is
based on their needs. Users
developing their own application can contract for technical support, but all customers are receiving
basic technical support.
Customization of Mobiaccess can h
appen on multiple levels. First of all, as a development framework it
allows one to configure the mobile applications deployed onto the mobile devices. If some functionality
that is needed on mobile devices by the business logic
is missing from
the
framewo
rk,
it
can be
implemented as
an
add
-
in. If the server side needs additional functionality, e.g. accessing remote
systems or custom actions executed during synchronization, they can be implemented and added to the
SyncServer’s execution logic. These tasks c
an be done by customers as all documentation and API is
available, however usually they are implemented by InfomatiX’s development team.
2.5.
Data and functional templates
2.5.1.
CashTime
CashTime has been integrated with several accounting systems
; for the purposes o
f the project
we have
chosen one of them, called Precíz, a Hungarian accounting software (that is the reason for the non
-
English field names). The integration’s aim is to exchange accounting information between the two
systems. CashTime exports invoices, l
edgers, checkout and bank vouchers. Precíz uses a custom data
format to import data.
Export data format is the same for every voucher types, and is shown
in
Table
2
(
data type notation:
d
–
date,
c(L)
–
character value with length of L,
n(P,S)
–
numeric data with
precision of P and scale of S).
No
DataType
FieldName
isMandatory
Description
1
c(3)
Naplo
Y
Log ID
2
c(10)
Bizszam
Y
Invoice number / Arrival code
3
c(3)
Bts
Y
Order number
4
c(4)
Ev
Y
Accounting year
5
c(2)
Konyvho
Y
Accounting month
6
c(2)
Koteg
Y
Constant data
7
d
Iktnap
Y
Create date
8
d
Bizdat
Y
Delivery date
9
d
Bizkelt
Y
Invoice date
10
d
Fizhat
N
Due date
11
c(1)
Tk
Y
Movement type ( T
–
income, K
–
expense)
12
c(9)
Fokszla
Y
GLCode
13
c(12)
Partner
N
Client/Supplier code
14
c(50)
Nev1
N
Client / Supplier name
Project Name
EMPOWER
Project Number
232372
Document
D4.4 InfomatiX Prototype
Date
28/2/2013
EMPOWER
:
A Semantic
Service
-
Oriented Private Adaptation Layer Enabling the Next Generation, Interoperable and Easy
-
to
-
Integrate Software Products
of European Software SMEs
FP7
-
SME
-
200
8
-
1:
“Research for the Benefit of Specific Groups (in particular SMEs)”
Page
21
of
79
No
DataType
FieldName
isMandatory
Description
15
c(50)
Nev2
N
Client / Supplier name 2
16
c(15)
IRSZAM
N
Zip code
17
c(30)
Varos
N
City
18
c(30)
UTCA
N
Street
19
c(10)
HSZ
N
Number
20
c(13)
ADOSZAM
N
Tax number
21
c(14)
EADOSZAM
N
EU tax number
22
c(2)
JELZO
N
Client /Supplier
23
c(9)
Afaszla
N
out of use
24
c(9)
KtgSzla
N
out of use
25
c(3)
Onelsz
N
out of use
26
c(30)
Onelsznev
N
out of use
27
c(9)
Ktghely
N
Cost place ID
28
c(30)
Ktgnev
N
Cost place name
29
c(20)
Munkasz
N
Engagement ID
30
c(30)
Msznev
N
Engagement name
31
c(20)
Szlaszam
N
Invoice number
32
c(20)
Alapbiz
N
out of use
33
c(1)
Fizmod
N
Payment type
34
n(16,2)
Alapn
Y
Net value without
tax
35
n(16,2)
Alapm
Y
Net value no tax
36
n(16,2)
alap0
Y
Net value with 0% tax
37
n(16,2)
alap1
Y
Net value with 5% tax
38
n(16,2)
alap2
Y
Net value with 25% tax
39
n(16,2)
Alap3
Y
Net value with 15% tax
40
n(16,2)
ado1
Y
5% tax value
41
n(16,2)
ado2
Y
25% tax value
42
n(16,2)
Ado3
Y
15% tax value
43
c(50)
Megj
N
Comment
44
c(9)
fokeszla
N
out of use
45
c(12)
epartner
N
out of use
46
c(3)
deviza
N
Currency ID
47
c(8)
arfbank
Y
Bank ID (for Currency rate)
48
d
arfdatum
Y
Currency rate date
49
c(1)
Arftip
Y
Type of currency rate
50
n(8,4)
arfertek
Y
Currency rate
Project Name
EMPOWER
Project Number
232372
Document
D4.4 InfomatiX Prototype
Date
28/2/2013
EMPOWER
:
A Semantic
Service
-
Oriented Private Adaptation Layer Enabling the Next Generation, Interoperable and Easy
-
to
-
Integrate Software Products
of European Software SMEs
FP7
-
SME
-
200
8
-
1:
“Research for the Benefit of Specific Groups (in particular SMEs)”
Page
22
of
79
No
DataType
FieldName
isMandatory
Description
51
n(16,2)
dAlapn
Y
Net total in default currency
52
c(3)
Ancsop1
N
out of use
53
c(20)
Anegys1
N
out of use
54
c(30)
EgyNev1
N
out of use
55
c(3)
Ancsop2
N
out of use
56
c(20)
Anegys2
N
out of use
57
c(30)
EgyNev2
N
out of use
58
c(3)
Ancsop3
N
out of use
59
c(20)
Anegys3
N
out of use
60
c(30)
EgyNev3
N
out of use
61
c(20)
Szerszam
N
out of use
60
c(30)
SzerNev
N
out of use
Table
2
: CashTime
data format.
An integration of CashTime uses the fields denoted by ‘Y’ in the is
Mandatory column, and the
y can be
found collected in the
Table
3
for easier overview.
No
DataType
FieldName
isMandatory
Description
1
c(3)
Naplo
Y
Log ID
2
c(10)
Bizszam
Y
Invoice number / Arrival code
3
c(3)
Bts
Y
Order number
4
c(4)
Ev
Y
Accounting
year
5
c(2)
Konyvho
Y
Accounting month
6
c(2)
Koteg
Y
Constant data
7
d
Iktnap
Y
Create date
8
d
Bizdat
Y
Delivery date
9
d
Bizkelt
Y
Invoice date
11
c(1)
Tk
Y
Movement type ( T
–
income, K
–
expense)
12
c(9)
Fokszla
Y
GLCode
34
n(16,2)
Alapn
Y
Net value without tax
35
n(16,2)
Alapm
Y
Net value no tax
36
n(16,2)
alap0
Y
Net value with 0% tax
37
n(16,2)
alap1
Y
Net value with 5% tax
38
n(16,2)
alap2
Y
Net value with 25% tax
39
n(16,2)
Alap3
Y
Net value with 15% tax
Project Name
EMPOWER
Project Number
232372
Document
D4.4 InfomatiX Prototype
Date
28/2/2013
EMPOWER
:
A Semantic
Service
-
Oriented Private Adaptation Layer Enabling the Next Generation, Interoperable and Easy
-
to
-
Integrate Software Products
of European Software SMEs
FP7
-
SME
-
200
8
-
1:
“Research for the Benefit of Specific Groups (in particular SMEs)”
Page
23
of
79
No
DataType
FieldName
isMandatory
Description
40
n(16,2)
ado1
Y
5% tax
value
41
n(16,2)
ado2
Y
25% tax value
42
n(16,2)
Ado3
Y
15% tax value
47
c(8)
arfbank
Y
Bank ID (for Currency rate)
48
d
arfdatum
Y
Currency rate date
49
c(1)
Arftip
Y
Type of currency rate
50
n(8,4)
arfertek
Y
Currency rate
51
n(16,2)
dAlapn
Y
Net
total in default currency
Table
3
: CashTime types and fields.
All of the fields listed above must be available in the web service layer to enable the integration.
2.5.2.
Distiller
Distiller is currently integrated to third party systems using its export/import function that can
read/write files and database tables.
In the frame of the this project w
e plan to implement the
integration of Ordering and Invoicing modules.
These modules
have the following schema
s
(
Figure
6
and
Figure
7
)
that can be considered as
underly
ing
meta
-
models for integration.
Figure
6
: Distiller Ordering module
schema
.
Project Name
EMPOWER
Project Number
232372
Document
D4.4 InfomatiX Prototype
Date
28/2/2013
EMPOWER
:
A Semantic
Service
-
Oriented Private Adaptation Layer Enabling the Next Generation, Interoperable and Easy
-
to
-
Integrate Software Products
of European Software SMEs
FP7
-
SME
-
200
8
-
1:
“Research for the Benefit of Specific Groups (in particular SMEs)”
Page
24
of
79
Figure
7
: Distiller invoicing module
schema
.
The integration also requires exchanging master data. Distiller
stores mast
er data in the following
schema (
Figure
8
,
Figure
9
,
Figure
10
,
Figure
11
).
Project Name
EMPOWER
Project Number
232372
Document
D4.4 InfomatiX Prototype
Date
28/2/2013
EMPOWER
:
A Semantic
Service
-
Oriented Private Adaptation Layer Enabling the Next Generation, Interoperable and Easy
-
to
-
Integrate Software Products
of European Software SMEs
FP7
-
SME
-
200
8
-
1:
“Research for the Benefit of Specific Groups (in particular SMEs)”
Page
25
of
79
Figure
8
: Customer Master
Schema
Figure
9
: Material master
schema
.
Partners
ID
Sdesc
InvoiceNAME
InvoiceNR
InvoiceCity
InvoiceZIP
InvoiceAddress
TAXNUM
TypeID
deleted
Palm
Sortiment
Basereduction
EXACTID
CreditLimit
ExciseLicense
WorkingLicense
ShopType
ShopTypeID
Sdesc
Description
deleted
PaymentTypes
UNID
SDesc
Description
deleted
DayOffset
IsCash
Shop
RUID
Sdesc
Name
EXACTID
EXACTPARTNERID
City
ZIP
Address
Contact
Manager
PhoneNO
FaxNO
email
Note
AreaID
SubTypeID
LastVisited
Item
ItemID
NECOMID
Name
ETK
VTSZ
ITJ
SubTypeID
EAN
ListPrice
ProductPrice
BasePrice
TAXCounted
VAT
NATTAXHUF
Orderable
PointValue
ItemCategory
QtyOnstock
deleted
Item2Categories
UNID
ItemID
CategoryID
deleted
ItemCategories
ID
ItemMainCategoryID
SDesc
Description
deleted
PartnerID
ImportTrID
ItemSubType
SubTypeID
NECOMID
TypeID
Sdesc
Description
deleted
BaseStrippingId
ItemType
TypeID
NECOMID
Sdesc
Description
deleted
AType
Project Name
EMPOWER
Project Number
232372
Document
D4.4 InfomatiX Prototype
Date
28/2/2013
EMPOWER
:
A Semantic
Service
-
Oriented Private Adaptation Layer Enabling the Next Generation, Interoperable and Easy
-
to
-
Integrate Software Products
of European Software SMEs
FP7
-
SME
-
200
8
-
1:
“Research for the Benefit of Specific Groups (in particular SMEs)”
Page
26
of
79
Figure
10
: Prices
schema
.
Figure
11
: Listing
schema
.
One can see that the Distiller system has an extensive schema supporting any scenarios
occurring at the
customers, however this makes it on the other hand rather difficult to define a general schema that can
be used in the integration with other systems via the semantic web service layer. Therefore we chose a
smaller subset of data fields th
at can be used for integration purposes.
Item
ItemID
NECOMID
Name
ETK
VTSZ
ITJ
SubTypeID
EAN
ListPrice
ProductPrice
BasePrice
TAXCounted
VAT
NATTAXHUF
Orderable
PointValue
ItemCategory
Shop
RUID
Sdesc
Name
EXACTID
EXACTPARTNERID
City
ZIP
Address
Contact
Manager
PhoneNO
FaxNO
email
Note
AreaID
SubTypeID
LastVisited
Sortiment
UNID
RUID
ItemID
PARTNERID
ItemSubTypeID
Required
deleted
Sdesc
ImportTrID
CategoryID
ShopTypeId
ShopSubtypeId
ShopCatID
PartnerCatID
RuleLevel
Project Name
EMPOWER
Project Number
232372
Document
D4.4 InfomatiX Prototype
Date
28/2/2013
EMPOWER
:
A Semantic
Service
-
Oriented Private Adaptation Layer Enabling the Next Generation, Interoperable and Easy
-
to
-
Integrate Software Products
of European Software SMEs
FP7
-
SME
-
200
8
-
1:
“Research for the Benefit of Specific Groups (in particular SMEs)”
Page
27
of
79
Customer master
:
No
DataType
FieldName
Description
1
c(50)
CustomerId
Customer code
2
c(50)
Name1
Customer name
3
c(50)
Name2
Customer name 2
4
c(15)
Zip
Zip code (billing address)
5
c(30)
City
City (billing
address)
6
c(30)
Street
Street (billing address)
7
c(10)
HouseNo
House number (billing address)
8
c(50)
Country
Country (billing address)
9
c(15)
sZip
Zip code (shipping address)
10
c(30)
sCity
City (shipping address)
11
c(30)
sStreet
Street
(shipping address)
12
c(10)
sHouseNo
House number (shipping address)
13
c(50)
sCountry
Country (shipping address)
14
c(13)
TaxNo
Tax number
15
c(14)
EuTaxNo
EU tax number
16
n(10,0)
shopCategory
Category
17
n(10,0)
Chain
The chain this shop belongs
to
18
n(10,0)
ShopId
Shop code
Table
4
: Custom master database table.
Product master
:
No
DataType
FieldName
Description
1
c(50)
ProductId
Product code
2
c(50)
Name
Product name
3
c(100)
Description
Product description
4
c(15)
Packaging
Packaging type
5
c(30)
Type
Product type
6
c(30)
SubType
Product subtype
7
c(30)
Category
Product category
Table
5
: Product master database table.
Prices
:
No
DataType
FieldName
Description
1
c(50)
ProductId
Product
code
2
c(50)
CustomerId
Customer code
3
n(10,2)
Price
Price
Project Name
EMPOWER
Project Number
232372
Document
D4.4 InfomatiX Prototype
Date
28/2/2013
EMPOWER
:
A Semantic
Service
-
Oriented Private Adaptation Layer Enabling the Next Generation, Interoperable and Easy
-
to
-
Integrate Software Products
of European Software SMEs
FP7
-
SME
-
200
8
-
1:
“Research for the Benefit of Specific Groups (in particular SMEs)”
Page
28
of
79
No
DataType
FieldName
Description
4
d
ValidFrom
Price is valid from
5
d
ValidUntil
Price is valid until
6
n(10,0)
ShopCategory
Category
7
n(10,0)
Chain
The chain this shop belongs to
8
n(10,0)
ShopId
Shop code
Table
6
: Prices database table.
Order
:
No
DataType
FieldName
Description
1
c(50)
OrderId
Order code
2
c(50)
CustomerId
Customer code
3
n(10,2)
Price
Total price
4
d
OrderDate
Date of the order
5
d
ShipmentDate
Date until shipment is
due
6
d
Paymentdate
Date until payment is due
7
c(50)
Status
Status (ordered, paid, shipped, etc)
8
n(10,0)
ShopId
Shop code
9
c(10000)
TextInfo
Textual content of order (for reprinting)
10
d
ApproveDate
Date of approval
11
c(50)
UserId
Code of the
user who have taken the order
12
c(50)
OrderType
Type of the order
13
c(200)
Comment
Comments/notes on the order
14
c(50)
SpecialDiscount
Special discount if applicable
Table
7
: Order database table.
Order
Details
:
No
DataType
FieldName
Description
1
c(50)
ODetailId
Order detail code
2
c(50)
OrderId
Order code
3
c(50)
ProductCode
Product code
4
n(10,0)
Amount
Amount of ordered items
5
n(10,2)
NetPrice
Price of unit without tax
6
n(10,2)
TotalPrice
Price with VAT
7
n(10,0)
DeliveredQty
Quantity of delivered items
Table
8
: Order Details database table.
Project Name
EMPOWER
Project Number
232372
Document
D4.4 InfomatiX Prototype
Date
28/2/2013
EMPOWER
:
A Semantic
Service
-
Oriented Private Adaptation Layer Enabling the Next Generation, Interoperable and Easy
-
to
-
Integrate Software Products
of European Software SMEs
FP7
-
SME
-
200
8
-
1:
“Research for the Benefit of Specific Groups (in particular SMEs)”
Page
29
of
79
2.6.
Integration need
2.6.1.
CashTime
CashTime is usually deployed to customers that already have an existing IT infrastructure that consists
among others
of
e.g. an accounting system. It is always a requirement to integrate with these
applications and the integrations should be as smooth and transparent
to
the users as possible. Until
now it was always the task of either of the parties to ensure integration b
y transforming its product’s
import or export feature to conform the other product’s expectations. We believe that this
customization step can be omitted with the semantic web service infrastructure that will be the result of
the EMPOWER project.
We presen
t in the
Table
9
,
Table
10
,
Table
11
and
Table
12
the problems that we
met during the integration of CashTime and Precíz.
Mapping for invoi
ces
Precíz uses the same hierarchy and field
s
set for invoices and invoice rows. In
the
rows some of the
fields header
data is repeated because of the export file structure.
No
Precíz
CashTime.Invoice
CashTime.InvoiceRow
Conflict
1
Naplo
<calculated>
<
calculated>
Missing data
2
Bizszam
Invoice.InvNo
Invoice.InvNo
Name
3
Bts
<calculated>
<calculated>
Enter the password to open this PDF file:
File name:
-
File size:
-
Title:
-
Author:
-
Subject:
-
Keywords:
-
Creation Date:
-
Modification Date:
-
Creator:
-
PDF Producer:
-
PDF Version:
-
Page Count:
-
Preparing document for printing…
0%
Σχόλια 0
Συνδεθείτε για να κοινοποιήσετε σχόλιο