Carrier Appointments Are Duplicating In The Database When Saved From Dock and Yard Manager Causing Application Instability (Doc ID 2211888.1)

Last updated on DECEMBER 09, 2016

Applies to:

Oracle Transportation Management - Version 6.4.1 to 6.4.3 [Release 6.4]
Information in this document applies to any platform.

Symptoms

ACTUAL BEHAVIOR
---------------
When creating appointments for shipments at a location through the dock manager, duplicate appointments are created for the respective time slot.


EXPECTED BEHAVIOR
-----------------------
It is expected that only one appointment is created.

STEPS
-----------------------
The issue can be reproduced with the following steps:

1. Navigate to Operational Planning -> Appointment Management -> Dock and Yard Managers
2. Search for the respective location
3. Schedule an appointment for a shipment at that location.
4. By querying the database, duplicate appointments are created for the same appointment start and end times.

Note: This issue only exists if you are using Internet Explorer 11 browser version compatible with Windows 10 operating system.  If you are not using IE 11 or if your computer is not on a Windows 10 platform, then this issue does not apply.

 

Note:  Once duplicate appointments are created, the following application instability is observed:

a. Trying to block or unblock an appointment slot AFTER the duplicated appointment and saving the change will not persist the change to the database. The issue is magnified if this is attempted more than once on the same time slot (as each time this is tried, a new record is created in the APPOINTMENT table with IS_BLOCKED=Y. However, the change is not seen on the screen.

b. When an issue of duplicated appointments happens, you can run a delete statement from the back end to remove one of the duplicate rows. Here is the behavior observed if you delete duplicate rows manually from the database:
b1. If for example, the user tried to block an appointment slot AFTER the duplicated appointment MORE than once (issue described in b), then the issue will still exist for that time slot as there are duplicated rows in APPOINTMENT table.

b2. If for example, the user tried to block an appointment slot AFTER the duplicated appointment ONLY once, then the issue (described in b) will no longer occur once the duplicated appointment is deleted, since only one unique row will remain for the time slot.

c. Trying to block or unblock an appointment BEFORE the duplicated appointment will work fine with no issues

 

Cause

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