Screen 2000 of SAPLBBP_SOCO_UI_ITS

Hello,
I have deleted the screen 2000 of SAPLBBP_SOCO_UI_ITS by mistake.
It is a test system for upgrade and I do not have access to any other SRM system.
Could anyone download and send me the file for the screen 2000 from an SRM 5.0 (SRM SERVER 5.5).
to download the screen, go to transaction SE51
program SAPLBBP_SOCO_UI_ITS
screen 2000
press "display"
from the menu go to "utilities -- more utilities -- upload/download -- download"
Regards,
Erdem Kocabas
[email protected]

Hi Marcin,
thanks a lot for the file...
When I try to upload the screen from SE51, I get the following error:
> File does not contain a screen
> Message no. 37250
I think we are at different patch levels.
Is there anybody at the package level below?
Regards,
Erdem
My package levels:
SAP_ABA                     700     0011     SAPKA70011
SAP_BASIS     700          0011     SAPKB70011
PI_BASIS                     2005_1_700     0011     SAPKIPYJ7B
ST-PI          2005_1_700     0003     SAPKITLQI3
SAP_BW                     700          0012     SAPKW70012
SAP_AP                     700          0008     SAPKNA7008
SRM_PLUS     550          0008     SAPKIBK008
SRM_SERVER     550          0008     SAPKIBKT08

Similar Messages

Fields missing in Screen 2000 for Infotype 580

Hi,
In PA30, when I go to create or change or display mode for an employee in infotype 580, there are only 4 fields shown. There should actually be over 10 fields in the screen. I checked the layout for the screen 2000 of program MP058000 in SE51 and it had all the fields there. In table T588M there was no entry with the module program name MP058000. I created an entry with this program for screen 2000, and chose the radio button Standard ( The first one) for all the fields that were there and still the screen in PA30 has only 4 fields.
Can anyone please help with this issue?
Additional Info: When i chose create or change for IT0580 in PA30 for an employee, there was a status message saying screen was modified, and that were i got the table name that i've mentioned above.
Thanks & Regards,
Pratheek Bhonsley

Hi Pratheek,
Please check the hiring date of employee to whom you are trying to enter and check the employee who joined before this financial year. If i am right, this info type screens are depends on hiring date of employee, if i am right..
At the same time, Please check the control record period also.
MVR
Edited by: MVRmvr on Jul 19, 2010 7:43 AM

Feature P0002, can not see Gender info on the IT0002 screen 2000.

Hi,
I m new to SAP HR. I need to fill gender information into info type 0002 and found that in the info type 0002, the Gender information is missing from the screen 2000.
Then I checked in the info type screen control (Change Screen Modifications), and have found that there are alternative screen mentained wih Variable key. Few variable keys mentioned are '01', '02', '06', '06KL' and so on. I do not understand the meaning of this. what are the '01', '02', '06', '06KL' are refering to? Whether the screen depends upon particular personnel number or user? I want to know what values (BUKRS, BTRTL,PERSG / or User group/ or MOLGA? ) should be set to '01', '02', '06', '06KL' so that I can view the alternative screen mentioned for these variable keys?
If any one has any idea please help me out.
Thanks,
Rupali

Hi Rupali,
It works like this..
1. Basically your USer Parameters are set to Certain UGR and MOLGA...(TCODE: SU3 / Parameters Tab)
For Example, lets say the UGR is 10 and MOL is 10.
2. Go to TCODE PE03 - Feature P0002 and check the radio button attributes, click display, hit the Struct. button
This will show the Structure name that is being used.. PME04... and the valid fields for decisions...
When you are creating/editing PE03 - Feature P0002.... you can basically base your decisions on any of these fields....
i.e. BUKRS, BTRTL, PERSG, PERSK, MOLGA, TCLAS, USERG... The return value is a Variable Key....(max of 2 chars)..say 11
For you to identify, just take one PERNR for which you are unable to see the Gender field... now click F1 on that field, see the technical parameters and identify which screen is called........say MP000200 / 2010
3. Go to SM30, Table T588M and check for the combination arrived above....i.e. MP000200 / 2010 / 11; double click on it and see if the field is in hidden mode.....
IN YOUR CASE, FIRST CHANGE THE PARAMETER SETTINGS to the MOL, UGR you want to and then test all the above....
Good Luck !!
Kumarpal Jain.

Call screen 2000

Hi,
i have created a new screen 2000 and in the screen i have some parameter which is a user will input a value of the material and in the same screen i need to output a material description based on the material inputted..
Does any body know how to do this?
thank you regards,
mae

Ok.. I have created a small test program which works fine for me, it also updates the description of the material.
REPORT ZTEST_NP.
PARAMETER:
P_WERKS TYPE T001W-WERKS.
*pushbutton select
SELECTION-SCREEN SKIP 1.
SELECTION-SCREEN PUSHBUTTON /30(10) SELECT USER-COMMAND RETR.
SELECTION-SCREEN BEGIN OF SCREEN 2000.
PARAMETERS: P_MATNR TYPE MATNR,
 P_MAKTX TYPE MAKTX.
SELECTION-SCREEN END OF SCREEN 2000.
AT SELECTION-SCREEN.
CASE SY-UCOMM.
 WHEN 'RETR'.
 CALL SELECTION-SCREEN 2000.
ENDCASE.
AT SELECTION-SCREEN ON P_MATNR. " << your field for material
DATA BEGIN OF LNA_DYNPF OCCURS 1.
 INCLUDE STRUCTURE DYNPREAD.
DATA END OF LNA_DYNPF.
SELECT SINGLE MAKTX
 INTO P_MAKTX
 FROM MAKT
 WHERE MATNR = P_MATNR
 AND SPRAS = SY-LANGU.
IF SY-SUBRC = 0.
 LNA_DYNPF-FIELDNAME = 'P_MAKTX'. " field name
 LNA_DYNPF-FIELDVALUE = P_MAKTX. " value
 APPEND LNA_DYNPF.
 CALL FUNCTION 'DYNP_VALUES_UPDATE'
 EXPORTING
 DYNAME = SY-CPROG " your program
 DYNUMB = '2000' " your screen
 TABLES
 DYNPFIELDS = LNA_DYNPF
 EXCEPTIONS
 INVALID_ABAPWORKAREA = 1
 INVALID_DYNPROFIELD = 2
 INVALID_DYNPRONAME = 3
 INVALID_DYNPRONUMMER = 4
 INVALID_REQUEST = 5
 NO_FIELDDESCRIPTION = 6
 UNDEFIND_ERROR = 7
 OTHERS = 8.
ENDIF.
Regards,
Naimesh Patel

Hiding a field in PA30 screen(for inoftype 0001)

Hi All,
I have an requirement that i have to hide a Cost center field in PA30 - for infotype 0001 .
I have maintained v_t588m in SM31 for screen 2000 i have selected the costcenter radiobutton to hide and saved but the changes are not effecting to the PA30 screen
and one more thing again am going and checking to this view the changes are not saved in the view.
Is i have to create new feature for this one ? if created,is have to maintain anything?
Please help on this.
Thanks & Regards,
Anil Kumar.

P0001 Organizational Assignment Infotype (0001): Screen Control Status: Active
5 TCLAS Transaction class for data storage
5 A Master data and time data
5 MOLGA Country Grouping
4 01 Germany
4 07 Canada
4 09 Denmark (DAENEMARK)
 4 10 USA
4 16 South Africa
 4 22 Japan (JAPAN)
 4 23 Sweden (SCHWEDEN)
 4 29 Argentina (ARGENTINA)
 4 34 Indonesia (INDONESIA)
 4 37 Brazil
5 40 India
5 DYNNR Number of the following screen
5 2000
5 3000
5 PERSK (1) Employee Subgroup
5 O
OE
5 otherwise
4 48 Philippines (PHILIPPINES)
 4 otherwise
4 B Applicant data
The Exp Shows for Country India(40) For Dynnr 3000 for Employee Subgroup 0 my Variable is OE.
This is the way U sud search for Variable.
~BiSu
Message was edited by:
 Biswajit Das
Message was edited by:
 Biswajit Das

Make Screen field non editable

Hi All,
We have following requirement in our project:
When entering infotype 1 in any action a check should be made to set default values in Work Contract. If Employee Group =u2019 1u2019, Work Contract u2018ZFu2019 should be set and this value must not be changed. If Employee Group u20181u2019 the Work Contract could be all other values except u2018ZFu2019.
We are using badi HRPAD00INFTY to handle the above requirement. But there is a problem. When we perform an action and go to infotype 1 screen the contract field is populated with correct value and is display only field. Once you press enter on the screen the field becomes an editable field and can be changed by the user. I debugged the program and found that PSYST-NSELC is set as NO (0) in the program MP000130 and is checked if it has a value YES in module p0001 called in PBO of screen 2000 include MP000120. If the value is YES only then BADI is called else not.
Can someone suggest what could be the problem area or any other way to meet the requirement ?
BR Jaideep,
Duplicate Post. Continue here: Screen field not getting editable..
Edited by: kishan P on Sep 9, 2010 2:20 PM

Can you explain how a physical inventory is done in your company., and what problems come up if a wrong date is entered?
In my company we create and print the inventory documents immediatly before counting, and we are making sure, that the volume can be counted, entered and difference posted on the same day.
Further we are setting a posting block in SAP, and of course we make sure that no physical movement happens during the count.
And of course we make sure that everyting what was received or issued prior to the count is already entered in sAP before we start creating the documents.
SAP takes the book inventory in the moment the counted quantity is entered in this case. No matter if the user enters a count date of today or of last week.
But if you close the field (which is not possible with customizing), then you have to make sure that you enter the count on the same day you have counted, because if you would enter the count on the next day, then your counting date would be wrong and you would not have a chance to enter the correct counting date.
And as SAP stores everything what a user enters, it is easy to identy the user who has fooled the system, and then the HR guy should do his job, especially as the physical inventory is in most countries a legal requirement, which has to be done seriously.
don't give authorization to the guys who dont follow your policies.

Cl_gui_alv_grid - I get a blank screen

I seem to be having a problem with my screen. The issue is that I am using cl_gui_alv_grid to display an ALV. However, I call set_table_for_first_display, I get a blank screen. I have verified that I have data in the field cat, outtab, and sort tables. Any ideas?
SCREEN 2000
PROCESS BEFORE OUTPUT.
MODULE status_2000.
MODULE create_fieldcat.
MODULE create_obj.
MODULE call_alv.
PROCESS AFTER INPUT.
module user_command_2000.
module exit at exit-command.
MODULE STATUS_2000 OUTPUT.
SET pf-status '2000'.
SET TITLEBAR '2000'.
ENDMODULE. " STATUS_2000 OUTPUT
*& Module CREATE_FIELDCAT OUTPUT
* text
MODULE CREATE_FIELDCAT OUTPUT.
 CLEAR wa_fieldcat.
 wa_fieldcat-fieldname = 'PSPID'.
 wa_fieldcat-tabname = 'IT_CONTRACT'.
 wa_fieldcat-ref_field = 'PSPID'.
 wa_fieldcat-ref_Table = 'PROJ'.
 wa_fieldcat-KEY = 'X'.
 APPEND wa_fieldcat TO it_fieldcat.
 CLEAR wa_fieldcat.
 wa_fieldcat-fieldname = 'POST1'.
 wa_fieldcat-tabname = 'IT_CONTRACT'.
 wa_fieldcat-ref_field = 'POST1'.
 wa_fieldcat-ref_Table = 'PROJ'.
 wa_fieldcat-KEY = 'X'.
 APPEND wa_fieldcat TO it_fieldcat.
 CLEAR wa_fieldcat.
 wa_fieldcat-fieldname = 'SO_VALUE'.
 wa_fieldcat-coltext = 'Sales Order Value'.
 wa_fieldcat-do_sum = 'X'.
 APPEND wa_fieldcat TO it_fieldcat.
 CLEAR wa_fieldcat.
 wa_fieldcat-fieldname = 'BILLED'.
 wa_fieldcat-coltext = 'Amount Billed'.
 wa_fieldcat-do_sum = 'X'.
 APPEND wa_fieldcat TO it_fieldcat.
 CLEAR wa_fieldcat.
 wa_fieldcat-fieldname = 'NEBTR'.
 wa_fieldcat-coltext = 'Cash Received'.
 wa_fieldcat-do_sum = 'X'.
 APPEND wa_fieldcat TO it_fieldcat.
 CLEAR wa_fieldcat.
 wa_fieldcat-fieldname = 'DMBTR'.
 wa_fieldcat-coltext = 'Retention'.
 wa_fieldcat-do_sum = 'X'.
 APPEND wa_fieldcat TO it_fieldcat.
 CLEAR wa_fieldcat.
 wa_fieldcat-fieldname = 'PERCENT_BILLED'.
 wa_fieldcat-coltext = 'Percent Billed'.
 wa_fieldcat-no_sum = 'X'.
 APPEND wa_fieldcat TO it_fieldcat.
 CLEAR wa_sort.
 wa_sort-spos = '1'.
 wa_sort-fieldname = 'PSPID'.
 wa_sort-SUBTOT = 'X'.
 APPEND wa_sort TO it_sort.
ENDMODULE. " CREATE_FIELDCAT OUTPUT
MODULE CREATE_OBJ OUTPUT.
IF g_custom_container IS INITIAL.
 CREATE object g_custom_container
 EXPORTING
 container_name = 'CCONTAINER'.
 CREATE object grid
 EXPORTING
 i_parent = g_custom_container.
 CREATE object g_handler.
 SET HANDLER g_handler->top_of_page FOR grid.
ENDIF.
ENDMODULE. " CREATE_OBJ OUTPUT
MODULE CALL_ALV OUTPUT.
 CALL METHOD grid->set_table_for_first_display
 EXPORTING
* i_buffer_active =
* i_bypassing_buffer =
* i_consistency_check =
* i_structure_name =
* is_variant =
* i_save =
* i_default = 'X'
* is_layout =
 is_print = wa_print
* it_special_groups =
* it_toolbar_excluding =
* it_hyperlink =
* it_alv_graphics =
* it_except_qinfo =
* ir_salv_adapter =
 CHANGING
 it_outtab = it_contract
 it_fieldcatalog = it_fieldcat
 it_sort = it_sort
* it_filter =
 EXCEPTIONS
 invalid_parameter_combination = 1
 program_error = 2
 too_many_lines = 3
 OTHERS = 4
 IF sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
 ENDIF.
Regards,
Davis
I believe the problem may be that I don't have the container in the attributes list of the screen. I am not sure why it isn't there.

I did, if this is what you mean:
MODULE CREATE_OBJ OUTPUT.
IF g_custom_container IS INITIAL.
 CREATE object g_custom_container
 EXPORTING
 container_name = 'CCONTAINER'.
 CREATE object grid
 EXPORTING
 i_parent = g_custom_container.
 CREATE object g_handler.
 SET HANDLER g_handler->top_of_page FOR grid.
ENDIF.
ENDMODULE. " CREATE_OBJ OUTPUT
Regards,
Davis

Two selection screen problem in one report

i have a two selection screens 1000 & 2000 in single report , which needs to be executed one after the other ,
the problem is when i execute second selection screen(2000) , the cursor is going back to at-selection-screen once again.
but i need to trigger start-of-selection directly after executing second selection screen,
the first selection screen 1000 will be executed with the help of select options..
the sample code is below .
at-selection-screen.
    perform validations.
   call selection screen 2000.
    at selection screen on value request p_adm
start-of-selection.
   main logic

Moderator message - Cross post locked
Rob

In IT0359 how to make one feild as visible in Screen Modification

Hi Experts,
I have one feild in IT0359 which is not visible.I checked in T558M and feild is checked as Standard settings.Still the feild is not visible in infotype. Appreciate your input in this regard.

Hi,
As per the Standard setting, the field will be available in te input screen as per the code. Check the code for the module pool MP035900, screen 2000 for the field, I guess it might be hidden by default in the code.
In case required to over write this hidden propoery of the screen, use the screen exit or make the field as RF (Required Field).
Thanks & Regards, Swapnil Mishra

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

How to change the entry screen for Fast entry

Hi,
My scenario is that I want to allow my user to enter the cost assignment as well for infotype 14, 15 and 2010 in the fast entry. I noticed that there is actually a screen in the module pool mp001400, mp001500 and mp200000 which include those 'cost assignment' fields.
For example, in mp001500, screen 2000 is the standard one while screen 5100 is the one with the 'cost assignment' fields. So I created an entry for mp001500 screen 5100 in table T588M and saved it. However, when I try to use the transaction PA70 to create it0015 records again, it still use the standard screen 2000.
What else I have to do so that when I use PA70, screen 5100 will be called up.
Thanks,
Francis

Hi there. Go into the IMG through transaction SPRO and follow this path:
Personnel management -> Personnel administration -> Customizing procedures -> Infotype Menus -> Set up infotype menu for fast data entry. Then select "screen types for fast data entry" and click the "choose" button. You can now see each infotype that is included in fast entry, the default screen, and the fast data entry screen. We use screen 5100 in certain cases for infotypes 0014 and 0015, so we have two entries in this table for each of those infotypes. Here are the values we have:
infotype, screen control, default value, fast data entry, selection report
0014 (blank) 4000 5000 RPLFST00
0014 01 4100 5100 RPLFST00
0015 (blank) 4000 5000 RPLFST00
0015 01 4100 5100 RPLFST00
We are on ERP2005. I hope this helps.
- April King
Message was edited by:
April King

Include a dialog screen in tabstrip of selection-screen

Hi All,
Could anyone please tell me how to include a dialog screen into selection-screen? We have a normal selection screen for a report but now we need to add some more function and this requires to key in material number in first column and quantity in second column in a tabstrip subscreen(eg. screen 2000) and put current select-options(screen 1000) in another tabstrip to make user easily switch between new filters and previous filters. I've no idea if it's possible to have a dialog screen included in a tabstrip in the selection-screen. So please give me some suggestion. Thanks.
Best Regards,
Jeff

Hi Jeff,
In the selection screen you need to call a custom tab strip that would have two sub-screens 1000 and 2000. It is completely designing of tab strip and its code manipulation.
Did you search for TAB STRIP IN SELECTION-SCREEN ?
This will help you in from start-up designing of tab-strip. It's not possible here in forum to explain all the steps in details.
For your help you can refer the link
[Sub-screen in Tab strip|Tabstrip and Subscreen;
This link gives you a complete idea on Tab strip
[Creating a Tab Strip Control|http://help.sap.com/saphelp_nw04/helpdata/en/04/10f2469e0811d1b4700000e8a52bed/frameset.htm]
Still you can search and find more as per your requirement.

HR Abap - How to grey out infotype 416 'Start' date on screen 2

Hi,
For infotype 416 I want to force the user to enter the Start date on the initial PA30 screen. Therefore I have to grey out the 'Start' Date field that appears in the second screen '2000' when creating a record.
Any ideas on how to do this?
Regards,
Warren.

Hi,
In order to add additional functionality and checks to the PBo & PAI of HR infotypes you need to
implement enhancement 'PBAS0001' using CMOD . Once you
have done this you need to go to the function modules EXIT_SAPFP50M_001 & EXIT_SAPFP50M_002
and create the includes within them i.e. ZXPADU01 and ZXPADU02. You can now enhance the
functionality of HR infotype PBO and PAI by simply adding code to these includes. See
example below:
HR Infotype User exits
Include ZXPADU01 for the PBO module
Incldue ZXPADU02 for the PAI module
*Example code.
CASE innnn-infty. "Infotype?
WHEN '0001'. "infotype 0001
Processing code
WHEN '0008'. "infotype 0008
Processing code.
etc.
WHEN OTHERS.
ENDCASE.
Hope this helps.
Reward if helpful.
Regards,
Sipra

Multiple selection screens with status gui

Hi,
I want to make a report with two selection screens and i should create a status gui for these two.
So, I've tried to do, the following:
* FIRST SCREEN
SELECTION-SCREEN BEGIN OF BLOCK bk WITH FRAME.
PARAMETERS: pa(200) TYPE c.
SELECT-OPTIONS: so FOR sflight-carrid.
SELECTION-SCREEN END OF BLOCK bk.
* /FIRST SCREEN
* SECOND SCREEN
SELECTION-SCREEN BEGIN OF SCREEN 2000.
SELECTION-SCREEN BEGIN OF BLOCK bk1 WITH FRAME.
PARAMETERS: pa2(200) TYPE c.
SELECTION-SCREEN END OF BLOCK bk1.
SELECTION-SCREEN END OF SCREEN 2000.
* /SECOND SCREEN
AT SELECTION-SCREEN OUTPUT.
SET PF-STATUS 'Z_STAT'.
SET TITLEBAR 'COISO'.
AT SELECTION-SCREEN.
IF sy-dynnr EQ '1000'.
 CASE sy-ucomm.
 WHEN 'BACK' OR 'EXIT' OR 'CANC'.
 LEAVE TO SCREEN 0.
 WHEN 'EXECUTAR'.
 CALL SELECTION-SCREEN 2000.
 IF sy-subrc <> 0.
 LEAVE TO SCREEN 1000.
 ENDIF.
 ENDCASE.
The problem is that on the first selection screen i have the status gui that I've created, but when i use CALL SELECTION-SCREEN 2000
the status gui (Z_STAT) is not assigned with the screen 2000.
Is this possible? If yes how, and how can i capture which button on status gui of screen 2000 was clicked, because the field sy-ucomm after the call selection-screen 2000 is not updated?
Regards,
Pedro Bessa

harsh bhalla,
its the same report. with two selection-screens. Can't i have status gui for both of them?
Gurpreet Singh,
I have a selection screen. Not a screen. Can a have a pbo for a selection-screen? or one for each selection-screen?
The table SSCRFIELDS and the field sy-ucomm stays with the value from the first selection-screen.
Regards,
Pedro Bessa

Back on a CALL SELECTION-SCREEN from an ALV

Hi all,
I have created a program with a normal selection-screen (1000).
According to the selected values, when I press "Execute" I go to a next selection-screen (2000) with instruction CALL SELECTION-SCREEN 2000.
Then I display an ALV.
When I press the back button, I want to go back to screen 2000, but actually I go directly to screen 1000.
PARAMETERS : p_choic1 RADIOBUTTON GROUP cho DEFAULT 'X'.
PARAMETERS : p_choic2 RADIOBUTTON GROUP cho.
SELECTION-SCREEN BEGIN OF SCREEN 2000.
PARAMETERS : p_table TYPE char10.
SELECTION-SCREEN END OF SCREEN 2000.
START-OF-SELECTION.
IF NOT p_choic1 IS INITIAL.
    CALL SELECTION-SCREEN 2000.
    PERFORM alv_process.
ENDIF.
Have you got any idea of what I can do to return to screen 2000 from the ALV after pressing Back button ?
Thanks.

Hi,
Follow below sample code...
SELECTION-SCREEN BEGIN OF SCREEN 2000.
PARAMETERS p_mat TYPE matnr.
PARAMETERS p_enam TYPE ernam.
SELECTION-SCREEN END OF SCREEN 2000.
START-OF-SELECTION.
set PF-STATUS 'STATUS'.
WRITE:/ p_mat,
          p_enam.
AT USER-COMMAND.
CASE SY-UCOMM.
WHEN 'S2000'.
      CALL SELECTION-SCREEN 2000.
WHEN 'EXIT'.
      EXIT.
ENDCASE.
Ram.

Screen 2000 of SAPLBBP_SOCO_UI_ITS

Similar Messages

Maybe you are looking for