s10nextscreen( )
Function Sets the next screen to be processed
Example s10nextscreen( "change_order" ).
Format data:
  myscreenid type string,
  mytabid type string.

  s10nextscreen(
    exporting
      screenid = myscreenid
      tabid = mytabid ).
Parameters
Name Type Description
screenid string
Screen id (HTML file)
tabid string
Tab id
Description With the method s10nextscreen() you determine the next screen to be displayed. At the same time, the current ABAP object becomes the active dialogue object.

Example:
s10nextscreen'main').

The path of the HTML file to be displayed is formed as follows: The value of the parameter "screenid" is combined with the name of the S10 class to form a file name, in the format "classname.screenid.html". For example, with screenid = "main" and classname "customer" the file name

"customer.main.html" is created.

This file is now saved in the project path under

classes/[classname]/views.[XX]/[filename]

where XX is the two-digit language key. In the example above and language German this would be

classes/customer/views.de/customer.main.html

If the file is not found in this way within the project, a second access is made in the MIME repository in the path

sap/bc/bsp/[namespace]/public/classes/[classname]/views.[XX]/[filename].

For example, for a class "/s10/customer":

sap/bc/bsp/s10/public/classes/customer/views.en/customer.main.html

This allows HTML files for global classes to be stored independently of the project.
Specifying the next screen is especially necessary in the logon method to determine the first screen to be displayed.

Please note that the ABAP object that calls s10nextscreen() always becomes the active dialogue object. Therefore, the calls

s10nextscreen'main').

and

mycustomer->s10nextscreen
'main').  

have different meanings: In the first case, the current object "me" becomes the active dialogue object, whereas in the second, "mycustomer".


While the next screen is carried out in a call mode by calling s10dialog(), s10nextscreen() merely sets the next screen to be processed following the current dialogue step. Processing thus continues after s10nextscreen() and can be overwritten by a s10nextscreen() still following in the same step.

If the application is already in a call mode when s10nextscreen() is called by a previously executed s10dialog(), s10nextscreen() remains at the current call level. Only through s10exitdialog() is the call mode ended and the next lower level processed.

By specifying the parameter "tabid" in s10nextscreen(), you can dynamically determine the active tab if a "tabstrip" is defined in the HTML page.

Example:
s10nextscreen
screenid 'contact'  tabid 'tabaddress' ).

HTML

<table class="tabstrip">
   
<tr>
         ...
        <td id="tabaddress" class="tab" onclick="S10ActivateTab(this);">
            Address
       
</td>
        ...
   
</tr>
</table>

 

Components S10 Framework