Hi Stan,
This meeting is schedule for 10am 26JUL17 and wanted to confirm that we are attending. Here is the background information that prompted the meeting with the Orion team:
From: Sara Betz Sent: Friday, June 23, 2017 2:16 PM To: Kathy Cobb Cc: Carol Gretz ; Fleet Plymire ; Shawn Guy ; Ben Lieb ; Neal Haggard ; Todd Hamrick Subject: RE: JMP Store/Duplicate Records
Hi Kathy-
Orion team has the largest share of work for the interim solution.
+ Fleet, Shawn, Ben and Neal – What is the effort on making the update to Orion Staging as an interim solution until JOI is in place? More than would be worthwhile for a 6 mo stopgap?
Thanks
Sara
From: Kathy Cobb Sent: Wednesday, June 21, 2017 2:43 PM To: Sara Betz <Sara.Betz@sas.com> Cc: Carol Gretz <Carol.Gretz@jmp.com> Subject: RE: JMP Store/Duplicate Records
Thank you Sara for sharing this information with us. As mentioned we don’t have a definite timeline for the initial phase of the JOI project but looking towards 01Jan2018. We will review the information below. Please advise if an interim process will be implemented.
Kathy
From: Sara Betz Sent: Tuesday, June 20, 2017 2:06 PM To: Carol Gretz <Carol.Gretz@jmp.com>; Kathy Cobb <Kathy.Cobb@jmp.com> Subject: FW: JMP Store/Duplicate Records
FYI
From: Sara Betz Sent: Thursday, June 08, 2017 4:09 PM To: Todd Hoffman <Todd.Hoffman@jmp.com>; John Jones <John.Jones@jmp.com> Cc: Todd Hamrick <Todd.Hamrick@sas.com>; John Stille <John.Stille@sas.com>; Jennifer Clayton <Jennifer.Clayton@sas.com>; Fleet Plymire <Fleet.Plymire@sas.com>; Shawn Guy <Shawn.Guy@sas.com> Subject: JMP Store/Duplicate Records
Hi John & Todd –
We’ve been meeting with Carol Gretz, Ashley Prince and Kathy Cobb every two weeks to discuss improvements to the JMP Store. One issue that we have been discussing is the prevalence of duplicate customer records as a result of how the current Orion integration is setup. We met with the Orion team to request a change to Orion Staging to fix the issue. Instead of updating Staging, they suggested it would be better tackled as part of the JOI (JMP Orion Integration) project. Below is more information on the problem and proposed solution. I would be interested in knowing more about your timelines for JOI. If they are in the distant future, we may want to circle back on an interim fix with Orion team – as I know this is causing pain for JMP, Contracts and CDM Team.
Background
For a traditional/offline order, Sales enters the company record in Orion and it is fed down to GIDB. Contracts may change the company name they use on the contract, but it is still just one company record shared by the two systems. With the Store, we’re seeing duplicate CDHub records come in from Orion because Orion Staging does not store/pass the CDHub IDs. Instead of updating the existing CDHub record to add an “Orion” name and indicate Orion is using the record, it is creating a duplicate company record.
Here is an example from a JMP order:
- Customer entered “VA Medical Center”. That is what is printed on the Order Confirmation and in their SETINIT
- SAS Store creates CDHub record 15228012 and passes the order to Orion, GIDB and Oracle.
- GIDB and Oracle use/accept the CDHub record 15228012 and cleanse/change the name, as desired. So record 15228012 is in use by Digital Platform, GIDB, Oracle with these names:
- SAS_STD Name - Houston VA Medical Center
- Legal Name - Houston VA Medical Center
- AKA Name – VA Medical Center
- Orion Staging does not have a mechanism to accept CDHub IDs, so it identifies it as a ‘new’ customer. The Orion users matches it to D&B record in Staging with the name “Houston Michael E Debakey VA Medical Center” and sends it to CDHub. It creates a second CDHub record 15238112 that is only being used by Orion with these names:
- SAS_STD Name – Houston Michael E Debakey VA Medical Center
- Orion Name - Houston Michael E Debakey VA Medical Center
Instead of creating a second CDHub record, we would like Orion to update the existing CDHub record to add the “Orion Name” (which is protected and only used by Sales). The duplicate records are creating a lot of work for back-end clean-up and confusion in reporting.
Proposed Solution
We would like Orion to accept the CDHub IDs from SAS Store order and pass them into CDHub to update the existing record – rather than create new. Fleet & Shawn suggested it be considered part of the JOI project. They envision a solution where SAS Store passes orders to JMP team instead of Orion Staging….and then JMP would pass the orders directly into Orion (bypassing Staging, it sounds)? If that is the case, then we would want to add CDHub IDs to the views used by JMP, so you could include them in passing the order to Orion.
Not sure of the timeline to implement, but we’re happy to help with the design of that work when the time comes.
Thanks
Sara
