<?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: version management in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/version-management/m-p/2540405#M577206</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi&lt;/P&gt;&lt;P&gt;good&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Version management in the Integration Repository permits versioning as follows:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;·        The Integration Builder manages multiple versions of a software component in an Integration Repository. In this way, different product versions can communicate with each other. Each design object is created in the context of a software component version that represents a unit of a product that can be shipped.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;·        Objects can also have new object versions when changes are made within a software component version. You also have the option of releasing changes to multiple objects simultaneously.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Versioning in the Integration Repository ensures that objects are shipped consistently, and as part of a product.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, there are no software component versions in the Integration Directory, because the configuration content is not shipped. Nevertheless, you can also release changes to the configuration for the entire runtime environment here. When you release the objects, the Integration Server updates the directory runtime cache.&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw04/helpdata/en/71/0b99063e1f974d9f25951746d04dc3/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw04/helpdata/en/71/0b99063e1f974d9f25951746d04dc3/content.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;&lt;P&gt;mrutyun^&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 20 Jul 2007 15:37:06 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-07-20T15:37:06Z</dc:date>
    <item>
      <title>version management</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/version-management/m-p/2540400#M577201</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;what is version management? what is this purpose,explain.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 20 Jul 2007 10:17:05 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/version-management/m-p/2540400#M577201</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-20T10:17:05Z</dc:date>
    </item>
    <item>
      <title>Re: version management</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/version-management/m-p/2540401#M577202</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;   Version Management &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Use&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This function allows you to:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Create multiple versions of a planned independent requirement &lt;/P&gt;&lt;P&gt;Create planned independent requirement quantities or dates for one material &lt;/P&gt;&lt;P&gt;Label a planned independent requirements as a reference &lt;/P&gt;&lt;P&gt;Create versions of planned independent requirements in simulative mode to see how each version affects the production and procurement plan. &lt;/P&gt;&lt;P&gt;Activities&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you want a planned independent requirement version to be included in the operative planning run, activate it. Inactive planned independent requirements versions are excluded from the operative planning run. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; Comparing Versions &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Procedure&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can compare versions entered for a material, and you can copy one or all schedule lines from the version you are using for comparison. You can use this function to copy the planned independent requirements or the schedule lines of other materials.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Select the version. &lt;/P&gt;&lt;P&gt;Select Edit ® Compare reqs with ® Reqmts version. &lt;/P&gt;&lt;P&gt;The dialog box Compare With appears.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Enter the material. &lt;/P&gt;&lt;P&gt;Enter the requirements plan number if the version that you want to use for comparison has a requirements plan number. &lt;/P&gt;&lt;P&gt;Enter the requirements type. &lt;/P&gt;&lt;P&gt;Enter the plant in which the version to be used for comparison is created. &lt;/P&gt;&lt;P&gt;Specify the version to be used for comparison: &lt;/P&gt;&lt;P&gt;&amp;#150; To select one version, select Selected version, and enter the required version.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;#150; To select all active versions, select All active versions.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;#150; To select all active and inactive versions, select All active/inactive versions.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Choose Continue.&lt;/P&gt;&lt;P&gt;Result&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The Compare Versions screen appears. On the left-hand side of the screen, the material or the version you selected in the dialog box is displayed. On the right-hand side of the screen, the material you selected on the entry screen is displayed.&lt;/P&gt;&lt;P&gt;Setting Periodicity for Versions &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Procedure&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To compare versions created using different periodicity, you can change the periodicity of both versions to a common periodicity using Change period. &lt;/P&gt;&lt;P&gt;If the same periodicity has been set for both versions, the system highlights the lines that contain different quantities, and displays the percentage of the deviation in a third column. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To set the periodicity for versions, select Edit ? Change period, and select the periodicity in which you want to compare the versions.&lt;/P&gt;&lt;P&gt;Result&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The system highlights the periods in which the versions in comparison differ from each other. It also displays the percentage deviation between the quantity on the right and the quantity on the left in the Dev % column.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;B&gt;&lt;/B&gt;&lt;/P&gt;&lt;P&gt;Reward points&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 20 Jul 2007 10:49:16 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/version-management/m-p/2540401#M577202</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-20T10:49:16Z</dc:date>
    </item>
    <item>
      <title>Re: version management</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/version-management/m-p/2540402#M577203</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Version Management of Repository Objects Locate the document in its SAP Library structure&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Use&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Version management is active for all objects of the ABAP Workbench.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Version management serves different purposes and user groups:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;The developer can keep track of his or her work ("What have I changed?")&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;The developer can restore a previous version by reactivating it.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;The system administrator can monitor work ("Which objects were changed and how in a specific time interval?")&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;It provides a basis for any auditor who requires a complete history of changes.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;It enables customers to use the system to adjust data after they have upgraded to a new release.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Activities&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can access version management from the following:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;Object Navigator (SE80)&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;Transport Organizer (SE09)&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;Display and maintenance transactions for Repository objects.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Version Management Locate the document in its SAP Library structure&lt;/P&gt;&lt;P&gt;Use&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Version management in the Integration Repository permits versioning as follows:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;·        The Integration Builder manages multiple versions of a software component in an Integration Repository. In this way, different product versions can communicate with each other. Each design object is created in the context of a software component version that represents a unit of a product that can be shipped.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;·        Objects can also have new object versions when changes are made within a software component version. You also have the option of releasing changes to multiple objects simultaneously.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Versioning in the Integration Repository ensures that objects are shipped consistently, and as part of a product.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, there are no software component versions in the Integration Directory, because the configuration content is not shipped. Nevertheless, you can also release changes to the configuration for the entire runtime environment here. When you release the objects, the Integration Server updates the directory runtime cache.&lt;/P&gt;&lt;P&gt;Integration&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can also export objects of an Integration Repository or an Integration Directory to import them into another repository or directory (for example, during system relocation). In doing so, versioning of the corresponding software component version is taken into account.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;See also: Transporting XI Objects.&lt;/P&gt;&lt;P&gt;Features&lt;/P&gt;&lt;P&gt;Change Lists&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The Integration Builder supports object versioning for both the repository and for the directory using the user-specific change lists. When an object is saved for the first time, a new object version is created, which is added to the change list. When an object in the change list is activated, the object version is closed and is made visible for other users.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;See also Selecting Individual Objects.&lt;/P&gt;&lt;P&gt;Products and Software Component Versions&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A product can have multiple versions. Each product version is a shipment unit visible for customers. The software component versions used in a product version can be called in the System Landscape Directory.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;See also: Structure linkSoftware Catalog.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the context of SAP Exchange Infrastructure, the products and software component versions that are of interest are those that are to exchange messages with each other. When development starts they must be imported from the System Landscape Directory into the Integration Builder.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;See also: Importing Software Component Versions.&lt;/P&gt;&lt;P&gt;Release Transfer&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the transition from one software component version to a new software component version, you can either transfer all, or just some of the design objects from the previous version. This release transfer also enables you to transfer objects to older software component versions.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;See also: Release Transfer.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Note&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Note the information contained under Compatibility of Changes when developing a new software component version.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;srinivas&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;B&gt;&lt;/B&gt;*&lt;STRONG&gt;reward for useful answers&lt;/STRONG&gt;*&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 20 Jul 2007 11:01:42 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/version-management/m-p/2540402#M577203</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-20T11:01:42Z</dc:date>
    </item>
    <item>
      <title>Re: version management</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/version-management/m-p/2540403#M577204</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi Spart cus,&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;&lt;/P&gt;&lt;P&gt;Use of Version management:&amp;lt;/b&amp;gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Version management is active for all objects of the ABAP Workbench. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Version management serves different purposes and user groups:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. The developer can keep track of his or her work ("What have I changed?")&lt;/P&gt;&lt;P&gt;2. The developer can restore a previous version by reactivating it.&lt;/P&gt;&lt;P&gt;3. The system administrator can monitor work ("Which objects were changed and how in a specific time interval?")&lt;/P&gt;&lt;P&gt;4. It provides a basis for any auditor who requires a complete history of changes.&lt;/P&gt;&lt;P&gt;5. It enables customers to use the system to adjust data after they have upgraded to a new release.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Activities&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can access version management from the following:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Object Navigator (SE80)&lt;/P&gt;&lt;P&gt;Transport Organizer (SE09)&lt;/P&gt;&lt;P&gt;Display and maintenance transactions for Repository objects.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;hope this helps you.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;Thasneem&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 20 Jul 2007 11:22:00 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/version-management/m-p/2540403#M577204</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-20T11:22:00Z</dc:date>
    </item>
    <item>
      <title>Re: version management</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/version-management/m-p/2540404#M577205</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;The main use of Version management is to see the current active version of the object and also we can see the previous CTS which the modification has done for the same object and release the CTS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To see the current version of the object go for Utilities menu and then select Version Management.&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;Thanks &amp;amp; Regards,&lt;/P&gt;&lt;P&gt;Vasudeva Rao.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 20 Jul 2007 14:17:19 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/version-management/m-p/2540404#M577205</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-20T14:17:19Z</dc:date>
    </item>
    <item>
      <title>Re: version management</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/version-management/m-p/2540405#M577206</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi&lt;/P&gt;&lt;P&gt;good&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Version management in the Integration Repository permits versioning as follows:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;·        The Integration Builder manages multiple versions of a software component in an Integration Repository. In this way, different product versions can communicate with each other. Each design object is created in the context of a software component version that represents a unit of a product that can be shipped.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;·        Objects can also have new object versions when changes are made within a software component version. You also have the option of releasing changes to multiple objects simultaneously.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Versioning in the Integration Repository ensures that objects are shipped consistently, and as part of a product.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, there are no software component versions in the Integration Directory, because the configuration content is not shipped. Nevertheless, you can also release changes to the configuration for the entire runtime environment here. When you release the objects, the Integration Server updates the directory runtime cache.&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw04/helpdata/en/71/0b99063e1f974d9f25951746d04dc3/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw04/helpdata/en/71/0b99063e1f974d9f25951746d04dc3/content.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;&lt;P&gt;mrutyun^&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 20 Jul 2007 15:37:06 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/version-management/m-p/2540405#M577206</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-20T15:37:06Z</dc:date>
    </item>
    <item>
      <title>Re: version management</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/version-management/m-p/2540406#M577207</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;Pls refer this sap link:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;a href="http://help.sap.com/saphelp_nw04/helpdata/en/71/0b99063e1f974d9f25951746d04dc3/content.htm"&amp;gt;http://help.sap.com/saphelp_nw04/helpdata/en/71/0b99063e1f974d9f25951746d04dc3/content.htm&amp;lt;/a&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Pls reward points.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Ameet&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 21 Jul 2007 08:12:23 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/version-management/m-p/2540406#M577207</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-21T08:12:23Z</dc:date>
    </item>
  </channel>
</rss>

