Maintained infotypes for an employee

Hi
please fetch me the aprogramme or trasation code to find infotypes which are maintained toa employee
Thanks in advance
Sri

Hi Sr!^^,
You can check the Program HRPBSUSACTION.
Regards,
Shiv
Edited by: Shivram SAP on Oct 31, 2008 10:29 AM

Similar Messages

Update multiple infotypes for an employee

I have a requirement to update some fields in various PA infotypes like 0002, 0006, 0008, 0015, 0021 and a few custom PA infotypes (9xxx) for a given set of employees.
Is there any method by which I would be able to update the required fields of all the above listed infotypes for an employee in one go? Is it possible to update all the infotypes of all the given set of employees in one go?
Please let me know the FM that could be used to meet the requirement. An example would also be helpful.
Thanks,
Jiten

Please check if there is already personnel actions defined with all the infotypes you are trying to update. If you have them, then you can use HR_INFOTYPE_OPERATION or HR_MANTAIN_MASTERDATA very easily with one single call. For that please refer the logic of PA48 transaction, simple one.
If the personnel action is not defined, then you need to call the FM HR_INFOTYPE_OPERATION separately for each infotype. Or HR_MAINTAIN_MASTERDATA at once for all of them.
From the list of standard infotypes mentioned, only IT0008 is having repetitive structure, handle it as a special case else others looks very similar.
Note : I don't see IT0000 mentioned in the list, hence i presume that there are no personnel actions defined for this set. But you can get it confirmed from your functional folks.
Regards
Ranganath

Maintaining qualifications for an employee

We are having problems on a new system (customer site) to maintain qualifications.
When trying to create a new qual. for an employee we get the message 'Action was cancelled'. I have double checked the customizing tables and can't find anything wrong. But I must be missing something.
Any ideas?

Hi
We faced this problem while upgrading the system to ECC 5.0. It was possible to assign qualifications via search term but not from the catalogue. We were getting the same error message (PQ022). We resolved this by applying OSS note 855853.
Hope this helps.
Regards,
Vikas Bhatia

Add 2 infotypes for the employee sub group .......

hi all,
i got hold by a issue. as per the business requirement i have to add 2 infotypes for a infogroup . the main issues here is the those infotype should appear only for one of the employee sub group not for all. kindly do the needful.
grab the points for the solution.
thanks
vikram

hai vikram,
we can do it by using IGMOD feature.
Reward with points.
Regards,
Chiran Reddy.

Maintaining access for different Pers Area for different Infotypes.

Hello,
We have two Pers. Areas.
1000 and 1020.
HR coordinator would like to see Certain
Info types(9011) for 1000 and 1020 &
other infotypes for 1020 ONLY in PA20.
I tried to put the P_ORGINCON
with different PA as below.
Authorization level            M, R
Infotype                       0000, 0001, 0002, 0008
Personnel Area                 1020
Employee Group                 *
Employee Subgroup              *
Authorization Profile          *
Subtype                        *
Organizational Key             *
Manually   HR: Master Data with Context
Authorization level             M, R
Infotype                       9011
Personnel Area                 1000, 1020
Employee Group                 *
Employee Subgroup              *
Authorization Profile             *
Subtype                               *
Organizational Key               *
We are not maintaining the Org level permission for this Role.
Please advice.
Regards,
PT,

Hi,
look here:
http://help.sap.com/saphelp_47x200/helpdata/en/49/4398375ae2f84ae10000009b38f8cf/frameset.htm
http://help.sap.com/saphelp_47x200/helpdata/en/08/514e2143b511d182b30000e829fbfe/frameset.htm
A.

Infotype for Employee begin date and end date

Hi Friends,
Could any one tell me the infotype and fields for getting employee joining date and end date.
Regards,
Susmita.

Infotype 41 (Date Specifications) should have all dates.
Infotype 2...i.e. PA0002 BEGDA & ENDDA may not have actual start and end date depending on how your company maintains it.
In Infotype 41 (table PA0041)...get either BEGDA & ENDDA or get correct date based on qualifier DAR01-DAR12.
Thanks,
Pushpinder Randhawa

Maintain number range interval for master data upload for existing employee

Hi Experts,
1)I have the scenario to upload additional data for existing employees in PA. Employees are already existed in SAP HR , But additional Infotypes are required to maintain for those emploees
2) I have the senario where i have to upload master data for new employees.
Pls give the detailed description of how to maintain number range interval i.e. External or Internal for upload in both the above scenario. Do we have to maintain number range manually in master data record & then upload it Through BDC or LSMW?
<< Moderator message - Everyone's problem is important. But the answers in the forum are provided by volunteers. Please do not ask for help quickly. >>
Edited by: Rob Burbank on Jan 12, 2011 3:49 PM

>
s c patil wrote:
> 2) For new employees i have to maintain desired ( my or client?) number range in SAP system as External number range & then default that number range in NUMKAR & then maintain those number range in master data record & then get the data template filled by client & then upload the data & after that create new number range which is next to existing External number range as an Internal number range. & then default that Internal number range.
>
> Pls reply ASAP
Yes Mr. Patil...
For existing employees
you need to execute HIRING ACTION Through BDC with External number range. While recording you have to use atleast three infotype i.e. IT0000,IT0001,IT0002. In addition you can upload other infotype through PA30.
For new employees
While configuration you can create another number range as internal for new hiring. and use NUMKR feature as well.
Here I don't understand that why r u looking for upload process for new hiring, if it is not mass hiring. It should be day to day activities which would be done by user through PA40.
Best Regards,
Anand Singh

Calling infotype 0002 in ALV report for showing employee photo

Hi all,
The requirment from business side is a report in which employees personal data shuold be shown with employee photo, I had tried for employee photo in ALV report but it didnt sucessed, then I went for other solution like calling transaction in ALV report.
In this case I am calling Infotype 0002 but the issue is that the transaction PA20 is coming with PERNR but I am not able to go directlly to infotype which shows employee Photo,please suggest any solution.
Thaks.
JAY

Hi Jay,
It is possible. Please refer the syntax for the CALL TRANSACTION
CALL TRANSACTION ta { [AND SKIP FIRST SCREEN]
                    | [USING bdc_tab [bdc_options]] }.
You can do a recording till the required page comes & call the transaction accordingly. Hope, you are aware about the same.
For example, I just had a solution to go to the roles tab in the user profile and I did as below:
    CLEAR wa_bdcdata.
    wa_bdcdata-program = 'SAPLSUU5'.
    wa_bdcdata-dynpro   = '0050'.
    wa_bdcdata-dynbegin = k_ok.
    APPEND wa_bdcdata TO it_bdcdata.
    CLEAR wa_bdcdata.
    wa_bdcdata-fnam = 'BDC_CURSOR'.
    wa_bdcdata-fval   = 'USR02-BNAME'.
    APPEND wa_bdcdata TO it_bdcdata.
    CLEAR wa_bdcdata.
    wa_bdcdata-fnam = 'USR02-BNAME'.
    wa_bdcdata-fval   = g_value.
    APPEND wa_bdcdata TO it_bdcdata.
    CLEAR wa_bdcdata.
    wa_bdcdata-fnam = 'BDC_OKCODE'.
    wa_bdcdata-fval   = 'SHOW'.
    APPEND wa_bdcdata TO it_bdcdata.
    CLEAR wa_bdcdata.
    wa_bdcdata-program = 'SAPLSUU5'.
    wa_bdcdata-dynpro   = '0100'.
    wa_bdcdata-dynbegin = k_ok.
    APPEND wa_bdcdata TO it_bdcdata.
    CLEAR wa_bdcdata.
    wa_bdcdata-fnam = 'BDC_OKCODE'.
    wa_bdcdata-fval   = '=ACTG'.
    APPEND wa_bdcdata TO it_bdcdata.
    g_opt-dismode = 'E'.
    g_opt-defsize = k_ok.
*** if user click on the User Name, call SU01
    CALL TRANSACTION 'SU01' USING it_bdcdata
                OPTIONS FROM g_opt.
Regards,
Selva K.

Error while updating HRA in infotype 581 for the employees.

Hi,
System is showing an error while updating HRA in infotype 581 for the employees.
The error is No Automatic updation for IT0008. Allowance Grouping not found.
What is this error. Please advice what to do in this case.

Hi Deepthi,
Check Table V_T7INA5,V_T7INA1,V_T7INA3 and V_T7INA9 also.
Check it,
Regards,
Vinod.
Edited by: vinod rao on Jul 30, 2008 1:23 PM

Maintaining Infotypes in PP01 for Central Person while already maintained n

Dear Team,
When we are using PP01 Transaction code by taking Object type Central Person system is showing is showing IT0001, IT0002, IT0006 and IT0009 etc. Please let us know the purpose of using all these infotypes as we have already maintained the same in PA30 u2013 Maintain master data
Could you please suggest us whether to update these infotypes here or not and what are implication of the same if we maintain them again here?
Kind Regards
Nagesh

Hi,
When you enter central person and click to see data it takes you to PA30 infotypes and this shows that there is CP-P relation and tells you that link exists from OM to PA for same.
It is sufficient to maintain infotypes in PA30 only as this just shows you linkage nothing more.
Thanks,
Ameet

Infotypes created for an employee

Dear experts.
Anyone know if SAP have a report or transaction for Know that infotype saved an employee?
Thanks in advance
Regards
Carmen G

Please use standard program below to see all infotype of employee in SAP system:
S_AHR_61015785 - Infotype Overview for Employee
Regards!
Woody.

Maintain texts for Infotype 0019 via ABAP.

Hi,
The issue is related to maintaining texts for Infotype 0019. I have a program below. The main problem is I am facing is for some records it inserts text in Infotype (0019) but for some it does not. Can anyone suggest why so or a way to resolve this problem ???
REPORT ytbctest009.
TABLES: pernr, pcl1.
INFOTYPES: 0019.
DATA: key LIKE pskey.
DATA: BEGIN OF ptext OCCURS 200.
DATA:   line(72).
DATA: END OF ptext.
SELECTION-SCREEN BEGIN OF BLOCK abc WITH FRAME TITLE text-001.
PARAMETERS:               p_pernr LIKE pernr-pernr.
SELECTION-SCREEN END OF BLOCK abc.
ptext-line = 'TEST 1'.
APPEND ptext.
ptext-line = 'Test 2'.
APPEND ptext.
ptext-line = 'Test 3'.
APPEND ptext.
rp-read-infotype p_pernr 0019 0019 '18000101' '99991231'.
SORT p0019 DESCENDING.
READ TABLE p0019 INDEX 1.
p0019-itxex = 'X'.
MOVE-CORRESPONDING p0019 TO key .
CALL FUNCTION 'HR_INFOTYPE_OPERATION'
EXPORTING
    infty         = '0019'
    number        = p_pernr
    validityend   = p0019-endda
    validitybegin = p0019-begda
    record        = p0019
    operation     = 'MOD'.
EXPORT ptext TO DATABASE pcl1(tx) ID key.
Thanks in advance.

Hi Rajashree,
I hope , below code will solve the problem.
<b>Main Code</b>
FUNCTION zhr_mustus_update_it0019.
*"*"Local interface:
*" IMPORTING
*"     VALUE(IM_PERNR) TYPE P0019-PERNR OPTIONAL
*"     VALUE(IM_USRID) TYPE PA0105-USRID OPTIONAL
*"     VALUE(IM_SUBTY) TYPE P0019-SUBTY
*"     VALUE(IM_TERMN) TYPE P0019-TERMN OPTIONAL
*"     VALUE(IM_MNDAT) TYPE P0019-MNDAT OPTIONAL
*"     VALUE(IM_BVMRK) TYPE P0019-BVMRK OPTIONAL
*"     VALUE(IM_TEXT) TYPE CHAR30 OPTIONAL
*" EXPORTING
*"     VALUE(EX_RETURN_MESSAGE) TYPE STRING
*"     VALUE(EX_MESSAGE_ID) TYPE ARBGB
*"     VALUE(EX_MESSAGE_NUMBER) TYPE MSGNR
*" EXCEPTIONS
*"      SYSTEM_FAILURE
*"      COMMUNICATION_FAILURE
REFRESH bdcdata.
REFRESH it_bdc_message.
* Validations
PERFORM validations USING im_usrid im_subty im_mndat
                   CHANGING im_pernr
                            g_task_date
                            g_rem_date.
* Return message
MOVE:
    g_message TO ex_return_message,
    'ZMSGHR' TO ex_message_id,
    g_msgno   TO ex_message_number.
* If there any error don't process
CHECK ex_return_message IS INITIAL.
* If reminder date is missing then its creation
IF im_mndat IS INITIAL.
* Fill BDC for PA30 Creation
    PERFORM fill_bdc_for_creation USING im_pernr
                                        im_subty
                                        im_text
                                        g_task_date
                                        g_rem_date.
ELSE.
* Its a change, Fill BDC for PA30 change
    PERFORM fill_bdc_for_change USING im_pernr
                                      im_subty
                                      im_termn
                                      im_bvmrk
                                      im_text.
ENDIF.
* Call transaction PA30
PERFORM bdc_call_transaction.
* Return message
MOVE:
    g_message TO ex_return_message,
    g_msgid   TO ex_message_id,
    g_msgno   TO ex_message_number.
ENDFUNCTION.
<b>All Above Subroutines,</b>
*& Form Validations
* Validations for MUS/TUS
*      -->U_USRID      User id for TUS
*      -->U_SUBTY      Subtype 10 - MUS, 11 - TUS
*      -->U_MNDAT      Reminder date
*      <--PERNR        Person for MUS
*      <--U_TASK_DATE Task date
*      <--U_REM_DATE   Reminder date
FORM validations USING u_usrid     LIKE pa0105-usrid
                       u_subty     LIKE p0019-subty
                       u_mndat     LIKE p0019-mndat
              CHANGING u_pernr     LIKE p0019-pernr
                       u_task_date LIKE sy-datum
                       u_rem_date LIKE sy-datum.
DATA:
    BEGIN OF it_tmp_0019 OCCURS 0,
     termn LIKE pa0019-termn,
    END OF it_tmp_0019.
CLEAR g_message.
* Validations for MUS
IF u_subty EQ c_subty_10.
    MOVE sy-datum TO u_task_date.
    IF u_pernr IS INITIAL.
* Person number is missing
      MOVE:
        text-001 TO g_message,
        '003' TO g_msgno.
    ELSEIF u_mndat IS INITIAL.
* Its creation, check if there is already a open item
      SELECT pernr
        FROM pa0019
        INTO u_pernr
       WHERE pernr EQ u_pernr
         AND subty EQ u_subty
         AND bvmrk NE '2'.
        EXIT.
      ENDSELECT.
      IF sy-subrc EQ 0.
* Throw an error if there is already a open item
        MOVE:
          text-006 TO g_message,
          '004'    TO g_msgno.
      ENDIF.
    ENDIF.
ENDIF.
* Validations for TUS
IF u_subty EQ c_subty_11.
    IF u_usrid IS INITIAL
   AND u_pernr IS INITIAL.
* User/Person number is missing
      MOVE:
        text-002 TO g_message,
        '005'    TO g_msgno.
    ELSEIF NOT u_usrid IS INITIAL.
      SELECT pernr
        FROM pa0105
        INTO u_pernr
       WHERE usrid EQ u_usrid.
      ENDSELECT.
      IF u_pernr IS INITIAL.
* Person number is missing
        MOVE:
          text-001 TO g_message,
          '006' TO g_msgno.
      ENDIF.
    ENDIF.
    IF g_message IS INITIAL.
      SELECT termn
        FROM pa0019
        INTO TABLE it_tmp_0019
       WHERE pernr EQ u_pernr
         AND subty EQ u_subty
         AND bvmrk NE '2'.
      READ TABLE it_tmp_0019 WITH KEY termn = sy-datum.
* There is no open task for today
      IF sy-subrc NE 0.
        MOVE sy-datum TO u_task_date.
      ELSE.
* There is a open task for today, new task should be created next
* available date and reminder date is yesterday's date
        SORT it_tmp_0019 DESCENDING.
        READ TABLE it_tmp_0019 INDEX 1.
        u_task_date = it_tmp_0019-termn + 1.
        u_rem_date = sy-datum - 1.
      ENDIF.
    ENDIF.
ENDIF.
ENDFORM.                    "VALIDATIONS
*& Form Fill_bdc_for_creation
* BDC data for creation , Transaction PA30
*      -->U_PERNR      Person
*      -->U_SUBTY      Subty MUS - 10, TUS - 11
*      -->U_TEXT       Text
*      -->U_TASK_DATE Task date
*      -->U_REM_DATE Task date
FORM fill_bdc_for_creation USING u_pernr LIKE p0019-pernr
                                 u_subty LIKE p0019-subty
                                 u_text TYPE char30
                                 u_task_date LIKE sy-datum
                                 u_rem_date LIKE sy-datum.
* Scree1
DATA:
    l_task_date(10),
    l_rem_date(10).
* Use system date as Task date
WRITE:
    u_task_date TO l_task_date,
    u_rem_date TO l_rem_date.
PERFORM bdc_dynpro      USING 'SAPMP50A' '1000'.
PERFORM bdc_field       USING 'RP50G-PERNR'
                                u_pernr.
PERFORM bdc_field       USING 'RP50G-CHOIC'
                                '0019'.
PERFORM bdc_field       USING 'RP50G-SUBTY'
                                u_subty.
PERFORM bdc_field       USING 'BDC_OKCODE'
                                '=INS'.
* Screen2
PERFORM bdc_dynpro      USING 'MP001900' '2000'.
PERFORM bdc_field       USING 'P0019-TMART'
                                u_subty.
PERFORM bdc_field       USING 'P0019-TERMN'
                                 l_task_date.
IF NOT u_rem_date IS INITIAL.
    PERFORM bdc_field       USING 'P0019-MNDAT'
                                   l_rem_date.
ENDIF.
PERFORM bdc_field       USING 'RP50M-TEXT1'
                                u_text.
PERFORM bdc_field       USING 'BDC_OKCODE'
                                '/00'.
PERFORM bdc_dynpro      USING 'MP001900' '2000'.
PERFORM bdc_field       USING 'P0019-TMART'
                                u_subty.
PERFORM bdc_field       USING 'P0019-TERMN'
                                 l_task_date.
IF NOT u_rem_date IS INITIAL.
    PERFORM bdc_field       USING 'P0019-MNDAT'
                                   l_rem_date.
ENDIF.
PERFORM bdc_field       USING 'RP50M-TEXT1'
                                u_text.
PERFORM bdc_field       USING 'BDC_OKCODE'
                                '=UPD'.
ENDFORM.                    "fill_bdc_for_creation
*& Form fill_bdc_for_change
* BDC data for change , Transaction PA30
*      -->U_PERNR    Person
*      -->U_SUBTY    subtype MUS - 10 , TUS - 11
*      -->U_MNDAT    Reminder date
*      -->U_BVMRK    Status
*      -->U_TEXT     Text
FORM fill_bdc_for_change USING   u_pernr LIKE p0019-pernr
                                 u_subty LIKE p0019-subty
                                 u_termn LIKE p0019-termn
                                 u_bvmrk LIKE p0019-bvmrk
                                 u_text TYPE char30.
* Scree1
DATA l_termn_date(10).
WRITE u_termn TO l_termn_date.
PERFORM bdc_dynpro      USING 'SAPMP50A' '1000'.
PERFORM bdc_field       USING 'RP50G-PERNR'
                                u_pernr.
PERFORM bdc_field       USING 'RP50G-CHOIC'
                                '0019'.
PERFORM bdc_field       USING 'RP50G-SUBTY'
                                u_subty.
PERFORM bdc_field       USING 'RP50G-BEGDA'
                                l_termn_date.
PERFORM bdc_field       USING 'RP50G-ENDDA'
                                l_termn_date.
PERFORM bdc_field       USING 'BDC_OKCODE'
                                '=MOD'.
* Screen2
PERFORM bdc_dynpro      USING 'MP001900' '2000'.
PERFORM bdc_field       USING 'P0019-TMART'
                                u_subty.
PERFORM bdc_field       USING 'P0019-TERMN'
                                 l_termn_date.
PERFORM bdc_field       USING 'RP50M-TEXT1'
                                u_text.
PERFORM bdc_field       USING 'P0019-BVMRK'
                                u_bvmrk.
PERFORM bdc_field       USING 'BDC_OKCODE'
                                '=UPD'.
ENDFORM.                    "fill_bdc_for_change
FORM bdc_call_transaction.
DATA:
    l_mode(1) TYPE c VALUE 'N',
    l_lines   TYPE i,
    l_msgvar1 LIKE balm-msgv1,
    l_msgvar2 LIKE balm-msgv2,
    l_msgvar3 LIKE balm-msgv3,
    l_msgvar4 LIKE balm-msgv4.
CALL TRANSACTION 'PA30' USING bdcdata MODE l_mode
                           MESSAGES INTO it_bdc_message.
* Get last message
DESCRIBE TABLE it_bdc_message LINES l_lines.
READ TABLE it_bdc_message INDEX l_lines.
MOVE:
    it_bdc_message-msgid TO g_msgid,
    it_bdc_message-msgnr TO g_msgno,
    it_bdc_message-msgv1 TO l_msgvar1,
    it_bdc_message-msgv2 TO l_msgvar2,
    it_bdc_message-msgv3 TO l_msgvar3,
    it_bdc_message-msgv4 TO l_msgvar4.
* Prepare message
CALL FUNCTION 'MESSAGE_PREPARE'
    EXPORTING
      language               = sy-langu
      msg_id                 = g_msgid
      msg_no                 = g_msgno
      msg_var1               = l_msgvar1
      msg_var2               = l_msgvar2
      msg_var3               = l_msgvar3
      msg_var4               = l_msgvar4
    IMPORTING
      msg_text               = g_message
    EXCEPTIONS
      function_not_completed = 1
      message_not_found      = 2
      OTHERS                 = 3.
IF sy-subrc <> 0.
    MOVE text-005 TO g_message.
ENDIF.
ENDFORM.                    "BDC_FIELD
*        Start new screen                                              *
FORM bdc_dynpro USING program dynpro.
CLEAR bdcdata.
bdcdata-program = program.
bdcdata-dynpro   = dynpro.
bdcdata-dynbegin = 'X'.
APPEND bdcdata.
ENDFORM.                    "BDC_DYNPRO
*        Insert field                                                  *
FORM bdc_field USING fnam fval.
CLEAR bdcdata.
bdcdata-fnam = fnam.
bdcdata-fval = fval.
APPEND bdcdata.
ENDFORM.                    "BDC_FIELD
Cheers.
Santosh.

ESI not coming for some employees

Hi,
For some Employees ESIC is not Deducting, though i have maintained Infotype 0588, but for some employees its coming...and in RT table Employer ESIC Contribution is coming, but in payslip Employees ESIC is not coming...please help me in this issue...
Thanks & Regards
Ragini NIkam
SAP-HR Consultant

Hi,
Please confirm the followings:
a) Are you able to see /3E1 & /3E1 for those cases in RT?
Ans: In RT Table only i am able to see /3er and not /3e1
b) Value of /112
Ans: /112 is coming Rs. 7988.50 thats my gross amount
c) Validity of IT0588 (ESI)Please confirm the followings:
Ans: Validity is 01.04.2011 to 31.12.9999,
But sir how its coming for some employees and and for some its not.
Thanks & Regards
RAGINI Nikam
SAP-HR Consultant

Finding Manger for an employee

Hi Friends,
How can i find the manger for an employee?
Suppose if the employee has BU_Manager and FUNC_Manger and HR Business partner.
it would me most useful if you send the logic for it.......
Thanks in Advance,
Chandra.

In order to get the Manager or Supervisor we need to get the position           *
and organization unit of the manager for the person entered on the selection    *
screen by using the certain relations from the hrp1001 with the below fields    *
objid----Object ID                                                              *
otype--Object Type          ( O>org unit S>position P>persion )        *
rsign--Relationship Specification ( A>bottom up B-->top down      )        *
relat--Relationship Between Objects ( 002->Reports to                      *
                                         003--->Belongs to                       *
                                         008--->Holder                           *
                                         012--->Manages                 )        *
sclas--Type of Related Object ( O>org unit S>position P>persion c-->job)*
sobid----ID of Related Object                                                   *
Then we need to get the personnel number from that we need to get the details   *
of the manager by the infotype PA0002 by passing Personnel number               *
REPORT ygetsupervisor MESSAGE-ID zmsg.
               database tables used
TABLES:pa0001,       "Infotype 0001 (Org. Assignment)
       hrp1001,      "Infotype 1001
       pa0002.       "Infotype 0002 (Personal Data)
               internal tables declaration
*----internal tables for holding
DATA: t1001          LIKE p1001 OCCURS 0 WITH HEADER LINE,
      t1002          LIKE p1001 OCCURS 0 WITH HEADER LINE,
      t1003          LIKE p1001 OCCURS 0 WITH HEADER LINE,
      t1004          LIKE p1001 OCCURS 0 WITH HEADER LINE,
      t0001          LIKE p0001 OCCURS 0 WITH HEADER LINE,
      t0002          TYPE p0002 OCCURS 0 WITH HEADER LINE.
              variable declaration
*---0 to capture the id of the object "may be orgunit, position, persion.
DATA: g_sobid1 LIKE p1001-objid,
      g_sobid2 LIKE p1001-objid,
      g_sobid3 LIKE p1001-objid,
*--to capture the personnel number
      g_pernr LIKE pa0002-pernr.
              selection screen paramters
*----enter a valid personnel number
PARAMETERS:p_pernr LIKE pa0002-pernr.
             start of selection
START-OF-SELECTION.
*-- Get the Position for entered Personnel number
*----RH_READ_INFTY function module is used for the OM infotypes ..starting with HRP
CALL FUNCTION 'RH_READ_INFTY'
    EXPORTING
      plvar                = '01'
      otype                = 'P'
      objid                = p_pernr
      infty                = '1001'
      subty                = 'B008'
      begda                = sy-datum
      endda                = sy-datum
    TABLES
      innnn                = t1001
    EXCEPTIONS
      all_infty_with_subty = 1
      nothing_found        = 2
      no_objects           = 3
      wrong_condition      = 4
      wrong_parameters     = 5
      OTHERS               = 6.
IF sy-subrc <> 0.
    MESSAGE i000 WITH 'this number is not maintained in hrp1001'.
ENDIF.
*-- Get the latest record reading T1001 with following values
SORT t1001 BY begda DESCENDING .
READ TABLE t1001 WITH KEY objid = p_pernr   "personnel number
                            otype = 'P'       "Person
                            rsign = 'B'       "hirarchy top down
                            relat = '008'     "Holder
                            sclas = 'S'.      "Position
IF NOT t1001[] IS INITIAL.
    g_sobid1 = t1001-sobid.                  "ID of Related Object
*-- Get Org unit for the position obtained from above
    CALL FUNCTION 'RH_READ_INFTY'
      EXPORTING
        plvar = '01'
        otype = 'S'
        objid = g_sobid1
        infty = '1001'
        subty = 'A003'
        begda = sy-datum
        endda = sy-datum
      TABLES
        innnn = t1002.
ENDIF.
SORT t1002 BY begda DESCENDING .
READ TABLE t1002 WITH KEY objid = g_sobid1
                            otype = 'S'      "Position
                            rsign = 'A'      "bottom up
                            relat = '003'    "Belongs to
                            sclas = 'O'.     "org unit
IF NOT t1002[] IS INITIAL.
    g_sobid2 = t1002-sobid.
*-- Get position for the Org unit (Manager)
    CALL FUNCTION 'RH_READ_INFTY'
      EXPORTING
        plvar = '01'
        otype = 'O'
        objid = g_sobid2
        infty = '1001'
        subty = 'B012'
        begda = sy-datum
        endda = sy-datum
      TABLES
        innnn = t1003.
ENDIF.
SORT t1003 BY objid.
READ TABLE t1003 WITH KEY objid = g_sobid2
                            otype = 'O'      "org unit
                            rsign = 'B'      "hirarchy top down
                            relat = '012'    "Manages
                            sclas = 'S'.     "Position
IF NOT t1003[] IS INITIAL.
    g_sobid3 = t1003-sobid.
*-- Get Personnel number for the Manager
    CALL FUNCTION 'RH_READ_INFTY'
      EXPORTING
        plvar = '01'
        otype = 'S'
        objid = g_sobid3
        infty = '1001'
        subty = 'A008'
        begda = sy-datum
        endda = sy-datum
      TABLES
        innnn = t1004.
ENDIF.
READ TABLE t1004 WITH KEY objid = g_sobid3
                            otype = 'S'      "Position
                            rsign = 'A'      "bottom up
                            relat = '008'    "Holder
                            sclas = 'P'.     "Person
IF NOT t1004[] IS INITIAL.
    g_pernr = t1004-sobid+0(8).
*--Get name of Manager(Supervisor)
    CALL FUNCTION 'HR_READ_INFOTYPE'
      EXPORTING
        pernr     = g_pernr
        infty     = '0002'
      TABLES
        infty_tab = t0002.
    SORT t0002 BY pernr begda.
    READ TABLE t0002 INDEX 1.
    IF NOT t0002[] IS INITIAL.
      FORMAT COLOR 7 .
      SKIP 3.
      WRITE:/1(101) sy-uline .
      WRITE:/1 sy-vline,
             2 'manager personnel number',
             30 sy-vline,
             31 'manager first name' ,
             60 sy-vline,
             61 'manager lastname',
             101 sy-vline.
      FORMAT COLOR OFF.
      WRITE:/1(101) sy-uline .
      WRITE:/1 sy-vline,
             2 t0002-pernr COLOR 4,
             30 sy-vline,
             31 t0002-vorna COLOR 4,
             60 sy-vline,
             61 t0002-nachn COLOR 4,
             101 sy-vline.
      WRITE:/1(101) sy-uline .
    ENDIF.
ENDIF.

HR Infotype for disabled/handicapped

Hi,
Is there any standard infotype in HCM (Human Capital Management) to maintain records of the employees who are handicapped/ disabled? Can anyone please advise?
Thanks
AM

Hi,
you are using two infotypes simultaneously that is IT0001 and IT0021 which is incorrect. Dynamic actions are triggered on any action happened on one infotype to create or change or delete the other infotype record.
So can you tell on which infotype you want to trigger your dynamic action and which infotype you want to create.
If you want to trigger something on IT0021 change, then call subroutine in your dynamic action to read IT0001-PERSK value. and only put IT0021 fields with 'P' (plausibility check)
0021 04 8 F GET_PERSK(ZHR_GET_EMPSUBGRP)
in subroutine check for your conditions after retrieving the value of Emp Subgrp and assign the value as X for correct and blank for incorrect to RP50D-FLAG1
Check This field value with the X in and condition with your line 6 and 7 and your code should work
Hope this will be of help. Do let me know for further queries
guds
Edited by: guds on May 6, 2009 1:40 AM

Maintained infotypes for an employee

Similar Messages

Maybe you are looking for