In our earlier article last month we covered Audit Trail in Oracle Apps. This article explains the extra steps needed to enable Audit Trail in Oracle HRMS Module.
Firstly read the article Audit Trail in Apps
Why are the steps for Auditing slightly different in Oracle HRMS?
This is mainly due to Date-Tracking feature which is HRMS/Payroll Specific.
For Auditing HRMS tables.....
Step 1. Check if Profile AuditTrail:Activate at site level
select fnd_profile.value('AUDITTRAIL:ACTIVATE') from dual ;
Step 2. Defined Audit Group and Audit Table in sysadmin
Step 3. Run process 'AuditTrail Update Tables' from System Administrator
Step 4. Run process 'Audit Trail Update Datetracked Tables' --From HRMS Superuser
Having followed the above steps will cause data to be created in shadow HR tables, names of these tables end with _A.
To move the data from 'shadow tables' into 'HR_AUDIT and HR_AUDIT_COLUMNS', you need to run process 'Audit Report' from HRMS Super User responsibility. The shortname of this program is PAYAUDIT.
Next you can check....
SELECT OLD_VALUE, NEW_VALUE FROM HR_AUDITS AUD, HR_AUDIT_COLUMNS ADC WHERE AUD.AUDIT_ID = ADC.AUDIT_ID AND AUD.TABLE_NAME = 'PER_ALL_PEOPLE_F' AND ADC.COLUMN_NAME = 'a column name being tested against'
That completes the Audit for tables in Oracle HRMS/Payroll.
Apps2Fusion Articles 
Comments
I am starting my work on Oracle benefits.
Can you post the flow and tables related to Oracle benefits.
Than ks in advance
Currently, the New Hire process in HRSS is split into 3 different transactions:
1 . New Hire - Step 1 - this transaction is the seeded New Hire transaction with personalization s and field level controls extension
2. New Hire Step 2 - this transaction is actually the SIT's of Applicant Details, Job History and Company Property
3. New Hire Step 3 - this transaction is actually the Assignment EIT's of Job Info
Given that HRSS does not have date tracking, I cannot complete steps 2 and 3 when the New Hire is created with a future date. There is no way for me to find the future dated new hire in order to complete steps 2 and 3.
So can you give me work around for this please
Thank you
Amita
If I understand this correctly, your challenge is that SIT and EIT are attached to PersonId and Assignment Id respectively. The current snapshot[datetr ack=sysdate] makes these two records invisible to the user.
Few Options
------- -----
1. Do not create a person after date-tracking.
You can create a physical record of Person from today itself, but the assignment's Payroll related details will be effective in future. Doing so will resolve the issue of SIT, but for EIT you will struggle to assign a future dated job in this manner.
2. Implement 1 as above, and capture Job EIT information in SIT as well. But this will be a deviation from your design.
Anothe r option worth trying is to create this person as Applicant, so that record with effective sysdate gets created in per_people_f. Following this, date-track to future to create employment.
Thanks,
Anil Passi
What is version of the applications you are using?
As SSHR not supports the date track features.But some SSHR screens facilated with the dated information.
I believe that New Hire SSHR functionality facilitates with the effective dated information in the first screen.
Are you able to perform the Steps 2 & 3 with the current dated New hire?
Regards
KP/..
The version for
RDBMS : 9.2.0.5.0
Oracl e Applications : 11.5.10.2
Yes I am able to perform the step2 and step 3 for the current dated hire ...but I have created an employee performing step1 with future effective date say 07/16/2007 then I cannnot see that employee to perform the step 2 and step 3 .
While I see that person from the core form when I alter my date tracking effective date to 07/16/2007.
- Amita
Yes my challenge is in getting the person in the SSHR listing to go further and populate the SIT AND EIT ..yes the current snapshot[datetr ack=sysdate] makes these two records invisible to the user. but in the advanced search if I try searching based on the first name , last name and hire date=07/16/2007 the result set is no data exist .
Deviation in design is not possible at this stage ....but option 2 is something I can propose on the table .is there a way I can tweak the static query used in sshr by opening up the java page in jdevloper ?
Thanks
Amita
Yes, you can extend the ViewObject. but I didn't think that was an ideal solution, primarily because BC4J extensions get applied at site level, and hence extending the VO Query must be the last option.
I also suggest you raise a SR on Metalink.
Than ks,
Anil Passi
RSS feed for comments to this post