Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

Select-options in module pool. Please respond quickly

Former Member
0 Kudos

Hi Guru's,

I have created a program by following example in SDN ( which contains select options), I have called in the PBO and PAI, Select options which is in the subscreen area appears, but when I am giving some values into the select options

Say 10 to 20. now when I enter debug mode I was unable to catch the values entered in the subscreen area. Please let me know how to catch the values.

example.

REPORT ZSCREEN101.

TABLES

: z9mm_vend_qual. "Vendor Certification

data: s_low type matkl,

s_high type matkl.

SELECTION-SCREEN BEGIN OF SCREEN 101 AS SUBSCREEN.

SELECTION-SCREEN BEGIN OF LINE.

SELECT-OPTIONS : s_MATKL for z9mm_vend_qual-MATKL MATCHCODE OBJECT mcd.

SELECTION-SCREEN END OF LINE.

SELECTION-SCREEN END OF SCREEN 101.

In modulepool program I am calling in this manner below.

PROCESS BEFORE OUTPUT.

MODULE STATUS_0101.

CALL SUBSCREEN SUB_101

INCLUDING 'ZSCREEN101' '101'.

PROCESS AFTER INPUT.

CALL SUBSCREEN SUB_101.

Please let me know how to catch the variables which I have given in the screen.

Thanks in advance,

Sagar.

1 ACCEPTED SOLUTION

Former Member
0 Kudos

The logic looks OK at first glance - in debug you should see the 10 + 20 values in both the header row of S_MATKL (in LOW & HIGH) as well as the body of the table... but why have you defined "s_low type matkl and s_high type matkl". And where have you set you breakpoint - is there more logic not shown e.g. another module in the PAI after the subscreen call?

Jonathan

3 REPLIES 3

Former Member
0 Kudos

The logic looks OK at first glance - in debug you should see the 10 + 20 values in both the header row of S_MATKL (in LOW & HIGH) as well as the body of the table... but why have you defined "s_low type matkl and s_high type matkl". And where have you set you breakpoint - is there more logic not shown e.g. another module in the PAI after the subscreen call?

Jonathan

0 Kudos

Looks ok to me too. You should see the values in the s_MATKL while in debug.

Regards,

Rich Heilman

0 Kudos

Thanks for all the support friends,

after a long standing debug I was not able to find the s_matkl-low or s_matkl-high.

Here is the workaround I tried and it worked.

1. In call subscreen statement double click on the screen number .i.e. '0101'

2. now you will see another dynamic flowlogic opens for the screen.

3. go to attributes and then go to special attributes.

4. now against s_matkl-low and s-matkl-high check the Set Parameter ID, give P1 and P2 against each other save and activate it.

5. declare 2 variables plow and phigh of type matkl.

6. Now in the PAI user-command after calling the subscreen statement.

7. write:

GET PARAMETER ID 'P1' FIELD PLOW.

GET PARAMETER ID 'P2' FIELD PHIGH.

8. now we have the values entered in the select-options into plow and phigh

Thanks,

Sagar.