PAGING

[Former Member]

Hi All,

What do the terms "paging in sapgui" and "paging in application server" mean?

[Former Member]

Hi vijay,

1. TAbstrips

2. This concept comes into picture when we use page strips.

3. There are two options : (when there are page strips in a screen)

a) when we select/click a page strip,

PAI should fire

b) when we selcet/click a page strip,

PAI should not fire.

4. In A)

the SAPGUI collects ALL data of all Page strips,

in one single shot,

and hence, the whole data is stored/Paged

on the front-end computer (instead of app server)

5. Reverse is the case in B)

6. To get more information, check out

this link.

<a href="http://help.sap.com/saphelp_nw04/helpdata/en/17/5bf1b52ba211d2954f0000e8353423/content.htm">Paging Link</a>

regards,

amit m.

[ferry_lianto]

Hi Vijay,

<b>Paging in the SAPgui</b>

You need to assign a separate subscreen area to each tab title, and define the function codes of the tab titles with type P (local GUI function). In the screen flow logic, you call all the subscreens in the PBO event. This means that all of the tab pages reside locally on the SAPgui.

When the user chooses a tab title, paging takes place within the SAPgui. In this respect, the tabstrip control behaves like a single screen. In particular, the PAI event is not triggered when the user chooses a tab title, and no data is transported. While this improves the performance of your tabstrip control, it also has the negative effect that when the user does trigger the PAI event, all of the input checks for all of the subscreens are performed. This means that when the user is working on one tab page, the input checks may jump to an unfilled mandatory field on another page.

Local paging at the SAPgui is therefore most appropriate for screens that display data rather than for input screens.

<b>Paging on the Application Server</b>

One subscreen area is shared by all tab titles and called in the PBO event. You define the function codes of the individual tab titles without a special function type. When the user chooses a tab page, the PAI event is triggered, and you must include a module in your flow logic that activates the appropriate tab page and assigns the correct subscreen to the subscreen area.

Since the PAI event is triggered each time the user chooses a tab title, this method is less economical for the application server, but the input checks that are performed only affect the current tab page.

For more information, please check this link.

http://help.sap.com/saphelp_nw04/helpdata/en/17/5bf1b52ba211d2954f0000e8353423/content.htm

Hope this will help.

Regards,

Ferry Lianto

Please reward points if helpful.

[Former Member]

use this link...it'll clarify all ur doubts..

http://help.sap.com/saphelp_webas610/helpdata/en/17/5bf1b52ba211d2954f0000e8353423/content.htm

reward points if it helps

gunjan

[Former Member]

Hi vijay,

check the below links:

help.sap.com/saphelp_nw04/helpdata/ en/17/5bf1b52ba211d2954f0000e8353423/content.htm

help.sap.com/saphelp_nw04/helpdata/ en/17/5bf1b52ba211d2954f0000e8353423/content.htm

help.sap.com/saphelp_nw04/helpdata/ en/c4/3a6f1a505211d189550000e829fbbd/content.htm - 3k

regards,

keerthi.