Last updated on JULY 13, 2016
Applies to:PeopleSoft Enterprise HCM Time and Labor - Version 9.1 and later
Information in this document applies to any platform.
Expecting an exception to be generated if Rapid Time specifies a Combo Code that isn't in the account code table. Inserts the value into Reported Time but doesn't also insert it into the acct_cd_tbl. So now if they try to modify the time on the timesheet they cannot as they get an error. Why do we have the TLX00110 invalid combo code exception if we never throw it?
Verified the issue by duplicating issue on internal system and recreated the following, no exception generated from Rapid Time but time entered into reported time table. If user tries to modify this time using the timesheet they cannot as the timesheet throws an error. Time Admin creates payable time but also doesn't insert the transaction into the acct_cd_tbl to allow it to be valid on the timesheet in the future. If we are not going to throw an exception for this scenario how does the entry make it into the acct_cd_tbl for future use?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms