<?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: difference of data element and domain in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/difference-of-data-element-and-domain/m-p/3329642#M797621</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Suja,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;U&gt;&lt;STRONG&gt;Domain:&lt;/STRONG&gt;&lt;/U&gt;   - A domain describes the technical settings of a table field.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;   - A domain defines a value range, which sets the permissible data values for the fields, which refers to this domain.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  - A single domain can be used as basis for any number of fields that are identical in structure.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;U&gt;&lt;STRONG&gt;Data element:&lt;/STRONG&gt;&lt;/U&gt; &lt;/P&gt;&lt;P&gt; - A data element describes the role played by a domain in a technical context. &lt;/P&gt;&lt;P&gt; -  A data element contains semantic information.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward If Useful.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Chitra Parameswaran&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 22 Jan 2008 05:13:56 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-01-22T05:13:56Z</dc:date>
    <item>
      <title>difference of data element and domain</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/difference-of-data-element-and-domain/m-p/3329635#M797614</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi,&lt;/P&gt;&lt;P&gt;please tell me difference of data element and domain&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Jan 2008 04:29:39 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/difference-of-data-element-and-domain/m-p/3329635#M797614</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-22T04:29:39Z</dc:date>
    </item>
    <item>
      <title>Re: difference of data element and domain</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/difference-of-data-element-and-domain/m-p/3329636#M797615</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;STRONG&gt;Domains:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Domain is the central object for describing the technical characteristics of an attribute of an business objects. It describes the value range of the field. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Data Element:&lt;/STRONG&gt; &lt;/P&gt;&lt;P&gt;It is used to describe the semantic definition of the table fields like description the field. Data element describes how a field can be displayed to end-user. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Domain&lt;/STRONG&gt; is stored in &lt;STRONG&gt;DD01L&lt;/STRONG&gt; table&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Data elements&lt;/STRONG&gt; is stored in &lt;STRONG&gt;DD04L&lt;/STRONG&gt; table&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;REward points if useful.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Jan 2008 04:31:04 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/difference-of-data-element-and-domain/m-p/3329636#M797615</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-22T04:31:04Z</dc:date>
    </item>
    <item>
      <title>Re: difference of data element and domain</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/difference-of-data-element-and-domain/m-p/3329637#M797616</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Data element contains description of the field&lt;/P&gt;&lt;P&gt;domain contains the technical information&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Jan 2008 04:32:09 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/difference-of-data-element-and-domain/m-p/3329637#M797616</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-22T04:32:09Z</dc:date>
    </item>
    <item>
      <title>Re: difference of data element and domain</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/difference-of-data-element-and-domain/m-p/3329638#M797617</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A table is composed of fields. To create a field you need a data element. The data element contains the field labels and online documentation (also called F1 help) for the field. It is purely descriptive; it contains the semantic characteristics for the field, also known as the "business context." The labels you provide within a data element will be displayed on the screen beside an input field. The data element also contains documentation that is displayed when the user asks for help on that field by pressing the &lt;/P&gt;&lt;P&gt;F1 key. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A data element's definition requires a domain (see Figure 3.5). The domain contains the technical characteristics of a field, such as the field length and data type. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Domains and data elements are reusable. A domain can be used in more than one data element, and a data element can be used in more than one field and in more than one table. &lt;/P&gt;&lt;P&gt;For example, assume you need to design a customer information table called zcust that must contain work, fax, and home telephone numbers &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;create a field, you usually start by creating a domain for it. In this case, you might create a generic telephone number domain, name it zphone and give it a data type of CHAR and a length of 12. This would be a generic telephone number domain; most types of telephone numbers could be stored using this domain. As such, it can be used to define specific types of telephone numbers, such as fax or home telephone numbers. &lt;/P&gt;&lt;P&gt;After creating the domain to hold the purely technical description of a field, you then create a data element to hold the descriptive attributes of the field. In the data element you must enter the name of a domain to give it technical characteristics. Then, you enter the labels and documentation (F1 help) to describe the data you will store. In this example, you would probably create three data elements, one for each of the home, work, and fax telephone numbers. In each data element, you would enter field labels describing the type of telephone number you will store with it, and the F1 help for the end-user. &lt;/P&gt;&lt;P&gt;Having created the data elements, you can now create the table. You could create three phone number fields in the table (home, work, and fax) and assign the corresponding data element to each field. A data element is assigned to each field. This gives the field descriptive information from the data element and technical information from the domain that it references. When the field is used on a screen, it obtains a label and F1 help documentation from the data element, and its length and data type form the domain within the data element. &lt;/P&gt;&lt;P&gt;In another example, you might need to store a person's name in three different tables: customer, vendor, and employee tables. In the customer table you want to store a customer name, in the vendor table a vendor name, and in the employee table an employee name. Because it is a good idea to give the same data type and length to all person-name fields, you can create a single generic person-name domain, for example zpersname. Then you can create a data element for each business usage of a person's name: for the customer name, the vendor name, and the employee name. Within each data element you refer to your zpersname domain to give them all the same characteristics. You could then use these data elements to create fields within each table.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Jan 2008 04:51:43 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/difference-of-data-element-and-domain/m-p/3329638#M797617</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-22T04:51:43Z</dc:date>
    </item>
    <item>
      <title>Re: difference of data element and domain</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/difference-of-data-element-and-domain/m-p/3329639#M797618</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Domain provides technical attributes for field like data type, length, and possible value range.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Data element provides business context. i.e., it provides field labels for the field in the backend,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Data type :&lt;/P&gt;&lt;P&gt;A data element is an elementary type. It describes the type attributes (data type, field length and possibly the number of decimal places) and screen information (explanatory text or field help) about unstructured data objects (table fields and structure fields or variables).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Table fields and structure fields with the same contents should refer to the same data element. This ensures that the attributes of these fields are always consistent.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A data element can be referenced in ABAP programs with TYPE. This permits you to define variables that take on the type attributes of the data element in an ABAP program.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Domain : &lt;/P&gt;&lt;P&gt;A domain describes the technical attributes of a field, such as the data type or the number of positions in a field. The domain defines primarily a value range describing the valid data values for the fields referring to this domain.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Different technical fields of the same type can be combined in a domain. Fields referring to the same domain are changed at the same time when a domain is changed. This ensures the consistency of these fields.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Additional info about data element &lt;/P&gt;&lt;P&gt;1.Data type, number of places and possibly the decimal places were entered directly. In this case the field is not filled.&lt;/P&gt;&lt;P&gt;2.A data element is assigned to the field. The field then gets its data type, length and possibly decimal places from this data element. The semantic attributes of the element (field help, representation of the field in input templates with keyword text, column headers for list output of the table contents and editing of the output with parameter IDs) are also copied.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Domain - Specifies the technical attributes of a data &lt;/P&gt;&lt;P&gt;element - its data type, length, possible values, and &lt;/P&gt;&lt;P&gt;appearance on the screen.Each data element has an &lt;/P&gt;&lt;P&gt;underlying domain. A single domain can be the basis for &lt;/P&gt;&lt;P&gt;several data elements. Domains are objects in the ABAP &lt;/P&gt;&lt;P&gt;Dictionary. &lt;/P&gt;&lt;P&gt;             Data Element - Describes the business function &lt;/P&gt;&lt;P&gt;of a table field. Its technical attributes are based on a &lt;/P&gt;&lt;P&gt;domain, and its business function is described by its field &lt;/P&gt;&lt;P&gt;labels and documentation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Domain: describes the data type .&lt;/P&gt;&lt;P&gt;Data element: Nothing but the semantic representation of&lt;/P&gt;&lt;P&gt;fields (ex: Label names)&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;vasavi.&lt;/P&gt;&lt;P&gt;kindly reward if helpful.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Jan 2008 05:04:12 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/difference-of-data-element-and-domain/m-p/3329639#M797618</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-22T05:04:12Z</dc:date>
    </item>
    <item>
      <title>Re: difference of data element and domain</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/difference-of-data-element-and-domain/m-p/3329640#M797619</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;we can defferenciate them like this simply,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;domain&lt;/STRONG&gt;: where can maintain technical properties for the field&lt;/P&gt;&lt;P&gt;i.e. char type and lenth of the field..&lt;/P&gt;&lt;P&gt;ex: take kunnr field which char type is &lt;STRONG&gt;c&lt;/STRONG&gt; and lenth is &lt;STRONG&gt;10&lt;/STRONG&gt;, these char type c and lenth 10 we r maintaining in domain.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;data element:&lt;/STRONG&gt; where we can maintain business meaning for the field&lt;/P&gt;&lt;P&gt;i.e. name which can understand&lt;/P&gt;&lt;P&gt;ex: kunnr is nothing but customer no that we can define in dataelement..&lt;/P&gt;&lt;P&gt;&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;seshu.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Jan 2008 05:05:34 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/difference-of-data-element-and-domain/m-p/3329640#M797619</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-22T05:05:34Z</dc:date>
    </item>
    <item>
      <title>Re: difference of data element and domain</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/difference-of-data-element-and-domain/m-p/3329641#M797620</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A data element describes either an elementary type or a reference type.An elementary type is defined by the built-in data type, length and possibly the number of decimal places. These type attributes can either be defined directly in the data element or copied from a domain.&lt;/P&gt;&lt;P&gt;A reference type defines the types of reference variables in ABAP programs.&lt;/P&gt;&lt;P&gt;You can use a data element to define the type of a table field, structure component or the row type of a table type. A data element can also be referenced in ABAP programs with TYPE. As a result, variables that take on the attributes of a data element can be defined in an ABAP program&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Domain:&lt;/P&gt;&lt;P&gt;A domain defines a value range. A domain is assigned to a data element. All table fields or structure components that use this data element then have the value range defined by the domain. The relationship between the field or component and the domain is thus defined by the data element of the field or component.&lt;/P&gt;&lt;P&gt;Fields or components that refer to the same domain (with the assigned data elements) are also changed when the domain is changed. This ensures that the value ranges of these fields or components are consistent. Fields or components that are technically the same can thus be combined with a reference to the same domain.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;rewrd if its useful&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Jan 2008 05:06:15 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/difference-of-data-element-and-domain/m-p/3329641#M797620</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-22T05:06:15Z</dc:date>
    </item>
    <item>
      <title>Re: difference of data element and domain</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/difference-of-data-element-and-domain/m-p/3329642#M797621</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Suja,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;U&gt;&lt;STRONG&gt;Domain:&lt;/STRONG&gt;&lt;/U&gt;   - A domain describes the technical settings of a table field.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;   - A domain defines a value range, which sets the permissible data values for the fields, which refers to this domain.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  - A single domain can be used as basis for any number of fields that are identical in structure.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;U&gt;&lt;STRONG&gt;Data element:&lt;/STRONG&gt;&lt;/U&gt; &lt;/P&gt;&lt;P&gt; - A data element describes the role played by a domain in a technical context. &lt;/P&gt;&lt;P&gt; -  A data element contains semantic information.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward If Useful.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Chitra Parameswaran&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Jan 2008 05:13:56 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/difference-of-data-element-and-domain/m-p/3329642#M797621</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-22T05:13:56Z</dc:date>
    </item>
    <item>
      <title>Re: difference of data element and domain</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/difference-of-data-element-and-domain/m-p/3329643#M797622</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi,&lt;/P&gt;&lt;P&gt;elementary data type- all basic data types provided by sap&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;reference data type- any user defined data type that is in turn&lt;/P&gt;&lt;P&gt;                              defined  in a program using TYPE &lt;/P&gt;&lt;P&gt;                            e.g.-d1 .&lt;/P&gt;&lt;P&gt;                               data d1 type &amp;lt;basic sap data type&amp;gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;have i got the above definitions correct? if not give me the &lt;/P&gt;&lt;P&gt;proper explanation.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Jan 2008 05:54:17 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/difference-of-data-element-and-domain/m-p/3329643#M797622</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-22T05:54:17Z</dc:date>
    </item>
    <item>
      <title>Re: difference of data element and domain</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/difference-of-data-element-and-domain/m-p/3329644#M797623</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;yes, that declaration is correct.&lt;/P&gt;&lt;P&gt;reference type is type and like.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Jan 2008 06:30:32 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/difference-of-data-element-and-domain/m-p/3329644#M797623</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-22T06:30:32Z</dc:date>
    </item>
    <item>
      <title>Re: difference of data element and domain</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/difference-of-data-element-and-domain/m-p/3329645#M797624</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Data elements (elementary types)&lt;/P&gt;&lt;P&gt;Elementary types have no structure. They describe the data type attributes (such as given Dictionary data type, number of places) and information that is relevant for the screen (such as title) of unstructured data objects (variables/fields).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Structures (structured types) Structured types describe the structure and functions of any structured data objects, that is of data structures with components of any type.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A component can be a field with an elementary type or can itself be a structure. A table can also be used as a component in a structure.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A database table always has a structure and is therefore implicitly a structured type. However, the fields of a database table can only have an elementary type.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Table types Table types describe the structure and functions of internal tables in the ABAP program. Their rows can have any row type. Table types with elementary row type therefore can be defined just the same as multi-dimensional table types (table types with a table type as row type) or table types using structures with table-like components.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The basic objects for defining data in the ABAP Dictionary are tables, data elements and domains. The domain is used for the technical definition of a table field (for example field type and length) and the data element is used for the semantic definition (for example short description).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A domain describes the value range of a field. It is defined by its data type and length. The value range can be limited by specifying fixed values.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A data element describes the meaning of a domain in a certain business context. It contains primarily the field help (F1 documentation) and the field labels in the screen.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A field is not an independent object. It is table-dependent and can only be maintained within a table.&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;You can enter the data type and number of places directly for a field. No data element is required in this case. Instead the data type and number of places is defined by specifying a direct type.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The data type attributes of a data element can also be defined by specifying a built-in type, where the data type and number of places is entered directly.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Two Level Domain Example&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A domain defines a field technically and therefore it may&lt;/P&gt;&lt;P&gt;be used at different business levels.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A data element describes the meaning of a domain in a certain business context.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A domain, however, is used for the technical definition of a table field (for example field type and length).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Therefore, although a take-off airport (data element S_FROMAIRP) would have a different business meaning from an airport where a plane lands (data element S_TOAIRP), they could still have the same domain(here S_AIRPID) because technically we could assign the same number of characters whether the airport is a take-off or a landing airport.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Jan 2008 06:49:37 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/difference-of-data-element-and-domain/m-p/3329645#M797624</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-22T06:49:37Z</dc:date>
    </item>
    <item>
      <title>Re: difference of data element and domain</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/difference-of-data-element-and-domain/m-p/3329646#M797625</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi  ,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Domains&lt;/STRONG&gt;:Domain is the central object for describing the technical characteristics of an attribute of an business objects. It describes the value range of the field. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Data Element&lt;/STRONG&gt;: It is used to describe the semantic definition of the table fields like description the field. Data element describes how a field can be displayed to end-user. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward  points if it is usefull...&lt;/P&gt;&lt;P&gt;Girish&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Jan 2008 07:39:51 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/difference-of-data-element-and-domain/m-p/3329646#M797625</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-22T07:39:51Z</dc:date>
    </item>
    <item>
      <title>Re: difference of data element and domain</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/difference-of-data-element-and-domain/m-p/3329647#M797626</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;To create a field in  a table  you need a data element and domain to define its technical and non technical characterstics.&lt;/P&gt;&lt;P&gt;The data element contains the field labels and online documentation (also called F1 help) for the  field.The labels you provide within a data element will be displayed on the screen beside an input field.&lt;/P&gt;&lt;P&gt;A data element's definition requires a domain .The domain contains the technical characteristics of a field, such as the field length and data type.Domains and data elements are reusable. A domain can be used in more than one data element, and a data element can be used in more than one field and in more than one table. &lt;/P&gt;&lt;P&gt;Different technical fields of the same type can be combined in a domain. Fields referring to the same domain are changed at the same time when a domain is changed. This ensures the consistency of these fields.&lt;/P&gt;&lt;P&gt;To create a field in  a table  you need a data element and domain to define its technical and non technical characterstics.&lt;/P&gt;&lt;P&gt;The data element contains the field labels and online documentation (also called F1 help) for the  field.The labels you provide within a data element will be displayed on the screen beside an input field.&lt;/P&gt;&lt;P&gt;A data element's definition requires a domain .The domain contains the technical characteristics of a field, such as the field length and data type.Domains and data elements are reusable. A domain can be used in more than one data element, and a data element can be used in more than one field and in more than one table. &lt;/P&gt;&lt;P&gt;Different technical fields of the same type can be combined in a domain. Fields referring to the same domain are changed at the same time when a domain is changed. This ensures the consistency of these fields.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 23 Jan 2008 05:04:17 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/difference-of-data-element-and-domain/m-p/3329647#M797626</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-23T05:04:17Z</dc:date>
    </item>
    <item>
      <title>Re: difference of data element and domain</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/difference-of-data-element-and-domain/m-p/3329648#M797627</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;go thru the links for interesting stuff...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;domain&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_47x200/helpdata/en/fb/54833c4f3e092de10000000a114027/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_47x200/helpdata/en/fb/54833c4f3e092de10000000a114027/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;data element&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_47x200/helpdata/en/90/8d72feb1af11d194f600a0c929b3c3/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_47x200/helpdata/en/90/8d72feb1af11d194f600a0c929b3c3/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;teja.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 23 Jan 2008 05:26:21 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/difference-of-data-element-and-domain/m-p/3329648#M797627</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-23T05:26:21Z</dc:date>
    </item>
    <item>
      <title>Re: difference of data element and domain</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/difference-of-data-element-and-domain/m-p/3329649#M797628</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi prs,&lt;/P&gt;&lt;P&gt;i think ur answer is different and seems to be relevant also.&lt;/P&gt;&lt;P&gt;what is reference from which u got this answer?  it may be useful to me also.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 31 Jan 2008 04:24:25 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/difference-of-data-element-and-domain/m-p/3329649#M797628</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-31T04:24:25Z</dc:date>
    </item>
    <item>
      <title>Re: difference of data element and domain</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/difference-of-data-element-and-domain/m-p/3329650#M797629</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi suja,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Data Element : which describes the meaning of the field&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Domain : Which determines the technical characteristic of the field&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Regards,&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Azhar&lt;/STRONG&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Feb 2008 07:07:15 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/difference-of-data-element-and-domain/m-p/3329650#M797629</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-02-01T07:07:15Z</dc:date>
    </item>
    <item>
      <title>Re: difference of data element and domain</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/difference-of-data-element-and-domain/m-p/3329651#M797630</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hai,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Domain: Domain  Describes the Technical Attributes of a field.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Where as  Data elements describe the contextual meaning of a field.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 02 Feb 2008 11:26:33 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/difference-of-data-element-and-domain/m-p/3329651#M797630</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-02-02T11:26:33Z</dc:date>
    </item>
    <item>
      <title>Re: difference of data element and domain</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/difference-of-data-element-and-domain/m-p/3329652#M797631</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&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, 04 Feb 2008 09:21:20 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/difference-of-data-element-and-domain/m-p/3329652#M797631</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-02-04T09:21:20Z</dc:date>
    </item>
    <item>
      <title>Re: difference of data element and domain</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/difference-of-data-element-and-domain/m-p/3329653#M797632</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;A data element describes either an elementary type or a reference type.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;An elementary type is defined by the built-in data type, length and possibly the number of decimal places. These type attributes can either be defined directly in the data element or copied from a  domain.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A reference type defines the types of reference variables in ABAP programs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can use a data element to define the type of a table field, structure component or the row type of a table type. A data element can also be referenced in ABAP programs with TYPE. As a result, variables that take on the attributes of a data element can be defined in an ABAP program.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Information about the meaning of a table field or structure component and information about editing the corresponding screen field can be assigned to a data element. This information is automatically available to all screen fields that refer to the data element.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This information includes the display of the field in input templates using key word text, column headers for list output of the table contents (see Field Labels ), and output editing using parameter IDs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is also true for online field documentation. The text appearing in the field help (F1 help) in a field of an input template (see Documentation and Docu Status) comes from the corresponding data element.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The field CONNID (flight class) of table SBOOK refers to the data element S_CONN_ID. This data element gets its technical attributes (data type NUMC, field length 4) from domain S_CONN_ID. Data element S_CONN_ID describes the technical attributes and meaning (with an assigned long text and an explanatory short text) of field CONNID (and all other fields that refer to this data element).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A variable having the type of data element S_CONN_ID can be defined in an ABAP program with the statement DATA CONNID TYPE S_CONN_ID.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;chk this link - &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw70/helpdata/en/90/8d72feb1af11d194f600a0c929b3c3/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw70/helpdata/en/90/8d72feb1af11d194f600a0c929b3c3/content.htm&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 04 Feb 2008 10:08:01 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/difference-of-data-element-and-domain/m-p/3329653#M797632</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-02-04T10:08:01Z</dc:date>
    </item>
    <item>
      <title>Re: difference of data element and domain</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/difference-of-data-element-and-domain/m-p/3329654#M797633</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;domain contains technical specifications such as data types and data element contains symantecs such as field lables.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 04 Feb 2008 12:53:22 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/difference-of-data-element-and-domain/m-p/3329654#M797633</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-02-04T12:53:22Z</dc:date>
    </item>
  </channel>
</rss>

