My Oracle Support Banner

Retro Timecard Adjustments Are Posted Against the Wrong Operating Unit (Doc ID 1924940.1)

Last updated on JUNE 29, 2017

Applies to:

Oracle Time and Labor - Version 12.1.3 and later
Information in this document applies to any platform.

Symptoms

On :  12.1.3 version,

Find that when processing a Retro Adjustment timecard, that it is posted against an incorrect Operating Unit



 

Scenario:

Operating Units:


Responsibility: XXX Time Entry
MO: Operating Unit: XXX
ORG_ID: 86

Responsibility: ZZZ Time Entry
MO: Operating Unit: ZZZ
ORG_ID: 90


Employee

 
HXC_TIME_ATTRIBUTES table, there are a total 10 records (both of which are Correct)

 

Employee

 

In the HXC_TIME_ATTRIBUTES table, there are in total 20 records.


 

Steps to Reproduce:
The issue can be reproduced at will with the following steps:

1. Log into OTL responsibility tied to Operating Unit XXX
2. Submit a timecard
3. Do a back dated organization change on the employee's HR assignment (associated with ZZZ)
4. Log into OTL responsibility tied to Operating Unit B and update the timecard created in STEP 1. Change existing time details entered and save.


Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.