Token Value From Time Entry Rule Is Not Getting Passed To the Error Message In the Create Timecard API Call (Doc ID 1641036.1)

Last updated on AUGUST 18, 2023

Applies to:

Symptoms

On :  12.1.3 version,

ACTUAL BEHAVIOR  
---------------
Tokens value from time entry rule is not getting passed to the error message in the API call.

For example, in the self service timecard when the time entry rule is violated it shows:

Error
1. Error: The sum of hours against the standard expenditure types should always be equal tot he hours on the assignment record which is 45
2. Error: The sum of hours against the standard expenditure types should always be equal to the hours on the assignment record which is 37.5
3. The following time entry rule has violated the period maxmium (You have entered more than 37.5 hours)


For the same, the API call output shows:

 Start - Execute Deposit Process
 End - Execute Deposit Process
 Start - Message
 Message Name: ABC_OTL_STAN_HRS_MATCH
 Message Token: L_NORMAL_HRS&40
 Message: Error: The sum of hours against the standard expenditure types should
 always be equal to the hours on the assignment record which is &L_NORMAL_HRS
 Message Name: ABC_OTL_STAN_HRS_MATCH
 Message Token: L_NORMAL_HRS&45
 Message: Error: The sum of hours against the standard expenditure types should
 always be equal to the hours on the assignment record which is &L_NORMAL_HRS

and,

 Start - Message
 HXC_WTD_PERIOD_MAXIMUM
 Message Token: TER&You have entered more than 37.5 hours
 The following time entry rule has violated the period maximum (&TER)
 End - Messages

Both the seeded and custom time entry rules have this token value problem.

Development explains that:

Timestore Deposit API allows a call to Execute_deposit_process with a table type HXC_MESSAGE_TABLE_TYPE.   In case of an error, the relevant error messages are found in this table.
This table's record has member 'message_name' which holds the message code.
In addition there is a field 'message_tokens', which holds a '|' separated list of all the values for the tokens to use.

For seeded messages, including the one for TER shown, this token value should be populated.
For custom fast formulas customer should have their own code to populate the tokens.

EXPECTED BEHAVIOR
-----------------------
Expect token values to be displayed correctly.

Changes

Cause

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