<?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: data dictionary in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/data-dictionary/m-p/2450398#M549090</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&amp;lt;b&amp;gt;Database table&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;Tables can be defined independently of the database in the ABAP Dictionary. The fields of the table are defined together with their (database-independent) data types and lengths.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A table definition in the ABAP Dictionary has the following components:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Table fields: The field names and the data types of the fields contained in the table are defined here.&lt;/P&gt;&lt;P&gt;Foreign keys: The foreign keys define the relationships between this table and other tables.&lt;/P&gt;&lt;P&gt;Technical settings: The technical settings define how the table is created on the database.&lt;/P&gt;&lt;P&gt;Indexes: Indexes can be defined for the table to speed up data selection from the table.&lt;/P&gt;&lt;P&gt;There are three categories of database tables in the ABAP Dictionary.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A physical table definition is created in the database for the table definition stored in the ABAP Dictionary for transparent tables when the table is activated. The table definition is translated from the ABAP Dictionary to a definition of the particular database.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;On the other hand, pooled tables and cluster tables are not created in the database. The data of these tables is stored in the corresponding table pool or table cluster. It is not necessary to create indexes and technical settings for pooled and cluster tables&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Structure&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;A structure (structured type) consists of components (fields) whose types are defined.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A component can have an elementary type, a structured type, a table type or a reference type.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Structures are used especially to define the data at the interface of module pools and screens and to define the types of function module parameters.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Structures that are used more than once can be changed centrally because they were defined centrall. The active ABAP Dictionary makes this change at all relevant locations. ABAP programs or screen templates that use a structure are automatically adjusted when the structure changes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;View&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;A view is a logical view on one or more tables, that is, a view is not actually physically stored, instead being derived from one or more other tables.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the simplest case, this derivation process can involve simply suppressing the display of one or more fields from a table (projection) or transferring only certain records from a table to the view (selection). More complicated views can be assembled from several tables, with individual tables being linked using the relational join operation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Use&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;Logical views for the application permitting direct access to the data can be generated with the definition of view. The structure of such a view is defined by specifying the tables and fields involved in the view.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;MATCHCODE OBJECT&amp;lt;/b&amp;gt; &lt;/P&gt;&lt;P&gt;PARAMETERS p ... MATCHCODE OBJECT search_help.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The search help search_help must be defined in the ABAP Dictionary. The system now automatically displays the input help button for the field on the screen and activates the F4 key for it. When the user requests input help, the hit list of the search help appears, and when he or she selects an entry, the corresponding export parameter is placed in the input field.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The predecessors of search helps in the ABAP Dictionary were called matchcode objects, hence the name of the addition, MATCHCODE OBJECT in the PARAMETERS statement. Existing matchcode objects are still supported.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;REPORT demo_sel_screen_parameters_mco.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PARAMETERS p_carrid TYPE s_carr_id &lt;/P&gt;&lt;P&gt;           MATCHCODE OBJECT demo_f4_de.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The selection screen looks as follows:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Search help&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;A search help is an object of the ABAP Dictionary with which input helps (F4 helps) can be defined.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There are the following types of search helps:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Elementary search helps implement a search path for determining the possible entries.&lt;/P&gt;&lt;P&gt;Collective search helps contain several elementary search helps. A collective search help therefore provides several alternative search paths for possible entries.&lt;/P&gt;&lt;P&gt;Append search helps can be used to enhance collective search helps delivered by SAP with customer-specific search paths without requiring a modification.&lt;/P&gt;&lt;P&gt;The three components of the input help process described by a search help are the outer interface, the online behavior and the method of data collection.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The outer interface is defined by specifying the interface parameters. They define the context information to be used in the input help process and the attributes to be sent to the screen by the input help.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The search help attachment defines the field contents for parametrizing an import parameter and the fields of the input template in which the contents of the export parameters should be returned.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The dialog behavior and data collection are defined differently for elementary search helps and collective search helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The behavior of a search help can be made more flexible than usual with search help exits.&lt;/P&gt;&lt;P&gt;&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;Girish&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 29 Jun 2007 03:22:26 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-06-29T03:22:26Z</dc:date>
    <item>
      <title>data dictionary</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/data-dictionary/m-p/2450395#M549087</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hello &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;tell me about creation / purpose / apllication of &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;structure,views,matchcodes,search helps&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;with regards&lt;/P&gt;&lt;P&gt;Basavaraj....&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 Jun 2007 13:33:11 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/data-dictionary/m-p/2450395#M549087</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-06-28T13:33:11Z</dc:date>
    </item>
    <item>
      <title>Re: data dictionary</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/data-dictionary/m-p/2450396#M549088</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi&lt;/P&gt;&lt;P&gt;see this&lt;/P&gt;&lt;P&gt;it's at help.sap.com:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BC - ABAP Dictionary&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward points for useful Answers&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Anji&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 Jun 2007 13:44:37 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/data-dictionary/m-p/2450396#M549088</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-06-28T13:44:37Z</dc:date>
    </item>
    <item>
      <title>Re: data dictionary</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/data-dictionary/m-p/2450397#M549089</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;   You can check - &lt;A href="http://help.sap.com/saphelp_46c/helpdata/en/4f/991f82446d11d189700000e8322d00/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_46c/helpdata/en/4f/991f82446d11d189700000e8322d00/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards, &lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;Dj &lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;reward all helpful answers,&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 Jun 2007 20:32:49 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/data-dictionary/m-p/2450397#M549089</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-06-28T20:32:49Z</dc:date>
    </item>
    <item>
      <title>Re: data dictionary</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/data-dictionary/m-p/2450398#M549090</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&amp;lt;b&amp;gt;Database table&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;Tables can be defined independently of the database in the ABAP Dictionary. The fields of the table are defined together with their (database-independent) data types and lengths.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A table definition in the ABAP Dictionary has the following components:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Table fields: The field names and the data types of the fields contained in the table are defined here.&lt;/P&gt;&lt;P&gt;Foreign keys: The foreign keys define the relationships between this table and other tables.&lt;/P&gt;&lt;P&gt;Technical settings: The technical settings define how the table is created on the database.&lt;/P&gt;&lt;P&gt;Indexes: Indexes can be defined for the table to speed up data selection from the table.&lt;/P&gt;&lt;P&gt;There are three categories of database tables in the ABAP Dictionary.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A physical table definition is created in the database for the table definition stored in the ABAP Dictionary for transparent tables when the table is activated. The table definition is translated from the ABAP Dictionary to a definition of the particular database.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;On the other hand, pooled tables and cluster tables are not created in the database. The data of these tables is stored in the corresponding table pool or table cluster. It is not necessary to create indexes and technical settings for pooled and cluster tables&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Structure&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;A structure (structured type) consists of components (fields) whose types are defined.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A component can have an elementary type, a structured type, a table type or a reference type.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Structures are used especially to define the data at the interface of module pools and screens and to define the types of function module parameters.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Structures that are used more than once can be changed centrally because they were defined centrall. The active ABAP Dictionary makes this change at all relevant locations. ABAP programs or screen templates that use a structure are automatically adjusted when the structure changes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;View&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;A view is a logical view on one or more tables, that is, a view is not actually physically stored, instead being derived from one or more other tables.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the simplest case, this derivation process can involve simply suppressing the display of one or more fields from a table (projection) or transferring only certain records from a table to the view (selection). More complicated views can be assembled from several tables, with individual tables being linked using the relational join operation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Use&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;Logical views for the application permitting direct access to the data can be generated with the definition of view. The structure of such a view is defined by specifying the tables and fields involved in the view.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;MATCHCODE OBJECT&amp;lt;/b&amp;gt; &lt;/P&gt;&lt;P&gt;PARAMETERS p ... MATCHCODE OBJECT search_help.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The search help search_help must be defined in the ABAP Dictionary. The system now automatically displays the input help button for the field on the screen and activates the F4 key for it. When the user requests input help, the hit list of the search help appears, and when he or she selects an entry, the corresponding export parameter is placed in the input field.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The predecessors of search helps in the ABAP Dictionary were called matchcode objects, hence the name of the addition, MATCHCODE OBJECT in the PARAMETERS statement. Existing matchcode objects are still supported.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;REPORT demo_sel_screen_parameters_mco.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PARAMETERS p_carrid TYPE s_carr_id &lt;/P&gt;&lt;P&gt;           MATCHCODE OBJECT demo_f4_de.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The selection screen looks as follows:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Search help&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;A search help is an object of the ABAP Dictionary with which input helps (F4 helps) can be defined.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There are the following types of search helps:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Elementary search helps implement a search path for determining the possible entries.&lt;/P&gt;&lt;P&gt;Collective search helps contain several elementary search helps. A collective search help therefore provides several alternative search paths for possible entries.&lt;/P&gt;&lt;P&gt;Append search helps can be used to enhance collective search helps delivered by SAP with customer-specific search paths without requiring a modification.&lt;/P&gt;&lt;P&gt;The three components of the input help process described by a search help are the outer interface, the online behavior and the method of data collection.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The outer interface is defined by specifying the interface parameters. They define the context information to be used in the input help process and the attributes to be sent to the screen by the input help.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The search help attachment defines the field contents for parametrizing an import parameter and the fields of the input template in which the contents of the export parameters should be returned.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The dialog behavior and data collection are defined differently for elementary search helps and collective search helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The behavior of a search help can be made more flexible than usual with search help exits.&lt;/P&gt;&lt;P&gt;&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;Girish&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 29 Jun 2007 03:22:26 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/data-dictionary/m-p/2450398#M549090</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-06-29T03:22:26Z</dc:date>
    </item>
    <item>
      <title>Re: data dictionary</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/data-dictionary/m-p/2450399#M549091</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;structure:  it is series of fields named under one name.&lt;/P&gt;&lt;P&gt;rx: begin of struct1,&lt;/P&gt;&lt;P&gt;   var1 type i,&lt;/P&gt;&lt;P&gt;var2 type c,&lt;/P&gt;&lt;P&gt;end of struct.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;views:  it's a snapshot of a table ie to combine to diff tables.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;search help is nothing but f4 help.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 29 Jun 2007 15:14:15 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/data-dictionary/m-p/2450399#M549091</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-06-29T15:14:15Z</dc:date>
    </item>
  </channel>
</rss>

