Merged SO Not Always Kept With Active SO For A Chain Of System Merges
(Doc ID 2663501.1)
Last updated on MAY 03, 2020
Applies to:Oracle Healthcare Master Person Index - Version 18.104.22.168 and later
Information in this document applies to any platform.
On : 22.214.171.124 version, Master Index Main Component
When a chain of system merges takes place, the merged SO is not always kept with the active SO.
If for source system A, local id 111 is merged into local id 222, and then local id 222 is merged into local id 333, then under some circumstances local id 111 ends up on a different EUID to 222 and 333.
This occurs when local id 222 is on an EUID that also has an active local id from a different source system (say, source system B).
If local id 222 was the only active local id on its EUID, the system merge works as expected and all three local ids would end up on the same EUID (with 111 and 222 having a merged status).
The issue can be reproduced at will with the following steps:
1. Create three EUIDs, A, B and C, using a single source system and three local ids, 1, 2 and 3 respectively.
2. Add a second source system to EUID B for a different source. This means EUID B will have two SOs, with two different system codes.
3. Use the web service to merge local id 1 into local id 2. This will merge EUID A into B and change local id 1 to a status of merged.
4. Use the web service to merge local id 2 into local id 3. This will move local id 2 to EUID C and change its status to merged, but it leaves local id 1 on EUID B.
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