First of all, don't use WRITE
to create lists - this is stone-age technology. Store your data in an internal table based on a dictionary structure, then use the SALV library to create a list. Take a look at the sample program SALV_DEMO_TABLE_EVENTS
to see how to display a list and react to a double click. Note that you can throw away much of the demo program because it shows quite a lot of different functions.
Then, you don't "forward" anything to a transaction. You can call a transaction using the ABAP statement CALL TRANSACTION
(which should be obvious), and you can even pass some values using a crooked mix of SPA/GPA parameters and the addition ... AND SKIP FIRST SCREEN
. Be aware that this only works for certain kinds of transactions and only if they were programmed to do so. For this, you need to store the equipment number in a global variable using
SET PARAMETER ID 'EQN' FIELD l_my_equipment_number.
and then call the transaction
CALL TRANSACTION 'IE03' AND SKIP FIRST SCREEN.
Be aware that this statement does not perform the default authorization checks - if you need to do so, use the function module AUTHORITY_CHECK_TCODE
as specified by the keyword documentation.