IDOC T-Codes

Here is the list of important ALE IDOC transaction codes and its purposes for a quick reference.

SALE – This transaction code is used for access IMG ALE Configuration root
WE05 – IDoc overview
WE07 – IDoc statistics
WE20 – This transaction code is used for manually maintain partner profiles
WE21 – This transaction code is used for Ports in Idoc processing
WE47 – This transaction code is used for edit IDOC status values. (Real path: SALE -> Set-Up System Monitoring -> IDoc Status Display -> Edit IDoc Status Values)
WE60 – This transaction code is used for create IDoc documentation (IDOC header file)
SM59 – This transaction code is used for Create RFC Destinations
SM58 – Schedule RFC Failures
BD21 – Create IDocs from change pointers
BD50 – This transaction code is used for Activate Change Pointer for Message Type
BD52 – This transaction code is used for Activate change pointer per change.doc object
BD53 – This transaction code is used for Reduction of Message Types
BD55 – This transaction code is used for Defining settings for IDoc conversion
BD56 – This transaction code is used for Maintain IDOC Segment Filters
BD59 – This transaction code is used for Allocation object type -> IDOC type
BD61 – This transaction code is used for Activate Change Pointers – Globally
BD62 – This transaction code is used for Define rules
BD64 – This transaction code is used for Maintain customer distribution model
BD71 – This transaction code is used for Distribute customer distribution model
BD79 – This transaction code is used for Maintain rules
BD82 – This transaction code is used for Generate Partner Profiles
BD87 – This transaction code is used for Status Monitor for ALE Messages (Real access path is    Tools -> IDoc Interface/ALE -> Administration ->Monitoring -> IDoc Display ->Status Monitor )
BD88 – Outbound IDoc reprocessing
BDM2 – IDoc Trace
BDM5 – This transaction code is used for Consistency check
BDM7 – IDoc Audit Analysis
WEDI – This transaction code is used for ALE IDoc Administration
SARA – This transaction code is used for IDoc archive administration
BALE – ALE Distribution Administration

Call a Transaction in New Session Window

Call a transaction in New Session from ALV Hotspot.

We can use FM  ABAP4_CALL_TRANSACTION for this. But from SCN, I found an excellent way to do so.

Create a Remote enable function module:

ZFM_CALL_TCODE_IN_NEW_WINDOW :
-----------------------------------------------------
function zfm_call_tcode_in_new_window.
*"----------------------------------------------------------------------
*"*"Local Interface:
*"  IMPORTING
*"     VALUE(TCODE) TYPE  SY-TCODE
*"     VALUE(VBELN) TYPE  VBELN
*"     VALUE(PARAID) TYPE  MEMORYID
*"----------------------------------------------------------------------

set parameter id paraid field vbeln.
  call transaction tcode and skip first screen.

endfunction.

---------------------------------------------------------------
Call the FM from the program:

You have to use the following code segment  in program to call that Function Module ,
-------------------------------------------------
      lv_tcode = 'VA43'.              "Tcode to Call
      lv_vbeln = gs_out-vbeln.
      lv_paraid = 'KTN'.
      call function 'ZFM_CALL_TCODE_IN_NEW_WINDOW' starting new task 'TEST'
        destination 'NONE'
        exporting
          tcode         = lv_tcode
          vbeln         = lv_vbeln
          paraid        = lv_paraid
                .
------------------------------------------------

*Ref: https://wiki.scn.sap.com/wiki/display/Snippets/How+to+Call+a+Transaction+in+New+Session+Window

ABAP Performance and Tuning

What tools can be used to help with performance tuning?

ST05 is the performance trace. It contain the SQL Trace plus RFC, enqueue and buffer trace. Mainly the SQL trace is is used to measure the performance of the select statements of the program.
SE30 is the Runtime Analysis transaction and can be used to measure the application performance. 
SAT transaction is the replacement of the pretty outdated SE30. Provides same functionality as SE30 plus some additional features.
ST12 transaction (part of ST-A/PI software component) is a combination of ST05 and SAT. Very powerful performance analysis tool used primarily by SAP Support.
One of the best tools for static performance analyzing is Code Inspector (SCI). There are many options for finding common mistakes and possible performance bottlenecks.