Military LOA tracking on PA Infotypes

I was wondering if anyone could recommend a PA Infotype to track U.S Military Leave of Absence on a non-payroll related infotype. We want to be able to determine when an employee goes and returns from Military Leave.

Couldn't we use Absences Infotype and configure a subtype as 'Military Leave' and track the same? I think it should work. Also, we could use IT 0081 'Military Service' in case we need to build a scenario.
Regards
Lincoln

Similar Messages

Report to track changes to infotypes prior to running the payroll interfac

wants a report to track changes to infotypes prior to running the payroll interface. The attached report looks like it should work but it returns nothing. Is there config that turns on "Track Changes": for select infotypes? If so, can they be activated for key infotypes so this report will run?
Name, Address, position, etc.
Not attendance and absence ITs.

Hi,
IMG Personnel Management Personnel Admin Tools Revision Set up change document:
This node has three items:
Infotypes to be logged
Field Group Definitions
Field Group Characteristics
Using these three options you define which infotypes you wish to log, then which fields, then you define which groups of fields are to be saved. Click each link, or see the sections below:
Infotypes to be logged
Here you define which PA infotype numbers you require logging. Select New Entries and enter a transaction class (A for Pers Admin, B for recruitment), then enter the infotype number and save.
Field Group Definition
When changes are made to a logged infotype, the field contents before and after are recorded. This is the very reason for logging the infotype, but there is an overhead in performance and disk space used so it needs to be given consideration. Typically you will want to record fields that are pay relevant.
Using the field group definition, you specify which fields you wish to record changes in. When any of the fields in the group are changed, all the fields in the group are saved. You can use an asterisk to log all the fields of the infotype but this is not recommended for space and performance, also there are many fields on an infotype that you will not be using, that will be saved also. Ideally you will pick individual fields of the infotype and enter them like so:
The field group number is a freely defined number you allocate to the group, it will be used in the next step. For normal use, simply pick any number not already used in that infotype. All fields with the same field group number are recorded in the log, even if they have not changed.
Click New Entries and enter the infotype number, field group number and field names that you wish to record.
Field Group Characteristics
When you have set up the field group numbers, use the field group characteristics to activate the logging of those fields. You can also specify a supplementary field group; this means that the contents of another field group can also be saved at the same time, even though the contents have not changed. In practise it is not used much. Simply select new entries, enter the transaction class, infotype, and in the DocFieldGr enter the number you assigned to the field names that you want to store, then enter L for Long Term Documents (short are not supported)
The Audit Report
To access the report showing the logged infotype changes, use the HR report tree available from various menu paths, including:
Main Menu Human Resources Pers Management Administration Info System Reports - Documents Infotype change logged changes in infotype data. (RPUAUD00).
When you run the report, select the infotypes you require, and select and execute.
Cheers
Prasanth

Track Overage in Infotype 0021 subtype 2 (Child)

Hi Experts,
Is there any other way to track dependents especially the subtype 2 - Child in family member/ dependents, if they are already reach the overage? (21years old) Can we make it on Dynamic Actions?
Edited by: Jan Christian Cu on Aug 8, 2011 9:53 AM

Hi,
I would probably do the DELIMIT inside your program. This way you can connect to the right record.
Regards,
Serge

Some question on pa and om

hi
some question
if employee work in us and then gone to uk
how u track
it
whcin infotype
and what is dotted reporting
in simple mantice
and how to assign diff number range in org mangemnt for job, postion and org unit like 200-300,100-200,400-500.
from
rajani

Hi Rajani,
To address dual reporting relationship ,OM has A/088 relationship,please check tcode -OOOT and select object type S-Positions and essential relationship.
OONR is tcode for number ranges -the first two letter in the subgroup denotes the plan version and the last two letter is the object type
for ex -01S-would denote plan version 01 and object type S-postion and whether the numbers are going to be asisgned internally by the system or externally by the user.
01$$ would denotes its application for all object types,should the $ be used .
select the subgroup and click on number range maintainance and you will be able to see the numbers assigned or edit them by clicking change interval button and you can assign the from and to number accordingly.The numbers gets assigned when the particular object is created.
ex-you assign the subgroup as $$S-which means its for all plan version and object type S
when you create an object type using PP01 for ex the numbers gets assigned for that object created.
Hope this helps.
Regards
KG
Edited by: SAPenjoy:) on Aug 19, 2010 11:30 AM

OM log turned on - should we remove database table log?

Hi
We have turned on the OM-logging via T77CDOC_CUST. This is done for object type O and S for infotypes 1000 and 1001.
My question now is:
We plan to turn off "log data changes" for HRP1000 and HRP1001 (from SE11->Technical settings).
Can anyone comment on any side-effects if we turn this log off?
Best regards
Kirsten

You configure the PD infotype change log in table T77CDOC_CUST and display it with program RHCDOC_DISPLAY. The PD audit log can track changes to infotypes 1000, 1001, and 1002. You may want to track changes to PD infotypes simply to ensure that everyone follows company guidelines, or you may need to implement this feature as part of a corporate governance policy. It also works in mySAP ERP Central Component
The creation of change documents is only activated for the combination of plan version, object type, and infotype/subtype you enter in this table. Only entries for which X is entered in the Active field are
considered.
if you activate the creation of change documents for all Personnel Planning infotypes, for example, the system performance deteriorates. Therefore, you should only activate the creation of change documents for the combination of plan version, object type, and infotype/subtype for which you require this function.

Use change pointers to send complete employee in HRMD_A

Hi
I need to distribute employee data from my SAP system. I want to send a Idoc every time a record in PA30 is changed. But know it only sends out a IDoc with the infotype that is changed, I need to distribute all infotype's.
Example: One person is changed in infotype IT0002. I need to send out not only IT0002 but also IT0006 and IT0008.
Is there a way to solve this?
Best Regards,
Morten

Hello Morten,
Yes, you can do it. I have done same thing in one of my interface. You need to write code into BADI.
BADI : BDCP_BEFORE_WRITE
Method : FILTER_BDCPV_BEFORE_WRITE
Basic idea is to populate internal table change_pointers with remaining infotype details.
Refer following code for reference....
BADI implemented in order to send customised data as
maintained in the distribution mdoel
METHOD if_ex_bdcp_before_write~filter_bdcpv_before_write.
Type Declaration
TYPES : BEGIN OF ts_range,
            sign    TYPE tvarv-sign,
            option TYPE tvarv-opti,
            low     TYPE tvarv-low,
            high    TYPE tvarv-high,
          END OF ts_range.
TYPES : BEGIN OF ts_group,
            int_grp     TYPE zthr_infty_subty-int_grp,
          END OF ts_group.
Internal table
DATA:
    lt_zthr_infty_subty TYPE TABLE OF zthr_infty_subty,
    lt_dist_infty_subty TYPE TABLE OF t788u,
    lt_groups           TYPE TABLE OF ts_group.
DATA:
    lt_changed_objects TYPE TABLE OF hrobjinfty.
DATA :
    lr_infty    TYPE RANGE OF t591s-infty, " Range for infotypes
    lr_subty    TYPE RANGE OF t591s-subty. " Range for subtypes.
Work Areas
DATA:
    lw_change_pointers   TYPE bdcpv,
    lw_change_pointers1 TYPE bdcpv,
    lw_text(254)         TYPE c,
    lw_infty             TYPE ts_range,
    lw_subty             TYPE ts_range,
    lw_groups            TYPE ts_group.
DATA:
    lw_zthr_infty_subty TYPE zthr_infty_subty,   "Infotype & Subtype
    lw_zthr_infty_subty1 TYPE zthr_infty_subty,   "Infotype & Subtype
    lw_dist_infty_subty TYPE t788u.              "Infotypes
DATA:
    lw_changed_objects   TYPE hrobjinfty,
    lw_changed_objects1 TYPE hrobjinfty,
    lw_changed_objects2 TYPE hrobjinfty.
Local Variables
DATA:
    lv_tabix      TYPE sy-tabix,      " Table index
    lv_cpident    TYPE cpident,       " Change pointer no.
    lv_pernr      TYPE pa0000-pernr, " Employee Number
    lv_tabname    TYPE dd02t-tabname, " Table Name
    lv_abkrs      TYPE pa0001-abkrs, " Payroll Area
    lv_infty(4)   TYPE n.             " Infotype Number
Local Constants
CONSTANTS:
    lc_e       TYPE t591s-sprsl   VALUE 'E',
    lc_i       TYPE tvarv-sign    VALUE 'I',
    lc_x       TYPE c             VALUE 'X',
    lc_7       TYPE c             VALUE '7',
    lc_p       TYPE otype         VALUE 'P',
    lc_zhrmd   TYPE edi_mestyp    VALUE 'ZHRMD_A',
    lc_eq      TYPE tvarv-opti    VALUE 'EQ',
    lc_pa(2)   TYPE c             VALUE 'PA',
    lc_begda   TYPE sy-datum      VALUE '19000101',
    lc_02      TYPE pa0001-abkrs VALUE '02',
    lc_1000(4) TYPE n             VALUE '1000',
    lc_2000(4) TYPE n             VALUE '2000'.
Clear all local variables / internal tables / Work Areas
REFRESH : lt_groups,
            lr_infty,
            lr_subty,
            lt_changed_objects.
CLEAR : lv_tabix,
          lv_abkrs,
          lw_change_pointers,
          lw_dist_infty_subty,
          lv_tabname,
          lw_groups.
Select only otypes and infotypes from distribution model
Read change infotype / subtype data
IF NOT change_pointers[] IS INITIAL.
    LOOP AT change_pointers INTO lw_change_pointers.
      lw_changed_objects = lw_change_pointers-tabkey.
Filter CE Employee if Pay-Area not '02'          ***
      IF flt_val EQ lc_zhrmd.    " Check for CE emploeyee
        SELECT abkrs
          INTO lv_abkrs
          FROM pa0001 UP TO 1 ROWS
        WHERE pernr EQ lw_changed_objects-objid
          AND endda GE sy-datum
          AND begda LE sy-datum
          AND abkrs EQ lc_02.
        ENDSELECT.
        IF sy-subrc EQ 0.
          APPEND lw_changed_objects TO lt_changed_objects.
        ELSE.
          DELETE change_pointers.
        ENDIF.
      ELSE.
        APPEND lw_changed_objects TO lt_changed_objects.
      ENDIF.    " IF flt_val EQ lc_zhrmd.
    ENDLOOP. " LOOP AT change_pointers INTO lw_change_pointers.
    lv_cpident = lw_change_pointers-cpident.
ENDIF. "IF NOT change_pointers[] IS INITIAL.
Select only otypes and infotypes from distribution model**
Select corresponding infotypes / subtypes from table    **
ZTHR_INFTY_SUBTY to create change pointers              **
CALL FUNCTION 'RH_DISTRIBUTED_INFOTYPES'
    EXPORTING
      message_type            = flt_val
      check_model             = lc_x
    TABLES
      distributed_infty_subty = lt_dist_infty_subty.
IF NOT lt_dist_infty_subty[] IS INITIAL.
Read table ZTHR_INFTY_SUBTY
    SELECT mandt                         " Client
           mestyp                        " Message Type
           infty                         " Infotype
           subty                         " Info Subtype
           int_grp                       " Change pointer group
      INTO TABLE lt_zthr_infty_subty
      FROM zthr_infty_subty AS a
      FOR ALL ENTRIES IN lt_dist_infty_subty
      WHERE mestyp EQ flt_val
        AND infty EQ lt_dist_infty_subty-infty.
    IF sy-subrc EQ 0.
      CLEAR : lw_changed_objects.
      LOOP AT lt_changed_objects INTO lw_changed_objects.
        MOVE : lw_changed_objects TO lw_changed_objects2.
        AT NEW objid.
Read all groups belongs to infotype.
          CLEAR : lw_groups.
          REFRESH: lt_groups.
          LOOP AT lt_zthr_infty_subty INTO lw_zthr_infty_subty
                  WHERE infty = lw_changed_objects2-infty
                    AND subty = lw_changed_objects2-subty.
            lw_groups = lw_zthr_infty_subty-int_grp.
            APPEND lw_groups TO lt_groups.
          ENDLOOP. " LOOP AT lt_zthr_infty_subty INTO ....
Do not create change pointer if infotype not maintained in
table 'ZTHR_INFTY_SUBTY'.
          IF sy-subrc NE 0.
            DELETE change_pointers WHERE
                        tabkey+12(4) = lw_changed_objects2-infty
                    AND tabkey+16(4) = lw_changed_objects2-subty.
          ENDIF. " IF sy-subrc NE 0.
Read all infotypes belongs to all above groups.
          LOOP AT lt_groups INTO lw_groups.
            LOOP AT lt_zthr_infty_subty INTO lw_zthr_infty_subty
                          WHERE int_grp EQ lw_groups-int_grp.
Check if change pointer already present
              READ TABLE lt_changed_objects INTO lw_changed_objects1
                  WITH KEY infty = lw_zthr_infty_subty-infty
                           subty = lw_zthr_infty_subty-subty.
              IF sy-subrc NE 0.
Check if data exist for infotype / subtype
                IF lw_changed_objects-otype EQ lc_p.
                  CONCATENATE : lc_pa lw_zthr_infty_subty-infty
                         INTO   lv_tabname.
                  SELECT SINGLE pernr
                    INTO lv_pernr
                    FROM (lv_tabname)
                   WHERE subty EQ lw_zthr_infty_subty-subty
                     AND pernr EQ lw_changed_objects2-objid.
                  IF sy-subrc EQ 0.    " Change pointer for employee
Create change pointer for infotype / subtype combination
                    ADD 1 TO lv_cpident.
                    lw_change_pointers-cpident      = lv_cpident.
            lw_change_pointers-tabkey+12(4) = lw_zthr_infty_subty-infty.
            lw_change_pointers-tabkey+16(4) = lw_zthr_infty_subty-subty.
                    lw_change_pointers-tabkey+20(8) = lc_begda.
                    APPEND lw_change_pointers TO change_pointers.
                  ENDIF. " IF sy-subrc EQ 0.
                ELSE.
Create change pointer for Org Data
                  ADD 1 TO lv_cpident.
                  lw_change_pointers-cpident      = lv_cpident.
            lw_change_pointers-tabkey+12(4) = lw_zthr_infty_subty-infty.
            lw_change_pointers-tabkey+16(4) = lw_zthr_infty_subty-subty.
                  lw_change_pointers-tabkey+20(8) = lc_begda.
                  APPEND lw_change_pointers TO change_pointers.
                ENDIF. " IF lw_changed_objects-objtyp EQ lc_p.
              ENDIF. " IF sy-sybrc NE 0.
            ENDLOOP. " LOOP AT lt_zthr_infty_subty INTO..
          ENDLOOP. " LOOP AT lt_groups INTO lw_groups.
        ENDAT. " AT NEW objid.
      ENDLOOP. " LOOP AT lt_changed_objects INTO lw_changed_objects.
    ENDIF. " IF sy-subrc EQ 0.
ENDIF. " IF NOT lt_dist_infty_subty[] IS INITIAL.
ENDMETHOD.
But make sure you maintained remaining infotypes in distribution model. I have created table zthr_infty_subty twhere I am keeping track of all infotype and subtype for which I have to send a data.. You can hardcode values in u r program if you want / if you know the all infotype for which you have to send data.
if you still have any doubt / issues let me know your email id will mail you badi-code.
Cheers,
Nilesh

Logged Changes !!

STD Program for Logged changes in Infotype RPUAUD00 is not working:doesn't show any change information..What settings do we need to set
done settings in Personnel Management >Personnel Administration >Tools >Revision >Set up change document >HR documents: Infotypes to be logged...still not working .....any help

In R/3 Release 4.7, SAP introduced an audit log to track changes to Personnel Development (PD) infotypes. The audit log for PD infotypes provides similar functionality to the well-known Personnel Administration (PA) infotype log. You configure the PA audit log on tables T585A, T585B, and T585C and display it via program RPUAUD00.
You configure the PD infotype change log in table T77CDOC_CUST and display it with program RHCDOC_DISPLAY. The PD audit log can track changes to infotypes 1000, 1001, and 1002. You may want to track changes to PD infotypes simply to ensure that everyone follows company guidelines, or you may need to implement this feature as part of a corporate governance policy. It also works in mySAP ERP Central Component (ECC).
Cheers,
TG

Creating global actions

Hi
I am presently involved in a global implementation for PA/OM. We have a global list of infotypes and there are country specific infotypes.
I had one doubt/clarification
Doubt - The action (New Hire) picks up the infogroup from which of the following usergr/ molga or the Personal Area ??
Explaination -
So I have 2 infogroups - 10 and 40
*Under usergp/ Molga - 40* - in the user profiles -
In IT 0000 under usergp/ molga 40 I assign the Personal Area to a US Personal Area i.e US01 it takes up the infotypes of MOLGA 10. Is there any way I restrict it or give an error to avoid using that PA for the usergp - 40
Thanks
Sudhir

Sikandar - A couple of quick things, we would be activating the global employee in SAP to tavel people who travel. So there would be different personnel numbers for the employee which would be tracked through various infotypes i.e. 0081, 0710, 0707 and 0715.
So it would not be different if an employee moves from India to the US or from US to India they would be tracked. They would have many personnel nos but only one person ID or global ID.
Hope this helps
Sudhir

OM Infotype change log Tracking

Hello Experts,
I have a requirement to write a custom Interface program to track the changes in OM infotype. This custom Interface will be run daily to track the changes in OM infotype if any on daily basis.
I know i can use AEDTM (Changed on) date field to track the changes but this will not be able to cover all possible scenarios. This date (AEDTM) does not get updated in SAP when an infotype is delimited. So such scenarios will be missed if i use AEDTM.
I have certain function modules which can be used to track the changes in PA infotype. But I am not able to find any function module or class or related object which can track the changes in OM infotype.
If any one of you have any idea or suggestion on this, Kindly help me.
Appreciate your help!
Rupesh

Hi Srinivas,
Thanks for your prompt reply!
As per your suggestion:-
ok here goes additional info:
tcode : bd52
message type hrmd_a
you can mention object type, table and fields for which change pointers can be activated.
So you mean I need to maintain the OM infotypes 1000, 1001, 1005, 1010, 1610 and 1641 (these are OM infotypes we need to track for changes) and all their fields in this message type view. How does the change pointer gets activated by maintaing this. Can you please brief me about this process.
then I believe you should be able to design and create a program that checks these change pointers in a batch job and transfers data
Can you pls brief me how this can be achieved through a custom program. May be u can share the Inputs from your technical teammate who has designed the program for you.
I will also discuss with my functional counterpart about this solution.
Thanks much.
Rupesh

Ok i work at a military base and there were iPod touch's given out to some units and I have found one and would like to return it but don't know the owner so is there a way to track a name with the serial number?

Ok i work at a military base and there were iPod touch's given out to some units and I have found one and would like to return it but don't know the owner so is there a way to track a name with the serial number? Or how can I find out who owns it?

No. Turn it into the military police.

Need to track deleted records only in all infotypes

Hi all,
I want to track all the deleted records only from all infotypes. PCL4 stores all the changes records. But I want only the deleted records.
Please suggest how to achieve it?

hi,
try this t.code PC00_M99_UDIR for restore the payroll results directory
RupaPrasad.

Tracking infotype changes

Hi,
I got a requirement like this. I have to send a report to client on hourly basis on infotype changes.
I do not know how to capture changes in a hour. I know how to track daily(using PCL4).
So please share your valuable experience.
Thanks,
Ravi Visarapu.

Hi Priya,
Thanks for quick reply and information.It is helpful to me but confirm me one thing.
In FM HR_INFOTYPE_LOG_GET_DETAIL what is the role of BTIME import parameter. Is it considered after that time or before that particular time.
my requirement is , with in a hour (every hour new updates whether change, delete or insert etc ).So how do I pass the from and to time limits in the functionmodule.
Appreciate your help.
Regards,
Ravi.

Are there any provisions in place for overseas military not able to buy direct from Apple Store to get an option of a track pad instead of magic mouse when buying a new iMac? It seems that the new OS is going to NEED trackpad and magic mouse will moot

I AM A PASSIONATE APPLE USER. Please don't get me wrong. I love every Apple product we have. I am just a bit discouraged that as a person living and working overseas, I do not have the same opportunity to build my Mac to my specifications. I am bound to buying the products through the Exchange. I appreciate that they are carried but when I compare to the Store, I am discouraged that there are some FREE options offered to Stateside folks not offered to AAFES/Exchange consumers. I want a track pad instead of a mouse. It seems that is where Mac technology is headed. Lion will all but REQUIRE it for many of the new features coming! Apple should offer new purchasers the opportunity for a free upgrade to a track pad!

You can provide feedback > Apple - Feedback

Tracking Infotypes

Hi Gurus,
I have an critical issue where the record maintained for infotype 0040- with 2 subtypes for 2 different dates are suddenly got vanished but for the previous month the payroll records the subtypes are available .
I checked with RPLINFC0 / HTWLINF0, It gives me a log along with the changes made in the infotype record, when i click on the dates it gives me the data with the numbers and units of 0040.
But now when i try to see the same in PA30 system shows no data is available, i am wondering where the data has vanished........I believe its not been deleted .
I was tring to run RPUAUD00 but no use as T585A,T585B,T585C is not maintained so no results even if i maintain it also it will be for future need.
Can any body please help me on retrieving the previous details.......i dont know where the data is....please help.

Hi Fedrico & Remi,
Thanks for your updates, Fedrico can you please guide me a bit more on the same i mean the process for checking it in SE16 one by one and Remi i have already gone through the threads all talk about T585A,T585B,T585C to be configured .
Yes i can consider it for future purpose but please guide me for the current scenario....please advice.
Is there any possible other way through which i can get the data of the infotype along with the user details who else could have done any changes to it if possible.

Tracking infotype chnages

plz reply
Hello,
I am coding to get fileds of infotpe changes .
I can not use standard program RPUAUD00 for my requirement.
for FM HR_INFOTYPE_LOG_GET_DETAIL it exports only itab & fields, but i need to fetch head-opera too, which i can not get from this FM.
Also why HEAD's aedtm field is showing zeros?
How to get new field values and old field values by HEADER and BELEGE.
Will appreciate your reply.
Thanks.
Edited by: rita pat on Mar 27, 2009 3:45 PM

U'll get the changed fields in the TABLES : FIELDS
CALL FUNCTION 'HR_INFOTYPE_LOG_GET_DETAIL'
EXPORTING
    logged_infotype        = logged_infotype
AUTH_CHECK             = 'X'
USE_ARCHIVE            = ' '
IMPORTING
SUBRC                  = SUBRC
TABLES
    infty_tab_before       = infty_tab_before
    infty_tab_after        = infty_tab_after
   FIELDS                 = FIELDS
To know which operation was carried out ..
If both infty_tab_before and infty_tab_after are filled then it is Update ..
If only infty_tab_after is filled then it is Insert
If only infty_tab_before is filled then it is delete .
check include .. LPA_INFTY_LOGF02 for more details ..
    case header-opera.
    when 'U'.
      append after_image.
      append before_image.
    when 'I'.
      append after_image.
    when 'D'.
      append before_image.

Military LOA tracking on PA Infotypes

Similar Messages

Maybe you are looking for