<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Business Terms as a Critical Success Factor for Data Warehousing</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Peter Lehmann</string-name>
          <email>peter.lehmann@lawsonmardon.com</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Johann Jaszewski</string-name>
          <email>Jaszewsk@prinz-atm.cs.Uni-Magdeburg.DE</email>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Lawson Mardon Singen</institution>
          ,
          <addr-line>Alusingen-Platz 1, D-78221 Singen</addr-line>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Otto-von-Guericke-Universität Magdeburg</institution>
          ,
          <addr-line>Fakultät für Wirtschaftsinformatik, Universitätsplatz 2, D-39106 Magdeburg</addr-line>
        </aff>
      </contrib-group>
      <abstract>
        <p>This paper describes aspects of the data warehouse project at Lawson Mardon Singen, a German supplier of flexible packaging materials. We focus our work on the methodology of re-constructed business terms as our modeling approach. The goal is to provide high quality data based on clear defined business terms for end user's decision support in their business process.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1 Introduction</title>
      <sec id="sec-1-1">
        <title>The Lawson Mardon Packaging Group is one of the</title>
        <p>leading manufacturer of flexible packaging materials. At
the German location in Singen, blank and improved
aluminum-foils are produced for the packaging industry
in the market segments food, pharma and cosmetics. With
almost 1200 employees, a revenue of over 600 million</p>
      </sec>
      <sec id="sec-1-2">
        <title>DM was obtained in 1998. Within the company, a large</title>
        <p>project was initiated to substitute the existing host
applications by SAP’s standard software package R/3.
Subsystems are stock management, purchasing,
production planing, company controlling, financial
accounting, plant management, quality-management and
sales and distribution. Several HP Unix systems are used
as database servers based on Oracle DMBS . At the final
stage about 600 clients have to be supported.</p>
      </sec>
    </sec>
    <sec id="sec-2">
      <title>2 The Data Warehouse Project</title>
      <p>The copyright of this paper belongs to the paper’s authors. Permission to copy
without fee all or part of this material is granted provided that the copies are not
made or distributed for direct commercial advantage.</p>
      <sec id="sec-2-1">
        <title>Proceedings of the International Workshop on Design and</title>
      </sec>
      <sec id="sec-2-2">
        <title>Management of Data Warehouses (DMDW'99)</title>
        <p>Heidelberg, Germany, 14. - 15. 6. 1999
(S. Gatziu, M. Jeusfeld, M. Staudt, Y. Vassiliou, eds.)
http://sunsite.informatik.rwth-aachen.de/Publications/CEUR-WS/Vol-19/
language. These objects are elements of the (natural)
business language and relate to database tables and
columns. Business terms can be clustered subject
oriented. If these clusters are named “material
management” or “purchasing” end user can easily relate
these structures to their daily business process. The
complexity of data warehouse data structures are hidden
behind a semantic layer of clear defined business term.</p>
        <sec id="sec-2-2-1">
          <title>This approach requires a unique (clear) understanding of</title>
          <p>an used term such as “order entry”.</p>
          <p>As an example image the key figure “order entry” as an
important key performance indicator of a company. If you
ask five persons in different departments for a definition
of “order entry” you might get five different answers
depending on the departments. A salesman has a different
view on “order entries” (customer’s view: what has to be
shipped) as a person who is involved in production and
planing (manufacturing’s view: what has to be produced).</p>
        </sec>
        <sec id="sec-2-2-2">
          <title>Thus, the data warehouse approach at Lawson Mardon</title>
        </sec>
        <sec id="sec-2-2-3">
          <title>Singen is based on a methodology to consolidate business terms to integrate them into the meta data of the warehouse system.</title>
          <p>4</p>
        </sec>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>Methodology</title>
      <sec id="sec-3-1">
        <title>4.1 Our Approach</title>
        <sec id="sec-3-1-1">
          <title>While customizing the new ERP-System for the business</title>
          <p>process “material management” in 1998 we setup a data
warehouse as a prototype using the new SAP Business</p>
        </sec>
        <sec id="sec-3-1-2">
          <title>Information Warehouse. The prototype was constructed to</title>
          <p>gain experiences with methods and tools to obtain a proof
of concept in a small, but representative environment
(“start small – think big”). The database consists of
information object (-types) from the material management
process such as MATERIAL, SUPPLIER, STOCK or</p>
        </sec>
        <sec id="sec-3-1-3">
          <title>ORDER. The data was extracted from the SAP operative system and enriched with legacy host data. We spend 6 months on extending the data warehouse stepwise to critically proof the concept.</title>
        </sec>
      </sec>
      <sec id="sec-3-2">
        <title>4.2 Reconstruction Of Business Terms</title>
        <p>In using the prototype our end users were conflicted with
different business term definitions, such as “order entry”
already mentioned above. The key figures were
“interpreted” in as many different ways as definitions
(interpretations) had been around. Based on the work
from E. Ortner [Ort97] we established a methodology to
obtain company wide clear defined business terms in
using a critical language approach (figure 1).
Collection of statements
• What does the term mean?
• Which objects are included within the term?
• Which characteristics does the term possess?
• Is the term suitable in general?
• Etc.</p>
      </sec>
      <sec id="sec-3-3">
        <title>4.2.2 Finding Defects In Terms</title>
        <sec id="sec-3-3-1">
          <title>Business term definition contains a lot of lingual defects</title>
          <p>such as weaknesses or contradictions. To define the
meaning (semantics) of a term the two concepts
“intention” and “extension” has to be introduced.
Intention means the set of objects which are covered by
the term while extension denotes the set of characteristics
(criteria) which are necessary to identify that an object
belongs to a term set or not. The following term defects
can be identified:
• Synonyms, e.g. terms which have the same meaning
(intention and extension). Example: internal orders or
workshop orders. Those terms are not forbidden in
general if they are known and controlled.
• Homonyms, e.g. terms which are written equal but
have a different meaning (intention and extension).
Example: order entry (customer view) and order entry
(manufacturing view). Homonyms must be cleared
and distinguished, such as customer order entry and
production order entry.
• Equipollents: e.g. same objects (extension) are seen
under a different view (Intention) and denoted
different. Example: stock quantity and stock value.</p>
        </sec>
        <sec id="sec-3-3-2">
          <title>Equipollent has to become uncovered.</title>
          <p>• Weakness, e.g. as no clear demarcation (Intention) is
obtained the set of objects which are covered by the
term (extension) are weak. Example: do orders with
7-2
•
status “not shipped” belong to the key figure “open
order quantity” or not? Weak terms must be cleared.</p>
        </sec>
        <sec id="sec-3-3-3">
          <title>Wrong terms, e.g. terms those meaning (Intention and extension) has changed over time. Wrong terms must be replaced.</title>
        </sec>
      </sec>
      <sec id="sec-3-4">
        <title>4.2.3 Classification Of Statements</title>
        <p>The collection of single statements can be classified for
database applications into:
• Statements about information objects and their
attributes
• Statements about relationships between information
objects
• Statements about events
• Statements about integrity constraints.</p>
        <sec id="sec-3-4-1">
          <title>The statements can be used for the creation of object types (entities) and its relationships within a conceptual data model. Connection words are used for constructing the data model.</title>
        </sec>
      </sec>
      <sec id="sec-3-5">
        <title>4.2.3 Constructing The Conceptual Data Model</title>
        <sec id="sec-3-5-1">
          <title>Based on natural language statements the classified statements can be used to construct a (graphical) entity relationship model.</title>
          <p>The natural language documentation of the relationships
between business terms is the basis for verification and
discussion between IT and company departments. The
(formal) language of a data model is the language of the
data engineer but the dialog with the end user is based on
natural language.
4.2.5</p>
        </sec>
      </sec>
      <sec id="sec-3-6">
        <title>Further Modeling Steps</title>
        <sec id="sec-3-6-1">
          <title>We focused on the modeling of data analysis applications</title>
          <p>as our main interest. In an university research project the
modeling approach was adopted to multidimensional
analysis purposes. The method was expanded by the
concepts “key figures” and “dimension”. Figure 3 shows
the conceptual approach schema [Yak98]:</p>
          <p>Real world
Collection of Statements
The results of the single modeling steps are documented
in the meta data repository of the data warehouse. It is
used as the basis for generating the logical structures
(multidimensional or relational). The meta data of the
repository has been extended with a lexicon component to
serve as a dictionary for business term management and
documentation of the relationship between them.
4.3</p>
        </sec>
      </sec>
      <sec id="sec-3-7">
        <title>Organisational Aspects Of Term Definition</title>
        <sec id="sec-3-7-1">
          <title>The process to business term definition is organize as shown in figure 4: Figure 4: Organization of Business Term Definition</title>
        </sec>
        <sec id="sec-3-7-2">
          <title>A business process is represented by one or more employees with sophisticated knowledge about the business process. These persons are call “process multiplicators”. Their responsibility is to act as a</title>
          <p>7-3
communicator between business process requirements
and the project team. They organize and pre-filter the
information requests and coordinate its realization. They
initialize the definition of new business term definitions
and they are responsible for the organization of the
definition process. A business term is defined by a “god
father” who is responsible for the meaning (semantics) of
a term which belongs to his/her business process. He also
determines the group of persons responsible for reviewing
the definition.</p>
        </sec>
        <sec id="sec-3-7-3">
          <title>The review group is determined for each business term.</title>
        </sec>
        <sec id="sec-3-7-4">
          <title>Its task is to critical review the definition and to release</title>
          <p>the term to be valid company wide.</p>
          <p>The business term administration is responsible for formal
reviews to the completeness of cross references. It
forwards the business terms to the review group,
evaluates methods and procedures and administrates the
tools used for business term definition.</p>
        </sec>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>5 Implementation</title>
      <sec id="sec-4-1">
        <title>5.1 Business Terms and Meta Data</title>
        <p>An appropriated end user access to the data warehouse is
a critical success factor for acceptance and for efficient
and effective information supply. Without any structuring
the end user will not find the information needed – a
circumstance which may convert an elegant data
warehouse solution into a data cemetery. It was the goal
of our system architecture to obtain a complete, consistent
and always actual documentation about the objects of the
data warehouse. Therefore a web application was
designed with Oracle tools. The application serve as an
interface between the meta data repository and the
frontend tools for SAP Business Information Warehouse. The
end user reaches the business term dictionary with an
“information navigator”, a kind of help system. The
information navigator accesses the business term
dictionary and displays the information objects in end
users terminology. An example is (figure 5):
•
•
•
•
•</p>
        <sec id="sec-4-1-1">
          <title>Which information objects are available for my problem?</title>
        </sec>
        <sec id="sec-4-1-2">
          <title>How are they defined?</title>
        </sec>
        <sec id="sec-4-1-3">
          <title>To who can I talk to?</title>
        </sec>
        <sec id="sec-4-1-4">
          <title>How is the access to the information object organized?</title>
        </sec>
        <sec id="sec-4-1-5">
          <title>Which reports are using the term?</title>
          <p>Reports
• Which are available ?
• What is represented ?
• Access rights ?
...</p>
          <p>Data analysis
• Which cubes exist ?
• What is the content ?
• Access rights ?
...</p>
          <p>Key figures
• Which key figures exit?
• What is the content ?
• Wer darf sie abfragen?
...</p>
          <p>Business terms
• Which term exists ?
• How are they defined ?
• Existing synonyms ?
• Who is responsible ?
• Impact / Cross refs ? ...</p>
          <p>Warehouse-objects
• Which infoobjects exist?
• What does they mean ?
• Access rights ?
...</p>
          <p>Warehouse-Queries
• Which queries exist ?
• What is the description ?
• Access rights ?
...</p>
          <p>Business Support applications
• Which application exist ?
• What can you do with it?
• Access rights ?
...</p>
        </sec>
        <sec id="sec-4-1-6">
          <title>As Lawson Mardon Singen is operating on the global</title>
          <p>market it is necessary to obtain world wide access to the
data warehouse. Therefore intranet technology plays an
important role for our warehouse project. The tool used
for designing an appropriated user interface is Dynasight
from Arcplan [ARC99]. Dynasight is certified to access</p>
        </sec>
        <sec id="sec-4-1-7">
          <title>SAP Business Information Warehouse and other common data warehouse platforms.</title>
        </sec>
        <sec id="sec-4-1-8">
          <title>To access SAP Business Information Warehouse a central</title>
          <p>Dynasight-Server connects to the system and asks for
processing an end user request. The OLAP-Server
processes the query in dialog with the data warehouse
kernel. The data returned contains a link to the business
term dictionary. The Dynasight-Server automatical
creates a dynamic document with a hyperlink to the
business term dictionary (figure 8). Any browser can
present the (Java) documents.</p>
        </sec>
        <sec id="sec-4-1-9">
          <title>The end user can directly reach the business term dictionary on clicking on the link which is contained in the document title (figure 7). Figure 7: Linking business term dictorary</title>
          <p>Operative
data
SAP R/3
Business termst
dynaSight-Server</p>
        </sec>
      </sec>
      <sec id="sec-4-2">
        <title>Insight-Anwendungen</title>
        <sec id="sec-4-2-1">
          <title>ODBO Insight</title>
          <p>File
ODBO
Insight</p>
          <p>File
SAP BW
OLAP Server
Insight</p>
          <p>File
SAP BW
Startup pages
dynaCGI
dynaJava
Applet
HTML
Insight with dynaSight
extensions
Internet</p>
        </sec>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>Experiences</title>
      <p>Our main focus was to integrate clear defined business
terms into the meta data of the warehouse to obtain a high
quality information supply. After 4 months we have
defined 500 business terms. We expect 2000 terms until
the end of 1999. The main experiences are:
•
•
•
•
•
•
•</p>
      <sec id="sec-5-1">
        <title>Time is needed to implement (establish) the method in the organisation.</title>
      </sec>
      <sec id="sec-5-2">
        <title>The method works in prinziple – some further research work has to be done to support business term life cycle.</title>
      </sec>
      <sec id="sec-5-3">
        <title>High acceptance and understanding from the end user</title>
        <p>for the need to critical business term definition</p>
      </sec>
      <sec id="sec-5-4">
        <title>Start from the beginning of the project. Reverse documentation is very time consuming and difficult to obtain</title>
      </sec>
      <sec id="sec-5-5">
        <title>A sponor is needed as an advocate for the required time expense</title>
      </sec>
      <sec id="sec-5-6">
        <title>Tools support ER Modelling with classified business term are available such as Oracle Designer/2000 [ORA99]</title>
      </sec>
      <sec id="sec-5-7">
        <title>A tool is needed to administrate and integrate the the business term definitions into the meta data repository of the data warehouse.</title>
      </sec>
      <sec id="sec-5-8">
        <title>In the need future we will link SAP’s Knowlegde</title>
      </sec>
      <sec id="sec-5-9">
        <title>Mangement Modul with SAP Business Information</title>
      </sec>
      <sec id="sec-5-10">
        <title>Warehouse. Interface mechanisms are currently under study.</title>
        <p>End Users
[ORA99] Oracle Corp., http://www.oracle.com,
11-apr99.</p>
      </sec>
      <sec id="sec-5-11">
        <title>Methodenneutraler Fachentwurf,</title>
      </sec>
      <sec id="sec-5-12">
        <title>Wirtschaftsinformatik, Stuttgart,</title>
      </sec>
      <sec id="sec-5-13">
        <title>Warehouse,</title>
      </sec>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [ARC99]
          <article-title>Arcplan's DynaSight</article-title>
          . http://www.arcplan.de, 13-apr-99
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [Ort97]
          <string-name>
            <given-names>E.</given-names>
            <surname>Ortner.</surname>
          </string-name>
          Teubner-Reihe Leipzig,
          <year>1997</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>[SAP99] SAP Business Information http://www.sap-ag.de/bw, 11-apr-99.</mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>