‎2007 Mar 06 2:58 PM
hI
wht is the diff b/w se09/se10 and wht is the use of sm59?
thnaks
‎2007 Mar 06 3:09 PM
Hi,
SE01 is the main screen of the Change and transport Organizer. From here the administrator can acheive all tasks related to transport requests - such as create, change, view logs, display client/delivery transports, etc. SE09 and SE10 can also be accessed from here. However, not all developers might be granted access to this transaction.
SE09 is the workbench transport requests transaction - here the developers can track changes to all ABAP workbench objects (dictionary, reports, module pools, etc). This is a developer-specific transaction and mostly all developers have access to this transaction.
SE10 is the customizing request display transaction - this displays all the customizing requests in the system. Again, this could be restricted to Business analysts if required, since they would be doing most of the customizing changes in the system.
SM59 is used to display and maintenance of RFC (Remote Function Calls) destinations.
Hope this will help.
Regards,
Ferry Lianto
‎2007 Mar 06 3:00 PM
SE09 is the workbench transport requests transaction - here the developers can track changes to all ABAP workbench objects (dictionary, reports, module pools, etc). This is a developer-specific transaction and mostly all developers have access to this transaction.
SE10 is the customizing request display transaction - this displays all the customizing requests in the system. Again, this could be restricted to Business analysts if required, since they would be doing most of the customizing changes in the system.
SM59 is used to maintain RFC destinations
‎2007 Mar 06 3:09 PM
Hi,
SE01 is the main screen of the Change and transport Organizer. From here the administrator can acheive all tasks related to transport requests - such as create, change, view logs, display client/delivery transports, etc. SE09 and SE10 can also be accessed from here. However, not all developers might be granted access to this transaction.
SE09 is the workbench transport requests transaction - here the developers can track changes to all ABAP workbench objects (dictionary, reports, module pools, etc). This is a developer-specific transaction and mostly all developers have access to this transaction.
SE10 is the customizing request display transaction - this displays all the customizing requests in the system. Again, this could be restricted to Business analysts if required, since they would be doing most of the customizing changes in the system.
SM59 is used to display and maintenance of RFC (Remote Function Calls) destinations.
Hope this will help.
Regards,
Ferry Lianto