<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Why three levels?? in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/why-three-levels/m-p/3179946#M757058</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Abhishek,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Usage of Data elements &amp;amp; domains supports reusability.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You must be knowing that data element defines sematic characters &amp;amp; domain defines technical characters.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;say for example,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You want to create tables customer_detials, Vendor_details &amp;amp; employee_details.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;All the 3 tables contains the name of the customer or vendor or employee.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You create a domain of CHAR(20) which can be used in dataelement of first name, second name, surname. These data elements can be used in the tables.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thus later if you decide to increase/decrease the size assigned to any of the fields, its enough to change in domain else you need to change in first name, second name &amp;amp; surname of all tables which is cumbersome.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thats why 3 levels which eases the maintenance.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Naga Sai Swapna&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 10 Dec 2007 11:53:49 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-12-10T11:53:49Z</dc:date>
    <item>
      <title>Why three levels??</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/why-three-levels/m-p/3179943#M757055</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi experts,&lt;/P&gt;&lt;P&gt;                 Why any fields in the data dictionary has three levels of hierarchy or grouping? Why do we have data elements,domain and data types?Why datatypes alone is not sufficient for any field?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I will reward points for clear explanations.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TIA&lt;/P&gt;&lt;P&gt;Abhishek&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 10 Dec 2007 11:01:29 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/why-three-levels/m-p/3179943#M757055</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-12-10T11:01:29Z</dc:date>
    </item>
    <item>
      <title>Re: Why three levels??</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/why-three-levels/m-p/3179944#M757056</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;A field in SAP DDIC is defined using domain and data &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;elements. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Domain describes the data type and length of the field, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ie it gives the technical details of the field.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And, Data element describes what the data element means &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;in business context, ie the semantic information &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regarding the field. (You get the same through the F1 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;documentation.)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DDIC is responsible for enforcing the data integrity, &lt;/P&gt;&lt;P&gt;and managing data without redundancy. Now data &lt;/P&gt;&lt;P&gt;redundancy is reduced by linking similar information to &lt;/P&gt;&lt;P&gt;the same data definition. For example, an employee &lt;/P&gt;&lt;P&gt;table will contain Name, so will be the case in a &lt;/P&gt;&lt;P&gt;Customer table. Now both of the information are of &lt;/P&gt;&lt;P&gt;similar technical qualities however they are of &lt;/P&gt;&lt;P&gt;different semantic details. In this case to avoid &lt;/P&gt;&lt;P&gt;redundancy we can use the same domain for name fields &lt;/P&gt;&lt;P&gt;in both the fields and use different data elements for &lt;/P&gt;&lt;P&gt;the semantic details.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Besides, this helps in easy access of development &lt;/P&gt;&lt;P&gt;objects. Having similar objects can help us find &lt;/P&gt;&lt;P&gt;different objects of similar kind.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this was helpful.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Rajesh. K. Soman&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For further reading you can refer the link below.&lt;/P&gt;&lt;P&gt;&lt;A href="http://en.wikipedia.org/wiki/ABAP#The_ABAP_dictionary" target="test_blank"&gt;http://en.wikipedia.org/wiki/ABAP#The_ABAP_dictionary&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 10 Dec 2007 11:42:53 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/why-three-levels/m-p/3179944#M757056</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-12-10T11:42:53Z</dc:date>
    </item>
    <item>
      <title>Re: Why three levels??</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/why-three-levels/m-p/3179945#M757057</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Abhishek,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Data Type and Length are the characterstics that are common in betwween data-element and data-domain. There are other things which signify the importance of both in the dictionary. &lt;/P&gt;&lt;P&gt;Please see the creation screen for both the items and you will get the desired information.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regds,&lt;/P&gt;&lt;P&gt;Gaurav&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 10 Dec 2007 11:44:01 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/why-three-levels/m-p/3179945#M757057</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-12-10T11:44:01Z</dc:date>
    </item>
    <item>
      <title>Re: Why three levels??</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/why-three-levels/m-p/3179946#M757058</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Abhishek,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Usage of Data elements &amp;amp; domains supports reusability.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You must be knowing that data element defines sematic characters &amp;amp; domain defines technical characters.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;say for example,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You want to create tables customer_detials, Vendor_details &amp;amp; employee_details.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;All the 3 tables contains the name of the customer or vendor or employee.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You create a domain of CHAR(20) which can be used in dataelement of first name, second name, surname. These data elements can be used in the tables.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thus later if you decide to increase/decrease the size assigned to any of the fields, its enough to change in domain else you need to change in first name, second name &amp;amp; surname of all tables which is cumbersome.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thats why 3 levels which eases the maintenance.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Naga Sai Swapna&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 10 Dec 2007 11:53:49 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/why-three-levels/m-p/3179946#M757058</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-12-10T11:53:49Z</dc:date>
    </item>
    <item>
      <title>Re: Why three levels??</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/why-three-levels/m-p/3179947#M757059</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Why any fields in the data dictionary has three levels of hierarchy or grouping? &lt;/P&gt;&lt;P&gt;Answer:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A Unique or one way of representing Data Types are Domain.&lt;/P&gt;&lt;P&gt;Data types can be of two types one of which is elementary  type which again has two options Domain and Built in Type(Mostly customized) .  This explains Domain&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Data types --&amp;gt; 1)elementary &lt;/P&gt;&lt;P&gt;                            &lt;/P&gt;&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;                      i)Domain   ii)Built in&lt;/P&gt;&lt;P&gt;               --&amp;gt;2) Reference Type which is again divided in to i))Name of Ref type and ii))Reference to Predefined Type&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Data elements ---&amp;gt; Data Types &lt;/P&gt;&lt;P&gt;                              |____Domain&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Why datatypes alone is not sufficient for any field?&lt;/P&gt;&lt;P&gt;Answer:&lt;/P&gt;&lt;P&gt;Your Data element is your SAP Table Fields which you use in real scenarios like for example an Employee table has emp no,empname&lt;/P&gt;&lt;P&gt;empno - data element data type can be INT (4) which can also be  domain &lt;/P&gt;&lt;P&gt;             or declare reference type instead of domain&lt;/P&gt;&lt;P&gt;Data types should have either Elementary type or Reference type.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CHECK SE11 for more information.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward Points if useful.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Anita&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 10 Dec 2007 12:25:36 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/why-three-levels/m-p/3179947#M757059</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-12-10T12:25:36Z</dc:date>
    </item>
  </channel>
</rss>

