Logged changes in infotype data

There is a program RPUAUD00 provided by SAP which allows us to see any changes that happens to data in an infotype through add / modify / delete. When you execute this this program and specify the employee code and infotype in the selection screen, it gives us details of when the data was changed, who changed the data and what data was changed in a particular infotype.

There are few standard infotypes like 0000, 0001, 0002 and few of your own created infotypes starting with 9 (9XXX) for which you are able to see the log through this program.

But there are certain other infotypes like 0008, 0581 for which this log is not coming.

There are some configuration or customising is to be done so that this log starts generating for these infotypes and RPUADU00 can read it.

The IMG menu path is:

Personnel Management > Personnel Administration > Tools > Revision > Set up change document

When you execute this node choose

'HR Documents - infotypes to be logged'

Add entries in this table to audit more infotypes.

Transaction class A is for HR master data, class B is for applicant data.

Extracting Daily Changes from HR Infotypes

I am looking for recommendations for extracting daily changes from HR and Payroll Infotypes to populate outbound interfaces. We will have approximately 300,000 employees active and inactive implemented in our system.

We are currently reviewing a strategy to extract records based on the Updated Date from the header portion of an infotype. Our concern is performance. The Updated Date field is not part of the primary infotype key. We have considered putting a secondary index of that field to help with performance.

Another strategy is to use the audit function to create log entries each timefields have been changed on an infotype.

Has anyone used this functionality?
Has anyone implemented HR with at least 100,000 employees? How did you tackle
this issue? What types of performance problems were encountered? Which
strategy is the most efficient?

Any information you could provide would be helpful.
We are running SAP Version 3.1G, on SUN Hardware with Solaris Operating system
over an Oracle database residing in UNIX.

I have used the audit functionality in a couple of implementations, It

sounds like you can use for your requirements.

Here is what you need to do:

1. You need to configure three tables, T585A, T585B, and T585C (if you use SM31, enter table name, do customizing, it'll take to the place in the IMG in 3.0 versions)

2. you need to run the report RPUAUD00

There are some issues you need to think about before configuring the audit
log tables;

1. You have to analyze what you need to audit, do not audit all fields on
an infotype, and by no means audit all infotypes.

2. Depending on how much you want to audit, the log report could be
extremely big, hence putting a strain in the performance of your system

3. Frequency of the report

I hope this will help you.