<?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: Append Structure Vs Include Structure + Help View in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/append-structure-vs-include-structure-help-view/m-p/3826687#M920220</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;1. Append Structures &lt;/P&gt;&lt;P&gt;Append structures are used for enhancements that are not included in the standard. This includes special developments, country versions and adding customer fields to any tables or structures.&lt;/P&gt;&lt;P&gt;An append structure is a structure that is assigned to exactly one table or structure. There can be more than one append structure for a table or structure.&lt;/P&gt;&lt;P&gt;The following enhancements can be made to a table or structure TAB with an append structure:&lt;/P&gt;&lt;P&gt;·        Insert new fields in TAB,&lt;/P&gt;&lt;P&gt;·        Define foreign keys for fields of TAB that already exist,&lt;/P&gt;&lt;P&gt;·        Attach search helps to fields of TAB that already exist,&lt;/P&gt;&lt;P&gt;These enhancements are part of the append structure, i.e. they must always be changed and transported with the append structure.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Customizing Includes &lt;/P&gt;&lt;P&gt;A Customizing include is a structure that satisfies a special naming convention. The name of a Customizing include begins with u2018CI_u2019 and the include is in the customer namespace.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If enhancements are already planned in the standard using customer-specific fields, such Customizing includes are included. in the corresponding standard table or standard structure. The Customizing include (that is the definition of the structure itself) is usually first created in the customer system and filled with fields by special Customizing transactions.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Customers can thus enhance tables and structures of the standard system without themselves having to modify the table and structure definitions. This means that these enhancements will not be lost when upgrading. If a table or structure of the standard system is enhanced with customer fields using a Customizing include, these customer fields are automatically inserted in the new delivered table or structure definition during an upgrade.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you create a Customizing include for a table or structure, only those enhancements are allowed that are consistent with the enhancement category of the enhanced table or structure. For more information, see Structure Enhancements.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Customers can but need not create a Customizing include and fill it with fields. If there is no Customizing include, there is no error message when the table or structure including it is activated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A Customizing include can be contained in several tables or structures, so that they remain consistent when the include is modified.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2.&lt;/P&gt;&lt;P&gt;a.Help Views &lt;/P&gt;&lt;P&gt;You have to create a help view if a view with outer join is needed as selection method of a  search help.&lt;/P&gt;&lt;P&gt;b.Database Views &lt;/P&gt;&lt;P&gt;A database view is defined in the ABAP Dictionary as a logical view on one or more tables. A database view is automatically created in the underlying database when it is activated. Data about an application object is often distributed on several database tables. A database view provides an application-specific view on such distributed data.&lt;/P&gt;&lt;P&gt;c. Maintenance view.&lt;/P&gt;&lt;P&gt;A maintenance view is used for maintaining the data in this table manually. You can create a maintenance view for database tables (or views) and via transaction SM30 you can maintain (create, change, delete) the data.&lt;/P&gt;&lt;P&gt;d. Projection Views &lt;/P&gt;&lt;P&gt;Projection views are used to hide fields of a table. This can minimize interfaces; for example when you access the database, you only read and write the field contents actually needed.&lt;/P&gt;&lt;P&gt;A projection view contains exactly one table. You cannot define selection conditions for projection views.&lt;/P&gt;&lt;P&gt;There is no corresponding object in the database for a projection view. Access to a projection view is mapped by the SAP System onto the corresponding access to its base table. It is also possible to access pooled tables or cluster tables with a projection view&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 17 May 2008 17:57:00 GMT</pubDate>
    <dc:creator>Sm1tje</dc:creator>
    <dc:date>2008-05-17T17:57:00Z</dc:date>
    <item>
      <title>Append Structure Vs Include Structure + Help View</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/append-structure-vs-include-structure-help-view/m-p/3826686#M920219</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;&lt;/P&gt;&lt;P&gt;1/ Please tell me the difference between these two way of modifying table.&lt;/P&gt;&lt;P&gt;Which one is useful when ?&lt;/P&gt;&lt;P&gt;2/ What is Help View and how it is different from Other Views(Database,Projection,Maintainance) ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Sonal&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 17 May 2008 16:45:35 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/append-structure-vs-include-structure-help-view/m-p/3826686#M920219</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-05-17T16:45:35Z</dc:date>
    </item>
    <item>
      <title>Re: Append Structure Vs Include Structure + Help View</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/append-structure-vs-include-structure-help-view/m-p/3826687#M920220</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;1. Append Structures &lt;/P&gt;&lt;P&gt;Append structures are used for enhancements that are not included in the standard. This includes special developments, country versions and adding customer fields to any tables or structures.&lt;/P&gt;&lt;P&gt;An append structure is a structure that is assigned to exactly one table or structure. There can be more than one append structure for a table or structure.&lt;/P&gt;&lt;P&gt;The following enhancements can be made to a table or structure TAB with an append structure:&lt;/P&gt;&lt;P&gt;·        Insert new fields in TAB,&lt;/P&gt;&lt;P&gt;·        Define foreign keys for fields of TAB that already exist,&lt;/P&gt;&lt;P&gt;·        Attach search helps to fields of TAB that already exist,&lt;/P&gt;&lt;P&gt;These enhancements are part of the append structure, i.e. they must always be changed and transported with the append structure.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Customizing Includes &lt;/P&gt;&lt;P&gt;A Customizing include is a structure that satisfies a special naming convention. The name of a Customizing include begins with u2018CI_u2019 and the include is in the customer namespace.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If enhancements are already planned in the standard using customer-specific fields, such Customizing includes are included. in the corresponding standard table or standard structure. The Customizing include (that is the definition of the structure itself) is usually first created in the customer system and filled with fields by special Customizing transactions.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Customers can thus enhance tables and structures of the standard system without themselves having to modify the table and structure definitions. This means that these enhancements will not be lost when upgrading. If a table or structure of the standard system is enhanced with customer fields using a Customizing include, these customer fields are automatically inserted in the new delivered table or structure definition during an upgrade.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you create a Customizing include for a table or structure, only those enhancements are allowed that are consistent with the enhancement category of the enhanced table or structure. For more information, see Structure Enhancements.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Customers can but need not create a Customizing include and fill it with fields. If there is no Customizing include, there is no error message when the table or structure including it is activated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A Customizing include can be contained in several tables or structures, so that they remain consistent when the include is modified.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2.&lt;/P&gt;&lt;P&gt;a.Help Views &lt;/P&gt;&lt;P&gt;You have to create a help view if a view with outer join is needed as selection method of a  search help.&lt;/P&gt;&lt;P&gt;b.Database Views &lt;/P&gt;&lt;P&gt;A database view is defined in the ABAP Dictionary as a logical view on one or more tables. A database view is automatically created in the underlying database when it is activated. Data about an application object is often distributed on several database tables. A database view provides an application-specific view on such distributed data.&lt;/P&gt;&lt;P&gt;c. Maintenance view.&lt;/P&gt;&lt;P&gt;A maintenance view is used for maintaining the data in this table manually. You can create a maintenance view for database tables (or views) and via transaction SM30 you can maintain (create, change, delete) the data.&lt;/P&gt;&lt;P&gt;d. Projection Views &lt;/P&gt;&lt;P&gt;Projection views are used to hide fields of a table. This can minimize interfaces; for example when you access the database, you only read and write the field contents actually needed.&lt;/P&gt;&lt;P&gt;A projection view contains exactly one table. You cannot define selection conditions for projection views.&lt;/P&gt;&lt;P&gt;There is no corresponding object in the database for a projection view. Access to a projection view is mapped by the SAP System onto the corresponding access to its base table. It is also possible to access pooled tables or cluster tables with a projection view&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 17 May 2008 17:57:00 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/append-structure-vs-include-structure-help-view/m-p/3826687#M920220</guid>
      <dc:creator>Sm1tje</dc:creator>
      <dc:date>2008-05-17T17:57:00Z</dc:date>
    </item>
    <item>
      <title>Re: Append Structure Vs Include Structure + Help View</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/append-structure-vs-include-structure-help-view/m-p/3826688#M920221</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Sonal&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If a standard table needs to be enhanced I usually use both kinds of includes:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.) Create unique APPEND structure for standard table&lt;/P&gt;&lt;P&gt;2.) Include INCLUDE structure into APPEND structure&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;Standard table&lt;/P&gt;&lt;/LI&gt;&lt;UL&gt;&lt;LI level="2" type="ul"&gt;&lt;P&gt;APPEND structure&lt;/P&gt;&lt;/LI&gt;&lt;UL&gt;&lt;LI level="3" type="ul"&gt;&lt;P&gt;INCLUDE structure 1&lt;/P&gt;&lt;/LI&gt;&lt;LI level="3" type="ul"&gt;&lt;P&gt;INCLUDE structure 2&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/UL&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The INCLUDE structure usually group customer fields of similar semantics (e.g. address fields).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Advantage of this approach:&lt;/P&gt;&lt;P&gt;I need to touch the standard table only once when I add the APPEND structure.&lt;/P&gt;&lt;P&gt;Any further changes will happen on custom objects located in custom packages.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;  Uwe&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 17 May 2008 20:12:45 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/append-structure-vs-include-structure-help-view/m-p/3826688#M920221</guid>
      <dc:creator>uwe_schieferstein</dc:creator>
      <dc:date>2008-05-17T20:12:45Z</dc:date>
    </item>
    <item>
      <title>Re: Append Structure Vs Include Structure + Help View</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/append-structure-vs-include-structure-help-view/m-p/3826689#M920222</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;1.     Table performance can be increased in 2 ways. &lt;/P&gt;&lt;P&gt;            &lt;STRONG&gt;Append structure.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;                    if you wnat to add fields at the end  of a table.It is specific to pne particular table.&lt;/P&gt;&lt;P&gt;           &lt;STRONG&gt;Include structure&lt;/STRONG&gt;                   &lt;/P&gt;&lt;P&gt;                if you want to add fields in between the existing fields as per the requirement, it is reusable.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. &lt;U&gt;views&lt;/U&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;       Help View is to provide F1 help. it generally deals with Outer joins. Views are nothing but a  predefined select query with specific fields . It can not hold dat aphysically.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;reward if helpful&lt;/P&gt;&lt;P&gt;rgds&lt;/P&gt;&lt;P&gt;umakanth&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 19 May 2008 06:21:05 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/append-structure-vs-include-structure-help-view/m-p/3826689#M920222</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-05-19T06:21:05Z</dc:date>
    </item>
    <item>
      <title>Re: Append Structure Vs Include Structure + Help View</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/append-structure-vs-include-structure-help-view/m-p/3826690#M920223</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;1. Append Structures&lt;/P&gt;&lt;P&gt;Append structures can only be assigned to a single table. &lt;/P&gt;&lt;P&gt;Append structures are created in the custome rnamespace ( ZZ or YY)&lt;/P&gt;&lt;P&gt;In case of new versions of the standard table during upgrade, the append structures are automatically appended to the new version of the standard table&lt;/P&gt;&lt;P&gt;Append structures can not be used with cluster and pool tables&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Append structures are created in transaction SE11. Display the standard table fields and press the Append structure button.&lt;/P&gt;&lt;P&gt;When you press the button, SAP sugests a name for the new append structure. After you has accepted the name, &lt;/P&gt;&lt;P&gt;a screen will be shown where you can enter the new fields.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Remember to activate.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. Customizing Includes&lt;/P&gt;&lt;P&gt;Some of the SAP standard tables contains special include statements called Customizing includes. In contrast to Append structures, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Note that customizing includes are created by SAP, but the customer supply the fields for the include.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Customizing includes begin with CI_ and is part of the customer namespace&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;One Customizing include can be inserted into more than one table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can find Customizing includes in SE11 under structures.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Try to take a look at table RKPF which uses the Customizing include CI_COBL (In an IDES system). Next try to add a field to CI_COBL, and activate it. If you go back to table RKPF you will se that your new field has been added.&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 followings are different types of views: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- &lt;STRONG&gt;Database View&lt;/STRONG&gt;   (SE11) &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Database views are implement an inner join, that is, only records of the primary table (selected via the join operation) for which the corresponding records of the secondary tables also exist are fetched. Inconsistencies between primary and secondary table could, therefore, lead to a reduced selection set.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In database views, the join conditions can be formulated using equality relationships between any base fields. In the other types of view, they must be taken from existing foreign keys. That is, tables can only be collected in a maintenance or help view if they are linked to one another via foreign keys. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- *Help View *   ( SE54) &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Help views are used to output additional information when the online help system is called.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When the F4 button is pressed for a screen field, a check is first made on whether a matchcode is defined for this field. If this is not the case, the help view is displayed in which the check table of the field is the primary table. Thus, for each table no more than one help view can be created, that is, a table can only be primary table in at most one help view.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- *Projection View *&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Projection views are used to suppress or mask certain fields in a table (projection), thus minimizing the number of interfaces. This means that only the data that is actually required is exchanged when the database is accessed. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A projection view can draw upon only one table. Selection conditions cannot be specified for projection views. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- *Maintenance View *  ( SE54 ) &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Maintenance views enable a business-oriented approach to looking at data, while at the same time, making it possible to maintain the data involved. Data from several tables can be summarized in a maintenance view and maintained collectively via this view. That is, the data is entered via the view and then distributed to the underlying tables by the system. &lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;HELP VIEW in detail&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;You have to create a help view if a view with outer join is needed as selection method of a  search help.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The selection method of a search help is either a table or a view. If you have to select data from several tables for the search help, you should generally use a database view as selection method. However, a database view always implements an inner join. If you need a view with outer join for the data selection, you have to use a help view as selection method.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;All the tables included in a help view must be linked with foreign keys. Only foreign keys that have certain attributes can be used here . The first table to be inserted in the help view is called the primary table of the help view. The tables added to this primary table with foreign keys are called secondary tables.&lt;/P&gt;&lt;P&gt;A help view implements an outer join, i.e. all the contents of the primary table of the help view are always displayed. You therefore should not formulate a selection condition for fields in one of the secondary tables of the help view. If records of these secondary tables cannot be read as a result of this selection condition, the contents of the corresponding fields of the secondary table are displayed with initial value.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; To create help view pls go through the following link , it may be helpful.&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw70/helpdata/en/cf/21ecd2446011d189700000e8322d00/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw70/helpdata/en/cf/21ecd2446011d189700000e8322d00/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;reward points if helpful,&lt;/P&gt;&lt;P&gt;Thanks &amp;amp; regards,&lt;/P&gt;&lt;P&gt;Madhavi.M&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: Madhavi vallepu on May 19, 2008 9:00 AM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 19 May 2008 06:52:30 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/append-structure-vs-include-structure-help-view/m-p/3826690#M920223</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-05-19T06:52:30Z</dc:date>
    </item>
  </channel>
</rss>

