FEBA selection screen in ECC 6.0

Hi all,
We are migrating from 4.6C to ECC 6.0 and in the FEBA transaction, the initial selection screen looks totally different.
Rather than the "usual" screen starting with the selection fields application, company code, etc., we get a window in which many statement selections can be entered and once we select a statement, the statement is shown.
We do have 2 separate ECC 6.0 test systems and on 1 system FEBA shows the same as we have in 4.6C, but in the second ECC 6.0 test system, FEBA acts as just described. I've looked in the FEBA-view menu as well as customising but without luck.
So getting the "old" FEBA look is apparently possible, but does anyone know how to set it up?
Thanks!
Rene

Do you have the EA-FIN extension set active on the system where FEBA is different? I think that may be the reason.
We've been on ECC 6.0 for 2 years (we upgraded from 4.7). We had been using FEBA prior to the upgrade and did not see any changes with FEBA after the upgrade, however we did not activate EA-FIN as a part of the upgrade. Recently we have activated EA-FIN on our Development system only - and I just found that on that system, when I go into FEBA, I'm automatically re-routed to the new EBS post-processing transaction FEBAN. The FEBAN transaction has the statement selections that you describe. So I'm wondering if on your system where FEBA is different, the EA-FIN extension set is active and you are actually getting routed into FEBAN when you try to access FEBA on that system.
I have not, however, figured out if there is a setting that can be changed to get the "old" FEBA back. It could be that this is SAP's way of forcing companies to start using FEBAN instead of FEBA - and we'll just have to adjust. If you figure out how to get the old FEBA back - let us know!
Regards,
Shannon

Similar Messages

SAP Query selection screen issues after ECC upgrade

Hi all
We have a custom query created and assigned to a custom transaction code, which after upgrade to ECC 6.0 we find that the selection screen layout is different from what was available in 4.6C system.
All the fields required are available.
However, the sequence of the fields on the screen is different from the 4.6C after the upgrade.
Can anyone help identify the issue so that the issue can be resolved?
Thanks
Vinodh S

Hi N_niki
There is no resolution as such.
We had raised a Customer message with SAP and were informed that this was expected as the procedure to execute the reports was changed in ECC when compared to 4.6 (technical changes) and hence this issue shall remain for some queries wherein the old changes need to be brought back using an option in the SAP Query.
Please refer to SAP Note # 723577 which could provide a better explanation for the issue.
Hope this helps.
Thanks
Vinodh Sudhakaran

ECCS : custom characteristics into standard report selection screen

Hello guys,
I have added a custom characteristic which is also a subasignment to the EC-CS module.
This field now appears into the standard report selection screen as expected.
I want to define this field as a mandatory selection field, do you know if this is possible? (exemple of standard report CX34A)
Thank you in advance for your help
best regards
Pascal.

Hi Thereza,
This field is already flaged
I have found the following solution : create a variant and assign it to the standard transcation with transaction SE93..
Best regards

How to create a F4 help for a report selection screen field

hi,
can any one guide me to create F4 help for a field in a selection screen in a report program,plz give me a sample code

hi,
Here are the following ways
1.with the help of match code objects we can create the F4 Functionality for Field.
Syntax is :
PARAMETERS: p_org LIKE t527x-orgeh MATCHCODE OBJECT zorg.
2. One more thing is we can do it with Search Help's also.
3. Even we can do it HELP Views also.
Help Views:
You have to create a help view if a view with outer join is needed as selection method of a search help
The selection method of a search help is either a table or a view. If you have to select data from several tables for the search help, you should generally use a database view as selection method. However, a database view always implements an inner join. If you need a view with outer join for the data selection, you have to use a help view as selection method.
All the tables included in a help view must be linked with foreign keys. Only foreign keys that have certain attributes can be used here. The first table to be inserted in the help view is called the primary table of the help view. The tables added to this primary table with foreign keys are called secondary tables.
The functionality of a help view has changed significantly between Release 3.0 and Release 4.0. In Release 3.0, a help view was automatically displayed for the input help (F4 help) for all the fields that were checked against the primary table of the help view. This is no longer the case in Release 4.0.
As of Release 4.0, you must explicitly create a search help that must be linked with the fields for which it is offered (see Linking Search Helps with Screen Fields ).
Existing help views are automatically migrated to search helps when you upgrade to a release higher than 4.0.
A help view implements an outer join, i.e. all the contents of the primary table of the help view are always displayed. You therefore should not formulate a selection condition for fields in one of the secondary tables of the help view. If records of these secondary tables cannot be read as a result of this selection condition, the contents of the corresponding fields of the secondary table are displayed with initial value.
<REMOVED BY MODERATOR>
Edited by: Alvaro Tejada Galindo on Feb 15, 2008 3:15 PM

Vendor in selection screen of MB5B

Business requirement is - In transaction MB5B (Stock on posting date), when users select Special stock option, Vendor should be available in selection screen. Purpose is to know Vendor consignment stocks on posting date. Does any one have any clue about how to achieve this or any other alternative suggestion to meet this business requirement ?

Hi,
We need stock balance by Vendor as on date and not material documents posted on a date. So, MB51 and MB59 does not help. Thanks for the response.
Edited by: Tushar123 on Feb 10, 2011 6:14 AM

Displaying error message while entering selection screen fields

Moderator message: don't offer points
hi experts...
i generated a report.
in that report, the selection screen fields are plant and material type..
now my rqmt is like this :
if user enters any plant except '8210' in the selection screen, then a pop up should appear like.. enter 8210 plant only, and the cursor should remain in the same screen allowing user to enter correct plant.
and then same with the case of material type also..user should enter 'mcfe' material type only..
im using message classes like this:
if so_bwkey-low ne '8210' or so_bwkey-high ne '8210'.
message i000(zts).
endif.
if so_mtart-low is not initial and so_mtart-high is not initial and so_mtart-low ne 'mcfe'
or so_mtart-high ne 'mcfe'.
message i001(zts).
endif.
with this logic, when i enter plant..it is prompting
1) enter plant 8210 only..
and then when i press enter key it is again prompting
2)enter material type mcfe only..
but iam not entering material type here..
i want to get 2nd error message if and only if i enter material type..
help me regarding this issue..
<<text removed>>
thanks in advance,
harini.
Edited by: Matt on Feb 9, 2009 10:14 AM

Hi,
Use Error type message in SELECTION SCREEN EVENT.It will place the cursor in the relevant Field.
At SELECTION-SCREEN ON SO_BWKEY-Low.
if so_bwkey-low ne '8210' .
message E000(zts).
endif.
At SELECTION-SCREEN ON SO_BWKEY-HIGH.
if so_bwkey-high ne '8210'.
message E000(zts).
endif.
At SELECTION-SCREEN ON so_mtart-LOW.
if so_mtart-low is not initial and so_mtart-low ne 'mcfe' .
message E001(zts).
endif.
At SELECTION-SCREEN ON so_mtart-HIGH.
if so_mtart-high is not initial
and so_mtart-high ne 'mcfe'.
message E001(zts).
endif.
This will resolve the issue..
Regards,
Gurpreet

Issue with tabbed block in selection screen

Hi All,
I have created a report program with the following code.
SELECTION-SCREEN BEGIN OF SCREEN 100 AS SUBSCREEN.
PARAMETERS: p1 TYPE c LENGTH 10.
SELECTION-SCREEN END OF SCREEN 100.
SELECTION-SCREEN BEGIN OF SCREEN 200 AS SUBSCREEN.
PARAMETERS: q1 TYPE c LENGTH 10.
SELECTION-SCREEN END OF SCREEN 200.
SELECTION-SCREEN: BEGIN OF TABBED BLOCK mytab FOR 10 LINES,
 TAB (20) button1 USER-COMMAND push1,
 TAB (20) button2 USER-COMMAND push2,
 END OF BLOCK mytab.
INITIALIZATION.
button1 = 'Selection Screen 1'.
button2 = 'Selection Screen 2'.
mytab-prog = sy-repid.
mytab-dynnr = 0100.
mytab-activetab = 'PUSH1'.
AT SELECTION-SCREEN.
CASE sy-dynnr.
 WHEN 1000.
 CASE sy-ucomm.
 WHEN 'PUSH1'.
 mytab-dynnr = 100.
 WHEN 'PUSH2'.
 mytab-dynnr = 200.
 ENDCASE.
ENDCASE.
Execute the program and click on the second tab-page. Now, click on the 'Execute' button or press F8 (there is no specific functionality coded here).
The issue now is that the first tab-page is displayed, instead of the second tab remaining displayed. I require the navigation to remain within the second tab-page after the EXECUTE button is clicked.
Could someone help me out with this issue?
Regards,
Dinup
Edited by: Dinup Sudhakaran on Feb 18, 2008 1:40 PM

Hi,
Go through below document with example code.
It will help you.
Tabstrip Controls on Selection Screens
As with screens, you can now use tabstrip controls on selection screens. To do this, you must define a tabstrip area and the associated tab pages, and assign a subscreen to the tab pages. You do not have to (indeed, cannot) declare the tabstrip control or program the screen flow logic in your ABAP program, since both are automatically generated.
To define a tabstrip area with tab pages, use the following statements in your selection screen definition:
SELECTION-SCREEN: BEGIN OF TABBED BLOCK <tab_area> FOR <n> LINES,
 TAB (<len>) <tab1> USER-COMMAND <ucom1>
 [DEFAULT [PROGRAM <prog>] SCREEN <scrn>],
 TAB (<len>) <tab2> USER-COMMAND <ucom2>
 [DEFAULT [PROGRAM <prog>] SCREEN <scrn>],
 END OF BLOCK <tab_area>.
This defines a tabstrip control <tab_area> with size <n>. The tab pages <tab1>, <tab2> are assigned to the tab area. <len> defines the width of the tab title. You must assign a function code <ucom> area to each tab title. You can find out the function code from the field SY-UCOMM in the AT SELECTION-SCREEN event.
For each tab title, the system automatically creates a character field in the ABAP program with the same name. Before the selection screen is displayed, you can assign a text to the field. This then appears as the title of the corresponding tab page on the selection screen.
You must assign a subscreen to each tab title. This will be displayed in the tab area when the user chooses that title. You can assign one of the following as a subscreen:
A subscreen screen defined using the Screen Painter.
A selection screen subscreen, defined in an ABAP program.
You can make the assignment either statically in the program or dynamically at runtime. If, at runtime, one of the tab titles has no subscreen assigned, a runtime error occurs.
Static assignment
Use the DEFAULT addition when you define the tab title. You can specify an ABAP program and one of its subscreens. If you do not specify a program, the system looks for the subscreen in the current program. When the user chooses the tab title, it is activated, and the subscreen is assigned to the tabstrip area. The static assignment is valid for the entire duration of the program, but can be overwritten dynamically before the selection screen is displayed.
Dynamic assignment
For each tab area, the system automatically creates a structure in the ABAP program with the same name. This structure has three components PROG, DYNNR, and ACTIVETAB. When you assign the subscreens statically, the structure contains the name of the ABAP program containing the subscreen, the number of the subscreen, and the name of the tab title currently active on the selection screen (and to which these values are assigned). The default active tab page is the first page. You can assign values to the fields of the structure before the selection screen is displayed, and so set a subscreen dynamically.
If you assign a normal subscreen screen to a tab title, the dialog modules containing its flow logic must be defined in the current ABAP program. If the subscreen is a selection screen, user actions will trigger the AT SELECTION-SCREEN event and its variants (see Selection Screen Processing). This includes when the user chooses a tab title. If one selection screen is included on another, AT SELECTION-SCREEN will be triggered at least twice firstly for the "included" selection screen, then for the selection screen on which it appears.
REPORT demo_sel_screen_with_tabstrip.
DATA flag(1) TYPE c.
SUBSCREEN 1
SELECTION-SCREEN BEGIN OF SCREEN 100 AS SUBSCREEN.
SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME.
PARAMETERS: p1(10) TYPE c,
 p2(10) TYPE c,
 p3(10) TYPE c.
SELECTION-SCREEN END OF BLOCK b1.
SELECTION-SCREEN END OF SCREEN 100.
SUBSCREEN 2
SELECTION-SCREEN BEGIN OF SCREEN 200 AS SUBSCREEN.
SELECTION-SCREEN BEGIN OF BLOCK b2 WITH FRAME.
PARAMETERS: q1(10) TYPE c OBLIGATORY,
 q2(10) TYPE c OBLIGATORY,
 q3(10) TYPE c OBLIGATORY.
SELECTION-SCREEN END OF BLOCK b2.
SELECTION-SCREEN END OF SCREEN 200.
STANDARD SELECTION SCREEN
SELECTION-SCREEN: BEGIN OF TABBED BLOCK mytab FOR 10 LINES,
 TAB (20) button1 USER-COMMAND push1,
 TAB (20) button2 USER-COMMAND push2,
 TAB (20) button3 USER-COMMAND push3
 DEFAULT SCREEN 300,
 END OF BLOCK mytab.
INITIALIZATION.
button1 = text-010.
button2 = text-020.
button3 = text-030.
mytab-prog = sy-repid.
mytab-dynnr = 100.
mytab-activetab = 'BUTTON1'.
AT SELECTION-SCREEN.
CASE sy-dynnr.
 WHEN 1000.
 CASE sy-ucomm.
 WHEN 'PUSH1'.
 mytab-dynnr = 100.
 mytab-activetab = 'BUTTON1'.
 WHEN 'PUSH2'.
 mytab-dynnr = 200.
 mytab-activetab = 'BUTTON2'.
 ENDCASE.
 WHEN 100.
 MESSAGE s888(sabapdocu) WITH text-040 sy-dynnr.
 WHEN 200.
 MESSAGE s888(sabapdocu) WITH text-040 sy-dynnr.
ENDCASE.
MODULE init_0100 OUTPUT.
LOOP AT SCREEN.
 IF screen-group1 = 'MOD'.
 CASE flag.
 WHEN 'X'.
 screen-input = '1'.
 WHEN ' '.
 screen-input = '0'.
 ENDCASE.
 MODIFY SCREEN.
 ENDIF.
ENDLOOP.
ENDMODULE.
MODULE user_command_0100 INPUT.
MESSAGE s888(sabapdocu) WITH text-050 sy-dynnr.
CASE sy-ucomm.
 WHEN 'TOGGLE'.
 IF flag = ' '.
 flag = 'X'.
 ELSEIF flag = 'X'.
 flag = ' '.
 ENDIF.
ENDCASE.
ENDMODULE.
START-OF-SELECTION.
WRITE: / 'P1:', p1,'Q1:', q1,
 / 'P2:', p2,'Q2:', q2,
 / 'P3:', p3,'Q3:', q3.
This program defines two selection screens 100 and 200, as subscreens, and places a tabstrip control area with three tab pages on the standard selection screen. A subscreen screen 300 (from the same program) is assigned statically to the third tab page.
The layout of screen 300 is:
The input/output fields P1 to Q3 are defined by using the parameters from the ABAP program The pushbutton has the function code TOGGLE.
The screen flow logic for screen 300 is as follows:
PROCESS BEFORE OUTPUT.
MODULE init_0100.
PROCESS AFTER INPUT.
MODULE user_command_0100.
Both dialog modules are defined in the ABAP program.
When you run the program, the standard selection screen appears. In the INITIALIZATION event, the texts are defined on the tab titles, the subscreen selection screen 100 is assigned to the tab area, and the first tab title is activated.
User actions on the selection screen are processed in the AT SELECTION-SCREEN event block. In particular, it is here that the subscreens are assigned and tab titles activated when the user chooses one of the first two tab titles. This is not necessary for the third tab title, since the dynamic assignment (screen 300) is always placed in the structure MYTAB when the user chooses it.
Before the subscreen screen is displayed, the PBO module INIT_100 is executed. User actions on the subscreen screen trigger the PAI module. This includes when the user chooses a tab title. After that, the AT SELECTION-SCREEN event is triggered.
Messages in the status line show where an action has been processed.

Index of Values in the List Boxes on a Selection Screen

Hi,
I have a list box on the selection screen for Month field. It has the values Jan, Feb, Mar....etc in it.
These entries, I added thru the VRM_SET_VALUES.
Now, I want to default the month to current month SY-DATUM+4(2).
Is there any FM to which I can send this SY-DATUM+4(2) as an Index and the corresponding value gets set for the Month field.
As an alternatvie, I could use Case Sy-DATUM+4(2). when '01'. p_month = 'Jan'. etc etc.. But I want to avoid this big case statement.
Please suggest.
Thanks,
Suryakiran D.

Hi Suryakiran,
Try to use the func MONTH_NAMES_GET.It will
return the month name along with the number.
And also you can directly select from table T247
Thanks&Regards,
Siri.
Message was edited by: Srilatha T

'Text' of a variable in Bex selection screen

Hello,
We have a customer exit variable in Bex Query selection.it is mandatory,ready for input,interval which is on 0CALMONTH2.
In Bex selection screen i am not getting text of default/entered months.
for example: if default value is 2 to 4,then text would be FEB to APR.
what could be the reason?how to get teaxts of entered values?
(we have one more customer exit variable on 0CALMONTH2 which is single value and it shows text of enterd values in bex selection)
In web it is working fine.
Rakesh

Hi,
Try to create an another customer exit variable for 0CALMONTH2 with mandatory,ready for input,interval. refer the abap code of the another customer exit variable(single value variable) of 0CALMONTH2 which you have mentioned in the bracket and modify the abap code based on the selection - interval. hope it helps.
Regs,
Vachan

Standard input help in zreport selection screen

Hi All,
   I am having a selection sceen like S_PERNR FOR PA0001-PERNR.
   when I put f4 help then it is comming right and showing the value
of personnel number which is correct.
   But when you execute the transaction PA30 and select f4 help in
personnel number then it iscomming with window and all information
is cooming. I want to put that help on my selection screnn S_PERNR FOR PA0001-PERNR.
is it possible? Please give me the solution.
Thanks,
Rakesh

Yes, i am getting input help for position in that program also in ECC 6.0 version.
SELECT-OPTIONS:pchobjid FOR pchdy-objid_seq.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR pchobjid-low.
rhx-f4-objid-low pchplvar pchotype pchobjid '' ''.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR pchobjid-high.
rhx-f4-objid-high pchplvar pchotype pchobjid '' ''.
AT SELECTION-SCREEN ON pchobjid.
PERFORM check_objid_sign(rhxchk00) USING pchobjid-sign.
Which version are you working ?
Note: Plz post only one question per thread.

How to filter by manager's name using selection screen

Hi all,
I am trying to modify the report to filter data from the report based on the manger name given in selection screen. As the manger's name was given in selection screen.. records have to come only of the employee how were working under that entered manager name.
I am unable to follow this code to modify.. where to add select criteria to filter... please make modify to my code..
I am pasting my code here, Can any one kindly help for this scenario.
TABLES: PA0001, "HR Master Record: Infotype 0001 (Org. Assignment),
 PA0002,
 P0000,
 PA9001,
 PA0007,
 HRP1001, "Infotype 1001 DB Table
 PA0034. "HR Master Record: Infotype 0034 (Corporate Function)
*Internal table for holding output data
DATA: IT_PA0002 LIKE PA0002 OCCURS 100 WITH HEADER LINE,
 IT_PA9001 LIKE PA9001 OCCURS 100 WITH HEADER LINE,
 IT_PA0007 LIKE PA0007 OCCURS 100 WITH HEADER LINE,
 IT_PA0034 LIKE PA0034 OCCURS 100 WITH HEADER LINE.
DATA: IT_RET LIKE BAPIRET2,
 IT_ACT LIKE BAPI_SWHACTOR OCCURS 0,
 IT_STR LIKE BAPI_STRUC OCCURS 0,
 IT_ORG LIKE BAPI_OBJEC OCCURS 0,
 IT_POS LIKE BAPI_OBJEC OCCURS 0,
 IT_SUP LIKE BAPI_OBJEC OCCURS 0,
 IT_FCAT LIKE BAPI_HRAQFIELDDESCRIPTION OCCURS 0,
 IT_FDAT LIKE BAPI_HRFIELDDATA OCCURS 0,
 IT_ORGS TYPE STANDARD TABLE OF BAPI_OBJEC WITH HEADER LINE,
 IT_POSS TYPE STANDARD TABLE OF BAPI_OBJEC WITH HEADER LINE,
 IT_SUPR TYPE STANDARD TABLE OF BAPI_OBJEC WITH HEADER LINE,
 V_DATE TYPE SY-DATUM,
 IT_T500P LIKE T500P OCCURS 0 WITH HEADER LINE,
 IT_TT500P LIKE T500P OCCURS 0 WITH HEADER LINE,
 IT_T001P LIKE T001P OCCURS 0 WITH HEADER LINE .
DATA: IT_PA0001 LIKE PA0001 OCCURS 100 WITH HEADER LINE,
 P_ENDDA LIKE sy-datum.
DATA: Begin of I_HRE,
 pernr like pa0001-pernr, "Emp Number
 nachn like pa0002-nachn, "Last Name
 vorna like pa0002-vorna, "First Name
 plans like BAPI_OBJEC-LONG_TEXT, "Position
 div_text like pa9001-div_text,
 kztim like ZKZTIM_VAUES-name,
 stext like T591S-STEXT, "Corporate function text
 werks like BAPI_OBJEC-LONG_TEXT,
 btrtl like pa0001-btrtl,
 orgeh like BAPI_OBJEC-LONG_TEXT,
 kostl like pa0001-kostl,
 mstbr like pa0001-mstbr, "Supervisor
 End of I_HRE.
DATA: I_HR like I_HRE occurs 100 with header line.
DATA: V_PLANS LIKE PA0001-PLANS,
 V_EMP LIKE PA0001-PERNR,
 V_KOSTL LIKE PA0001-KOSTL,
 V_SUPER LIKE BAPI_OBJEC-LONG_TEXT,
 V_EMP_POS LIKE BAPI_OBJEC-LONG_TEXT,
 V_SUPER_POS LIKE BAPI_OBJEC-LONG_TEXT,
 V_HEADER TYPE N VALUE 1,
 V_COUNTER TYPE N VALUE 1,
 EMP_INDICATOR TYPE N,
 V_ORGEH LIKE BAPI_OBJEC-LONG_TEXT,
 V_WERKS LIKE BAPI_OBJEC-LONG_TEXT,
 V_KZTIM LIKE ZKZTIM_VAUES-NAME,
 V_STEXT LIKE T591S-STEXT.
DATA: v_file TYPE string, "Detail Filename
 v_filerecord(1000),
 f_filerecord(1000),
 drive(3),
 mstbr like pa0001-mstbr, "Supervisor
 count type n value 0.
SELECTION-SCREEN BEGIN OF BLOCK SELECTION WITH FRAME TITLE TEXT-001.
SELECT-OPTIONS: S_PERNR FOR P0000-PERNR,
 S_WERKS FOR PA0001-WERKS,
 S_BTRTL FOR PA0001-BTRTL,
 S_PERSG FOR PA0001-PERSG,
 S_ORGEH FOR PA0001-ORGEH,
 S_DIV FOR PA9001-DIV_CODE,
 S_KZTIM FOR PA0007-KZTIM,
 S_sname for pa0001-sname, " this is to enter name
 " as manager name
 S_FUNKT FOR PA0034-FUNKT.
SELECTION-SCREEN END OF BLOCK SELECTION.
SELECTION-SCREEN BEGIN OF BLOCK SELECTION1 WITH FRAME TITLE TEXT-002.
PARAMETERS: P_BEGDA LIKE SY-DATUM DEFAULT sy-datum.
* P_ENDDA LIKE SY-DATUM DEFAULT '99991231'.
SELECTION-SCREEN END OF BLOCK SELECTION1.
START-OF-SELECTION.
if P_BEGDA is initial.
p_begda = sy-datum.
endif.
if P_ENDDA is initial.
p_endda = sy-datum.
endif.
if S_PERSG is initial.
* S_PERSG-SIGN = 'I'.
* S_PERSG-OPTION = 'EQ'.
* S_PERSG-LOW = '1'.
* APPEND S_PERSG.
* S_PERSG-SIGN = 'I'.
* S_PERSG-OPTION = 'EQ'.
* S_PERSG-LOW = '6'.
* APPEND S_PERSG.
 S_PERSG-SIGN = 'I'.
 S_PERSG-OPTION = 'NE'.
 S_PERSG-LOW = '5'.
 APPEND S_PERSG.
endif.
SELECT * FROM PA0001 into IT_PA0001
 WHERE PERNR IN S_PERNR
 AND WERKS IN S_WERKS
 AND BTRTL IN S_BTRTL
 AND PERSG IN S_PERSG
 AND ORGEH IN S_ORGEH
 AND BEGDA LE P_BEGDA
 AND ENDDA GE P_ENDDA.
 APPEND IT_PA0001.
ENDSELECT.
IF not S_DIV[] is initial.
 SELECT * FROM PA9001 into IT_PA9001
 WHERE DIV_CODE IN S_DIV.
 APPEND IT_PA9001.
 ENDSELECT.
ENDIF.
IF not S_KZTIM[] is initial.
 SELECT * FROM PA0007 into IT_PA0007
 WHERE KZTIM IN S_KZTIM.
 APPEND IT_PA0007.
 ENDSELECT.
ENDIF.
IF not S_FUNKT[] is initial.
 SELECT * FROM PA0034 into IT_PA0034
 WHERE FUNKT IN S_FUNKT.
 APPEND IT_PA0034.
 ENDSELECT.
ENDIF.
SORT IT_PA0001 by SNAME.
LOOP AT IT_PA0001.
 IF not S_DIV[] is initial.
 READ TABLE IT_PA9001 with key pernr = IT_PA0001-PERNR.
 IF sy-subrc ne 0.
 continue.
 ENDIF.
 ENDIF.
 IF not S_KZTIM[] is initial.
 READ TABLE IT_PA0007 with key pernr = IT_PA0001-PERNR.
 IF sy-subrc ne 0.
 continue.
 ENDIF.
 ENDIF.
 IF not S_FUNKT[] is initial.
 READ TABLE IT_PA0034 with key pernr = IT_PA0001-PERNR.
 IF sy-subrc ne 0.
 continue.
 ENDIF.
 ENDIF.
 V_COUNTER = 1.
 V_EMP = IT_PA0001-PERNR.
 V_KOSTL = IT_PA0001-KOSTL.
* WRITE: (10) V_EMP, (20) PA0002-NACHN, (20) PA0002-VORNA.
 WRITE: / SY-VLINE. " Left border
 WHILE V_EMP NE ''.
 PERFORM GET_SUPER CHANGING V_EMP V_SUPER
 V_EMP_POS.
 if v_emp ne ''.
 select single * into it_pa0002 from pa0002
 where pernr = v_emp
 and begda LE p_begda
 and endda GE p_endda.
 IF V_HEADER = 1.
 PERFORM HEADING.
 V_HEADER = 0.
 ENDIF.
 WRITE: (10) V_EMP, (17) IT_PA0002-NACHN
 ,(17) IT_PA0002-VORNA, (40) V_EMP_POS.
 move v_emp to i_hr-pernr.
 move IT_PA0002-NACHN to i_hr-nachn.
 move IT_PA0002-VORNA to i_hr-vorna.
 move V_EMP_POS to i_hr-plans.
 EMP_INDICATOR = V_COUNTER.
 IF V_COUNTER = 1.
 select single * into it_pa9001 from pa9001
 where pernr = v_emp
 and begda LE p_begda
 and endda GE p_endda.
 select single * into it_pa0007 from pa0007
 where pernr = v_emp
 and begda LE p_begda
 and endda GE p_endda.
 PERFORM GET_KZTIM_TEXT CHANGING it_pa0007-kztim V_KZTIM.
 select single * into it_pa0034 from pa0034
 where pernr = v_emp
 and begda LE p_begda
 and endda GE p_endda.
 PERFORM GET_FUNKT_TEXT CHANGING it_pa0034-funkt v_stext.
 write: (8) IT_PA9001-DIV_CODE, (17) V_KZTIM,
 (25) V_STEXT.
 move IT_PA9001-DIV_CODE to i_hr-div_text.
 move v_KZTIM to i_hr-kztim.
 ENDIF.
 IF V_COUNTER = 0.
 WRITE: (1) '|'.
 ENDIF.
 IF V_COUNTER = 1.
 PERFORM GET_NAMES.
 WRITE: (20) V_WERKS, (5) IT_PA0001-BTRTL
 ,(20) V_ORGEH,(11) V_KOSTL, (3) '|'.
 V_COUNTER = 0.
 move V_WERKS to i_hr-werks.
 move IT_PA0001-BTRTL to i_hr-btrtl.
 move V_ORGEH to i_hr-orgeh.
 move V_KOSTL to i_hr-kostl.
 ENDIF.
 clear it_pa0002.
 refresh it_pa0002.
 endif.
 V_EMP = V_SUPER.
 move V_SUPER to i_hr-mstbr.
 if EMP_INDICATOR EQ 1.
 append i_hr.
 endif.
 clear i_hr.
 ENDWHILE.
NEW-LINE.
CLEAR : V_KZTIM, it_pa9001, it_PA0007.
ENDLOOP.
* Check if its a background Job
IF SY-BATCH NE SPACE.
 perform write_file. "Output File
ENDIF.
ULINE.
*& Form GET_SUPER
* This subroutine takes the position number and get the position
* number that it reports to and then who is holding that position and
* then the name of the person who is holding that position in order to
* provide the supervisors name for the person in that position.
* --> p1 text
* <-- p2 text
FORM GET_SUPER CHANGING EMP_SUB EMP_SUPER
 EMP_SUB_POS .
DATA: v_reporto like hrp1001-varyf value space,
 v_holder like hrp1001-varyf value space,
 v_filled like hrp1001-varyf value space,
 v_otype like hrp1001-otype value space,
 v_objid like hrp1001-objid value space.
CLEAR: v_reporto, v_holder, v_filled, v_otype, v_objid,
 EMP_SUB_POS.
Select single plans
 into v_plans
 from pa0001
 where pernr = emp_sub
 and begda LE p_begda
 and endda GE p_endda.
 CALL FUNCTION 'BAPI_ORGUNITEXT_DATA_GET'
 EXPORTING
 PLVAR = '01'
 OTYPE = 'S'
 OBJID = v_PLANS
 KEYDATE = SY-DATUM
 SCENARIO = ' '
* EVALPATH = 0
 EVALDEPTH = 0
 IMPORTING
 RETURN = IT_RET
 TABLES
* ACTORTAB = IT_ACT
* STRUCTURALDATA = IT_STR
 OBJECTSDATA = IT_SUP
* FIELDCATALOGUE = IT_FCAT
* FIELDDATA = IT_FDAT
 IF SY-SUBRC EQ 0.
 READ TABLE IT_SUP INTO IT_SUPR
 WITH KEY PLAN_VERS = '01'
 OBJECTTYPE = 'S'
 OBJECT_ID = v_PLANS.
 IF SY-SUBRC EQ 0.
 MOVE IT_SUPR-LONG_TEXT TO EMP_SUB_POS.
 ENDIF.
 ENDIF.
Select Single varyf
 into v_reporto
 from hrp1001
 where otype = 'S'
 and objid = v_plans
 and rsign = 'A'
 and relat = '002'
 and begda LE p_begda
 and endda GE p_endda.
if sy-subrc = 0.
 move v_reporto+0(1) to v_otype.
 move v_reporto+2(8) to v_objid.
 Select single varyf
 into v_holder
 from hrp1001
 where otype = v_otype
 and objid = v_objid
 and rsign = 'A'
 and relat = '008'
 and begda LE p_begda
 and endda GE p_endda.
 if sy-subrc = 0.
 move v_holder+0(1) to v_otype.
 move v_holder+2(8) to v_objid.
 EMP_SUPER = v_objid.
 IF EMP_SUB = EMP_SUPER.
 EMP_SUPER = ''.
 ENDIF.
* Select single varyf
* into v_filled
* from hrp1001
* where otype = v_otype
* and objid = v_objid
* and rsign = 'A'
* and relat = '209'.
* if sy-subrc = 0.
* CLEAR: IT_RET, IT_ACT, IT_STR, IT_FCAT, IT_FDAT,
* IT_SUP, IT_SUPR.
* REFRESH: IT_POSS.
* move v_filled+0(2) to v_otype.
* move v_filled+2(8) to v_objid.
* CALL FUNCTION 'BAPI_ORGUNITEXT_DATA_GET'
* EXPORTING
* PLVAR = '01'
* OTYPE = v_otype
* OBJID = v_objid
* KEYDATE = V_DATE
* SCENARIO = ' '
** EVALPATH = 0
* EVALDEPTH = 0
* IMPORTING
* RETURN = IT_RET
* TABLES
** ACTORTAB = IT_ACT
** STRUCTURALDATA = IT_STR
* OBJECTSDATA = IT_SUP
** FIELDCATALOGUE = IT_FCAT
** FIELDDATA = IT_FDAT
* IF SY-SUBRC EQ 0.
* READ TABLE IT_SUP INTO IT_SUPR
* WITH KEY PLAN_VERS = '01'
* OBJECTTYPE = v_otype
* OBJECT_ID = v_objid.
* IF SY-SUBRC EQ 0.
* MOVE IT_SUPR-LONG_TEXT TO EMP_SUPER.
* ENDIF.
* ENDIF.
* endif.
 endif.
endif.
 if sy-subrc <> 0.
 EMP_SUPER = ''.
 endif.
ENDFORM. " GET_SUPER
*& Form HEADING
* text
* --> p1 text
* <-- p2 text
FORM HEADING .
FORMAT INTENSIFIED OFF. " Remove any INTENSIFIED
FORMAT COLOR COL_HEADING INTENSIFIED." Title color
WRITE: (10) 'Employee', (17) 'Last Name'
 ,(17) 'First Name', (40) 'Position'
 ,(8) 'Division', (17) 'Management Type'
 ,(25) 'Corporate Function'
 ,(20) 'Personnel Area', (5) 'PSA'
 ,(20) 'Org. Unit',(11) 'Cost Center',(3) '|'
 ,(10) 'Supervisor', (17) 'Last Name'
 ,(17) 'First Name', (40) 'Position', (1) '|'
 ,(10) 'Supervisor', (17) 'Last Name'
 ,(17) 'First Name', (40) 'Position', (1) '|'
 ,(10) 'Supervisor', (17) 'Last Name'
 ,(17) 'First Name', (40) 'Position', (1) '|'
 ,(10) 'Supervisor', (17) 'Last Name'
 ,(17) 'First Name', (40) 'Position', (1) '|'
 ,(10) 'Supervisor', (17) 'Last Name'
 ,(17) 'First Name', (40) 'Position', (1) '|'
 ,(10) 'Supervisor', (17) 'Last Name'
 ,(17) 'First Name', (40) 'Position', (1) '|'
 ,(10) 'Supervisor', (17) 'Last Name'
 ,(17) 'First Name', (40) 'Position', (1) '|'
 ,(10) 'Supervisor', (17) 'Last Name'
 ,(17) 'First Name', (40) 'Position', (1) '|'
 ,(10) 'Supervisor', (17) 'Last Name'
 ,(17) 'First Name', (40) 'Position', (1) '|'
ULINE . " Line below titles
 NEW-LINE.
 WRITE: / SY-VLINE. " Left border
FORMAT COLOR OFF.
ENDFORM. " HEADING
*& Form GET_NAMES
* text
* --> p1 text
* <-- p2 text
FORM GET_NAMES .
CLEAR: IT_RET, IT_ACT, IT_STR, IT_ORG, IT_POS, IT_FCAT, IT_FDAT,
 IT_ORGS, IT_POSS, V_ORGEH, V_WERKS.
REFRESH: IT_ORGS, IT_POSS.
MOVE SY-DATUM TO V_DATE.
CALL FUNCTION 'BAPI_ORGUNITEXT_DATA_GET'
 EXPORTING
 PLVAR = '01'
 OTYPE = 'O '
 OBJID = IT_PA0001-ORGEH
 KEYDATE = V_DATE
 SCENARIO = ' '
* SCENARIO = 'MDT1'
* EVALPATH = '0 '
 EVALDEPTH = 0
 IMPORTING
 RETURN = IT_RET
 TABLES
* ACTORTAB = IT_ACT
* STRUCTURALDATA = IT_STR
 OBJECTSDATA = IT_ORG
* FIELDCATALOGUE = IT_FCAT
* FIELDDATA = IT_FDAT
IF SY-SUBRC EQ 0.
 READ TABLE IT_ORG INTO IT_ORGS
 WITH KEY PLAN_VERS = '01'
 OBJECTTYPE = 'O '
 OBJECT_ID = IT_PA0001-ORGEH.
 IF SY-SUBRC EQ 0.
 MOVE IT_ORGS-LONG_TEXT TO V_ORGEH.
 ENDIF.
ENDIF.
CALL FUNCTION 'HR_TMW_READ_T500P'
 EXPORTING
 PERSA = IT_PA0001-WERKS
 IMPORTING
 W500P = IT_T500P
 EXCEPTIONS
 NO_ENTRY_FOUND = 1
 OTHERS = 2.
IF SY-SUBRC <> 0.
 MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
IF SY-SUBRC EQ 0.
 MOVE IT_T500P-NAME1 TO V_WERKS.
 CLEAR: IT_T500P.
 REFRESH: IT_T500P.
ENDIF.
* CALL FUNCTION 'HR_TMW_READ_T001P'
* EXPORTING
* PERSA = PA0001-WERKS
* BTRTL = PA0001-BTRTL
* IMPORTING
* W001P = IT_T001P
* EXCEPTIONS
* NO_ENTRY_FOUND = 1
* OTHERS = 2.
* IF SY-SUBRC <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
* ENDIF.
* IF SY-SUBRC EQ 0.
* MOVE IT_T001P-BTEXT TO IT_HRR05-BTRTL.
* ENDIF.
ENDFORM. " GET_NAMES
*& Form GET_KZTIM_TEXT
* text
* <--P_V_EMP text
* <--P_V_KZTIM text
FORM GET_KZTIM_TEXT CHANGING P_KZTIM_ID
 P_KZTIM.
select single NAME into P_KZTIM from ZKZTIM_VAUES
 where TYPE eq P_KZTIM_ID.
ENDFORM. " GET_KZTIM_TEXT
*& Form GET_FUNKT_TEXT
* text
* <--P_V_EMP text
* <--P_V_KZTIM text
FORM GET_FUNKT_TEXT CHANGING P_FUNKT_ID
 P_STEXT.
select single STEXT into P_STEXT from T591S
 where SPRSL eq 'EN' and
 INFTY eq '0034' and
 SUBTY eq P_FUNKT_ID.
ENDFORM. " GET_KZTIM_TEXT
*& Form write_file
* text
* --> p1 text
* <-- p2 text
FORM write_file .
* Checking the System ID
if sy-sysid = 'RD1'.
 drive = 'D:\'.
else.
 drive = 'M:\'.
endif.
* concatenate drive sy-sysid
* '\Output\Reports\HR\HR_Public\Emp_Hierarchy'
* sy-datum
* '.xls' into v_file.
concatenate drive sy-sysid
 '\Output\Reports\HR\HR_Public\Emp_Hierarchy.xls'
 into v_file.
OPEN DATASET v_file FOR OUTPUT in text mode encoding default.
concatenate 'Employee'
 'Last Name'
 'First Name'
 'Position'
 'Division'
 'Management Type'
 'Corporate Function'
 'Personnel Area '
 'PSA'
 'Org. Unit'
 'Cost Center'
 'Supervisor'
 'Last Name'
 'First Name'
 'Position'
 'Supervisor'
 'Last Name'
 'First Name'
 'Position'
 'Supervisor'
 'Last Name'
 'First Name'
 'Position'
 'Supervisor'
 'Last Name'
 'First Name'
 'Position'
 'Supervisor'
 'Last Name'
 'First Name'
 'Position'
 'Supervisor'
 'Last Name'
 'First Name'
 'Position'
 'Supervisor'
 'Last Name'
 'First Name'
 'Position'
 'Supervisor'
 'Last Name'
 'First Name'
 'Position'
 'Supervisor'
 'Last Name'
 'First Name'
 'Position'
 into v_filerecord
 separated by CL_ABAP_CHAR_UTILITIES=>HORIZONTAL_TAB.
transfer v_filerecord to v_file. "Writing to file
clear v_filerecord.
loop at IT_PA0001.
 do.
 if count eq 0.
 read table i_hr with key pernr = IT_PA0001-pernr.
 concatenate i_hr-pernr
 i_hr-nachn
 i_hr-vorna
 i_hr-plans
 i_hr-div_text
 i_hr-kztim
 i_hr-stext
 i_hr-werks
 i_hr-btrtl
 i_hr-orgeh
 i_hr-kostl
 into v_filerecord
 separated by CL_ABAP_CHAR_UTILITIES=>HORIZONTAL_TAB.
 mstbr = i_hr-mstbr.
 count = count + 1.
 else.
 read table i_hr with key pernr = mstbr.
 concatenate v_filerecord
 i_hr-pernr
 i_hr-nachn
 i_hr-vorna
 i_hr-plans
 into f_filerecord
 separated by CL_ABAP_CHAR_UTILITIES=>HORIZONTAL_TAB.
 v_filerecord = f_filerecord.
 mstbr = i_hr-mstbr.
 clear i_hr.
 endif.
 if mstbr eq space.
 exit.
 endif.
 enddo.
 transfer v_filerecord to v_file. "Writing to file
 clear: v_filerecord, f_filerecord, count.
endloop.
CLOSE DATASET v_file.
ENDFORM. " write_file
Edited by: Surender Batlanki on Feb 20, 2008 7:50 AM
Edited by: Surender Batlanki on Feb 20, 2008 7:59 AM
Edited by: Surender Batlanki on Feb 20, 2008 8:12 AM
Edited by: Surender Batlanki on Feb 20, 2008 3:16 PM
Edited by: Alvaro Tejada Galindo on Feb 20, 2008 9:26 AM

Hi Surender,
In the Perform GET_SUPER, you are getting manager's OBJID. Use this OBJID and from PA0001 get Manger's name.
While passing data to output table, filter that table by Manager's name and then pass output table for display.
Hope this helps u.
<REMOVED BY MODERATOR>
Regards,
Preeti
Edited by: Alvaro Tejada Galindo on Feb 20, 2008 9:26 AM

Adding Sales Office to FBL5N selection screen

Hi,
I need to add Sales Office to FBL5N. Now the DDF logical data base doesn't have the table KNVV. So is there any other option to add this field to FBL5N selection screen. Along with this I need to add custom columns as well to the report outcome, which I think BTE would help me.
Now instead of coping the report I would prefer to use some sort of config in the logical database if possible. Could any one can suggest me on this.
Many Thanks!
Somnath

In addition to that you have to run one std program also
start report RFPOSXEXTEND. After starting, a pop-up appears, you must click YES.
Edited by: Sarang Gujrati on Feb 25, 2010 1:26 PM
Edited by: Sarang Gujrati on Feb 25, 2010 1:27 PM

Problem in displaying selection screen of a abap-hr report

Hi,
I have developed a abap-hr report in ver..6.2.I have used logical data base PNP for it.It was working fine.
But when i migrate it into ver.4.6, I can see no selection screen for the report.
How to get the selection-screen?
Please help me through.
Thanks in advance,
Raj.
Edited by: raj b on Feb 20, 2008 8:00 AM

Hi Raj,
Please check whether you have assigned any report category for the PNP selection screen in the version 6.2.
The report category might not exist in the 4.6 version and that might be the reason the selection screen is not appearing.
Cheers,
Aditya

Change in LDP PNP Selection Screen

Dear Friends,
As you all are aware that for LDP PNP we have a selection screen. In the selection screen, Personnel Number field has to be changed as Employee Number. Can some one tell how we can acieve this?
Thanks
Somu

Hi,
Changing of text will not be possible.
You can change it at data element level which will affect at all places where the data element is used. That is also possible only in ECC.
You can create ur own field if u need and give it a text but then automatic filtering will not be possible.
Regards,
Divya

Selection-screen validation

Hi Experts,
Please can any one give me the details ..
1)What is the actual use of selection screen validation?
2) When we use Selection-screen validation?
3)If we are not written the selection-screen validation is there any effect?
I know how to write the validation for a selection screen. But why i am asking above questions is I am very new to ABAP .My Functionl people also new to ABAP. They told me one report.I asked me what are the validation for selection screen . At that time they told there is no validation.
Thats the reason to ask above questions..
please tell me the details..
Thanks In Advance..
Thanks and Regards
Siri..

Abhi,
Selection Screen Validation are used for correct input processing.
Selection screen elements are used further in select queries to fetch data. if user enters some wrong input
we will unnecessarily hit the data base with wrong values and select will fail , hence validation of the input
will avoid unnecessary data base hit.
<REMOVED BY MODERATOR>
Edited by: Alvaro Tejada Galindo on Feb 27, 2008 12:26 PM

FEBA selection screen in ECC 6.0

Similar Messages

Maybe you are looking for