<?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: help on views in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/help-on-views/m-p/2449628#M548898</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 about an application object is often distributed on several tables. By defining a view, you&lt;/P&gt;&lt;P&gt;can define an application-dependent view that combines this data. The structure of such a view is&lt;/P&gt;&lt;P&gt;defined by specifying the tables and fields used in the view. Fields that are not required can be&lt;/P&gt;&lt;P&gt;hidden, thereby minimizing interfaces. A view can be used in ABAP programs for data selection.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Four different view types are supported. These differ in the way in which the view is implemented&lt;/P&gt;&lt;P&gt;and in the methods permitted for accessing the view data.&lt;/P&gt;&lt;P&gt;1. Database views  are implemented with an equivalent view on the database.&lt;/P&gt;&lt;P&gt;2. Projection views  are used to hide fields of a table (only projection).&lt;/P&gt;&lt;P&gt;3. Help views  can be used as selection method in search helps .&lt;/P&gt;&lt;P&gt;4. Maintenance views permit you to maintain the data distributed on several&lt;/P&gt;&lt;P&gt;tables for one application object at one time.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Example:&lt;/P&gt;&lt;P&gt;Travel agencies often have to check what customer is booked on what flights (see the Flight Model The corresponding data is distributed on several tables:&lt;/P&gt;&lt;P&gt;1. SCUSTOM: Customer data such as the customer number, name, address.&lt;/P&gt;&lt;P&gt;2. SBOOK: Booking data such as the carrier, flight number, passenger (customer number).&lt;/P&gt;&lt;P&gt;3.SPFLI: Flight data such as the city of departure and destination.&lt;/P&gt;&lt;P&gt;You can get an overall view of all existing bookings by creating a view on tables SCUSTOM,&lt;/P&gt;&lt;P&gt;SBOOK and SPFLI.&lt;/P&gt;&lt;P&gt;You can determine all the bookings in table SBOOK for a customer number (ID) for the customer&lt;/P&gt;&lt;P&gt;number in table SCUSTOM. Using the carrier ID (CARRID) and the flight number (CONNID), the&lt;/P&gt;&lt;P&gt;flight information can be read from table SPFLI for a booking that is found.&lt;/P&gt;&lt;P&gt;This results in the following join conditions for the view:&lt;/P&gt;&lt;P&gt;SBOOK-MANDT = SCUSTOM-MANDT&lt;/P&gt;&lt;P&gt;SBOOK-CUSTOMID = SCUSTOM-ID&lt;/P&gt;&lt;P&gt;SPFLI-MANDT = SBOOK-MANDT&lt;/P&gt;&lt;P&gt;SPFLI-CARRID = SBOOK-CARRID&lt;/P&gt;&lt;P&gt;SPFLI-CONNID = SBOOK-CONNID&lt;/P&gt;&lt;P&gt;MANDT CARRID CONNID FLDATE BOOKID CUSTOMID ... SBOOK&lt;/P&gt;&lt;P&gt;MANDT CARRID CONNID ...CITYFROM ...CITYTO ... SPFLI&lt;/P&gt;&lt;P&gt;001&lt;/P&gt;&lt;P&gt;001&lt;/P&gt;&lt;P&gt;MANDT ID NAME CITY ... SCUSTOM&lt;/P&gt;&lt;P&gt;001 122356 Smith New York ...&lt;/P&gt;&lt;P&gt;122356&lt;/P&gt;&lt;P&gt;122356&lt;/P&gt;&lt;P&gt;...&lt;/P&gt;&lt;P&gt;...&lt;/P&gt;&lt;P&gt;001&lt;/P&gt;&lt;P&gt;001&lt;/P&gt;&lt;P&gt;New York&lt;/P&gt;&lt;P&gt;Berlin Tokyo&lt;/P&gt;&lt;P&gt;AA Berlin&lt;/P&gt;&lt;P&gt;AA&lt;/P&gt;&lt;P&gt;LH&lt;/P&gt;&lt;P&gt;LH&lt;/P&gt;&lt;P&gt;48&lt;/P&gt;&lt;P&gt;324&lt;/P&gt;&lt;P&gt;324&lt;/P&gt;&lt;P&gt;48&lt;/P&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;&lt;P&gt;3689&lt;/P&gt;&lt;P&gt;3690&lt;/P&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;&lt;P&gt;The join conditions can also be derived from the existing foreign key relationships between the tables of the view&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 02 Jul 2007 10:02:03 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-07-02T10:02:03Z</dc:date>
    <item>
      <title>help on views</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/help-on-views/m-p/2449627#M548897</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;could any body help on creating classification view basically please send some code ....&lt;/P&gt;&lt;P&gt;i am new in sap&lt;/P&gt;&lt;P&gt;if possible help me on the below issue &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i have done bdc recording for mm01 and mm02 for creating or updating material number into sap system .. there is a column called division in legacy system for that column division three values are there. they are 009,004,001.. they might have created classification view for division 009 materials.&lt;/P&gt;&lt;P&gt;how to find if there is any classification view created for division 004 materials .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;now i was asked to create classification view for 001 and 004 division materials ...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 30 Jun 2007 19:14:54 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/help-on-views/m-p/2449627#M548897</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-06-30T19:14:54Z</dc:date>
    </item>
    <item>
      <title>Re: help on views</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/help-on-views/m-p/2449628#M548898</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 about an application object is often distributed on several tables. By defining a view, you&lt;/P&gt;&lt;P&gt;can define an application-dependent view that combines this data. The structure of such a view is&lt;/P&gt;&lt;P&gt;defined by specifying the tables and fields used in the view. Fields that are not required can be&lt;/P&gt;&lt;P&gt;hidden, thereby minimizing interfaces. A view can be used in ABAP programs for data selection.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Four different view types are supported. These differ in the way in which the view is implemented&lt;/P&gt;&lt;P&gt;and in the methods permitted for accessing the view data.&lt;/P&gt;&lt;P&gt;1. Database views  are implemented with an equivalent view on the database.&lt;/P&gt;&lt;P&gt;2. Projection views  are used to hide fields of a table (only projection).&lt;/P&gt;&lt;P&gt;3. Help views  can be used as selection method in search helps .&lt;/P&gt;&lt;P&gt;4. Maintenance views permit you to maintain the data distributed on several&lt;/P&gt;&lt;P&gt;tables for one application object at one time.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Example:&lt;/P&gt;&lt;P&gt;Travel agencies often have to check what customer is booked on what flights (see the Flight Model The corresponding data is distributed on several tables:&lt;/P&gt;&lt;P&gt;1. SCUSTOM: Customer data such as the customer number, name, address.&lt;/P&gt;&lt;P&gt;2. SBOOK: Booking data such as the carrier, flight number, passenger (customer number).&lt;/P&gt;&lt;P&gt;3.SPFLI: Flight data such as the city of departure and destination.&lt;/P&gt;&lt;P&gt;You can get an overall view of all existing bookings by creating a view on tables SCUSTOM,&lt;/P&gt;&lt;P&gt;SBOOK and SPFLI.&lt;/P&gt;&lt;P&gt;You can determine all the bookings in table SBOOK for a customer number (ID) for the customer&lt;/P&gt;&lt;P&gt;number in table SCUSTOM. Using the carrier ID (CARRID) and the flight number (CONNID), the&lt;/P&gt;&lt;P&gt;flight information can be read from table SPFLI for a booking that is found.&lt;/P&gt;&lt;P&gt;This results in the following join conditions for the view:&lt;/P&gt;&lt;P&gt;SBOOK-MANDT = SCUSTOM-MANDT&lt;/P&gt;&lt;P&gt;SBOOK-CUSTOMID = SCUSTOM-ID&lt;/P&gt;&lt;P&gt;SPFLI-MANDT = SBOOK-MANDT&lt;/P&gt;&lt;P&gt;SPFLI-CARRID = SBOOK-CARRID&lt;/P&gt;&lt;P&gt;SPFLI-CONNID = SBOOK-CONNID&lt;/P&gt;&lt;P&gt;MANDT CARRID CONNID FLDATE BOOKID CUSTOMID ... SBOOK&lt;/P&gt;&lt;P&gt;MANDT CARRID CONNID ...CITYFROM ...CITYTO ... SPFLI&lt;/P&gt;&lt;P&gt;001&lt;/P&gt;&lt;P&gt;001&lt;/P&gt;&lt;P&gt;MANDT ID NAME CITY ... SCUSTOM&lt;/P&gt;&lt;P&gt;001 122356 Smith New York ...&lt;/P&gt;&lt;P&gt;122356&lt;/P&gt;&lt;P&gt;122356&lt;/P&gt;&lt;P&gt;...&lt;/P&gt;&lt;P&gt;...&lt;/P&gt;&lt;P&gt;001&lt;/P&gt;&lt;P&gt;001&lt;/P&gt;&lt;P&gt;New York&lt;/P&gt;&lt;P&gt;Berlin Tokyo&lt;/P&gt;&lt;P&gt;AA Berlin&lt;/P&gt;&lt;P&gt;AA&lt;/P&gt;&lt;P&gt;LH&lt;/P&gt;&lt;P&gt;LH&lt;/P&gt;&lt;P&gt;48&lt;/P&gt;&lt;P&gt;324&lt;/P&gt;&lt;P&gt;324&lt;/P&gt;&lt;P&gt;48&lt;/P&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;&lt;P&gt;3689&lt;/P&gt;&lt;P&gt;3690&lt;/P&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;&lt;P&gt;The join conditions can also be derived from the existing foreign key relationships between the tables of the view&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 02 Jul 2007 10:02:03 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/help-on-views/m-p/2449628#M548898</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-02T10:02:03Z</dc:date>
    </item>
  </channel>
</rss>

