<?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: transparent table in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/transparent-table/m-p/3448467#M828353</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Radharaman,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Field in the table is used for only name purpose. Like MATNR for Material number, WERKS for Plant like that...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But Data Element is the one which will contains semantic attributes of the field like text of that element. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Domain will have techinical attrbutes like type and length.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Dataelement will have the domain. And one more thing is that, In data element without Domain you can define technical attributes for the fields.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward If Helpful.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;--&lt;/P&gt;&lt;P&gt;Sasidhar Reddy Matli.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 12 Feb 2008 06:24:10 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-02-12T06:24:10Z</dc:date>
    <item>
      <title>transparent table</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/transparent-table/m-p/3448462#M828348</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;what is the difference between field and data element in table.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 12 Feb 2008 06:14:27 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/transparent-table/m-p/3448462#M828348</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-02-12T06:14:27Z</dc:date>
    </item>
    <item>
      <title>Re: transparent table</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/transparent-table/m-p/3448463#M828349</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Data element specifies the length and description of the field (i.e technical attributes of a field)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1 data element can be attached to many fields of a table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Example: Check table BKPF (transaction SE11/12)&lt;/P&gt;&lt;P&gt;BELNR is the technical name of the field.&lt;/P&gt;&lt;P&gt;BELNR_D is its data element which defines how much data the field can hold and the data should be of which type (char/numc/int etc). Also the description 'Accounting Document Number' is specified in the data element&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 12 Feb 2008 06:20:35 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/transparent-table/m-p/3448463#M828349</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-02-12T06:20:35Z</dc:date>
    </item>
    <item>
      <title>Re: transparent table</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/transparent-table/m-p/3448464#M828350</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 element is one which have the symatic representation of your field in which you call the domine.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Domine is one which will have the technical atributes of the field.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Field is just a name of the column in your table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;hope it will be clear for you.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;reward Points if it is usefull&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;&lt;P&gt;Chandrra&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 12 Feb 2008 06:20:39 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/transparent-table/m-p/3448464#M828350</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-02-12T06:20:39Z</dc:date>
    </item>
    <item>
      <title>Re: transparent table</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/transparent-table/m-p/3448465#M828351</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 is a part of the database table, one of the components of the DB table structure.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However a data element is a reference for the DB field. It defines the technical attributes of the DB field i.e. length, type (char/int etc.).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A data element is hence an independent data dictionary object (created from SE11) and can exist by itself and be used in a number of database tables.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But a field can exist only under a database table and is unique to that database table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;Aditya&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 12 Feb 2008 06:21:35 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/transparent-table/m-p/3448465#M828351</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-02-12T06:21:35Z</dc:date>
    </item>
    <item>
      <title>Re: transparent table</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/transparent-table/m-p/3448466#M828352</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;In the description of a database table, the table lines consist of single fields or columns. An elementary data type must be assigned to each column. The elementary types in the ABAP Dictionary are data elements. Like data objects in ABAP programs, database tables and views have data types as attributes. A line of a database table or view has the data type of a flat structure, which consists of individual data elements.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Data elements in the ABAP Dictionary describe individual fields. They are the smallest indivisible units of the complex types described below, and are used to specify the types of columns in the database. Data elements can be elementary types or reference types.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;·        Elementary Types&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Elementary types are part of the dual-level domain concept for fields in the ABAP Dictionary. The elementary type has semantic attributes, such as texts, value tables, and documentation, and has a data type. There are two different ways to specify a data type:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;¡        By directly assigning an ABAP Dictionary type.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can assign a predefined ABAP Dictionary type and a number of characters to an elementary type. The ABAP Dictionary has considerably more predefined types than the ABAP programming language. The number of characters here is not the field length in bytes, but the number of valid characters excluding formatting characters. The data types are different because the predefined data types in the ABAP Dictionary have to be compatible with the external data types of the database tables supported by the SAP Web AS ABAP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reference Types&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reference types describe single fields that can contain references to global classes and interfaces from the ABAP class library.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In an ABAP program, you can use the TYPE addition to refer directly to a data element. The predefined Dictionary data types of the domain are then converted into the corresponding ABAP types. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you define a local data type in a program by referring to a data element as follows:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TYPES dtype TYPE data_element.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Hope this helps, Do reward.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 12 Feb 2008 06:21:48 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/transparent-table/m-p/3448466#M828352</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-02-12T06:21:48Z</dc:date>
    </item>
    <item>
      <title>Re: transparent table</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/transparent-table/m-p/3448467#M828353</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Radharaman,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Field in the table is used for only name purpose. Like MATNR for Material number, WERKS for Plant like that...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But Data Element is the one which will contains semantic attributes of the field like text of that element. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Domain will have techinical attrbutes like type and length.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Dataelement will have the domain. And one more thing is that, In data element without Domain you can define technical attributes for the fields.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward If Helpful.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;--&lt;/P&gt;&lt;P&gt;Sasidhar Reddy Matli.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 12 Feb 2008 06:24:10 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/transparent-table/m-p/3448467#M828353</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-02-12T06:24:10Z</dc:date>
    </item>
    <item>
      <title>Re: transparent table</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/transparent-table/m-p/3448468#M828354</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;  Difference between field and data element is :&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For one field say EMP_NAME  u can use data element NAME1 and&lt;/P&gt;&lt;P&gt; if u want a field CUST_NAME the same data element can be used for the &lt;/P&gt;&lt;P&gt;multiple fields depending on the requirement.....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The relation is here NAME1 is data element already defined in DDIC for&lt;/P&gt;&lt;P&gt;which u have domain NAME with the attributes like&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Type : Character&lt;/P&gt;&lt;P&gt;size : 31&lt;/P&gt;&lt;P&gt;Etc..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;this way ve declare for all fields it can be buttom up or TOp down...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;like field-&amp;gt; dataelement-&amp;gt;domain -&lt;/P&gt;&lt;HR originaltext="---" /&gt;&lt;P&gt; top down or&lt;/P&gt;&lt;P&gt;bottom up---domain-&amp;gt;data element-&amp;gt; field like this.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 12 Feb 2008 06:27:13 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/transparent-table/m-p/3448468#M828354</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-02-12T06:27:13Z</dc:date>
    </item>
    <item>
      <title>Re: transparent table</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/transparent-table/m-p/3448469#M828355</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Fields is just a name of table column to identify each one seperate and this name we can use in our program to update,insert and display.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;we can use the field name in many table but again you have to define the its technical attribute.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Date Element is technical name which dfine the type of the fields like it is character or numeric what is it's lenght.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We can use data element is many table it display the same attribute.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Data Domain : One more advanced concept given by SAP. &lt;/P&gt;&lt;P&gt;Domain contain the Value range which is not possible in data element.&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;one domain can be used in many data element but vise versa is not possible. you can't use domain in the table  directly for defining the table fields. yaa it can be used with data element at many table&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope it help you.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Swati&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 12 Feb 2008 06:28:09 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/transparent-table/m-p/3448469#M828355</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-02-12T06:28:09Z</dc:date>
    </item>
    <item>
      <title>Re: transparent table</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/transparent-table/m-p/3448470#M828356</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi &lt;/P&gt;&lt;P&gt;In data dictionary whenever we create table 's fields &lt;/P&gt;&lt;P&gt;it is defined in two ways&lt;/P&gt;&lt;P&gt;1. use &lt;STRONG&gt;built in type&lt;/STRONG&gt; ( or predefined data type) in this we can directly assign field &lt;STRONG&gt;name&lt;/STRONG&gt; and it s type char of 20 length.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. second way and preferable way is use data element .&lt;/P&gt;&lt;P&gt;it is like centeral location where u define the characteristic of field. for eg &lt;STRONG&gt;name&lt;/STRONG&gt; field can be used in no of tables and if in future any changes is required in characterstic of &lt;STRONG&gt;name&lt;/STRONG&gt; u can directly make in data element in stead of all table who use this &lt;STRONG&gt;name&lt;/STRONG&gt; field.&lt;/P&gt;&lt;P&gt;So now i hope data element concept is clear, generally we use name of field same as that of data element for better understanding and from clarity point.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rewards point if helpful. plssssssss&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 12 Feb 2008 06:45:58 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/transparent-table/m-p/3448470#M828356</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-02-12T06:45:58Z</dc:date>
    </item>
  </channel>
</rss>

