Hi Sagarika,

thank you for reaching out to us.

Kindly note that below are some naming conventions:

Keep names concise, avoid duplicates in namings
Good ex: P2P - SAP
Bad ex: P2P Purchase to Pay - SAP ERP

Keep coherent tree structure, meaning if a Pool contains 3 DMs for P2P, O2C, and AP, do not name the Pool 'P2P' or another name that doesn't sound like it includes all 3.

Good ex: Pool named 'SAP Prod' & Data Models named 'P2P SAP', 'O2C SAP'

Bad ex: Pool named 'SAP P2P and others' & Data Models named 'P2P SAP', 'O2C SAP'

For Data Models: a DM is usually for 1 process, so it should be named after the process. If there are several DMs for 1 process (>= 2 ERPs) then the ERP should be part of the name to reflect the scope of each DM

Good ex: Data Models 'P2P SAP' and 'P2P Oracle'

Bad ex: Data Models 'P2P 1' and 'P2P 2'

Please also check the below links for more best practices:

https://docs.celonis.com/en/data-model-best-practices.html
https://docs.celonis.com/en/best-practices--extraction.html
https://docs.celonis.com/en/best-practices-for-ml-workbench.html

We hope this helps with your request!
Best regards,
Lejla

---