Common application entities

User Experience
1

Hello Everyone,

I am building an application on top of Common Application (Common Data Model). I am seeking for clarifications from this conversation.

We have following entities.

Customer → Holds complete customer profile

Accounts → Holds customer accounts such as Bank accounts, Credit cards

Transactions → Holds debit/credit card transactions

which entities should be used to hold above data. My understanding is as follows

Common-LDM-Entity-Account-Consumer for customer profile (Individual or Company)

Common-LDM-Entity-ServiceAccount for customer accounts such as Bank accounts and credit cards

Common-LDM-Entity-Transaction for card transactions

Common-LDM-Entity-TransactionModule for single transaction insights

Any recommendations or suggestions are appreciated.

Thanks

Vinod

2

@VinodBavandlaI think you have it correct, with some special attention to the TransactionModule.

CDM is an account based model, which means that your Customer (from your EDM) indeed is an Account (CDM) and can be an organization or a natural person.

The Account (your EDM) is indeed the ServiceAccount (CDM)

If you are not interested in how your full transaction has been set-up (with all parties involved), you can use Transaction (CDM). This as the transactions are generally handled within an ERP system and you only need to get some details from it for your use-case)

3

@Ronald de Lignie has answered.

Just adding to it Transaction module sed to describe a transfer of money between parties. The transaction module includes the debit and credit parties and all intermediary agents who are involved in completing the transaction. Just to hold debit/credit transactions, Transaction is the entity you could use

4

@mohas19Thanks for your response.

Which entity is used to hold customer accounts such as Bank accounts, credit cards?

5

@VinodBavandlathe Service Account entity