on 09-12-2007 1:57 PM
hi
i want to know difference b/n se09&se10 tcodes?
diff b/n table &template in smartforms?
hi,
main difference between se09 and se10 is se09 for transport workbench request. and se10 for custemize req. means for functianl ppl.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
<b>Workbench Requests [Ext.](SE10)</b>When you change a Repository object of the ABAP Workbench, a query window appears
in which you need to specify a Workbench request. You can only save the changes if you
have assigned the object to a change request.
Workbench requests and the tasks assigned to them are normally used to record
changes to Repository objects and Customizing for all clients. However, you can also
include client-specific Customizing.
Whether the changes to Repository objects are transported depends on whether a
transport route is defined from the current SAP System for the development class of
these objects. From the system settings, the system automatically determines whether
the change requests are transportable and to which target system they should be
transported.
<b>Customizing requests [Ext.] (SE09)</b>Customizing requests record client-specific Customizing settings made in a single client
(the source client of the request).
Automatic recording of configuration activities in the Customizing work for a client can
be activated or deactivated for each client with Client Control [Ext.]. If automaticrecording is active, a query window appears when you change Customizing settings,
asking you to specify a Customizing request.
Whether Customizing requests are transported or not, does not depend on the objects
entered, as is the case with Workbench change requests. The Customizing requests in
an SAP System (or in a client if you use Extended Transport Control) are either all
transportable or all local, depending on the system setting. The system uses the
standard transport layer [Ext.] to determine automatically whether the change requests
are transportable and to which target system they should be transported. However, you
can change this manually.
Template is static. You have to tell beforehand how many lines have to be printed while table is dynamic, it determines the number of lines in runtime.
Mallick
Hi,
1) 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.
2) A simple solution is : table is a dynamic and template is a static
Regards
Sudheer
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Templates are stand alone and can be adjusted for height
They do not have loop at functionality though they can be used in a loop
Tables are used to print internal tables
They have a header and footer which will print only once.
Tables will also automatically wrap text in cells when they exceed cell length
Tables cannot be page protected
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi!
I've checked both transactions in SE93, and there is no difference at all.
They are calling the same program/dynpro with the same authority object.
Regards
Tamá
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
83 | |
10 | |
10 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.