Fan identity data integration and unification

• US 9,652,740 B2
• Filed: 12/30/2014
• Issued: 05/16/2017
• Est. Priority Date: 12/30/2014
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP SE
• Inventors: Janarthanam, Baskaran, Jain, Divyesh, Prabhu, Rajesh
• Primary Examiner(s): Stevens, Robert
• Application Number:
  US14/585,191
• Publication Number:
  US 20160188685A1
• Time in Patent Office: 868 Days
• Field of Search: 707602
• CPC Class Codes: G06F 16/2358 Change logging, detection, and notification replication G06F16/27
• CPC Class Codes: G06F 16/254 Extract, transform and load [ETL] procedures, e.g. ETL data flows in data warehouses
• CPC Class Codes: G06F 16/9535 Search customisation based on user profiles and personalisation
• CPC Class Codes: G06Q 10/10 Office automation; Time management

Abstract

An analytical request for information that includes queryable attributes mapped to corresponding fields of customer records from in-memory database of a number of data sources is received. Semantic mapping of the queryable attributes to the corresponding fields of the customer records is resolved according to semantic mapping metadata. A query that includes the corresponding fields is generated and over the in-memory database views and a number fan records each representing a unique fan entity. Fan related data is retrieved from the number of fan records and the in-memory database views based on the executed at least one query. Upon executing the query, at runtime the in-memory database views are dynamically integrated with the number fan records based on a cross-reference table linking the in-memory database views with the number of fan records based on a fan identifier.

Claims

1. A computer implemented method to retrieve fan related data from a fan identity platform, the method comprising:

receiving an analytical request for information that includes one or more queryable attributes mapped to corresponding one or more fields of one or more customer records from one or more in-memory database views from a plurality of database views of a plurality of data sources;

resolving a semantic mapping of the queryable attributes to the corresponding one or more fields of the one or more customer records according to semantic mapping metadata;

upon resolving the semantic mapping, generating at least one query at includes the corresponding one or more fields of the one or more customer records;

a processor executing the at lean(one query over the one or more in-memory database views and a plurality of fan records each associated with an unique fan entity; and

retrieving fan related data from the plurality of fan records and the one or more in-memory database views based on the executed at least one query.

2. The method of claim 1 further comprising:

at runtime, dynamically integrating the one or more in-memory database views with the plurality fan records based on a cross-reference table linking the one or more in-memory database views with the plurality of fan records based on a fan identifier.

3. The method of claim 1 further comprising generating the plurality of fan records by:

receiving a first customer record from a first data source from the plurality of data sources;

receiving a second customer record from a second data source from the plurality of data sources;

determining whether the first customer record matches the second customer record based on a plurality of unification rules; and

upon determining that first customer record matches the second customer record, unifying the first customer record and the second customer record into a first fan record from the plurality of fan records according to precedence metadata, wherein the precedence metadata specifies level of accuracy of the first data source compared to second data source.

4. The method of claim 3, wherein unifying the first customer record and the second customer record into the first fan record according to precedence metadata further comprises:

loading attribute values of the first customer record or the second customer record to corresponding attributes of the first fan record, wherein corresponding attributes of the first fan record are determined based on attributes mapping metadata.

5. The method of claim 3 further comprising:

upon determining that first customer record and the second customer record are not matching, generate a second fan record from a plurality of fan golden records by loading attribute values of the second customer record to corresponding attributes of the second fan record, wherein corresponding attributes of the second fan record are determined based on attributes mapping metadata.

7. The method of claim 3, wherein determining whether the first customer record matches the second customer record based on the plurality of unification rules further comprises:

when the first data source and the second data source are related systems and when the first customer record and the second customer record have same identifier, determining that the first customer record matches the second customer record.

8. The method of claim 3, wherein determining whether the first customer record matches the second customer record based on the plurality of unification rules further comprises:

resolving fan entity represented by the first customer record and the second customer record based on fuzzy relationships discovered in the plurality of data sources.

6. The method of claim wherein determining whether the first customer record matches the second customer record based on the plurality of unification rules further comprises:

when a set of attributes in the first customer record shares values with a corresponding set of attributes in the second customer record, determining that the first customer record and the second customer record are matching.

9. A computer system to retrieve fan related data from a fan identity platform, the system comprising:

a memory to store computer executable instructions;

at least one computer processor coupled to the memory to execute the instructions, to perform operations comprising;

receiving an analytical request for information that includes one or more queryable attributes mapped to corresponding one or more fields of one or more customer records from one or more in-memory database views from a plurality of database views of a plurality of data sources;

resolving a semantic mapping of the queryable attributes to the corresponding one or more fields of the one or more customer records according to semantic flapping metadata;

upon resolving the semantic mapping, generating at least one query that includes the corresponding one or more fields of the one or more customer records;

a processor executing the at least one query over the one or more in-memory database views and a plurality of fan records each associated with an unique fan entity; and

retrieve fan related data from the plurality of fan records and the one or more in-memory database views based on the executed at least one query.

10. The system of claim 9, wherein the operations further comprise:

at runtime dynamically integrating the one or more in-memory database views with the plurality fan records based on a cross-reference table linking the one or more in-memory database views with the plurality of fan records based on a fan identifier.

11. The system of claim 9, wherein the operations further comprise:

receiving a first customer record from a first data source from a plurality of data sources;

receiving a second customer record from a second data source from the plurality of data sources;

determining whether the first customer record matches the second customer record based on a plurality of unification rules; and

upon determining that first customer record matches the second customer record, a processor unifying the first customer record and the second customer record into a first fan record from the plurality of fan records according to precedence metadata, wherein the precedence metadata specifies level of accuracy of the first data source compared to second data source.

12. The system of claim 11, wherein unifying the first customer record and the second customer record into the first fan record according to precedence metadata further comprises:

loading attribute values of the first customer record or the second customer record to corresponding attributes of the first fan record, wherein corresponding attributes of the first fan record are determined based on attributes mapping metadata.

13. The system of claim 11, wherein the operations further comprise:

upon determining that first customer record and the second customer record are not matching, generate a second fan record from a plurality of fan golden records by loading attribute values of the second customer record to corresponding attributes of the second fan record, wherein corresponding attributes of the second fan record are determined based on attributes mapping metadata.

14. The system of claim 11, wherein determining whether the first customer record matches the second customer record based on the plurality of unification rules further comprises:

when a set of attributes in the first customer record shares values with a corresponding set of attributes in the second customer record, determining that the first customer record and the second customer record are matching.

15. A non-transitory computer readable medium storing instructions thereon, which when executed by a processor cause a computer system to:

receive an analytical request for information that includes one or more queryable attributes mapped to corresponding one or more fields of one or more customer records from one or more in-memory database views from a plurality of database views of a plurality of data sources;

resolve a semantic mapping of the queryable attributes to the corresponding one or more fields of the one or more customer records according to semantic mapping metadata;

upon resolving the semantic mapping, generate at least one query that includes the corresponding one or more fields of the one or more customer records;

execute the at least one query over the one or more in-memory database views and a plurality of fan of records each associated with an unique fan entity; and

retrieve fan related data from the plurality of fan records and the one or more in-memory database views based on the executed at least one query.

16. The computer readable medium of claim 15, wherein the instructions when executed by the processor cause the computer system further to:

at runtime dynamically integrate the one or more in-memory database views with the plurality fan records based on a cross-reference table linking the one or more in-memory database views with the plurality of fan records based on a fan identifier.

17. The computer readable medium of claim 15, wherein the instructions when executed by the processor cause the computer system further to further generate the plurality of fan records by:

receiving a first customer record from a first data source from the plurality of data sources;

receiving a second customer record from a second data source from the plurality of data sources;

determining whether the first customer record matches the second customer record based on a plurality of unification rules; and

upon determining that first customer record matches the second customer record, unifying the first customer record and the second customer record into a first fan record from the plurality of fan records according to precedence metadata, wherein the precedence metadata specifies level of accuracy of the first data source compared to second data source.

18. The computer readable medium of claim 17, wherein unifying the first customer record and the second customer record into the first fan record according to precedence metadata further comprises:

loading attribute values of the first customer record or the second customer record to corresponding attributes of the first fan record, wherein corresponding attributes of the first fan record are determined based on attributes mapping metadata.

19. The computer readable medium of claim 17, wherein the instructions when executed by the processor cause the computer system further to:

upon determining that first customer record and the second customer record are not matching, generate a second fan record from a plurality of fan golden records by loading attribute values of the second customer record to corresponding attributes of the second fan record, wherein corresponding attributes of the second fan record are determined based on attributes mapping metadata.

20. The computer readable medium of claim 17, wherein determining whether the first customer record matches the second customer record based on the plurality of unification rules further comprises:

when a set of attributes in the first customer record shares values with a corresponding set of attributes in the second customer record, determining that the first customer record and the second customer record are matching.