POPUP_TO_CONFIRM & CALL SCREEN in TRIP t-code of ECC 6.0 and ESS Portal

Hi All,
We are moving from 4.6c to ECC 6.0. In 4.6c, we use POPUP_TO_CONFIRM FM and CALL SCREEN command in a custom FM to raise a confirmation screen in the standard T&E Trip Transaction ( T-code TRIP) from Portal.
From Portal, in ESS screen, when a button is pressed we call this custom FM. This custom FM uses POPUP_TO_CONFIRM and CALL SCREEN. This works fine in 4.6c
Whereas, in ECC 6.0 it gives dump when these statements are encountered.
Question:
Does anyone know what is the solution or any alternative to these commands in ECC 6.0?
FYI - This question was earlier posted in ABAP Dynpro but no response.
Thanks,
SKJ

What is the error message you are getting?
The TRIP code may have been re-written to make more use of ABAP Objects which may place some constraints on what you can do, or it may be a unicode related issue.
Post more details of the user exit you are using to call your FM and the resulting error to see if more assistance is possible.
Andrew

Similar Messages

Recent call Screen bug on iPhone

The photo below is a screen capture from my iPhone 5c recent call screen. This bug began on my iPhone 4s and carried over once I backed up and then transferred that data to my new phone. This problem first began after an update a few months ago. Is there a way of getting rid of the bug without getting rid of my contacts,mail etc.? Thank you!

I have never seen this before, and you say it started before the last update, so it could not be an update bug. What troubleshooting have you tried? User troubleshooting steps are restart, reset, restore from backup, restore as new. If you restore the device as new and then test it before adding any additional content, it should work. If it does and you restore your backup and it fails again, then the problem is in your backup file. Mail and contacts can be restored from wherever you are syncing them to, i.e. supported application on the computer, cloud service. That would allow you to avoid the backup.

ESS Portal Trip/Expense form only prints the first page

Good morning;
Our users reported that when they display a trip/expense via Portal and then right mouse click in order to print the trip, only the first page prints out. If they go to the SAP Gui and run the TRIP transaction and display the trip in Print Preview form and print it, they get all the pages of the trip/expense printed.
Has anyone ever run into this strange issue before?
Thanks.
Scott.

Thanks for the quick response.
I'm assuming that you are refering to the IMG Path:
Cross-Application Components->Homepage Framework->Resources
->Define Resources
Select activity Define Resources (Change Entries)
When I check this in the IMG, we do not have a resource called EMPLOYEE_TRAVEL_TRIPFORM_SRV05.
Currently we are on ECC 5.0 and note 525862 references Rel 4.6c so I know that those corrections are part of our system. The 812903 note refers to ECC 6.0 only so this note I believe would not help us.
Should I add the resource EMPLOYEE_TRAVEL_TRIPFORM_SRV05 to the Configuration?
I see that note 1140369 references something about the EMPLOYEE_TRAVEL_TRIPFORM_SRV05 resource and has something to do with hight of the Trip form.
Scott.

My phone needs a restore but I can not because my pass code is active. It only allows me to go to the emergency call screen. I can't type in my pass code What should I do?

My phone needs a restore but I can not because my pass code is active. It only allows me to go to the emergency call screen. I can't type in my pass code What should I do?

Thank you so much I actually did have restrictions enabled. Ur too sweet thanks again for your help

ALV not getting refreshed when call screen is executed second time

I have 2 screens 9001 and 9002. In 9001 , I am displaying the fields of a database table in a Table Control. The user has to select some of those fields and click on a button 'Generate ALV'. After clicking , the control navigates to 9002 where I am displaying ALV with data in the selected fields(the other fields remain empty). (using custom container)
Now there is BACK button in 9002 where i have written LEAVE TO SCREEN 9001. After this if the user again make changes in column selection and click on 'Generate ALV' , then still the old alv data is displayed. (Mind you the structure of alv is same , only the selected fields should show data).
I am using REFRESH_ALV_DISPLAY also and when i tested this function independently , its working fine (although for interactive alv in the same screen).
I am making use of <fs> for dynamic internal table and i checked it using breakpoints , during the 2nd time , it contains the correctly updated data so i think the problem lies with alv
Kindly check this code
MODULE STATUS_9002 OUTPUT.
SET PF-STATUS 'ZALV'.
* SET TITLEBAR 'xxx'.
CREATE OBJECT C_CONT
 EXPORTING
 CONTAINER_NAME = 'CUST_CONT'
IF SY-SUBRC <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
IF OBJ_ALV IS INITIAL.
CREATE OBJECT OBJ_ALV
 EXPORTING
 I_PARENT = C_CONT
CALL METHOD OBJ_ALV->SET_TABLE_FOR_FIRST_DISPLAY
 EXPORTING
 I_STRUCTURE_NAME = INP_TABLE
 CHANGING
 IT_OUTTAB = <itab>
ELSE.
 CALL METHOD OBJ_ALV->REFRESH_TABLE_DISPLAY
ENDIF.
ENDMODULE. " STATUS_9002 OUTPUT
Edited by: amber22 on Sep 16, 2011 6:45 PM

Amber,
Something like:
*& Module STATUS_9001 OUTPUT
MODULE status_9001 OUTPUT.
SET PF-STATUS 'ST9001'.
ENDMODULE. " STATUS_9001 OUTPUT
*& Module USER_COMMAND_9001 INPUT
MODULE user_command_9001 INPUT.
CASE sy-ucomm.
 WHEN 'GEN'.
 SELECT * FROM spfli INTO TABLE gt_outtab.
 CALL SCREEN 9002.
 WHEN 'BACK'.
 LEAVE.
ENDCASE.
ENDMODULE. " USER_COMMAND_9001 INPUT
*& Module STATUS_9002 OUTPUT
MODULE status_9002 OUTPUT.
SET PF-STATUS 'ST9002'.
IF obj_alv IS INITIAL.
 CREATE OBJECT c_cont
 EXPORTING
 container_name = 'CUST_CONT'.
 CREATE OBJECT obj_alv
 EXPORTING
 i_parent = c_cont.
 CALL METHOD obj_alv->set_table_for_first_display
 EXPORTING
 i_structure_name = 'SPFLI'
 CHANGING
 it_outtab = gt_outtab.
ELSE.
 CALL METHOD obj_alv->refresh_table_display.
ENDIF.
ENDMODULE. " STATUS_9002 OUTPUT
*& Module USER_COMMAND_9002 INPUT
MODULE user_command_9002 INPUT.
CASE sy-ucomm.
 WHEN 'BACK'.
 CALL METHOD: obj_alv->free, c_cont->free.
 CLEAR: obj_alv, c_cont.
 CALL METHOD cl_gui_cfw=>flush.
 LEAVE TO SCREEN 9001.
ENDCASE.
ENDMODULE. " USER_COMMAND_9002 INPUT
Altough it's not a really nice solution... Why using 2 screens for example? you could use two containers instead...
Also I would recommand playing with the new salv class for your grids.
Anyway don't hesitate to give feed-back.
Kr,
m.

In CL_GUI_SPLITTER_CONTAINER ALV list is not show in called screen

Hello experts,
i come across a problem while using the class:CL_GUI_SPLITTER_CONTAINER ,
my codes is as follows:
data:declarations is as follows:
             data:gr_spliter     TYPE REF TO cl_gui_splitter_container,
                     gr_container1 TYPE REF TO cl_gui_container,
                     gr_container2 TYPE REF TO cl_gui_container,
                     gr_grid1       TYPE REF TO cl_gui_alv_grid,
                     gr_grid2       TYPE REF TO cl_gui_alv_grid,
step 0 Fit table contents:gt_out1 and gt_out2
step 1:   CREATE OBJECT gr_spliter
               EXPORTING
               parent            = cl_gui_container=>screen0
               ows               = 1
               columns         = 2
step 2: CALL METHOD gr_spliter->get_container
             EXPORTING
             row       = 1
            column    = 1
            RECEIVING
            container = gr_container1.
            CALL METHOD gr_spliter->get_container
             EXPORTING
             row       = 1
            column    = 2
            RECEIVING
            container = gr_container2.
step 3 :call screen 100 to show ALV.
in the screen's PBO ,i show ALV using CL_GUI_ALV_GRID,the codes is:
   CREATE OBJECT gr_grid1
    EXPORTING
      i_parent          = gr_container1
   CREATE OBJECT gr_grid2
    EXPORTING
      i_parent          = gr_container2
CALL METHOD gr_grid1->set_table_for_first_display
    EXPORTING
      i_structure_name              = Structure of table Gt_OUT1
    CHANGING
      it_outtab                     = gt_out1
CALL METHOD gr_grid2>set_table_for_first_display
    EXPORTING
      i_structure_name              = Structure of table Gt_OUT2
    CHANGING
      it_outtab                     = gt_out2
But after activing the program ,there is no ALV show in screen 100,I debug the program and find that
all the above object have been created corredtly.
if i create a custom contol named 'CONTAINER',and at Step 1 change the parent's value to 'CONTAINER',
then i could see the ALV　whick i hope in screen 100.
If i create a custom control in screen 100, the size of the alv will be different across different computer,
is it possible to use CL_GUI_CONTAINER=>screen0 as cl_gui_splitter_container's attribute parent value???
and i find that there are 10 attributes named screen0 to screen9 in class CL_GUI_CONTAINER,will you tell me the usage of
these attributes?
now i only konw that ,you could set a containers parent value to be CL_GUI_CONTAINER=>screen0,which you do't have to create
a custom control in your screen ,and the alv will be shown in full screen.and what the other attributes use (screen1,screen2,screen3,screen4 and so on)
now i am confused with the problem,i am sure any words from you will give me help to this question!
Hope to receive your advice!
Best regards!
yours Carl
Edited by: lakeandmoon on Aug 27, 2010 11:24 AM

Dear Carl,
I mean go to screen painter and place there CUSTOM_AREA (the icon with C letter). In program's PBO create CUSTOM_CONTAINER
module pbo output.
if custom_container is initial.
CREATE OBJECT custom_container
   EXPORTING container_name = 'CUSTOM_AREA'.\
endif.
endmodule.
Then you work only with CUSTOM_CONTAINER (i.e. as parent to SPLITTER_CONTAINER). Using subscreens here doens't really add the value, so you don't need any.
But how could i stretch the screen and this area to full screen?is it just gragging the screen to full screen and drag the subscreen or the custom control to full screen in screen painter?
Yes, this is what I mean
Regards
Marcin

Statement "CALL SCREEN" is not allowed in this form.

Hi,
Could anyone identify the short dump.
Statement "CALL SCREEN" is not allowed in this form.
There is probably an error in the program
"SAPLKKBL".
This program is triggered in the update task. There, the
following ABAP/4 statements are not allowed:
- CALL SCREEN
- CALL DIALOG
- CALL TRANSACTION
- SUBMIT
Error in
"POSTING_ILLEGAL_STATEMENT" " "
"SAPLKKBL" or "LKKBLU01"
"K_KKB_LIST_DISPLAY"
Regards
Manohar S

Short text
Statement "CALL SCREEN" is not allowed in this form.
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLKKBL" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
There is probably an error in the program
"SAPLKKBL".
This program is triggered in the update task. There, the
following ABAP/4 statements are not allowed:
- CALL SCREEN
- CALL DIALOG
- CALL TRANSACTION
| - SUBMIT
Information on where terminated
Termination occurred in the ABAP program "SAPLKKBL" - in "K_KKB_LIST_DISPLAY".
The main program was "RSM13000 ".
In the source code you have the termination point in line 441
of the (Include) program "LKKBLU01".
| The program "SAPLKKBL" was started in the update system.
This is the dump

Problem with call screen

Hi everybody, I did work a program with Tx SE38, in the program I call a screen.
START-OF-SELECTION.
PERFORM completa_lista.
CALL SCREEN 0100.
END-OF-SELECTION.
The program run very well, but. When the program is in screen 0100 and push the button BACK or button EXIT. Don't return to program that called to screen 0100, always return to the program SAPMSSY0 and then push again the button BACK or EXIT to return the program that called to screen 0100.
This is my code in the PAI:
MODULE user_command_0100 INPUT.
CASE sy-ucomm.
WHEN 'EXIT' OR 'BACK'.
LEAVE TO SCREEN 0.
ENDCASE.
ENDMODULE.
I try with SET SCREEN 0. or LEAVE TO SCREEN 0. But always return to the program SAPMSSY0
Is there a way to skip the program SAPMSSY0?

Hi ,
LEAVE TO SCREEN 0 will work in your case.
it comes back to the point from where it triggered screen 0100.
If you want to leave the program and come back to the easy access screen then you have to use LEAVE PROGRAM.
hope this helps!!
Regards,
Soumya Ranjan
Edited by: Soumya Ranjan on Dec 15, 2010 5:59 AM

JFileChooser.showSaveDialog() to be displayed along with calling screen

hi,
i have a frame ,in that i placed many components,one of the component is Jbutton,when the user click on this button ,it calls JFileChooser.showSaveDialog() to save a file in local system.
After opening "file save window" , without clicking file save button ,if i open some other application(like WSAD,textpad) i am not able to see "file save window" until unless i search for that window by using "alt+tab".
here what i am trying to say is "file save window " always needs to be on top of its calling screen.
i even used JFileChooser .showSaveDialog(Component parent) ,but still that is not happening,if anyone come across this problem ,please help me.
thanks in advance..

hi PhHein,
perfect answer.
Thanks for your reply,your answer made me think on my code .There was small issue in my code and its been resolved now.

How to call a transaction from ABAP code

Hi everybody,
How do I run a transaction from my ABAP code?
For example, through my ABAP code, I want to call the ME24 transaction (Maintain Purchase Order).
Thanks for the help,
Roy

CALL TRANSACTION
Syntax
CALL TRANSACTION ta { [AND SKIP FIRST SCREEN]
 | [USING bdc_tab [bdc_options]] }.
Extras:
1. ... AND SKIP FIRST SCREEN
2. ... USING bdc_tab [bdc_options]
Effect
The statement CALL TRANSACTION calls the transaction whose transaction code is contained in data object ta. The data object ta must be of character type and must contain the transaction code in uppercase letters. If the transaction specified in ta cannot be found, an untreatable exception is triggered. The additions suppress the display of the initial screen and allow you to execute the transaction using a batch input session.
At CALL TRANSACTION the calling program and its data is kept, and after exiting the called transaction, processing is resumed in the calling program after the call.
When the transaction is called, the ABAP program linked with the transaction code is loaded in a new internal session. The session of the calling program is kept. The called program runs in an SAP LUW of its own.
If the called transaction is a dialog transaction, after loading the ABAP program the event LOAD-OF-PROGRAM is triggered and the dynpro defined as initial dynpro of the transaction is called. The initial dynpro is the first dynpro of a dynpro sequence. The transaction is finished when the dynpro sequence is ended by encountering the next dynpro with dynpro number 0 or when the program is exited with the LEAVE PROGRAM statement.
If the called transaction is an OO transaction (as of release 6.10), when loading all programs except class pools the event LOAD-OF-PROGRAM is triggered and then the method linked with the transaction code is called. If the method is an instance method, implicitly an object of the corresponding class is generated and referenced by the runtime environment. The transaction is finished when the method is finished or when the program is exited using the LEAVE PROGRAM statement.
After the end of the transaction call, program execution of the calling program resumes after the CALL TRANSACTION statement.
Note
At the statement CALL TRANSACTION, the authorization of the current user to execute the called transaction is not checked automatically. If the calling program does not execute a check, the called program must check the authorization. To do this, the called program must call function module AUTHORITY_CHECK_TCODE.
Addition 1
... AND SKIP FIRST SCREEN
Effect
This addition suppresses the display of a screen of the initial dynpro of a called dialog transaction. The addition AND SKIP FIRST SCREEN suppresses the first screen under these prerequisites:
For the initial dynpro, in the Screen Painter the own dynpro number must not be specified as the next screen number.
All mandatory input fields of the initial dynpro must be filled completely and with the correct values by the SPA/GPA parameters
If these prerequisites are met, that screen of the dynpro is displayed that is specified in the Screen Painter as the next dynpro of the initial dynpro.
Example
If the static next dynpro of the initial dynpro of the called dialog transaction FLIGHT_TA is not the initial dynpro itself, its screen is suppressed, because its input fields are filled using the SPA/GPA parameters CAR and CON.
DATA: carrid TYPE spfli-carrid,
 connid TYPE spfli-connid.
SET PARAMETER ID: 'CAR' FIELD carrid,
 'CON' FIELD connid.
CALL TRANSACTION 'FLIGHT_TA' AND SKIP FIRST SCREEN.
Addition 2
... USING bdc_tab [bdc_options]
Effect
Use this addition to pass an internal table bdc_tab of row type BDCDATA from the ABAP Dictionary to a dialog transaction. The additions bdc_options control the batch input processing. When a transaction with addition USING is called, the system field sy-binpt is set to value "X" in the called program - while this transaction is running, no other transaction can be called with this addition.
The internal table bdc_tab is the program-internal representation of a batch input session and must be filled accordingly. The structure BDCDATA has the components shown in the table below.
Component Description
PROGRAM Name of the program of the called transaction
DYNPRO Number of the dynpro to be processed
DYNBEGIN Flag for the beginning of a new dynpro (possible values are "X" and " ")
FNAM Name of a dynpro field to be filled or batch input control statement, for example, to position the cursor
FVAL Value to be passed to the dynpro field or to the control statement
Using the internal table bdc_tab, you can provide any number of screens of the called transaction with input and user actions.
System Fields
sy-subrc Description
0 The batch input processing of the called transaction was successful.
< 1000 Error in the called transaction. If within the transaction a message was sent, you can receive it using the addition MESSAGES.
1001 Error in batch input processing.
Note
Outside of ABAP Objects you can specify the additions AND SKIP FIRST SCREEN and USING together. However, this does not make sense, because the addition AND SKIP FIRST SCREEN is desigend only to fill the mandatory input fields using SPA/GPA parameters, while the batch input table specified with USING controls the entire transaction flow including the display of the screens.
Example
Call of the Class Builder (transaction SE24) and display of class CL_SPFLI_PERSISTENT. The internal table bdcdata_tab contains the input for the batch input processing of the first dynpro (1000) of the transaction. Using structure opt, the batch input processing is set to suppress the first screen and to display the next screen in the standard size.
DATA class_name(30) TYPE c VALUE 'CL_SPFLI_PERSISTENT'.
DATA: bdcdata_wa TYPE bdcdata,
 bdcdata_tab TYPE TABLE OF bdcdata.
DATA opt TYPE ctu_params.
CLEAR bdcdata_wa.
bdcdata_wa-program = 'SAPLSEOD'.
bdcdata_wa-dynpro = '1000'.
bdcdata_wa-dynbegin = 'X'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'BDC_CURSOR'.
bdcdata_wa-fval = 'SEOCLASS-CLSNAME'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'SEOCLASS-CLSNAME'.
bdcdata_wa-fval = class_name.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'BDC_OKCODE'.
bdcdata_wa-fval = '=CIDI'.
APPEND bdcdata_wa TO bdcdata_tab.
opt-dismode = 'E'.
opt-defsize = 'X'.
CALL TRANSACTION 'SE24' USING bdcdata_tab OPTIONS FROM opt.

CALL SCREEN inside a FM ( parameter passing to PBO ) ?

Hello Friends,
I have the following issue:
I have a FM with some import parameter; inside the FM I am calling a screen. the screen has some input fields, and I have to set the value to input fields those import parameter of fm. I can staticaly set the input fields values in PBO, ( but as I said I need to take the values from FM ) is it possible ?
I try to set, in PBO ( pbo include ), but it did not recognise the FM import parameters---
Note, all those includes of PBO, and FM is in same FG....
Regards,

Hi guys,
Thanks for your input,
Problem solved, actually befoer calling the screen, I set the parameters:
like in my FM I have following code:
DESC_in = DESC.
LAUFZEIT_in = LAUFZEIT.
call screen 0100 STARTING AT 5 5.
Where as desc and laufzeit, are import parametes in the FM and desc_in and laufzeit_in are input fields on screen......
Anyway, thanks for your input..
Regards

Can we call screen from ALV report

Hi All,
I am in the process of creating a stand alone application. However I have stuck up here.
Problem: Can we call any screen from ALV report? If yes then how??? Can anyone give some code snippet??
All your help appreciated.
Thanks,
Jignesh

Hello Jignesh,
Here is an example, when you double click on a line, it pops with with another screen that holds details for the flight information.
CLASS lcl_event_handler DEFINITION.
PUBLIC SECTION.
    METHODS:
    handle_double_click FOR EVENT double_click
                        OF cl_gui_alv_grid
                        IMPORTING e_row
                                  e_column.
   ENDCLASS.                    "lcl_event_handler
CLASS lcl_event_handler IMPLEMENTATION.
METHOD handle_double_click.
    READ TABLE it_flight INTO wa_flight INDEX e_row-index.
    IF sy-subrc EQ 0.
      SELECT * FROM sbook
               INTO TABLE it_book
               WHERE carrid EQ wa_flight-carrid AND
                     connid EQ wa_flight-connid.
      CALL SCREEN 101 STARTING AT 10 10.
    ENDIF.
ENDMETHOD.                 "HANDLE_DOUBLE_CLICK
ENDCLASS.                    "LCL_EVENT_HANDLER
MODULE status_0101 OUTPUT.
Variant to save the layout
gv_repid = sy-repid.
IF g_custom_container2 IS INITIAL.
Create an instance for Custom Container 'ALV_GRID'
    CREATE OBJECT g_custom_container2
           EXPORTING container_name = gs_container2.
Create an instance for ALV Grid
    CREATE OBJECT g_grid2
           EXPORTING i_parent = g_custom_container2.
Variant to save the layout
    gs_layout-grid_title = 'Flight Bookings'.
    CALL METHOD g_grid2->set_table_for_first_display
      EXPORTING
        i_structure_name = 'SBOOK'
        is_layout        = gs_layout
      CHANGING
        it_outtab        = it_book[].
ELSE.
    CALL METHOD g_grid2->refresh_table_display.
ENDIF.                               "IF grid2 IS INITIAL.
Setting focus for created grid control
CALL METHOD cl_gui_control=>set_focus
    EXPORTING
      control = g_grid2.
CALL METHOD cl_gui_cfw=>flush.
ENDMODULE.                 " status_0101 OUTPUT
Refer to BC_ALV_GRID04 for ALV data declarations used in the above piece of code.

F4 on the called screen

Hi,
Ive created a screen in screen painter and its linked to the dictionary field of a ztable. When i call the screen thru a tcode, i can see the F4 help on the fields for which i hav created value tables in their domain.But when i call the same screen from alv list, i cannot see the F4 help that comes automatically from dictionary field.Why is this happening?
Thanks,
Nidhi.

Hi,
I think there is some confusion..Will giv an example.
I have screen no suppose 100.On that screen there is a field username which is linked to dictionary field.That dictionary field has a value table.So when i call screen 100 using a tcode, i get F4 help on the field username.Ive not written any code for this F4 help.Its coming directly from the dictionary field.Now, in the same program i generate an alv list.On that list there is a button. When i click that button, it calls that same screen 100 using syntax call screen <scr number>.I can see that field username on the screen but this time i cannot access F4 help.Why is this happening.
As u told me to mention reftab name and ref fieldname, am already doing that.Still its not working.
Nidhi.

WD navigation - Exiting application back to calling screen.

Hi Gurus,
Simple WD question. I'm developing an "exit" button that would enable the program to navigate back to the calling screen which is either an Iview or a UWL message.
I tried finding snippet, tuts and reference codes but couldn't any.
Is there any API or methods that enable me to retrieve the calling URL of the application? Or do I need a few more steps to generate/retrieve those URLs?
Any gurus kind enough to help? Thanks alot!
Regards,
Jansen

Janson,
Try using Exit plugs to accompolish your requirement.
1. In the Web Dynpro explorer expand the node <WD project> Web Dynpro Components <YourComponent> Component Interface Interface Views <YourComponent>InterfaceView and then double-click on it.
2. Select the tab "Plugs".
3. Add a new outbound plug of type "Exit plug" (Mark checkbox "Exit Plug" in the window that pops up for the New Outbound Plug) and name it as "AppExit" and choose Next.
4. By clicking "New", add a new parameter with name Url (Use exactly the same name Url) of type
String and choose Finish.
Now add the interface view controller usage to the required view from which you have to exit and go back to a URL.
1. Select the Web Dynpro Components <YourComponent> Views <YourView>.
2. Select the Properties tab.
3. Add the required usage of the controller <YourComponent>InterfaceView.
Then, create a button in your view (say "Back") and associate it to the event / action handler.(say, onActionExit).
In the event handler write the code like this:
public void onActionExit(com.sap.tc.webdynpro.progmodel.api.IWDCustomEvent wdEvent)
// controller
wdThis.wdGet<YourComponent>InterfaceViewController()
.wdFirePlugAppExit(<TargerURL>);
Please note that upon exiting, all the involved components will be destroyed automatically by the WD runtime.
All the aforementioned points are available in the standard tutorial
<a href="https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/webdynpro/inter-application-navigation%20in%20web%20dynpro.pdf">Inter-Application-Navigation</a>
You may refer the same for any further assistance.
Bala

Call Screen

Hi ALL,
I have a stmt call screen 100 inside a subroutine.On this screen i have a continue button.When i press the continue button i want the stmts below this call screen 100 stmt and all other subroutines to be executed.I dont want to stop as soon as my call screen is executed.
As this stmt is inside a subroutine, i cannot place all the other subroutines in the PAI of this screen 100 .
Pls suggest.

Hi,
Use it this way:-
Say you have for PAI module code:-
module m_100.
perform sub1.
perform sub2.
perform sub3.
endmodule.
form sub1.
"code
set screen <screen_number>.
"code
endform.
form sub2.
"code
endform.
form sub3.
"code
"code
leave screen.
endform.
This will execute all the code for sub1 and the set screen say 200 and will execute rest code for sub2 and sub3. When statement leave screen is encountered then the control moves to screen 200.
Hope this solves your problem.
Thanks & Regards,
Tarun Gambhir

POPUP_TO_CONFIRM & CALL SCREEN in TRIP t-code of ECC 6.0 and ESS Portal

Similar Messages

Maybe you are looking for