<?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: User Exits -  tcode IW31 in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/user-exits-tcode-iw31/m-p/1620446#M277603</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;Development class for Transport Organizer                                                                                &lt;/P&gt;&lt;P&gt;Related objects in the ABAP Workbench are grouped together in a            &lt;/P&gt;&lt;P&gt;    development class. The assignment of an object to a development class is   &lt;/P&gt;&lt;P&gt;    entered in the object directory (TADIR). The class determines the          &lt;/P&gt;&lt;P&gt;    transport layer that defines the transport attributes of an object.                                                                                &lt;/P&gt;&lt;P&gt;The development classes are described in table TDEVC. They can be          &lt;/P&gt;&lt;P&gt;    maintained in the following transactions:                                                                                &lt;/P&gt;&lt;P&gt;o   Transaction SE80 -&amp;gt; Enter development class -&amp;gt; Double-click the        &lt;/P&gt;&lt;P&gt;        development class                                                                                &lt;/P&gt;&lt;P&gt;o   Transaction SM30 - Table/view name V_TDEVC                                                                                &lt;/P&gt;&lt;P&gt;The development classes are themselves objects of the ABAP Workbench.      &lt;/P&gt;&lt;P&gt;    They belong to their own development classes.                                                                                &lt;/P&gt;&lt;P&gt;Use                                                                                &lt;/P&gt;&lt;P&gt;When an ABAP Workbench object is created, the system prompts you to       &lt;/P&gt;&lt;P&gt;     assign it to a development class. The development class should describe   &lt;/P&gt;&lt;P&gt;     the area that the object belongs to.                                                                                &lt;/P&gt;&lt;P&gt;The representation of the object tree in the ABAP Workbench (Transaction  &lt;/P&gt;&lt;P&gt;     SE80) uses the development class as a navigation aid. If there are more   &lt;/P&gt;&lt;P&gt;     than 100 objects of a certain type (that is, ABAP programs), the object   &lt;/P&gt;&lt;P&gt;     tree can no longer be clearly represented and it becomes increasingly     &lt;/P&gt;&lt;P&gt;     difficult to use the ABAP Workbench. In this case, we recommend creating  &lt;/P&gt;&lt;P&gt;     new development classes with the same transport layer and distributing    &lt;/P&gt;&lt;P&gt;     the objects to the new classes on the basis of the areas they belong to.                                                                                &lt;/P&gt;&lt;P&gt;There are the following naming conventions for development classes which  &lt;/P&gt;&lt;P&gt;     determine the class' functions:                                                                                &lt;/P&gt;&lt;P&gt;o   Development class begins with A-S or U-X:                             &lt;/P&gt;&lt;P&gt;         These classes are for SAP standard objects. Customer objects cannot   &lt;/P&gt;&lt;P&gt;         be created in them. Changes to objects of these classes are recorded  &lt;/P&gt;&lt;P&gt;         by the Transport Organizer (Request management) and can be            &lt;/P&gt;&lt;P&gt; transported (s. field transport layer.                                                                                &lt;/P&gt;&lt;P&gt;Development class begins with Y or Z:                                &lt;/P&gt;&lt;P&gt; Customer objects can be created in such classes. Changes to objects  &lt;/P&gt;&lt;P&gt; in these classes are recorded by the Transport Organizer (Request    &lt;/P&gt;&lt;P&gt; management). The objects can be transported to other SAP Systems     &lt;/P&gt;&lt;P&gt; (see the field transport layer).                                                                                &lt;/P&gt;&lt;P&gt;Development class begins with T (private test class):                &lt;/P&gt;&lt;P&gt; When such a class is created, you can specify whether you want       &lt;/P&gt;&lt;P&gt; changes to be recorded. If so, objects that are edited are recorded  &lt;/P&gt;&lt;P&gt; in local requests by the Transport Organizer. This class does        &lt;/P&gt;&lt;P&gt; not belong to a transport layer. Objects can only transported to     &lt;/P&gt;&lt;P&gt; other SAP Systems if a transport request is created.                                                                                &lt;/P&gt;&lt;P&gt;Development class begins with $ (local class):                       &lt;/P&gt;&lt;P&gt; Changes to objects are not recorded by the Transport Organizer. The  &lt;/P&gt;&lt;P&gt; class does not belong to a transport layer. The objects cannot be    &lt;/P&gt;&lt;P&gt; transported.                                                         &lt;/P&gt;&lt;P&gt; Development class begins with a namespace prefix:                    &lt;/P&gt;&lt;P&gt; If you have reserved a namespace, then you can create development    &lt;/P&gt;&lt;P&gt; classes (and other objects) whose names begin with the namespace     &lt;/P&gt;&lt;P&gt; prefix.                                                              &lt;/P&gt;&lt;P&gt; (Example of a namespace prefix /COMPANY/, example of a corresponding &lt;/P&gt;&lt;P&gt; development class /COMPANY/DEVCLASS)                                 &lt;/P&gt;&lt;P&gt; Changes to these development classes are recorded by the Transport   &lt;/P&gt;&lt;P&gt; Organizer, and can be transported.                                                                                &lt;/P&gt;&lt;P&gt;THanks,&lt;/P&gt;&lt;P&gt;Naren&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 20 Sep 2006 03:49:13 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2006-09-20T03:49:13Z</dc:date>
    <item>
      <title>User Exits -  tcode IW31</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/user-exits-tcode-iw31/m-p/1620443#M277600</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am new to user exits. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am looking for the user exit inside SAPLCOIH to change the basic start date (GSTRP) to the current date of order creation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I tried to use global search (Keyword: CALL CUSTOMER-FUNCTION) in SAPLCOIH to locate all the user exits. There are a numbers of them. Which is the correct one?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Btw, am i doing it the wrong way or looking at the wrong program?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any advices or hints? Thanks in advance. &lt;SPAN __jive_emoticon_name="happy"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 Sep 2006 03:27:50 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/user-exits-tcode-iw31/m-p/1620443#M277600</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-09-20T03:27:50Z</dc:date>
    </item>
    <item>
      <title>Re: User Exits -  tcode IW31</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/user-exits-tcode-iw31/m-p/1620444#M277601</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;  use the userexit  EXIT_SAPLCOIH_012..Enhancement - IWO10012..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  Other option to get the userexits are get the developement class of the program and then GOTO SMOD and in the information system give the development class and display the enhancements..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;THanks,&lt;/P&gt;&lt;P&gt;Naren&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 Sep 2006 03:30:56 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/user-exits-tcode-iw31/m-p/1620444#M277601</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-09-20T03:30:56Z</dc:date>
    </item>
    <item>
      <title>Re: User Exits -  tcode IW31</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/user-exits-tcode-iw31/m-p/1620445#M277602</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Naren,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I tried the user exit EXIT_SAPLCOIH_012 before. The user exit is wrapped by CUSTOMER_PRIOK_0120. Inside CUSTOMER_PRIOK_0120, there is a check for priority (PRIOK).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If i didnt input priority, the user exit will not be triggered. If i input priority, the basic start date value seems to be overwritten.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What's a developement class ? I am very new to ABAP.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 Sep 2006 03:45:55 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/user-exits-tcode-iw31/m-p/1620445#M277602</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-09-20T03:45:55Z</dc:date>
    </item>
    <item>
      <title>Re: User Exits -  tcode IW31</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/user-exits-tcode-iw31/m-p/1620446#M277603</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;Development class for Transport Organizer                                                                                &lt;/P&gt;&lt;P&gt;Related objects in the ABAP Workbench are grouped together in a            &lt;/P&gt;&lt;P&gt;    development class. The assignment of an object to a development class is   &lt;/P&gt;&lt;P&gt;    entered in the object directory (TADIR). The class determines the          &lt;/P&gt;&lt;P&gt;    transport layer that defines the transport attributes of an object.                                                                                &lt;/P&gt;&lt;P&gt;The development classes are described in table TDEVC. They can be          &lt;/P&gt;&lt;P&gt;    maintained in the following transactions:                                                                                &lt;/P&gt;&lt;P&gt;o   Transaction SE80 -&amp;gt; Enter development class -&amp;gt; Double-click the        &lt;/P&gt;&lt;P&gt;        development class                                                                                &lt;/P&gt;&lt;P&gt;o   Transaction SM30 - Table/view name V_TDEVC                                                                                &lt;/P&gt;&lt;P&gt;The development classes are themselves objects of the ABAP Workbench.      &lt;/P&gt;&lt;P&gt;    They belong to their own development classes.                                                                                &lt;/P&gt;&lt;P&gt;Use                                                                                &lt;/P&gt;&lt;P&gt;When an ABAP Workbench object is created, the system prompts you to       &lt;/P&gt;&lt;P&gt;     assign it to a development class. The development class should describe   &lt;/P&gt;&lt;P&gt;     the area that the object belongs to.                                                                                &lt;/P&gt;&lt;P&gt;The representation of the object tree in the ABAP Workbench (Transaction  &lt;/P&gt;&lt;P&gt;     SE80) uses the development class as a navigation aid. If there are more   &lt;/P&gt;&lt;P&gt;     than 100 objects of a certain type (that is, ABAP programs), the object   &lt;/P&gt;&lt;P&gt;     tree can no longer be clearly represented and it becomes increasingly     &lt;/P&gt;&lt;P&gt;     difficult to use the ABAP Workbench. In this case, we recommend creating  &lt;/P&gt;&lt;P&gt;     new development classes with the same transport layer and distributing    &lt;/P&gt;&lt;P&gt;     the objects to the new classes on the basis of the areas they belong to.                                                                                &lt;/P&gt;&lt;P&gt;There are the following naming conventions for development classes which  &lt;/P&gt;&lt;P&gt;     determine the class' functions:                                                                                &lt;/P&gt;&lt;P&gt;o   Development class begins with A-S or U-X:                             &lt;/P&gt;&lt;P&gt;         These classes are for SAP standard objects. Customer objects cannot   &lt;/P&gt;&lt;P&gt;         be created in them. Changes to objects of these classes are recorded  &lt;/P&gt;&lt;P&gt;         by the Transport Organizer (Request management) and can be            &lt;/P&gt;&lt;P&gt; transported (s. field transport layer.                                                                                &lt;/P&gt;&lt;P&gt;Development class begins with Y or Z:                                &lt;/P&gt;&lt;P&gt; Customer objects can be created in such classes. Changes to objects  &lt;/P&gt;&lt;P&gt; in these classes are recorded by the Transport Organizer (Request    &lt;/P&gt;&lt;P&gt; management). The objects can be transported to other SAP Systems     &lt;/P&gt;&lt;P&gt; (see the field transport layer).                                                                                &lt;/P&gt;&lt;P&gt;Development class begins with T (private test class):                &lt;/P&gt;&lt;P&gt; When such a class is created, you can specify whether you want       &lt;/P&gt;&lt;P&gt; changes to be recorded. If so, objects that are edited are recorded  &lt;/P&gt;&lt;P&gt; in local requests by the Transport Organizer. This class does        &lt;/P&gt;&lt;P&gt; not belong to a transport layer. Objects can only transported to     &lt;/P&gt;&lt;P&gt; other SAP Systems if a transport request is created.                                                                                &lt;/P&gt;&lt;P&gt;Development class begins with $ (local class):                       &lt;/P&gt;&lt;P&gt; Changes to objects are not recorded by the Transport Organizer. The  &lt;/P&gt;&lt;P&gt; class does not belong to a transport layer. The objects cannot be    &lt;/P&gt;&lt;P&gt; transported.                                                         &lt;/P&gt;&lt;P&gt; Development class begins with a namespace prefix:                    &lt;/P&gt;&lt;P&gt; If you have reserved a namespace, then you can create development    &lt;/P&gt;&lt;P&gt; classes (and other objects) whose names begin with the namespace     &lt;/P&gt;&lt;P&gt; prefix.                                                              &lt;/P&gt;&lt;P&gt; (Example of a namespace prefix /COMPANY/, example of a corresponding &lt;/P&gt;&lt;P&gt; development class /COMPANY/DEVCLASS)                                 &lt;/P&gt;&lt;P&gt; Changes to these development classes are recorded by the Transport   &lt;/P&gt;&lt;P&gt; Organizer, and can be transported.                                                                                &lt;/P&gt;&lt;P&gt;THanks,&lt;/P&gt;&lt;P&gt;Naren&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 Sep 2006 03:49:13 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/user-exits-tcode-iw31/m-p/1620446#M277603</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-09-20T03:49:13Z</dc:date>
    </item>
    <item>
      <title>Re: User Exits -  tcode IW31</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/user-exits-tcode-iw31/m-p/1620447#M277604</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Any other user exits i can use or is it i missed out something in EXIT_SAPLCOIH_012, thats why not working?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Other than using user exits, any workaround?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 Sep 2006 03:59:53 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/user-exits-tcode-iw31/m-p/1620447#M277604</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-09-20T03:59:53Z</dc:date>
    </item>
  </channel>
</rss>

