Timecard Creation HXC_TIMESTORE_DEPOSIT API Does Not Set Translation_Display_Key values (Doc ID 750188.1)

Last updated on JULY 15, 2016

Applies to:

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

Goal

The translation key is not getting populated for timecards created using the hxc_timestore_deposit API. However, it does get populated for timecards created via self service and timekeeper. We would like to know why this column is not getting set by the API's and maybe get some insight on how this column is used.

Solution

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms