My Oracle Support Banner

GetResponseTime Method Of FS Holiday API Service Business Service Produces Different Output In 20.11 and later Than In IP14 (Doc ID 2850161.1)

Last updated on FEBRUARY 23, 2022

Applies to:

Siebel CRM - Version 20.11 and later
Information in this document applies to any platform.

Symptoms

After upgrading from IP14 to 21.5, it was reported that GetResponseTime method of "FS Holiday API Service" business service produces different results than in IP14, even if the same input arguments are used.

Issue was reproduced by support in standard application ( 21.5, 21.10, 21.11 versions) with steps:

1. Set the 24hours flag for ENU locale in Administration data -> Locale and restart the siebel services.
2. Create a service schedule record in Administration Service -> Schedule:

Monday               00:00   -> 23.59
Tuesday              00:00   -> 23.59
Wenesday           00:00   -> 23.59
Thursday             00:00   -> 23.59
Friday                 00:00   -> 23.59
Saturday             00:00   -> 23.59

Note the row_id of the schedule record

3. Go to Administration Business Service -> Simulator and test the GetResponseTime method of "FS Holiday API Service" BS using the following input arguments:

 Start Time=10/15/2021
 Response Time=1
 Time Zone="(GMT+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna"
 ServiceCalendarId= the id of the service schedule record created in step 2
 Priority=1-ASAP
 Time Unit=Days

 
4. Press Run and check the Committed Time output.


In 21.x the results are different depending on the SADMIN time zone:
 
 e.g
 
a. SADMIN time zone: GMT -4    Committed Time = 10/16/2021 00:00:00
b. SADMIN time zone: GMT -8    Committed Time = 10/16/2021 00:00:00
c. SADMIN time zone: GMT +1    Committed Time = 10/15/2021 23:59:00
d. SADMIN time zone: GMT        Committed Time = 10/16/2021 00:00:00
e. SADMIN time zone: GMT +2   Committed Time = 10/16/2021 00:00:00
 
So, in 21.x when the user time zone is the same as the Time Zone entered as input parameter the Committed Time is "10/15/2021 23:59:00". In all other cases the Committed Time is "10/16/2021 00:00:00".
In IP4, no matter what time zone has the testing user, the result is always Committed Time = "10/16/2021 00:00:00".

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.