Sub Screen

Hi Gurus,
Am studying screen exits scenario. When am studying this scenario am getting a doubt that when creating the screen with transaction se80 and develop the screen in a particular function group. Normally function group is used for functional modules to store in a same group so that they can share global data. What the purpose of function group while creating the screen in a particular function group.
Hope my problem will be clear.
Points will be awarded.
Regards
Ravi

Hi,
A demo program to create subscreen in your ABAP Program
A demo program to create subscreen in your ABAP Program
This report will display the user last login date and time.
Subscreen selection 1 : User Name
                               2 : Last Login Date
                               3 : Class Belong To
Written by : SAP Basis, ABAP Programming and Other IMG Stuff
                   http://www.sap-img.com
REPORT ZSUBSCREEN.
TABLES: USR02,       "Logon data
        SSCRFIELDS. "FIELDS ON SELECTION SCREENS
SUBSCREEN 1
SELECTION-SCREEN BEGIN OF SCREEN 100 AS SUBSCREEN.
SELECTION-SCREEN BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-010.
   SELECT-OPTIONS: USERNAME FOR USR02-BNAME.
SELECTION-SCREEN END OF BLOCK B1.
SELECTION-SCREEN END OF SCREEN 100.
SUBSCREEN 2
SELECTION-SCREEN BEGIN OF SCREEN 200 AS SUBSCREEN.
SELECTION-SCREEN BEGIN OF BLOCK B2 WITH FRAME TITLE TEXT-020.
   SELECT-OPTIONS: LASTLOGI FOR USR02-TRDAT.
SELECTION-SCREEN END OF BLOCK B2.
SELECTION-SCREEN END OF SCREEN 200.
SUBSCREEN 3
SELECTION-SCREEN BEGIN OF SCREEN 300 AS SUBSCREEN.
SELECTION-SCREEN BEGIN OF BLOCK B3 WITH FRAME TITLE TEXT-030.
   SELECT-OPTIONS: CLASSTYP FOR USR02-CLASS.
SELECTION-SCREEN END OF BLOCK B3.
SELECTION-SCREEN END OF SCREEN 300.
STANDARD SELECTION SCREEN FOR SCROLLING LEFT AND RIGHT
SELECTION-SCREEN: FUNCTION KEY 1,
                  FUNCTION KEY 2.
SELECTION-SCREEN: BEGIN OF TABBED BLOCK SUB FOR 15 LINES,
                  END OF BLOCK SUB.
START-OF-SELECTION.
    SELECT * FROM USR02 WHERE BNAME IN USERNAME
                          AND ERDAT IN LASTLOGI
                          AND CLASS IN CLASSTYP.
       WRITE: / 'User ', USR02-BNAME,
                'Last Login Date ', USR02-TRDAT,
                'Last Login Time ', USR02-LTIME,
                'CLASS ', USR02-CLASS.
    ENDSELECT.
END-OF-SELECTION.
INITIALIZATION.
SCREEN ICON LEFT AND RIGHT
SSCRFIELDS-FUNCTXT_01 = '@0D@'.
SSCRFIELDS-FUNCTXT_02 = '@0E@'.
SUB-PROG = SY-REPID.
SUB-DYNNR = 100.
AT SELECTION-SCREEN.
CASE SY-DYNNR.
    WHEN 100.
      IF SSCRFIELDS-UCOMM = 'FC01'.
        SUB-DYNNR = 300.
      ELSEIF SSCRFIELDS-UCOMM = 'FC02'.
        SUB-DYNNR = 200.
      ENDIF.
    WHEN 200.
      IF SSCRFIELDS-UCOMM = 'FC01'.
        SUB-DYNNR = 100.
      ELSEIF SSCRFIELDS-UCOMM = 'FC02'.
        SUB-DYNNR = 300.
      ENDIF.
    WHEN 300.
      IF SSCRFIELDS-UCOMM = 'FC01'.
        SUB-DYNNR = 200.
      ELSEIF SSCRFIELDS-UCOMM = 'FC02'.
        SUB-DYNNR = 100.
      ENDIF.
ENDCASE.
Thanks,
Sankar M

Similar Messages

How to call a sub screen from abap report

Hellow friends,
how to call sub screen 1001 prog name SAPLMGD1
and main program SAPLMGMM screen 4000 of tcode MM02.
i need to call the sub screen from abap report

Hi Rajesh,
You can use FM MATERIAL_MAINTAIN_DIALOGUE to go to subcreen MRP1 in MM02.
Please check this sample code from other thread and enter 'MRP 1' for p_dytxt.
REPORT zsritest.
TABLES mara.
DATA: lv_bilds LIKE t133a-bilds,
ls_t130m LIKE t130m,
ls_rmmg1 LIKE rmmg1,
lwa_view TYPE mbildtab,
lwa_auswg TYPE mgauswg,
lt_views TYPE STANDARD TABLE OF mbildtab INITIAL SIZE 0,
lt_auswg TYPE STANDARD TABLE OF mgauswg INITIAL SIZE 0.
PARAMETERS: p_matnr LIKE mara-matnr,
p_werks LIKE marc-werks,
p_dytxt LIKE mbildtab-dytxt.
SELECT SINGLE * FROM mara WHERE matnr EQ p_matnr.
CHECK sy-subrc EQ 0.
CALL FUNCTION 'T130M_SINGLE_READ'
EXPORTING
tcode = 'MM02'
kzrfb = 'X'
IMPORTING
wt130m = ls_t130m
EXCEPTIONS
not_found = 1
wrong_call = 2
OTHERS = 3.
CALL FUNCTION 'BILDSEQUENZ_IDENTIFY'
EXPORTING
branche = mara-mbrsh
materialart = mara-mtart
tcode_ref = ls_t130m-trref
* KZRFB = ' '
IMPORTING
bildsequenz = lv_bilds
* KZ_BILDS_CHANGED =
EXCEPTIONS
wrong_call = 1
not_found = 2
OTHERS = 3.
CALL FUNCTION 'SELECTION_VIEWS_FIND'
EXPORTING
bildsequenz = lv_bilds
pflegestatus = mara-pstat
TABLES
bildtab = lt_views[]
EXCEPTIONS
call_wrong = 1
empty_selection = 2
OTHERS = 3.
ls_rmmg1-matnr = mara-matnr.
ls_rmmg1-werks = p_werks.
READ TABLE lt_views INTO lwa_view WITH KEY dytxt = p_dytxt.
CHECK sy-subrc EQ 0.
lwa_auswg-auswg = lwa_view-auswg.
APPEND lwa_auswg TO lt_auswg.
CALL FUNCTION 'MATERIAL_MAINTAIN_DIALOGUE'
EXPORTING
irmmg1 = ls_rmmg1
* IRMMG1_REF = ' '
KZ_EIN_DARK = 'X'
t_tcode = 'MM02'
* FLG_MATNR_RES = ' '
p_pstat = mara-pstat
* FLG_STAT_ALL = ' '
* CALL_MODE2 = ' '
* IMPORTING
* MATERIAL_NO =
* UPDATE_OK =
TABLES
iauswg = lt_auswg[]
EXCEPTIONS
no_authority = 1
OTHERS = 2.
IF sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
Regards,
Ferry Lianto

How can we take the cursor to a different sub-screen from the BADI?

Hi,
We have to do some validation on Header, Operation and Relationship of any work order (IW31, IW32). We have checked that validations can be done at BADI WORKORDER_UPDATE in the method u2018AT_SAVEu2019. But user wants us to take the Cursor back to the field and screen due to which the error is coming. How can we take the cursor to a different sub-screen from the BADI?
Thanks in Advance,
Pranav

You 'ran out of room' because you tried to put your entire question into what is the 'Topic line' of the post.
This is a fairly common error, as a scan of the topic list will show, and likely due to a design flaw in the layout of the composition page.
Most posters who make this error do so on their first post, and are able to avoid a similar misstep on their second and subsequent questions.
Regards,
Barry

How to create a new field in a sub screen in material master. ?

How to create a new field in a sub screen in material master. ?
Kindly help us.
LIke wise tell me how to create a new sub screen as per my desired

Follow the documentation of Logistics - General->Material Master->Configuring the Material Master->Create Program for Customized Subscreens to add the new field in material master.
Create Program for Customized Subscreens
In this IMG activity, you can create a function group of your own by copying function group MGD1 (for industry) or function group MGD2 (for retail). The subscreens are not copied, except for two subscreens which are copied for technical reasons. You can use this copy to create subscreens of your own which you can assign to a data screen in the activity Define Structure of Data Screens for Each Screen Sequence.
Requirements
Be sure to read the program documentation first.
Activities
1. Create a function group of your own by choosing Execute.
2. Enter a name containing up to 25 characters, beginning with the letter Y or Z, and choose Save.
3. Access the Object Navigator.
You do this from the SAP standard menu by choosing Tools -> ABAP Workbench, and then Object Navigator.
4. Display either program SAPLMGD1 (industry) or SAPLMGD2 (retail) as required.
5. Copy the subscreens as required, ensuring that they already contain as many as possible of the field names you want to use in your function group. You do this as follows:
a) Choose Screens, position the cursor on the corresponding subscreen, and choose Copy in the context menu.
b) Enter the program to which you want to copy the subscreen, prefixing it with SAPL, and enter a screen number. Use the screen number of the original subscreen where possible. If the F1 help is specific to a particular subscreen, this ensures that this context-specific help continues to be displayed.
Example
You have called your function group YENTERPRISE, to which you want to copy subscreen SAPLMGD1 2301. Enter SAPLYENTERPRISE as the program to which the subscreen is to be copied, and enter (preferably) 2301 as the screen number.
6. Return to the initial screen of the Object Navigator and display your program. In the example above, you would enter SAPLYENTERPRISE.
7. Choose Update object list.
8. Select the subscreen you have copied and activate it by choosing Activate in the context menu.
Using the Screen Painter, you can remove fields you do not require on the subscreen or include additional fields from other subscreens (see the ABAP Dictionary). For information on the Screen Painter, see the SAP library documentation BC ABAP Workbench Tools.
Points to consider when removing or adding fields
Make sure that a field statement exists for each field on the subscreen since data may not otherwise be transported correctly. You can use subscreen SAPLMGD1 2002 as an example.
For the fields you have added, include any check modules and modules for self-programmed F4 help that are called up for these fields on the original subscreen. You can do this by displaying the flow logic for the original subscreen and searching for such modules. They normally have the same names as the fields themselves. When you find a module, copy the corresponding module call to your subscreen.
If you change the order in which fields are transported that are checked together in the flow logic (such as the safety stock and minimum safety stock), you must deactivate the check module for the first field and activate it for the second. The system would otherwise transport the first field, and carry out the check before the second field is transported.
Any error messages that fields are unknown when activating the subscreen are due to the fields still being included in checks, even though you have removed the fields from the subscreen. Search for the fields in the source code and make the lines in which they appear comment lines. Then reactivate the screen.
9. Assign the subscreen to a data screen as required.
Note on transport
Use the Workbench Organizer to transport the copy you have created.
Proceed

Query about TABSTRIP Control within Sub screen

Hi Expert,
I have requirement like follows:
In IW32->Enhancement Tab screen is as subscreen and No: 0900.
Now I want to have 2 different sub screen say 0910 and 0920 each of this for different purpose according to
Order Type as per clients requirement.
Actaully I have developed screen 0900 already for some order type and now clients requirement changed i.e.
there are 2 different groups of Order types (say Grp1 and Grp2)
So, I proposed a solution for this as follows:
In Enhancement Tab of IW32 according to group of Order Type (either Grp1 or Grp2) only you will be able to
see fields for that perticular Grp either of 2.
Technical Solution is like...
1) I thought that I will create 2 subscreens say 0910 and 0920.
2) In 0910 i will insert all those fields which are designed already in 0900 which is for Grp1
3) and for Grp2 i will design 0920
4) according to Order Type only 0910 or 0920 client will be able to see.
Now I got stuck in between the screen development for 0920 because there are so many fields and i said to
client that they will be able to see those fields in different Tab strips.
I never worked on Tab Strip concept, I search so many forums and sites for Lesson on Tab Strip but not
understood how to proceed as per my specific requiment.
Please can anyone suggest me how to proceed further.
Thanks in advance.
Regards,
Jay.

There's no reason why you couldn't do it.
A tabstrip control is simply made of a subscreen area and a "tabstrip" above, where each tab corresponds to a button/function code. You have 2 ways to define/program it, "local" or "server", the difference being a better performance with the "local" (interesting in slow WAN).
In ABAPDOCU demos, you have 2 programs DEMO_DYNPRO_TABSTRIP_LOCAL and DEMO_DYNPRO_TABSTRIP_SERVER.
Sandra

Imqadmin: No. of messages not displayed correctly in durable subs screen

This question applies to the standalone platform edition of Message Queue v3.5 SP2 running on solaris.
I have a number of durable subscribers connecting to a topic. Each & all subscriber have a selector set to filter the data.
From imqadmin I can select the topic and bring up the broker destination properties. If I happen to have messages that have not been consumed (I halt my consumer code to test this), the count on the "basic" screen shows the current and correct number of messages waiting.
If I drill down and go to the Durable Subscriptions screen, the number of messages for the durable subscriber with the relevant selector is always 0... and doesn't seem to reflect that there are messages that haven't been consumed. (Even though my code does see the data come in when I reconnect the consumer).
Is this a bug in the imqadmin display or is there a reason why it can't display the message count correctly at the durable sub screen for consumers with a selector set?

I don't think I'm seeing the same bug... in my app the producer and consumer are both active.
Relevant information for this test:
1) My producer and consumer are both active at the same time.
2) My consumer is using a transacted session and it is also consuming messages synchronously
3) I produce 250 messages and send them to my destination (a topic)
4) For this test I force the consumer to fail on its handling of the data. Say it was trying to handle 50 messages - it rollsback the session and tries again. Therefore leaving 250 messages still in the topic.
The result is that when I display the destination properties screen using imqadmin:
1) The current number of messages count is displayed correctly as 250.
2) However, the count for the durable subscriber with the correct selector is still showing 0.
Once I allow the consumer to resume its work, all 250 messages are handled correctly by that consumer only and the count (in 1) is shown as 0.
So the producer, consumer process works fine but the imqadmin gui seems a little confused.

SELECT-OPTIONS in Module Pool Sub-Screen

Hi,
I have been working on a Module-Pool Development, in the header portion of the Screen, I have provided a Selection-Screen as a Sub-Screen because the requirement specifies to display a SELECT-OPTION in the Header Area.
Now the problem is that, when working with the Screen, as soon as I press <ENTER> the Main Screen re-calls the Selection-Screen in the Sub-Screen area and all the entries made in the Selection-Screen are reset/erased.
Kindly provide a solution either to stop the <ENTER> action to re-call the sub-screen. Or on any alternate method(s) to provide a SELECT-OPTION on a Module Pool based Screen UI.
MAIN SCREEN Code:
* PROCESS BEFORE OUTPUT
PROCESS BEFORE OUTPUT.
*~ Set PF-STATUS and TiTLE for Screen 100
MODULE status_0100.
*~ Call the Subscreen Dynamically
CALL SUBSCREEN subscr1 INCLUDING sy-cprog gv_dynnr1.
CALL SUBSCREEN subscr2 INCLUDING sy-cprog gv_dynnr2.
* PROCESS AFTER INPUT
PROCESS AFTER INPUT.
*~ Handle the Exit Commands of Screen 100
MODULE user_command_0100 AT EXIT-COMMAND.
*~ Handle the User Command(s) for screen 100
MODULE user_action_0100.
CALL SUBSCREEN subscr1.
CALL SUBSCREEN subscr2.
So whenever <ENTER> is pressed, the PBO re-calls:
CALL SUBSCREEN subscr1 INCLUDING sy-cprog gv_dynnr1.
and the Selection-Screen is reset.
Regards,
Nishant Nayyar.

Haii Nishant,
This problem was earlier solved by one of the members and after going through it i have now created a select-option in the Subscreen. Just create two input fields, name them as if they were low and high (for convinience as in case of select-option).
U now need to create a table of type rstabfield.
Ex: gt_rstab_bukrs type rstabfield.
Now create a button and assign a Fcode for it. When you click on this button then u need to implement the ranges functionality as in select-option. For that use the following function module:
CALL FUNCTION 'COMPLEX_SELECTIONS_DIALOG'
EXPORTING
TITLE = ' '
 TEXT = ''
 SIGNED = 'X'
 SEARCH_HELP = 'H_T001'
 TAB_AND_FIELD = gt_rstab_bukrs
TABLES
 RANGE = rg_bukrs1.
Hope it helps.
Best Regards,
rama

ALV Grid: refresh in sub screens

Hello All,
I have some issues with internal table display in ALV grid.
The following is the scenario.
I am in a wizard which has 2 sub screens (SScreen 1 and sscreen 2).
1)On sscreen 1, i have a input field,where i provide a value and on clicking the next button i get a list of values which i display on sub screen 2 using ALV grid.
2)Now i go back to sscreen1 and change the value in the input field,since i use on-request module, i know the value in the field has changed and now i need to display new set of values on sscreen 2.
In this case i clear the internal table, get new values for internal table and then call set_values_for_first_display().However i still get the old values displayed on SScreen 2!!!!.
Any suggestions on what i might be doing wrong?
Cheers
Dev

Hi Vijay,
Thanks for the info.
I will try refresh_table_display option after getting to work in a couple of hours.
I am initializing the grid and control everytime i change a value on Subscreen 1 in the PBO of Subscreen 2(the screen where the ALV list is displayed).
That is the reason why i call set_table_first_display, whenever there are new values in the internal table and avoid refresh_table_display.
Cheers
Dev

Custom sub-screen creation in 'MRP 4' tab of MM01

Hi All,
I have to add custom sub-screens in u2018Accounting 2u2019, u2018MRP 2u2019 and u2018MRP 4u2019 tabs of the Material Master transaction (MM01).
I could successfully add a sub-screen in u2018Accounting 2u2019, u2018MRP 2u2019 tabs by using SPRO (Logistics -> Material master -> Configuring the material master -> Define structure of data screens).
However, I could not able to add incase of u2018MRP 4u2019 tab, as Standard SAP has already used all the existing 6 sub-screens. If I try further to create any, I get the error u201CInsertion not possible since maximum number of sub-screens reached u201C.
Please help me out in this scenario.
Thanks in advance!

Screen number changed from 4000 to 4004 in SPRO, which allows to create a maximum of 10 subscreens.

Problem in populating field of same name in main & sub screen

Hi Guys,
I have a problem in my BDC program where the same field name appear in main screen and subscreen. Everytime i run the BDC program it will only populate to the field in main screen but not in the subscreen.
Below are the result of my BDC recording: Where PKHD-LGNUM, PKHD-LGTYP and PKHD-LGPLA exist in main screen 0110 and also sub screen.
SAPMMPKR 0110 X
 BDC_OKCODE =SAVE
 PKHD-LGPLA KB
 PKHD-LGNUM 100
 PKHD-LGTYP 150
 PKHD-BEHAZ 10
 PKHD-SIGAZ 8
 PKHD-BEHMG 50
 BDC_SUBSCR SAPMMPKR 0813INCLUDE8XX
 PKHD-UMLGO S020
 PKHD-LGNUM 100
 PKHD-LGTYP 150
 PKHD-LGPLA KB
 BDC_SUBSCR SAPMMPKR 0820INCLUDE820
 BDC_CURSOR PKHD-KOSTL
 PKHD-KOSTL 8441
 BDC_SUBSCR SAPMMPKR 0830INCLUDE830
This is the actual extract from SAP standard recording program, i even re-run the recording and it is not able to populate the value back into the subscreen fields of the same.
Any one encounter the same problem and solve it? please help me please.
Many thanks,
Jay

The transaction i'm dealing with is PK01, control cycle creation. There is a screen where we specified the control cycle data and there is a subscreen to specify stock transfer location. Problem when both these main and subscreen have fields tied to the same name and structure.
If the screen fields name are the same, logically the BDC suppose to populate both field at the same time, however in my case the BDC only populate to the one in the main screen while the fields in subscreen are left empty. I have tried to specify the subscreen before populating the screen field, the value just won;t go in. I suspect it is still the problem in specifying the subscreen in populating the BDCDATA. I just dont know how, i have tried every possible way of specifying the subscreen.

Sub screen: Handling the Radio button selection?

Hi,
Scenario:
I have a Main screen and a sub screen. From the main screen I am calling the sub screen. On the Sub screen, I have 2 radio button. On the selection of the Radio buttons, I am activating/deactivating few of the screen elements on the sub screen.
I have grouped the radio button and also tried assigning Function code to it, but in vain..:(
Issue
I am not able to handle the event triggered by the selection of the radio buttons?
Kindly suggest.
Regards
s@k

Hi,
Are you still have any Issue, Let us know
In the Main Screen Element List there is a field OK_CODE pass an entry into it
in the TOP Include
DATA : OK_CODE type SY-UCOMM. " This captures the OK_CODE from the Screen.
Since SUb Screen cant have their Own OK_CODE this can be handled in the Main Screen only
Try in PAI of Sub Screen using OK_CODE if it is not working then Implement the same in PAI of Main Screen
The system will generate UCOMM for Radio Button since they are in One Group only. Each Radio button cannt have a separate UCOMM assigned. In Screen Painter (if It is Module Pool) assign a FCode for the Radio Button.
Even if try changing the FCODe Value they still will have the New Changed Value but cannot be changed.
This automatically triggers PAI . only way to capture it is check
case ok_code. " Optionally you can omit this
when ok_code = 'RAD'. " This is common for all the Radio BUttons but cant be different
if r1 = 'X'.
elseif r2 'X' " Etc.
endif.
endcase.
Ram
Edited by: Ramchander Krishnamraju on Feb 26, 2010 10:37 AM

Problem with sub-screen actions on Cancel button

Hi all,
I have a problem with sub-screen.
I created a subscreen (screen sequence in MM01/MM02/MM03). When users leave this screen, I call POPUP_TO_CONFIRM to ask if they want to save the data.
1) My goal is: when they choose Cancel, no actions are performed and users will see the current screen. However, I cannot use command: SET SCREEN 0 or LEAVE TO SCREEN 0 because the system gives an error message:
*SET SCREEN not allowed in subscreens*.
2) How can we determine when the user leaves the screen? which value of SY-UCOMM will be used to check this?
Thanks in advance.

for dis SET SCREEN is not required.
Consider d code given below as n eg:
CALL FUNCTION 'POPUP_TO_CONFIRM'
 EXPORTING
 titlebar = 'SAVE'
 text_question = 'SOME _QUS'
 text_button_1 = 'YES'
 text_button_2 = 'NO'
 default_button = '2'
 display_cancel_button = ' '
 IMPORTING
 answer = l_ans
 EXCEPTIONS
 text_not_found = 1
 OTHERS = 2.
IF sy-subrc <> 0.
 MESSAGE e066.
ENDIF.
IF l_ans EQ '1'. " when yes is pressed
 MODIFY db.
 commit work.
 leave program.
ELSEIF l_ans EQ '2'. "when no is pressed
 leave program.
ELSE. " when cancel is pressed
ENDIF.
In above module when Yes is pressed it saves data den leave prog.
As no action is specified for cancel button it will remain on that screen only from which popup is called, in this way ur problem can be solved.
Reward properly.

How To handle User Command in Sub Screen .

How can we handle Sy-ucomm in sub screen .

You do that in the PAI of the screen (Process After Input)
MODUE PAI.
CASE SY-UCOMM.
WHEN 'XXXX.
WHEN 'YYY'.
ENDCASE.
Regards,
Ravi

Why the multiple selection can't work in sub screen

hi experts:
 when i try to use the sub-screen in the report,why the multiple selection function(SO_BCTXT) can't work normally in screen 1095:
the coding as below.will reward points if solve this issue
the main program in Subscreen:
PROCESS BEFORE OUTPUT.
module status_1005.
CALL SUBSCREEN area INCLUDING sy-repid lv_tab_number.
PROCESS AFTER INPUT.
MODULE cancel AT EXIT-COMMAND.
CALL SUBSCREEN area.
MODULE user_command_1005.
module user_command_1005 input.
my_ok = ok_code.
clear ok_code.
case my_ok.
 when 'TAB1'.
 mytabstrip-activetab = my_ok .
 lv_tab_number = 1095.
 when 'TAB2'.
 mytabstrip-activetab = my_ok .
 lv_tab_number = 1096.
 when 'CRET' or 'ONLI'.
 perform get_bc_set
 using
 so_chanb[]
 changing
 <fs_bcsetfield> .
 leave to screen 0.
endcase.
endmodule.
in the screen 1095:
PROCESS BEFORE OUTPUT.
MODULE %_INIT_PBO_J.
MODULE %_PBO_REPORT.
MODULE %_PF_STATUS.
MODULE %_SO_BCTXT.
MODULE %_END_OF_PBO.
PROCESS AFTER INPUT.
MODULE %_INIT_PAI_J.
CHAIN.
FIELD SO_BCTXT-LOW.
FIELD SO_BCTXT-HIGH.
MODULE %_SO_BCTXT.
ENDCHAIN.
FIELD !INCBCTY1 MODULE %_INCBCTY1 .
FIELD !INCBCTY2 MODULE %_INCBCTY2 .
FIELD !INCBCTY3 MODULE %_INCBCTY3 .
FIELD !INCBACT MODULE %_INCBACT .
FIELD !INCBINAC MODULE %_INCBINAC .
FIELD !INCLMAND MODULE %_INCLMAND .
FIELD !INCLOPTI MODULE %_INCLOPTI .
CHAIN.
FIELD SO_BCTXT-LOW.
FIELD SO_BCTXT-HIGH.
FIELD INCBCTY1 .
FIELD INCBCTY2 .
FIELD INCBCTY3 .
FIELD INCBACT .
FIELD INCBINAC .
FIELD INCLMAND .
FIELD INCLOPTI .
MODULE %_BLOCK_1095001.
ENDCHAIN.
CHAIN.
FIELD SO_BCTXT-LOW.
FIELD SO_BCTXT-HIGH.
FIELD INCBCTY1 .
FIELD INCBCTY2 .
FIELD INCBCTY3 .
FIELD INCBACT .
FIELD INCBINAC .
FIELD INCLMAND .
FIELD INCLOPTI .
MODULE %_END_OF_SCREEN.
MODULE %_OK_CODE_1000.
ENDCHAIN.
in the main report
selection-screen begin of screen 1095 as subscreen.
enquire Data
data l_text type as4text.
selection-screen begin of block b1 with frame title text-024.
select-options :
so_bctxt for l_text .
selection-screen skip 1 .
parameters:
incbcty1 type c as checkbox default abap_true ,
incbcty2 type c as checkbox default abap_true ,
incbcty3 type c as checkbox default abap_true .
selection-screen skip 1 .
parameters:
incbact type c as checkbox default abap_true ,
incbinac type c as checkbox default abap_true .
selection-screen skip 1 .
parameters:
inclmand type c as checkbox default abap_true ,
inclopti type c as checkbox default abap_true .
selection-screen end of block b1.
selection-screen end of screen 1095 .

Hiii
 In main program you have dclared subscreen area.
now First of all you have to declare a selection screen in your main program
selection-screen begin of screen 1005 as subscreen.
SELECT-OPTIONS s_bukrs1 for v_bukrs. "whatever you want in selection screen
selection-screen end of screen 1005.
IN PBO of your main screen (not in 1005) write
call subscreen SUB1 including sy-repid '1005'.
where SUB1 is your subscreen area name. And remember don't touch PBO or PAI of your 1005 screen, otherwise it will give you error. Yuo can just put text in layout of 1005 screen. but don't disturb other things.

Adding column in sub screen

Hi every one,
I have 10 columns in my sub screen, i would like to add one more column in that, can any one help me, how to create a new column in the sub screen.
ex:
Columns:          a   b   c    d
                        1   2   3    4
                        2   3   4    5
Now i want to add "e" column.
Thanks in advance.

The field should be tagged as Input on the parameter screen for that field. You can get there by
double clicking on the field in the first row of the table control. To get the values updated to the
actual internal table, there is a routine in the PAI that should look something like this.
*&spwizard: pai flow logic for tablecontrol 'TC_202'
LOOP AT mt_approvers.
    CHAIN.
      FIELD mt_approvers_rec-division.
      FIELD mt_approvers_rec-branch.
      FIELD mt_approvers_rec-appr_level.
      FIELD mt_approvers_rec-userid.
      FIELD mt_approvers_rec-name.
      MODULE tc_202_modify ON CHAIN-REQUEST.
    ENDCHAIN.
    FIELD mt_approvers_rec-sel
      MODULE tc_202_mark ON REQUEST.
ENDLOOP.
MODULE tc_202_user_command.
*&spwizard: module TC_202_change_tc_attr.
*&spwizard: module TC_202_change_col_attr.
You will need to add your field to the FIELD list.
The module it calles during that loop, will/should contain the code
MODIFY mt_approvers
    FROM mt_approvers_rec
    INDEX tc_202-current_line.
If after changing the parameter to allow Input, should it still not allow you to input, then in the PBO
routine there is likely code that sets the parameters to the table control to input = 0 and that would
need to change to allow input to the appropiate columns.

Sub Screen in Screen Painter

I created a screen in the screen painter and it works fine .
Now i want when i push a button to display a small selection criteria in a window subscreen (?) so to take some result.
I dont know if this can happen . Is there any FM to do this ?
Thanks a lot ...

hi,
for this u hav to do following steps
>>Define the sub-screen area(s) on a screen. Resizable, Minimum size and scrollable are the attributes
>>Define suitable sub-screen screens
>>Include the sub-screen screen in the sub-screen area.
>>Adjust the frame of the sub-screen within the "main" screen. Name the sub-screen in the Field name field.
>>Arrange the fields within the sub-screen so that they appear in the main screen .
>>You include a subscreen screen using the CALL SUBSCREEN statement in the flow logic of the main screen.
To include a subscreen screen in the subscreen area of the main screen and call its PBO flow logic, use the following statement in the PBO event of the main screen:
PROCESS BEFORE OUTPUT.
CALL SUBSCREEN in the PBO event. This can call PAI modules of the ABAP program in which the subscreen screen is defined. Data is transported between identically-named fields in the subscreen screen and the ABAP program either when the PAI event is triggered, or at the corresponding FIELD statements in the PAI flow logic of the subscreen screen.
thanks
Sachin

Sub Screen

Similar Messages

Maybe you are looking for