topic Re: Selection screen values as form params... in Application Development and Automation Discussions

Selection screen values as form params...

Former Member — Tue, 26 Oct 2010 12:00:51 GMT

Hi all: I want to pass my selection screen values into my forms as a parameter...maybe as a structure. What is the best way to accomplish? Thanks. Mat.

Re: Selection screen values as form params...

matt — Tue, 26 Oct 2010 12:05:16 GMT

I just use


PARAMETERS: p1 TYPE matnr,
           p2 TYPE i,
           p3 TYPE bukrs.

PERFORM my_sub USING P1 P2.
...
FORM my_sub USING i1 TYPE matnr
                 i2 TYPE i
                 i3 TYPE bukrs.

Is that what you're asking, or something deeper in program design.

Re: Selection screen values as form params...

Former Member — Tue, 02 Nov 2010 15:08:53 GMT

I've created a custom structure which includes a field for each of the fields on my selection screen. I use the function module RS_REFRESH_FROM_SELECTOPTIONS to retrieve the current values of my selection screen fields and assign to my structure. Trouble is the function module shows some selection screen fields as having no value when I set the value via a MEMORY ID. Why is it the function module returns no values for those fields but you can see the actual values on the selection screen...and how do I capture those values? Thanks. Mat.

Re: Selection screen values as form params...

Former Member — Tue, 02 Nov 2010 16:01:31 GMT

Hi,

Are you passing your program name to this FM. Please verify it once and more thing try to call this FM after the statment START-OF-SELECTION and make sure that the IMPORT MEMORY statment is before the FM is called and check the return of the IMPORT statement.

Let me know if any.

Regards,

Srinivas

Re: Selection screen values as form params...

roberto_vacca2 — Tue, 02 Nov 2010 16:08:50 GMT

Hi ..

How do you set your value? SET PARAMETER ID : 'RAC' FIELD racer? or what?..

Bye,

Re: Selection screen values as form params...

Former Member — Tue, 02 Nov 2010 16:12:40 GMT

I set the value when i declare the parameter:

PARAMETERS: p_kokrs TYPE kokrs OBLIGATORY MEMORY ID cac.

Re: Selection screen values as form params...

roberto_vacca2 — Tue, 02 Nov 2010 16:18:15 GMT

Did you try field symbols?.. They are in the dynamic memory so they should always be visible..

Re: Selection screen values as form params...

Former Member — Tue, 02 Nov 2010 16:27:11 GMT

Function module picks all values accept those set when I declare the parameter with the MEMORY ID extension as follows:

PARAMETERS: p_kokrs TYPE kokrs OBLIGATORY MEMORY ID cac.

Seems odd...doesn't it.

Re: Selection screen values as form params...

roberto_vacca2 — Tue, 02 Nov 2010 16:35:26 GMT

With memory ID instruction you're linking your report with your parameter.. You have to "break the chain between report's memory and function's memory.. the only way is a virtual bridge between the two..

Could you write much more abap code about this question?..

Re: Selection screen values as form params...

Former Member — Tue, 02 Nov 2010 16:53:44 GMT

The only code that is pertinent is the declaration of the parameter ID:

PARAMETERS: p_kokrs TYPE kokrs OBLIGATORY MEMORY ID cac.

And the call to the fm:

CALL FUNCTION 'RS_REFRESH_FROM_SELECTOPTIONS'

EXPORTING

curr_report = sy-cprog

TABLES

selection_table = lt_rsparams

EXCEPTIONS

not_found = 1

no_report = 2

OTHERS = 3.

For instance...when I run the program I can see the value set on the selection screen for p_kokrs. If I select F4 help for another field on the selection screen I immediatly call the fm to collect current values set for fields on the selection screen. I notice any values set by a MEMORY ID are not returned in the call to the fm...any value set manually is picked up. If I run the program and then F3 back up to the selection screen...and then select F4 help for the same field...I do get all the values returned in the fm. Why is that?

Re: Selection screen values as form params...

Former Member — Tue, 02 Nov 2010 17:04:06 GMT

OK...If the fm returns no value for the field in question...I do a get memory id and that returns the needed value.

Re: Selection screen values as form params...

roberto_vacca2 — Tue, 02 Nov 2010 17:07:29 GMT

I'm looking for an explanation... instead you can try this...

I noticed there are a lot of submit in the function module...Try to put, after CALL FUNCTION 'RS_REFRESH_FROM_SELECTOPTIONS'..

this..

If sy-subrc EQ 0.

COMMIT WORK AND WAIT.

ENDIF.

Re: Selection screen values as form params...

kesavadas_thekkillath — Tue, 02 Nov 2010 17:21:10 GMT


 If I select F4 help for another field on the selection screen I immediatly call the fm to collect current values set for fields on the selection screen. I notice any values set by a MEMORY ID are not returned in the call to the fm

Will you please make this some more clear

How are you collecting the current value set ? - Are you using DYNP_VALUES_READ ?