<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/tg/onlinemanual/tgerm" xml:lang="de" TopicType="Overview">
   <Header>
      <Title>Entity Relationship Modeling</Title>
      <Keyword type="header" order="d1e2448683">
         <Level1>Entity Relationship Modeling</Level1>
      </Keyword>
   </Header>
   <AimSection>
      <Paragraph>The primary objective of entity relationship modeling is to document the ERP
application databases. A data model describes the permanent storage  components
and their structures on multiple abstraction levels. Moreover, entity
relationship modeling aims at showing the meaning and relevance of data for an
organization. Part of the ERM-module is the Modeler, which enables you to edit
entity relationship diagrams, which graphically represent the data models. You
can create a new conceptual database design or document an existing database.
The data model is used to give information about the physical and/or logical
data model of the ERP package combination to which the enterprise model
applies. The data model does not yet influence the configuration of the ERP
software.</Paragraph>
   </AimSection>
   <GeneralSection>
      <Paragraph>The data model is located within the enterprise modeler environment.
Functionally, it is a subcomponent of the enterprise model.
In terms of modeling the data model is directly created without placing it in a
reference or project model, and without using a <Link href="/baanerp/tg/glossary/glossary#000093" role="glossary">repository</Link>.</Paragraph>
      <Paragraph>The following topics are available:</Paragraph>
   </GeneralSection>
</ManualTopic>