Include prog

Hi Can we control the include prog with control break statements?
case BUKRS.
when'a'.
include a
when 'b'.
include b.
endcase.

Thanks,
As we know in the generic include is given by SAP in the User exit.
we placed multiple includes in the generic include. we have many plants using the same exits.
when ever there is change for one plant it will affect other plants too. this causing some confusion.
So i want to control them basing on some control satatements.
I know we could do with Sub Routines.. But already we have includes in place so just trying to use the existng cding pattern..
If no other way to hanlde i got to opt for Subroutins..
Hope i am clear...

Similar Messages

Transport request problem with an include prog ... not working

Hello people I am in a predicament here. I have this SAP Enhancment program with a screen and include code
screen:
SAPLITO01080_XUSR1080_SAPLXTOB1000
include:
ZXTOBI01
right now it can be found either in the function grp XTOB or a project made by us (can be found in CMOD).
When I released the Transport Request with both of the above included. The screen SAPLITO01080_XUSR1080_SAPLXTOB1000 was sent to the prd server but the include code ZXTOBI01 didnt. I tried saving and creating a transport while editing it in XTOB and my project (ZPMTECH), and it still wont work. If any of you can give me some help regaring this I would be ever greatful. Thanks guys and take care.

"Try to see the code of your user exit in PROD, it seems the statament INCLUDE ZX...... is missing."
This is in DEV: In the SAP Enhancments ZPMTECH, the thing is here is that my enhancment comes from a screen. So I just add modules and click on the module and created an enhancment. the include code cannot be seen in ZPMTECH but it can be seen in the function XTOB. However in PRD XTOB does not have the include program nor the modules, but has the screen.
"In your request there should be only the include, not function (user-exit)."
That is how I have transporting it, still doesnt work unfortunatley.
Thanks.

How to create a top include for module pool program

hi all..
I want to add my global declarations in one top inlcude.. There are so many other includes in my pgm. But how can i create top include explicitly. Also I have one normal report pgm attached with this module pool.

hi Cynthia ,
there are two ways of creating a top include at your situation ,
1) Insert an include <Prog name >TOP in your mpool program and cut n paste your declarations there .. check if this works ...
2)else .. create another m pool program in SE80 , while creating a pop up will ask for with TOP include ... check mark that and then proceed ..
anything of these two will work ...
Reward if helpful !!
Regards,
Ranjita

Which include i can use instead of PNP LDB

Hi Friends -
Which standard include i can use for PNP LDB ?
am working in abap webdynpro and need to use some macro like rp_provide_from_last but for them we have to use pnp ldb and in abap webdynpro we can't define LDBs so i need the standard Include prog which can fulfill my requirment ..
Pls share your inputs on this.
Regards
Meeta

Hi Txs for your quick turn,
could you pls tell me what is wrong in my this code ,
include DBPNPMAC .
INFOTYPES 0000.
DATA: pnp-sw-found,
pnp-sy-tabix like sy-tabix.
parameters : p_begda like pa0001-begda,
p_endda like pa0001-endda.
START-OF-SELECTION.
RP_PROVIDE_FROM_LAST p0000 space p_begda p_endda .
if PNP-SW-FOUND = 1 .
write : / p0000-pernr,p0000-begda,p0000-endda.
endif.
end-of-selection.
am not getting any output but if i use LDB pnp and get pernr i will get ..
but i cant use LDB pls suggest me what i shd do ?
Regards
Meeta

Changes in STANDARD Prog...

Hi frnds,
i have changed the standard prog or include prog in DEV server. here my doubt is, in PROD server how these changes will go. as of now i am not working on PROD server. i hope, when i transport the request # the changes may go and change the prog in PROD server. am i right?
thanks in advance.
regards,
balu

Hi frnds,
thanks for your response.
i have tried to do using user exist and badi. but those things are not worked fully as per client requirement. for this, i have placed query in SDN forum also. some ppl gave good solutions. u can check my previous queries.
in me21n, i have placed one field (vendor sub range) in header using screen exist. that value should go for item level. i have completed this using badi. but that badi is triggering for whenever user has changed/entered the value in any item. suppose if user forgot to enter the value in header initially and user entered some 100 items and he gave the value for header. in this situation that badi was not working. i mean for 100 items that value not passed. but after entering any item then the header value passed to subsequent items. i found that, badi is calling only whenever user enter/change the value in item.
this is the only reason to change the standard prog.
thanks once again for all.
hi Norman Salter, what is BTEs?
regards,
balu

GETWA_NOT_ASSIGNED - Field symbol has not yet been assigned.

Hi Experts,
I am facing the following dump u201CGETWA_NOT_ASSIGNED u201C, Termination occurred in the ABAP program "SAPLDSVAS_GRAPH" - in u201CSET_EXTREME_VALUES".The main program was "RDSMOP_MAIN ".
In the source code you have the termination point in line 275 of the (Include) program "LDSVAS_GRAPHACI".
Friends I am facing this issue while generating EWA report for R3 server only, Iu2019m able to generate EWA report for other servers like BI, CRM. But while creating EWA report for ERP server Iu2019m getting this dump.
Certain thing I would like to highlight. Recently we did a support pack upgrade, mine is a Solman 7.0 EHP1 system. We update the support pack up to " SPS 6 ".Before the support pack upgrade it was working fine, I was able to generate the EWA report for all my servers.
Do any body face similar kind of problem?
Responses are highly appreciable
Thanks & Regards
Dusmanta

Hi,
Can you please debugg the same code from line 245 of include prog LDSVAS_GRAPHACI.
do me->category_count times. " I think the value of category count is zero.
 lv_index = sy-index + 1.
 write lv_index to lv_fieldname+15 left-justified.
 assign (lv_fieldname) to <lv_value>.
Thanks
Subhankar

How to retrieve data from a CGI to SAP?

Hi guys,
I'm looking for a way to retrieve information from a CGI page into SAP. This CGI generates a XML with the response from the parameters I use on the URL.
I can xsl transform the result into ABAP variables, but first I need to know how to get that information.
As anyone come across this or knows how to do it?
Thanks in advance,
Ricardo

Hi,
In your case, Include prog is part of FM, no need to treat it as an Entity.
Now, Your Answer -
In SCRIPT - IN Page Window -->
 PERFORM GET_MVAT_TIN IN PROGRAM Z_SCRIPT_PERFORMS_ABAPDB3
 USING &VBDKR-KUNRE&
 CHANGING &STCD1&
 CHANGING &STCD2&
 ENDPERFORM
 IF &STCD1& <> ' '
 MVAT Number :</> &STCD1&
 ENDIF
Then go to SE38 --> Creat prog with type - Subroutine pool
In that Write FORM statement for this PERFORM.
FORM get_mvat_tin TABLES inttab STRUCTURE itcsy
 outtab STRUCTURE itcsy.
DATA : v_kunre TYPE kna1-kunnr,
 v_stcd1 TYPE kna1-stcd1,
 v_stcd2 TYPE kna1-stcd2.
LOOP AT outtab.
 CLEAR outtab-value.
 MODIFY outtab.
ENDLOOP.
READ TABLE inttab INDEX 1.
v_kunre = inttab-value.
IF v_kunre CA sy-abcde.
ELSE.
 UNPACK v_kunre TO v_kunre.
ENDIF.
 " Here You can take your Funcion module ***************************
SELECT SINGLE stcd1 stcd2 FROM kna1 INTO (v_stcd1, v_stcd2)
 WHERE kunnr = v_kunre.
IF sy-subrc = 0.
 READ TABLE outtab INDEX 1.
 WRITE v_stcd1 TO outtab-value.
 MODIFY outtab INDEX 1.
 READ TABLE outtab INDEX 2.
 WRITE v_stcd2 TO outtab-value.
 MODIFY outtab INDEX 2.
ENDIF.
ENDFORM.

Creation of Tab Strips control

Hi Guy's,
Please help me How to create the Tacbstript control in Screen painter(SE51) step-by-step procedure.
Thanks,
Sai

Hi,
Very good docu....
Tabstrip Controls
A tabstrip control is a screen object consisting of two or more pages. Each tab page consists of a tab title and a page area. If the area occupied by the tabstrip control is too narrow to display all of the tab titles, a scrollbar appears, allowing you to reach the titles that are not displayed. There is also a pushbutton that allows you to display a list of all tab titles.
Tabstrip controls allow you to place a series of screens belonging to an application on a single screen, and to navigate between them easily. The recommended uses and ergonomic considerations for tabstrip controls are described in the Tabstrip Control section of the SAP Style Guide.
From a technical point of view, a tab page is a subscreen with a pushbutton assigned to it, which is displayed as the tab title.
The tabstrip control is the set of all the tab pages. Tabstrip controls are therefore subject to the same restrictions as subscreens. In particular, you cannot change the GUI status when you switch between pages in the tabstrip control. However, they are fully integrated into the screen environment, so present no problems with batch input.
To use a tabstrip control on a screen, you must be using a SAPgui with Release 4.0 or higher, and its operating system must be Motif, Windows 95, MacOS, or Windows NT with version 3.51 or higher.
When you create a tabstrip control, you must:
Define the tab area on a screen and the tab titles.
Assign a subscreen area to each tab title.
Program the screen flow logic.
Program the ABAP processing logic.
You must then decide whether you want to page through the tabstrip control at the SAPgui or on the application server. In the first case, each tab page has its own subscreen. In the second, there is a single subscreen area that is shared by all tab pages.
Defining the Tabstrip Control Area and Tab Titles
You define both the tabstrip area and the tab titles in the screen layout.
The tabstrip area has a unique name and a position, length, and height. You can also specify whether the tabstrip area can be resized vertically or horizontally when the user resizes the window. If the area supports resizing, you can specify a minimum size for it.
When you define a tabstrip area, it already has two tab titles. Tab titles are technically exactly the same as pushbuttons. To create additional tab titles, simple create pushbuttons in the row containing the tab titles. Tab titles have the same attributes as pushbuttons, that is, each has a name, a text, and a function code. You can also use icons and dynamic texts with tab titles.
Assigning a Subscreen Area to a Tab Title
You must assign a subscreen area to each tab title. There are two ways of doing this:
Paging in the SAPgui
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.
Paging on the Application Server
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.
Procedure in Either Case
You create the subscreen areas within the tabstrip area. You assign the subscreen areas to one or more tab titles in the Screen Painter by selecting one or more titles. You can also assign a subscreen area to a tab title in the tab title attributes by entering the name of the subscreen area in the Reference field attribute.
The procedure for the alphanumeric Screen Painter is described under Creating Tabstrip Controls.
If you are paging at the SAPgui, create a subscreen area for each tab title. If you are paging at the application server, select all tab titles and create a single subscreen area. The subscreen areas may not cover the top line of the tab area. However, within a tab area, more than one subscreen area can overlap.
Programming the Flow Logic
In the flow logic, all you have to do by hand is include the correct subscreens. The screen flow and data transport to the ABAP program is the same as for normal subscreens. There are two ways of programming the screen flow logic, depending on how you have decided to page through the tabstrip control.
Paging in the SAPgui
When you page in the SAPgui, you must include a subscreen for each subscreen area:
PROCESS BEFORE OUTPUT.
CALL SUBSCREEN: <area1> INCLUDING [<prog 1>] <dynp 1>,
 <area2> INCLUDING [<prog 2>] <dynp 2>,
 <area3> INCLUDING [<prog 3>] <dynp 3>,
PROCESS AFTER INPUT.
CALL SUBSCREEN: <area1>,
 <area2>,
 <area3>,
Paging on the Application Server
When you page on the application server, you only have to include a subscreen for the one subscreen area:
PROCESS BEFORE OUTPUT.
CALL SUBSCREEN <area> INCLUDING [<prog>] <dynp>.
PROCESS AFTER INPUT.
CALL SUBSCREEN <area>.
Handling in the ABAP Program
Before you can use a tabstrip control in your ABAP program, you must create a control for each control in the declaration part of your program using the following statement:
CONTROLS <ctrl> TYPE TABSTRIP.
where <ctrl> is the name of the tabstrip area on a screen in the ABAP program. The control allows the ABAP program to work with the tabstrip control. The statement declares a structure with the name <ctrl> . The only component of this structure that you need in your program is called ACTIVETAB.
Use in the PBO event
Before the screen is displayed, you use the control to set the tab page that is currently active. To do this, assign the function code of the corresponding tab title to the component ACTIVETAB:
<ctrl>-ACTIVETAB = <fcode>.
When you page at the SAPgui, you only need to do this once before the screen is displayed. This initializes the tabstrip control. The default active tab page is the first page. After this, the page activated when the user chooses a tab title is set within SAPgui.
When you page on the application server, you must assign the active page both before the screen is displayed for the first time, and each time the user pages. At the same time, you must set the required subscreen screen.
You can suppress a tab page dynamically by setting the ACTIVE field of table SCREEN to 0 for the corresponding tab title.
Use in the PAI event
In the PAI event, ACTIVETAB contains the function code of the last active tab title on the screen.
When you page in the SAPgui, this allows you to find out the page that the user can currently see. When you page at the application server, the active tab page is controlled by the ABAP program anyway.
The OK_CODE field behaves differently according to the paging method:
Paging in the SAPgui
When you page in the SAPgui, the PAI event is not triggered when the user chooses a tab title, and the OK_CODE field is not filled. The OK_CODE field is only filled by user actions in the GUI status or when the user chooses a pushbutton either outside the tabstrip control or on one of the subscreens.
Paging on the application server
If you are paging at the application server, the PAI event is triggered when the user chooses a tab title, and the OK_CODE field is filled with the corresponding function code.
To page through the tabstrip control, you must assign the function code to the ACTIVETAB component of the control:
<ctrl>-ACTIVETAB = <ok_code>.
This statement overwrites the function code of the last active tab page with that of the new tab title. At the same time, you must ensure that the correct subscreen is inserted in the subscreen area.
Otherwise, tabstrip controls are handled like normal subscrens in ABAP programs, that is, the ABAP program of a subscreen screen must contain the dialog modules called from the flow logic of the subscreen.
Examples
Tabstrip control, paging at SAPgui
REPORT DEMO_DYNPRO_TABSTRIP_LOCAL.
CONTROLS MYTABSTRIP TYPE TABSTRIP.
DATA: OK_CODE TYPE SY-UCOMM,
 SAVE_OK TYPE SY-UCOMM.
MYTABSTRIP-ACTIVETAB = 'PUSH2'.
CALL SCREEN 100.
MODULE STATUS_0100 OUTPUT.
SET PF-STATUS 'SCREEN_100'.
ENDMODULE.
MODULE CANCEL INPUT.
LEAVE PROGRAM.
ENDMODULE.
MODULE USER_COMMAND INPUT.
SAVE_OK = OK_CODE.
CLEAR OK_CODE.
IF SAVE_OK = 'OK'.
 MESSAGE I888(SABAPDOCU) WITH 'MYTABSTRIP-ACTIVETAB ='
 MYTABSTRIP-ACTIVETAB.
ENDIF.
ENDMODULE.
The next screen (statically defined) for screen 100 is itself. It has the following layout:
The screen contains a tabstrip area called MYTABSTRIP with three tab titles PUSH1, PUSH2 and PUSH3. The function codes have the same name, and all have the function type P. One of the subscreen areas SUB1 to SUB3 is assigned to each tab title. The pushbutton has the name BUTTON and the function code OK.
In the same ABAP program, there are three subscreen screens 110 to 130. Each of these fits the subscreen area exactly. The layout is:
The screen flow logic for screen 100 is as follows:
PROCESS BEFORE OUTPUT.
MODULE STATUS_0100.
CALL SUBSCREEN: SUB1 INCLUDING SY-REPID '0110',
 SUB2 INCLUDING SY-REPID '0120',
 SUB3 INCLUDING SY-REPID '0130'.
PROCESS AFTER INPUT.
MODULE CANCEL AT EXIT-COMMAND.
CALL SUBSCREEN: SUB1,
 SUB2,
 SUB3.
MODULE USER_COMMAND.
The screen flow logic of subscreens 110 to 130 does not contain any module calls.
When you run the program, a screen appears on which the second tab page is active, since the program sets the ACTIVETAB component of the structure MYTABSTRIP to PUSH2 before the screen is displayed. The user can page through the tabstrip control without the PAI event being triggered. One of the three subscreens is included on each tab page.
When the user chooses Continue, the PAI event is triggered, and an information message displays the function code of the tab title of the page that is currently active.
Tabstrip control with paging on the application server.
REPORT DEMO_DYNPRO_TABSTRIP_LOCAL.
CONTROLS MYTABSTRIP TYPE TABSTRIP.
DATA: OK_CODE TYPE SY-UCOMM,
 SAVE_OK TYPE SY-UCOMM.
DATA NUMBER TYPE SY-DYNNR.
MYTABSTRIP-ACTIVETAB = 'PUSH2'.
NUMBER = '0120'.
CALL SCREEN 100.
MODULE STATUS_0100 OUTPUT.
SET PF-STATUS 'SCREEN_100'.
ENDMODULE.
MODULE CANCEL INPUT.
LEAVE PROGRAM.
ENDMODULE.
MODULE USER_COMMAND INPUT.
SAVE_OK = OK_CODE.
CLEAR OK_CODE.
IF SAVE_OK = 'OK'.
 MESSAGE I888(SABAPDOCU) WITH 'MYTABSTRIP-ACTIVETAB ='
 MYTABSTRIP-ACTIVETAB.
ELSE.
 MYTABSTRIP-ACTIVETAB = SAVE_OK.
 CASE SAVE_OK.
 WHEN 'PUSH1'.
 NUMBER = '0110'.
 WHEN 'PUSH2'.
 NUMBER = '0120'.
 WHEN 'PUSH3'.
 NUMBER = '0130'.
 ENDCASE.
ENDIF.
ENDMODULE.
The statically-defined next screen for screen 100 is itself, and its layout is the same as in the above example. However, the function codes of the three tab titles have the function type <blank> and they all share a single subscreen area SUB.
The same subscreen screens 110 to 130 are defined as in the last example.
The screen flow logic for screen 100 is as follows:
PROCESS BEFORE OUTPUT.
MODULE STATUS_0100.
CALL SUBSCREEN SUB INCLUDING SY-REPID NUMBER.
PROCESS AFTER INPUT.
MODULE CANCEL AT EXIT-COMMAND.
CALL SUBSCREEN SUB.
MODULE USER_COMMAND.
In this example, the program includes a subscreen screen in the subscreen area SUB dynamically during the PBO event.
The screen flow logic of subscreens 110 to 130 does not contain any module calls.
This example has the same function as the previous example, but the paging within the tabstrip control is implemented on the application server. Each time the user chooses a tab title, the function code from the OK_CODE field is assigned to the ACTIVETAB component of structure MYTABSTRIP. At the same time, the variable NUMBER is filled with the screen number of the subscreen that has to be displayed in the subscreen area SUB of the tabstrip control.
Pls. reward if useful...

How to retrieve data from a function module and use it in sap script??

I have a report program, which calls a function module. This function module internally calls an include program. In this program, I have a variable which is to be used in the sap script. How can I send this variable to the sap script

Hi,
In your case, Include prog is part of FM, no need to treat it as an Entity.
Now, Your Answer -
In SCRIPT - IN Page Window -->
 PERFORM GET_MVAT_TIN IN PROGRAM Z_SCRIPT_PERFORMS_ABAPDB3
 USING &VBDKR-KUNRE&
 CHANGING &STCD1&
 CHANGING &STCD2&
 ENDPERFORM
 IF &STCD1& <> ' '
 MVAT Number :</> &STCD1&
 ENDIF
Then go to SE38 --> Creat prog with type - Subroutine pool
In that Write FORM statement for this PERFORM.
FORM get_mvat_tin TABLES inttab STRUCTURE itcsy
 outtab STRUCTURE itcsy.
DATA : v_kunre TYPE kna1-kunnr,
 v_stcd1 TYPE kna1-stcd1,
 v_stcd2 TYPE kna1-stcd2.
LOOP AT outtab.
 CLEAR outtab-value.
 MODIFY outtab.
ENDLOOP.
READ TABLE inttab INDEX 1.
v_kunre = inttab-value.
IF v_kunre CA sy-abcde.
ELSE.
 UNPACK v_kunre TO v_kunre.
ENDIF.
 " Here You can take your Funcion module ***************************
SELECT SINGLE stcd1 stcd2 FROM kna1 INTO (v_stcd1, v_stcd2)
 WHERE kunnr = v_kunre.
IF sy-subrc = 0.
 READ TABLE outtab INDEX 1.
 WRITE v_stcd1 TO outtab-value.
 MODIFY outtab INDEX 1.
 READ TABLE outtab INDEX 2.
 WRITE v_stcd2 TO outtab-value.
 MODIFY outtab INDEX 2.
ENDIF.
ENDFORM.

Pricing messages are not appering in WEB UI?

Hi Team,
Please help me on this.
In GUI crmd_order->sold to party->product's->item's->condition's.
In webui->Account confirmation->create order->item's (add product)->edit the item->Price details assignment block
Here i am createing another pricing condition based some other condition for eg: if the value of the pricicng condition is 4$ and i am adding another condition with value 2$ and click on enter at that i am getting one information(warning)message in popup.
But the same thing when i am doing in WEB UI message is not appering,we need to display same message.
Message details:
Message ID: PRC_PRI
Message number:711
Triggering point:
se38->SAPLPRC_INT
Include prog->lprc_intf02
PLease find the attached imagees for reference.
Please help me on the same.
Thanks,
Narasimha M

Solved using note 1346861.

Steps to create tabstrip for subscreen in selection screen

hi,
can let me know the steps taken to create subscreen in selection screen and put in tabstrip?
i need to have 3 screens. 1000 being the tabstrip, 2000 being first subscreen and 3000 being the second subscreen.
i have the abap code but i do not know the steps to create especially 1000 screen.
for 2000 and 3000, once i activated the program, these 2 screens added but i do not know where can i create the 1000 screen.
also, should i use wizard to create tabstrip?
please advise. thanks
SELECTION-SCREEN BEGIN OF SCREEN 2000 AS SUBSCREEN. SELECTION-SCREEN BEGIN OF BLOCK x WITH FRAME TITLE text-001.
SELECT-OPTIONS: para1 FOR field1 ,
 para2 FOR field2.
SELECTION-SCREEN END OF BLOCK x.
SELECTION-SCREEN END OF SCREEN 2000.
SELECTION-SCREEN BEGIN OF SCREEN 3000 AS SUBSCREEN.
SELECTION-SCREEN BEGIN OF BLOCK y WITH FRAME TITLE text-002.
SELECT-OPTIONS: para3 FOR field3 ,
 para4 FOR field4.
SELECTION-SCREEN END OF BLOCK y.
SELECTION-SCREEN:SKIP.
SELECTION-SCREEN END OF SCREEN 3000.

e_l,
See the total doc.. with example.
Assigning a Subscreen Area to a Tab Title
You must assign a subscreen area to each tab title. There are two ways of doing this:
Paging in the SAPgui
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.
Paging on the Application Server
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.
Procedure in Either Case
You create the subscreen areas within the tabstrip area. You assign the subscreen areas to one or more tab titles in the Screen Painter by selecting one or more titles. You can also assign a subscreen area to a tab title in the tab title attributes by entering the name of the subscreen area in the Reference field attribute.
The procedure for the alphanumeric Screen Painter is described under Creating Tabstrip Controls.
If you are paging at the SAPgui, create a subscreen area for each tab title. If you are paging at the application server, select all tab titles and create a single subscreen area. The subscreen areas may not cover the top line of the tab area. However, within a tab area, more than one subscreen area can overlap.
Programming the Flow Logic
In the flow logic, all you have to do by hand is include the correct subscreens. The screen flow and data transport to the ABAP program is the same as for normal subscreens. There are two ways of programming the screen flow logic, depending on how you have decided to page through the tabstrip control.
Paging in the SAPgui
When you page in the SAPgui, you must include a subscreen for each subscreen area:
PROCESS BEFORE OUTPUT.
CALL SUBSCREEN: <area1> INCLUDING [<prog 1>] <dynp 1>,
 <area2> INCLUDING [<prog 2>] <dynp 2>,
 <area3> INCLUDING [<prog 3>] <dynp 3>,
PROCESS AFTER INPUT.
CALL SUBSCREEN: <area1>,
 <area2>,
 <area3>,
Paging on the Application Server
When you page on the application server, you only have to include a subscreen for the one subscreen area:
PROCESS BEFORE OUTPUT.
CALL SUBSCREEN <area> INCLUDING [<prog>] <dynp>.
PROCESS AFTER INPUT.
CALL SUBSCREEN <area>.
Handling in the ABAP Program
Before you can use a tabstrip control in your ABAP program, you must create a control for each control in the declaration part of your program using the following statement:
CONTROLS <ctrl> TYPE TABSTRIP.
where <ctrl> is the name of the tabstrip area on a screen in the ABAP program. The control allows the ABAP program to work with the tabstrip control. The statement declares a structure with the name <ctrl> . The only component of this structure that you need in your program is called ACTIVETAB.
Use in the PBO event
Before the screen is displayed, you use the control to set the tab page that is currently active. To do this, assign the function code of the corresponding tab title to the component ACTIVETAB:
<ctrl>-ACTIVETAB = <fcode>.
When you page at the SAPgui, you only need to do this once before the screen is displayed. This initializes the tabstrip control. The default active tab page is the first page. After this, the page activated when the user chooses a tab title is set within SAPgui.
When you page on the application server, you must assign the active page both before the screen is displayed for the first time, and each time the user pages. At the same time, you must set the required subscreen screen.
You can suppress a tab page dynamically by setting the ACTIVE field of table SCREEN to 0 for the corresponding tab title.
Use in the PAI event
In the PAI event, ACTIVETAB contains the function code of the last active tab title on the screen.
When you page in the SAPgui, this allows you to find out the page that the user can currently see. When you page at the application server, the active tab page is controlled by the ABAP program anyway.
The OK_CODE field behaves differently according to the paging method:
Paging in the SAPgui
When you page in the SAPgui, the PAI event is not triggered when the user chooses a tab title, and the OK_CODE field is not filled. The OK_CODE field is only filled by user actions in the GUI status or when the user chooses a pushbutton either outside the tabstrip control or on one of the subscreens.
Paging on the application server
If you are paging at the application server, the PAI event is triggered when the user chooses a tab title, and the OK_CODE field is filled with the corresponding function code.
To page through the tabstrip control, you must assign the function code to the ACTIVETAB component of the control:
<ctrl>-ACTIVETAB = <ok_code>.
This statement overwrites the function code of the last active tab page with that of the new tab title. At the same time, you must ensure that the correct subscreen is inserted in the subscreen area.
Otherwise, tabstrip controls are handled like normal subscrens in ABAP programs, that is, the ABAP program of a subscreen screen must contain the dialog modules called from the flow logic of the subscreen.
Examples
Tabstrip control, paging at SAPgui
REPORT DEMO_DYNPRO_TABSTRIP_LOCAL.
CONTROLS MYTABSTRIP TYPE TABSTRIP.
DATA: OK_CODE TYPE SY-UCOMM,
 SAVE_OK TYPE SY-UCOMM.
MYTABSTRIP-ACTIVETAB = 'PUSH2'.
CALL SCREEN 100.
MODULE STATUS_0100 OUTPUT.
SET PF-STATUS 'SCREEN_100'.
ENDMODULE.
MODULE CANCEL INPUT.
LEAVE PROGRAM.
ENDMODULE.
MODULE USER_COMMAND INPUT.
SAVE_OK = OK_CODE.
CLEAR OK_CODE.
IF SAVE_OK = 'OK'.
 MESSAGE I888(SABAPDOCU) WITH 'MYTABSTRIP-ACTIVETAB ='
 MYTABSTRIP-ACTIVETAB.
ENDIF.
ENDMODULE.
The next screen (statically defined) for screen 100 is itself. It has the following layout:
The screen contains a tabstrip area called MYTABSTRIP with three tab titles PUSH1, PUSH2 and PUSH3. The function codes have the same name, and all have the function type P. One of the subscreen areas SUB1 to SUB3 is assigned to each tab title. The pushbutton has the name BUTTON and the function code OK.
In the same ABAP program, there are three subscreen screens 110 to 130. Each of these fits the subscreen area exactly. The layout is:
The screen flow logic for screen 100 is as follows:
PROCESS BEFORE OUTPUT.
MODULE STATUS_0100.
CALL SUBSCREEN: SUB1 INCLUDING SY-REPID '0110',
 SUB2 INCLUDING SY-REPID '0120',
 SUB3 INCLUDING SY-REPID '0130'.
PROCESS AFTER INPUT.
MODULE CANCEL AT EXIT-COMMAND.
CALL SUBSCREEN: SUB1,
 SUB2,
 SUB3.
MODULE USER_COMMAND.
The screen flow logic of subscreens 110 to 130 does not contain any module calls.
When you run the program, a screen appears on which the second tab page is active, since the program sets the ACTIVETAB component of the structure MYTABSTRIP to PUSH2 before the screen is displayed. The user can page through the tabstrip control without the PAI event being triggered. One of the three subscreens is included on each tab page.
When the user chooses Continue, the PAI event is triggered, and an information message displays the function code of the tab title of the page that is currently active.
Tabstrip control with paging on the application server.
REPORT DEMO_DYNPRO_TABSTRIP_LOCAL.
CONTROLS MYTABSTRIP TYPE TABSTRIP.
DATA: OK_CODE TYPE SY-UCOMM,
 SAVE_OK TYPE SY-UCOMM.
DATA NUMBER TYPE SY-DYNNR.
MYTABSTRIP-ACTIVETAB = 'PUSH2'.
NUMBER = '0120'.
CALL SCREEN 100.
MODULE STATUS_0100 OUTPUT.
SET PF-STATUS 'SCREEN_100'.
ENDMODULE.
MODULE CANCEL INPUT.
LEAVE PROGRAM.
ENDMODULE.
MODULE USER_COMMAND INPUT.
SAVE_OK = OK_CODE.
CLEAR OK_CODE.
IF SAVE_OK = 'OK'.
 MESSAGE I888(SABAPDOCU) WITH 'MYTABSTRIP-ACTIVETAB ='
 MYTABSTRIP-ACTIVETAB.
ELSE.
 MYTABSTRIP-ACTIVETAB = SAVE_OK.
 CASE SAVE_OK.
 WHEN 'PUSH1'.
 NUMBER = '0110'.
 WHEN 'PUSH2'.
 NUMBER = '0120'.
 WHEN 'PUSH3'.
 NUMBER = '0130'.
 ENDCASE.
ENDIF.
ENDMODULE.
The statically-defined next screen for screen 100 is itself, and its layout is the same as in the above example. However, the function codes of the three tab titles have the function type <blank> and they all share a single subscreen area SUB.
The same subscreen screens 110 to 130 are defined as in the last example.
The screen flow logic for screen 100 is as follows:
PROCESS BEFORE OUTPUT.
MODULE STATUS_0100.
CALL SUBSCREEN SUB INCLUDING SY-REPID NUMBER.
PROCESS AFTER INPUT.
MODULE CANCEL AT EXIT-COMMAND.
CALL SUBSCREEN SUB.
MODULE USER_COMMAND.
In this example, the program includes a subscreen screen in the subscreen area SUB dynamically during the PBO event.
The screen flow logic of subscreens 110 to 130 does not contain any module calls.
This example has the same function as the previous example, but the paging within the tabstrip control is implemented on the application server. Each time the user chooses a tab title, the function code from the OK_CODE field is assigned to the ACTIVETAB component of structure MYTABSTRIP. At the same time, the variable NUMBER is filled with the screen number of the subscreen that has to be displayed in the subscreen area SUB of the tabstrip control
Pls. reward if useful

ALV Display on ME2N

Hi!
I'd like to ask if you can help me with my ALV display like the one in transaction code ME2N. I have difficulty setting up the part on the Purchasing Document field where there is a button on the upper-left side of the table view that can extract or retract the values under the PO document number. What would be the setup for this in ALV Fieldcat?
Rewarding Points will be given accordingly
Many Thanks!

U have to Change All Include Prog. ref. in this Program like
INCLUDE
FM06LT01
FM06LCS1
FM06LCS2
FM06LCS3
FM06LCS4
FM06LCEK
FM06LCEK_01
FM06LCEK_02
FM06LCEK_03

Can we call sceen of one program into another?

Hi ABAPers,
I wish to know whether, is it possible to call the screen of one program through another program? I know, calling a subroutine of a program from another is possible but i want to know whether calling screen of one program from another is possible or not?
Also if its possible then how?
Regards,
Sonu.

Hi,
We can call the subscreens ...
CALL SUBSCREEN <area> INCLUDING [<prog>] <dynnr>.
The screen of a subscreen that you call is placed in the subscreen area <area> on the main screen.
If you do not specify a program <prog>, the system uses a screen from the current ABAP program. If you do specify a program <prog>, the system uses a screen from the program <prog> for the subscreen. This program is treated in the same way as an external subroutine call. In other words, it is loaded into the program group of the calling program, or, if it is a function group, as its own program group in the same internal session as the calling ABAP program.
Regards
Sudheer

Regd: User Exists

Hi All,
Is there any User Exists for modifying
1. Customer Master (SD Modlue based)
2. Payment Terms (SD Modlue based)
3. Delivery Location (SD Modlue based)
4. Pricing List (SD Modlue based)
5. Sales Tax (SD Modlue based)
And the process to work with those userexits. Pls.
Help and suggestion will be much appreciated.
Thanks.
Ganesh.

Hi,
Can u tell me the specific Userexits in the Include Prog MV45AFZZ which i should modify to get the results for
1. Customer Master (SD Modlue based)
2. Payment Terms (SD Modlue based)
3. Delivery Location (SD Modlue based)
4. Pricing List (SD Modlue based)
5. Sales Tax (SD Modlue based)
Pls so suggest me.
Thanks.
Ganesh.

Passing itab in a perform statement

Hi Experts,
In a Fucn Module, I need to write a perform statement and the corresponding FORM lies in an include. I need to pass an internal table(itab) & workarea(wa_itab) in perform as below :
Declaration of itab:
types: BEGIN OF ty_out1,
 f1(16) TYPE c,
 f2 TYPE wrbtr,
 END OF ty_out1.
data : itab type standard table of ty_out1,
 wa_itab type ty_out1,
PERFORM <form name> tables itab
USING wa_itab
test1.
Dbl click on above perform takes us to an include prog and the form is declared as below -
what should be the syntax of the FORM in INCLUDE statement.
Note: I should not use the top include of the main prog for any declarations.
form search_slash tables ptab2 like itab
 using wa2_itab like wa_itab
 test2 .
Now what should be the syntax of the form above? Is the above right?
Please suggest
Thanks
Dan

Hi,
If you want to pass only the internal table with header line,
then use tables ptab2 structure wa2_itab
For internal table with header line use:
tables ptab2 like wa2_itab
or
tables ptab2[ ] like wa2_itab.
Hope this helps.
Reward if helpful.
Regards,
Sipra

Include prog

Similar Messages

Maybe you are looking for