DIFFERENCE BETWEEN SE09 AND SE10

[Former Member]

HI

WHAT ARE THE DEFFERENCE BETWEEN

T.CODE(SE09) AND SE10

[Former Member]

SE09 is the transaction code for workbench organiser.Workbench organiser is the set of utilities for development change management.All Development changes are tracked via Workbench organiser.

SE10 is for Customosing organiser.Customising organiser is the set of tools for customising change management.All customizing changes are tracked via customising organiser

[matt]

In later versions of SAP, it would at first glance appear that there is no difference at all. They run EXACTLY the same program and screen. Look at SE10 and SE09 in transaction SE93 if you don't believe me.

However... within the program there is some subtle logic that makes them run ever so slightly differently. But for most day to day purposes - no difference.

matt

[Former Member]

SE09 is the transaction code for workbench organiser.Workbench organiser is the set of utilities for development change management.All Development changes are tracked via Workbench organiser.

SE10 is for Customosing organiser.Customising organiser is the set of tools for customising change management.All customizing changes are tracked via customising organiser.

[Former Member]

Hi,

No difference.

Thanks,

Sriram Ponna.

[Former Member]

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.

regards,

Mutyala Sunilkumar

[Former Member]

Hi

You can go link given below :

http://www.saptechies.com/what-is-difference-between-t-code-se09-se10/

With Regards

Nikunj Shah

[sivasatyaprasad_yerra]

There is no difference between SE09 and SE10. But there is a difference between SE01 and SE09.

Regards,

Siva.

[Former Member]

hi ,

there is no difference between se09 and se10 as far as my knowledge is concerned.

Rgds.,

subash

[Former Member]

There is a small difference between SE09 and SE10 because they are both report type transactions...

*&---------------------------------------------------------------------*
*&      Form  NAVIGATION
*&---------------------------------------------------------------------*
.......
    WHEN 'SE09'.
      CALL TRANSACTION 'SE09'.

.......
    WHEN OTHERS.
      PERFORM umfeld USING pv_command.
  ENDCASE.
ENDFORM.                               " INFO_ACCESS

*&---------------------------------------------------------------------*
*&      Form  UMFELD
*&---------------------------------------------------------------------*
.......

      lv_tcode = pv_command.
      CALL FUNCTION 'AUTHORITY_CHECK_TCODE'
           EXPORTING
                tcode  = lv_tcode
           EXCEPTIONS
                ok     = 0
                not_ok = 2.
      IF sy-subrc <> 0.
        MESSAGE s647(tk) WITH pv_command.
      ELSE.
        CALL TRANSACTION pv_command.
      ENDIF.

FUNCTION authority_check_tcode.
.......
* correction: Regarding the fixed values of domain TCDCOUPOKF
*             tcdcouples-okflag = ' ' will now lead to:
*               a- 'don't check', if tcode =  sy-tcode  OR to
*               b- 'check',       if tcode <> sy-tcode

SE09

Table:          TCDCOUPLES
Displayed Fields:   7 of   7  Fixed Columns:                2  List Width 0250

   TCODE                  CALLED                 MODIFIER     MODDATE    MODTIME  OKFLAG MAINTFLAG

   SE09                   SE01                   SAP          00.00.0000 00:00:00 X      X
   SE09                   SE03                   SAP            .  .       :  :   X      X
   SE09                   SE07                   SAP          00.00.0000 00:00:00 X      X
   SE09                   SE09                   SAP          00.00.0000 00:00:00 X      X
   SE09                   SE11                   SAP          00.00.0000 00:00:00 X      X
   SE09                   SE14                   SAP          00.00.0000 00:00:00 X      X

SE10

Table:          TCDCOUPLES
Displayed Fields:   7 of   7  Fixed Columns:                2  List Width 0250

   TCODE                  CALLED                 MODIFIER     MODDATE    MODTIME  OKFLAG MAINTFLAG

   SE10                   SE01                   SAP          19.01.2000 09:32:30 N
   SE10                   SE09                   SAP          19.01.2000 09:32:38 N
   SE10                   SE10                   SAP            .  .       :  :   X      X
   SE10                   SE13                   SAP          19.01.2000 09:32:45 X
   SE10                   SM12                   SAP          00.00.0000 00:00:00 X      X

[ThomasZloch]

After some CONVT_NO_NUMBER dumps I finally came up with the only correct answer:

1