<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/tg/onlinemanual/em000850" xml:lang="it">
   <Header>
      <Title>Introduction</Title>
      <Keyword type="header" order="d1e2047043">
         <Level1>Introduction</Level1>
         <Level2>Data models</Level2>
      </Keyword>
      <Keyword type="header" order="d1e2047049">
         <Level1>Data models</Level1>
         <Level2>introduction</Level2>
      </Keyword>
   </Header>
   <AimSection ID="aim_em000850">
      <Paragraph>The data model is the fourth type of diagram you can model in
		the Modeler. A data model describes the permanent storage components, and their
		structures, on multiple abstraction levels.</Paragraph>
   </AimSection>
   <GeneralSection>
      <Paragraph>Entity relationship modeling aims to show the meaning and
		relevance of data for an organization. The main aim of entity relationship
		modeling is to document the LN application databases.</Paragraph>
      <Paragraph>Part of the ERM-module is the Modeler. With this modeler you can
		edit entity relationship diagrams and graphically represent the data models.
		You can create a new conceptual database design or document an existing
		database.</Paragraph>
      <Paragraph>The data model supplies information about the physical or
		logical data model of the package combination to which the enterprise model
		applies. The data model does not yet influence the configuration of the LN software.</Paragraph>
      <Paragraph>The data model is located within the enterprise modeler
		environment; functionally, it is a subcomponent of the enterprise
		model.</Paragraph>
      <Paragraph>In terms of modeling, the data model is directly created without
		placing it in a reference or project model, and without using a
		repository.</Paragraph>
   </GeneralSection>
</ManualTopic>