Reltio Connect

 View Only

  • 1.  Why is it an issue if a consolidated profile has more than 200 crosswalks?

    Reltio Employee
    Posted 06-07-2021 15:51
    What can I do to reduce or mitigate this?

    ------------------------------
    Chris Detzel
    Community Program Manager
    Reltio
    ------------------------------


  • 2.  RE: Why is it an issue if a consolidated profile has more than 200 crosswalks?
    Best Answer

    Reltio Employee
    Posted 06-07-2021 15:53
    This is usually a SYMPTOM of mismatched Data Model.  For Example:  Insurance companies often talk about "Customers", but they are referring to their Insurance Policies or whatever type of coverage.  In reality, a Customer may have multiple policies and customer data will be captured 5 multiple times.  If a policy is mapped to Reltio Customer, then there will be multiple customers with likely EXACT same data.  It will show as 1 Customer with multiple CROSSWALKS to various policies.

    Issue #1 --> What happens when data on only ONE of those matched policies changes?  Do all other policies change?  We would effectively update the customer and publish that update back to the source.  That could be undesirable behavior.

    Issue #2 --> What happens when one of the policies get additional customers as beneficiaries?  It could cause a major data conflict with other policies.

    In short,  Multiple policies should have 1 customer and policies should be an entity in itself.​​

    ------------------------------
    Adnan Selak
    ------------------------------

    Original Message


  • 3.  RE: Why is it an issue if a consolidated profile has more than 200 crosswalks?

    Founding Member
    Posted 06-09-2021 15:04
    We have also hit this.   it causes poor performance as # moves towards 200,  and then issues once it reaches 200.   We have this as a topic for governance going forward and can give you the scenario where we see it the most.
    A 3rd party Company is handling the Billing for multiple Hospitals.   
    The Billing company is ABC Billing company at 123 North St , city, state, zip.
    The business creates an account for every Hospital this billing company bills with the actual name of the Hospital but the address of 123 North ST.
    Reason they do this,  is they want all the accounts consolidated under the one billing company,   but need to see the different transactions for each individual hospital.    So it is one customer,  but servicing many and our users want to be able to see it 'consolidated' or by the individual accounts represented within the customer.   

    This may be due to limitation in how ERP's were originally configured, or limits in the functionality an ERP has.   As we move to a consolidated ERP this is a topic to resolve.   I believe we need to consider relationships from the ERP between accounts,  which currently we do not,  as the SAP system had over a million relationships.

    ------------------------------
    Angela Wawrzaszek
    Manager, MDM governance and Application Enablement
    ------------------------------

    Original Message


  • 4.  RE: Why is it an issue if a consolidated profile has more than 200 crosswalks?

    Founding Member
    Posted 06-11-2021 06:56
    Hi Angela,

    I have also encountered the 200+ crosswalk issue, but the root cause was due to a combination of some bugs in the application that loads the data and some issues with our config.

    In your case, wouldn't the 3rd party billing company be the "source" of the data, and therefore every transaction would be coming in on one crosswalk?

    Regards,
    Walt

    ------------------------------
    Walt Feldman
    Digital Data Lead
    Subway
    ------------------------------

    Original Message


  • 5.  RE: Why is it an issue if a consolidated profile has more than 200 crosswalks?

    Founding Member
    Posted 06-11-2021 09:50
    The 3rd Party is our Source for the 'true' customer,  and exists once.   the problem is our Business Units create a separate customer for Every location it bills to.   So if this one Billing Company bills 100 Hospitals,  then our SAP system creates 50 customers,  our JDE creates 100 Customers.  In Reltio we merge them all together because it really is 'one' location, and we hit 200 crosswalks.      Future State,  the Business should not be creating these as individual customers but as One, and then within the customer have locations related for associating the transactions against if the desire to segregate the invoicing is needed.   The customer itself should be One Account in the ERP.

    ------------------------------
    Angela Wawrzaszek
    Manager, MDM governance and Application Enablement
    ------------------------------

    Original Message


  • 6.  RE: Why is it an issue if a consolidated profile has more than 200 crosswalks?

    Founding Member
    Posted 06-11-2021 14:30
    Does every customer have some unique identifier (i.e. customer ID)? Or if the issue is location driven is there a unique site ID? If so, you may be able to apply my favorite solution ever, and make the customer and/or site ID the surrogate crosswalk value.

    ------------------------------
    Walt Feldman
    Digital Data Lead
    Subway
    ------------------------------

    Original Message


  • 7.  RE: Why is it an issue if a consolidated profile has more than 200 crosswalks?

    Founding Member
    Posted 06-14-2021 09:24

    Hi Walt we do use surrogate key's for the address.   The issue is there are 200+ unique customer id's.

     

    Angela Wawrzaszek
    MDM Manager 
    Master Data Management - Data standardization and process alignment 

    +1 315.291.3565 office 
    Angela.Wawrzaszek@Hillrom.com 

    Hill-Rom 

    hillrom.com 


     

     

     



    CONFIDENTIAL NOTICE: If you are not the intended recipient of this message, you are not authorized to intercept, read, print, retain, copy, forward, or disseminate this communication. This communication may contain information that is proprietary, attorney/client privileged, attorney work product, confidential or otherwise legally exempt from disclosure. If you have received this message in error, please notify the sender immediately either by phone or by return e-mail, and destroy all copies of this message, electronic, paper, or otherwise.




    Original Message


  • 8.  RE: Why is it an issue if a consolidated profile has more than 200 crosswalks?

    Reltio Employee
    Posted 06-14-2021 09:14
    Hi Angela,

    I would model this with customer "type".  The 3rd party should be of type "Aggregate Billing Org" or something like that.  Other customers, that get billed through the Aggregate Org, would then be setup as individual customers that are related to the Aggregate Billing Org.  If your addresses are modeled as a separate entity (Location), then all can be related to that one address.   Otherwise (if your address is a Nested/Child attribute), your solution would work temporary. You would move the issue from having too many crosswalks to having too many children entities and the overall customer entity still being very large.

    ------------------------------
    Adnan Selak
    ------------------------------

    Original Message


Related Content