Calling executable program with selection screen

[Former Member]

Hello experts,

I am working on product management system hierarchy. The hierarchy is like

•   PRODUCTS
  • SUBPRODUCT
    • VERSION
      • PACKAGE

we can create transport for VERSION directly from CONTEXT MENU. Next step is download transport to client PC. I have used the utility tool to download transport to desktop pc. The utility tool is defined with type 1 program so i have directly used it in hierarchy program using

SUBMIT <prg name> statement. Everything works fine but one. When i click on download transport

  

Then screen appears as below

What i want to do is when one select Download Transport then corresponding transport value should appear in the REQUEST/TASK on selection screen i.e. in this case DE9K908297. This transport entry is automatically saved under VERSION table when created. I just don't understand how to achieve this, If anybody have idea regarding this issue please share it with me. FYI i am attaching code for utility tool with this discussion.

Thanks,

Avadhut

[former_member302911]

Use SUBMIT <prog_name> WITH SELECTION TABLE <TABLE> AND RETURN.

<TABLE> Example:

DATA: ltb_seltab        TYPE STANDARD TABLE OF rsparams,
          lst_seltab        TYPE rsparams,

     lst_seltab-selname  = 'P_REQUEST'.
     lst_seltab-sign     = 'I'.
     lst_seltab-option   = 'EQ'.
     lst_seltab-low      = <Number of request>.
     APPEND lst_seltab TO ltb_seltab.

Regards,

Angelo.

[muneshpatwari]

Hi,

Please refer to the following link:

http://help.sap.com/saphelp_nw04s/helpdata/en/9f/dba51a35c111d1829f0000e829fbfe/content.htm

Regards,

Munesh.

[Former Member]

SUBMIT <program name>   VIA SELECTION-SCREEN WITH <parameter name> = '<value>'.

[Former Member]

Hi experts,

I have tried by using all the above statements but still not getting value in the screen box. I have debugged the code and observed that value is not being assigned to selection screen parameter. There may be Something spooky in the utility tool code. I will check it.

Thanks,

Avadhut

[Private_Member_7726]

Hi,

I'd restrict the setting of default value for p_reqest in INITIALIZATION event as follows (though that could NOT be the reason parameter does not receive value given via SUBMIT in ABAP 702 at least):

Edit in: no, forget it, the p_reqest is initial at the beginning of INITIALIZATION event, and SYSTEM-CALL IMPORT SELECTIONS (in Form HANDLE_SUBTY_WITH_SELTAB of RSDBRUNT), which sets the value to that of SUBMIT statement comes after INITIALIZATION event in our 702 System. The logic does work in our 702 System as it is, in other words...

INITIALIZATION.

  if p_reqest is initial .

    CONCATENATE sy-sysid 'K*' INTO p_reqest.

  endif .

and check the SUBMIT statement in calling programm once again (if the parameter name is correct, for example).

cheers

Janis

[Former Member]

Hi experts,

There was spelling mistake original was P_REQEST and i was using P_REQUEST. Well thanks for your replies.