What is the diffrence of 'call screen 100' and 'leave to screen 100'

Thank u

hi,
You can insert a screen sequence. This adds another layer to a stack.
You insert a screen sequence using the CALL SCREEN <nnnn> statement.
Note: Layers created in this way must be removed afterwards. You can do this by setting the next screen
statically or dynamically to the initial value (0) an the end of the inserted screen sequence.
To interrupt processing of the current screen and branch to a new screen (or sequence of screens), use
the CALL SCREEN <nnnn> statement. The screen <nnnn> must belong to the same program.
In the program, the system constructs a stack. The stack has to be destroyed before the end of the
program.
To return to the statement following the CALL SCREEN statement, you can use either SET SCREEN 0.
LEAVE SCREEN. or LEAVE TO SCREEN 0. The screen that called the other screen is then processed
further.
If you use the above statements outside a call chain, the program terminates, and control returns to the
point from which it was called. You can also terminate a program using the ABAP statement LEAVE
PROGRAM.
To interrupt processing of the current screen and branch to a new screen (or sequence of screens), use
the CALL SCREEN <nnnn> statement. The screen <nnnn> must belong to the same program.
In the program, the system constructs a stack. The stack has to be destroyed before the end of the program.
To return to the statement following the CALL SCREEN statement, you can use either SET SCREEN 0.
LEAVE SCREEN. or LEAVE TO SCREEN 0. The screen that called the other screen is then processed
further.
To specify the next screen and leave the current screen in a single step, use the LEAVE TO SCREEN <nnnn> statement.
Hope this helps, DO reward.
Edited by: Runal Singh on Apr 3, 2008 3:11 PM

Similar Messages

What is the diffrence between My Runnable Interface and Java Runnable

Hi folks
all we know that interfaces in java just a decleration for methods and variables.
so my Question is why when i create an interface its name is "Runnable" and i declared a method called "run" inside it.then when i implements this interface with any class don't do the thread operation but when i implement the java.lang.Runnable the thread is going fine.
so what is the diffrence between My Runnable Interface and Java Runnable?
thnx

Hi folks
all we know that interfaces in java just a decleration
for methods and variables.
so my Question is why when i create an interface its
name is "Runnable" and i declared a method called
"run" inside it.then when i implements this interface
with any class don't do the thread operation but when
i implement the java.lang.Runnable the thread is going
fine.
so what is the diffrence between My Runnable Interface
and Java Runnable?
thnxClasses and interfaces are not identified by just their "name", like Runnable. The actual "name" the compiler uses is java.lang.Runnable. So even if you duplicate the Runnable interface in your own package, it's not the same as far as the compiler is concerned, because it's in a different package.
Try importing both java.util.* and java.awt.* (which both have a class or interface named List), and then try to compile List myList = new ArrayList();

What is the diffrence between package javax.sql and java.sql

Is javax designed for J2EE?
And when to use package javax?

Hi,
What is the diffrence between package javax.sql and java.sql?The JDBC 2.0 & above API is comprised of two packages:
1.The java.sql package and
2.The javax.sql package.
java.sql provides features mostly related to client
side database functionalities where as the javax.sql
package, which adds server-side capabilities.
You automatically get both packages when you download the JavaTM 2 Platform, Standard Edition, Version 1.4 (J2SETM) or the JavaTM 2, Platform Enterprise Edition, Version 1.3 (J2EETM).
For further information on this please visit our website at http://java.sun.com/j2se/1.3/docs/guide/jdbc/index.html
Hope this helps.
Good Luck.
Gayam.Srinivasa Reddy
Developer Technical Support
Sun Micro Systems
http://www.sun.com/developers/support/

What is the diffrence between a blanket PO and a Framework order?

What is the diffrence between a blanket PO and a Framework order?

Hi
You have to use document type Frame work order for Blanket PO.
You can use blanket purchase orders to procure consumable materials or services for which it is not worth creating a separate purchase order for each procurement transaction.
Blanket purchase orders are usually valid for a longer period of time. You can directly post the invoices for the materials and services procured for this blanket purchase order.
Raju

What is the diffrence between OMB plus command and OMB command

what is the diffrence between OMB plus command and OMB command?
are they both TCL command?

Hi Alena,
Welcome to SDN.
Check this
EXIT in Loops and Modularization Units
Basic form
EXIT.
Effect
Within a loop structure:
Terminates looop processing (DO, WHILE, LOOP, SELECT).
Within subroutines and other modularization units (but not in a loop structure):
Leaves the subroutine or modularization unit (FORM, MODULE, FUNCTION, TOP-OF-PAGE, END-OF-PAGE).
Outside loop structures and modularization units (report processing):
Terminates report processing and triggers list display.
But not sure about
atexit() .. ,may use in Object Oriented Programming.
(C++)
"At exit-command in module pool."
Mohinder
Edited by: Mohinder Singh Chauhan on Aug 1, 2008 8:06 AM

What is the diffrence between linksys ea4200 v1 and v2?

The title says my message.
what is the diffrence? and why can i not find the ea4200 at the support page and at the buy page.?

Hi there. There's no EA4200 with Cisco just EA4500, EA3500, and EA2700. Perhaps you mean, E4200? There is an E4200 V1 and V2. The main difference apart from hardware version 1 is that the E4200 V2 can be installed or configured via the Classic Userinterface (means logging in to 192.168.1.1) or with the newest Cisco Connect Cloud where you can create an account and from there you can either set it up locally or remotely. . You can check the links below.
http://www6.nohold.net/Cisco2/ukp.aspx?vw=1&docid=7824947fe4444ac3ad5ccb896007e9b8_Getting_to_Know_t...
http://www6.nohold.net/Cisco2/ukp.aspx?vw=1&docid=19d223f0c48c470484a99a28a40f5c6b_Getting_to_know_t...

$.ajax(): what is the difference between calling a transaction and Xacute query?

I can call either:
$.ajax({
     type: "GET",
     url: "/XMII/Illuminator?QueryTemplate=somePathToXacute/someXacute&Content-Type=text/xml&Params...",
     dataType: "xml",
     success: function (result) {...}
$.ajax({
     type: "GET",
     url: "/XMII/Runner?Transaction=somePathToTransaction/someTran&Content-Type=text/xml&Params...&OutputParameter=outXML",
     dataType: "xml",
     success: function (result) {...}
When I call an Xacute query, the first execution works, but the second doesn't. I figured out that I have to add "cache:false" and then it is okay. If I use a transaction instead of Xacute query, it works with or without cache. Why is that? Transactions are not cached? Only Xacute queries?
What is the cost difference in time if I call directly a transaction, instead of an Xacute query? What is the advantage to call an Xacute at all?
Thx

Hi Tibor,
These points should clarify your doubts:
1. Transactions are not cached but queries are.
2. Advantage of using Xacute query is that the Illuminator service used to call Xacute query supports JSON from MII 14.0. Use content-type as text/json in the URL. But the restriction is that the transaction should return the XML in MII Rowsets-Rowset format.
3. Though both the calls would take almost time(I think) but you should call transaction directly( no need to wrap it with Xacute query if not required).
Regards,
Rohit Negi.

WHAT IS THE DIFFRENCE BET WENN PLANNED DEPRECIATION AND UNPLANNED DEPRECIAT

WHAT IS THE DIFFERENCE BETWEEN PLANNED DEPRECIATION AND UNPLANNED DEPRECIATION

Hi
Usually depreciatio is planned for all the assets from the date of purchase of the asset based on cost of asset, useful life of asset, scrap value , etc.
In Planned depreciation we depreciate the asset as per our planned figures for the entire life of the asset
where as in unplanned depreciation, depreciation is not as per our planned figures, it may vary due to fire, theft, partial damage, etc.
Here not only the depreciation amount but also the useful life of the asset will be effected.
Assign points if useful

What's the diffrence between hdr-cx000/b and hdr-cx900e?

I am not from the US but I am browsing the product specification of the hdr-cx900 and I just noticed that there are 2 specific models and I don't know what are the difference between the 2. I have dealt with the sony's customer service here in my country and they seem not to know the difference.

Do you mean the CX900/b and the CX900e?If I looked at the specs right the CX900/b is an NTSC camcorder and the CX900e is a PAL camcorder. Sony CX900/b: http://store.sony.com/hd-camcorder-with-1-sensor-zid27-HDRCX900/B/cat-27-catid-All-Handycam-Camcorders Sony CX900e: http://www.sony.co.uk/electronics/handycam-camcorders/hdr-cx900e/specifications

What is the diffrence between "Key to Select" and "Selected Key" while creating Radio Buttons?

While creating radio buttons there is a confusion regarding two properties "Key to Select" and "Selected Key".Can anybody explain it with example?
Thanks,
Vimal

Hi Vimal,
Please find my explanation as below
Key to Select: This is the unique key for each radio button to identify which one is selected
Selected Key: This holds the "KEY" of selected radio button
Example:
   Let us say we have 2 radio buttons : Male & Female
     Create a context attribute SELECTED_KEY of type STRING.
     Create an action ON_SELECT for radio button select event
     Now,
     the properties for "MALE" radio button as below
          KEY_TO_SELECT = 'M'
          SELECTED_KEY = "bind to the context attribute SELECTED_KEY
          OnSelect = 'ON_SELECT'.
     The properties for 'Female" radio button as below
          KEY_TO_SELECT = 'F'
          SELECTED_KEY = "bind to the context attribute SELECTED_KEY
          OnSelect = 'ON_SELECT'.
If we select radio button 'Male', we get the key as 'M' and for 'Female' radio button 'F'.
check inside the event handler method ONACTIONON_SELECT, you get the 'KEY' of selected radio button.
So, the context attribute 'SELECTED_KEY' gets filled with the key of selected radio button
Hope this helps you in distinguishing the 'KEY TO SELECT' & 'SELECTED KEY' .
Regards,
Rama

What's The Diffrence between ipod touch 2g and ipod touch 3g

I got my ipod touch and i can't tell if it's a 2g or 3g. Can someone tell me the differences or where i can find out.

If you got an 8GB model it's a 2nd generation. Use this article to determine the model.
http://support.apple.com/kb/ht1353
Regards
Andy

What is the Diffrence between Adaptive and Webi Job Server

Hello,
What is the diffrence between Adaptive Job server and Webi Job server?
In my BO server we didn't have Webi Job server but we are able to schedule the webi reports successfully.
Any Idea on this.
Thanks,
Nimesh.

I believe the Adaptive Job Server is on a generic shell server that behave as a Webi Job Server when it processes webi reports, as a program job server when it processes program object etc.

What is the procedure for calling three screens in order?

Hi friends,
Can anyone solve my problem of knowing how to call three screens.
In one screen i will be give say emp-id and password
it has to go to next screen have 2 radiobuttons functional and technical after selecting it has to go next screen where employee name timein and timeout will be there where i have to store employee name and timein and out in a table please its urgent can any one help with this. Creation of screens are perfect but only calling the screens in order and storing the data in a table is my problem.
Solutions will be surely rewarded.

hi,
screens can be called by any one of the following methods:
1.using a t-code
2.from abap program
if ur calling it from abap program, make use of CALL SCREEN
syntax:
CALL SCREEN <dynnr>.
statement to call a screen and its subsequent sequence within that program. The flow logic of each screen calls dialog modules in the program that called the screen.
When the screen sequence ends, control returns to the statement after the original CALL SCREEN statement.
To termintate the screen sequence, use LEAVE TO SCREEN.
These statements exit the current screen and call the defined next screen. If the next screen is screen 0, the entire screen sequence concludes.
please rewards points if useful.
regards
sandhya

What is the diffrence between sap events and application events

Hi all,
what is the diffrence between sap events and application events.Can any one tell me with examples.
regards,

Hi,
Look at this,
<b>System Events (Default)</b>
The event is passed to the application server, but does not trigger the PAI. If you have registered an event handler method in your ABAP program for the event (using the SET HANDLER statement), this method is executed on the application server.
Within the event handler method, you can use the static method SET_NEW_OK_CODE of the global class CL_GUI_CFW to set a function code and trigger the PAI event yourself. After the PAI has been processed, the PBO event of the next screen is triggered.
The advantage of using this technique is that the event handler method is executed automatically and there are no conflicts with the automatic input checks associated with the screen. The disadvantage is that the contents of the screen fields are not transported to the program, which means that obsolete values could appear on the next screen. You can work around this by using the SET_NEW_OK_CODE method to trigger field transport and the PAI event after the event handler has finished.
<b>Application Events</b>
The event is passed to the application server, and triggers the PAI. The function code that you pass contains an internal identifier. You do not have to evaluate this in your ABAP program. Instead, if you want to handle the event, you must include a method call in a PAI dialog module for the static method DISPATCH of the global class CL_GUI_CFW. If you have defined an event handler method in your ABAP program for the event (using the SET HANDLER statement), the DISPATCH method calls it. After the event handler has been processed, control returns to the PAI event after the DISPATCH statement and PAI processing continues.
The advantage of this is that you can specify yourself the point at which the event is handled, and the contents of the screen fields are transported to the application server beforehand. The disadvantage is that this kind of event handling can lead to conflicts with the automatic input checks on the screen, causing events to be lost.
Hope u understood.
Thanks&Regards,
Ruthra.R

What are the parameters in Call transaction method?

Hi ABAPER'S,
Please give me what are the parameters in call transaction method?
Thanks,
Prakash

Processing batch input data with CALL TRANSACTION USING is the faster of the two recommended data transfer methods. In this method, legacy data is processed inline in your data transfer program.
Syntax:
CALL TRANSACTION <tcode>
USING <bdc_tab>
MODE <mode>
UPDATE <update>
<tcode> : Transaction code
<bdc_tab> : Internal table of structure BDCDATA.
<mode> : Display mode:
A
Display all
E
Display errors only
N
No display
<update> : Update mode:
S
Synchronous
A
Asynchronous
L
Local update
A program that uses CALL TRANSACTION USING to process legacy data should execute the following steps:
Prepare a BDCDATA structure for the transaction that you wish to run.
With a CALL TRANSACTION USING statement, call the transaction and prepare the BDCDATA structure. For example:
CALL TRANSACTION 'TFCA' USING BDCDATA
MODE 'A'
UPDATE 'S'.
MESSAGES INTO MESSTAB.
IF SY-SUBRC <> 0.
<Error_handling>.
ENDIF.
The MODE Parameter
You can use the MODE parameter to specify whether data transfer processing should be displayed as it happens. You can choose between three modes:
A Display all. All screens and the data that goes in them appear when you run your program.
N No display. All screens are processed invisibly, regardless of whether there are errors or not. Control returns to your program as soon as transaction processing is finished.
E Display errors only. The transaction goes into display mode as soon as an error in one of the screens is detected. You can then correct the error.
The display modes are the same as those that are available for processing batch input sessions.
The UPDATE Parameter
You use the UPDATE parameter to specify how updates produced by a transaction should be processed. You can select between these modes:
A Asynchronous updating. In this mode, the called transaction does not wait for any updates it produces to be completed. It simply passes the updates to the SAP update service. Asynchronous processing therefore usually results in faster execution of your data transfer program.
Asynchronous processing is NOT recommended for processing any larger amount of data. This is because the called transaction receives no completion message from the update module in asynchronous updating. The calling data transfer program, in turn, cannot determine whether a called transaction ended with a successful update of the database or not.
If you use asynchronous updating, then you will need to use the update management facility (Transaction SM12) to check whether updates have been terminated abnormally during session processing. Error analysis and recovery is less convenient than with synchronous updating.
S Synchronous updating. In this mode, the called transaction waits for any updates that it produces to be completed. Execution is slower than with asynchronous updating because called transactions wait for updating to be completed. However, the called transaction is able to return any update error message that occurs to your program. It is much easier for you to analyze and recover from errors.
L Local updating. If you update data locally, the update of the database will not be processed in a separate process, but in the process of the calling program. (See the ABAP keyword documentation on SET UPDATE TASK LOCAL for more information.)
The MESSAGES Parameter
The MESSAGES specification indicates that all system messages issued during a CALL TRANSACTION USING are written into the internal table <MESSTAB> . The internal table must have the structure BDCMSGCOLL .
You can record the messages issued by Transaction TFCA in table MESSTAB with the following coding:
(This example uses a flight connection that does not exist to trigger an error in the transaction.)
DATA: BEGIN OF BDCDATA OCCURS 100.
INCLUDE STRUCTURE BDCDATA.
DATA: END OF BDCDATA.
DATA: BEGIN OF MESSTAB OCCURS 10.
INCLUDE STRUCTURE BDCMSGCOLL.
DATA: END OF MESSTAB.
BDCDATA-PROGRAM = 'SAPMTFCA'.
BDCDATA-DYNPRO = '0100'.
BDCDATA-DYNBEGIN = 'X'.
APPEND BDCDATA.
CLEAR BDCDATA.
BDCDATA-FNAM = 'SFLIGHT-CARRID'.
BDCDATA-FVAL = 'XX'.
APPEND BDCDATA.
BDCDATA-FNAM = 'SFLIGHT-CONNID'.
BDCDATA-FVAL = '0400'.
APPEND BDCDATA.
CALL TRANSACTION 'TFCA' USING BDCDATA MODE 'N'
MESSAGES INTO MESSTAB.
LOOP AT MESSTAB.
WRITE: / MESSTAB-TCODE,
MESSTAB-DYNAME,
MESSTAB-DYNUMB,
MESSTAB-MSGTYP,
MESSTAB-MSGSPRA,
MESSTAB-MSGID,
MESSTAB-MSGNR.
ENDLOOP.
The following figures show the return codes from CALL TRANSACTION USING and the system fields that contain message information from the called transaction. As the return code chart shows, return codes above 1000 are reserved for data transfer. If you use the MESSAGES INTO <table> option, then you do not need to query the system fields shown below; their contents are automatically written into the message table. You can loop over the message table to write out any messages that were entered into it.
Return codes:
Value
Explanation
0
Successful
<=1000
Error in dialog program
> 1000
Batch input error
System fields:
Name:
Explanation:
SY-MSGID
Message-ID
SY-MSGTY
Message type (E,I,W,S,A,X)
SY-MSGNO
Message number
SY-MSGV1
Message variable 1
SY-MSGV2
Message variable 2
SY-MSGV3
Message variable 3
SY-MSGV4
Message variable 4
Error Analysis and Restart Capability
Unlike batch input methods using sessions, CALL TRANSACTION USING processing does not provide any special handling for incorrect transactions. There is no restart capability for transactions that contain errors or produce update failures.
You can handle incorrect transactions by using update mode S (synchronous updating) and checking the return code from CALL TRANSACTION USING. If the return code is anything other than 0, then you should do the following:
write out or save the message table
use the BDCDATA table that you generated for the CALL TRANSACTION USING to generate a batch input session for the faulty transaction. You can then analyze the faulty transaction and correct the error using the tools provided in the batch input management facility.

What is the diffrence of 'call screen 100' and 'leave to screen 100'

Similar Messages

Maybe you are looking for