Documentation
Contacts
CRM Contact represents a person associated with an Account and keeps the person connected to the shared AkshaERP Business Partner contact foundation.
What CRM Contact is for
Use CRM Contact for a person who belongs to a CRM Account/customer relationship. The contact combines reusable Business Partner contact identity with CRM-specific relationship fields such as status, preferred channel and last/next contact dates.
A Contact must belong to an Account during creation. The active edit screen locks the Account selector so users do not casually move a person and their CRM context from one customer to another.
Quick reference
Contact operating summary
| Area | Reviewed behavior |
|---|---|
| Required on save | Account, Contact Name and Status. |
| Account relationship | CRM Account is mandatory during create and fixed in the active edit screen. |
| Shared identity | New CRM Contact creation creates the Business Partner contact under the Account Partner when needed. |
| Role | Selected from maintained Partner Contact Roles. |
| Status | Selected from Value Set CRM_CONTACT_STATUS_CODE. |
| Communication | Email, Phone, WhatsApp and Preferred Channel are available on the active form. |
| Actions | Save and Close. The active Contact screen has no additional Actions menu. |
Contact fields
| Field | Requirement | Meaning / significance |
|---|---|---|
| Account | Hard save requirement | CRM Account/customer the person belongs to. Disabled during edit after relationship is established. |
| Partner | Derived / read-only | Underlying Business Partner/customer identity associated with the selected Account. |
| Salutation | Optional fixed choice | Reviewed values: Mr, Ms, Mrs, Dr and Prof. |
| Contact Name | Hard save requirement | Person name used throughout CRM relationship context. |
| Role | Optional LOV | Maintained Partner Contact Role rather than an arbitrary ungoverned classification. |
| Designation | Optional | Job title/designation. |
| Department | Optional | Department or functional area at the customer. |
| Optional | Contact email. | |
| Phone | Optional | Telephone number. |
| Optional | WhatsApp-capable contact number. | |
| Preferred Channel | Optional free text in active UI | Preferred engagement channel recorded for CRM users. |
| Status | Hard save requirement | CRM Contact lifecycle/status from the maintained CRM_CONTACT_STATUS_CODE Value Set. |
| Last Contact Date | Optional date | Most recent relationship touchpoint reference. |
| Next Contact Date | Optional date | Planned next relationship touchpoint reference. |
| Description / Notes | Optional | Relationship-specific notes. |
Contact lookup sources
| Control | Source | Behavior |
|---|---|---|
| Account | CRM Accounts | Select the customer relationship for the Contact. |
| Role | Partner Contact Roles | Provides controlled role labels/codes. |
| Status | Value Set CRM_CONTACT_STATUS_CODE | Available Status choices follow active application setup. |
Business Partner synchronization
When CRM creates a new Contact, it creates the corresponding Business Partner contact under the selected Account’s Partner and then creates the CRM Contact extension.
Editing supported identity/communication fields such as Contact Name, Email, Phone, WhatsApp and Preferred Channel updates the Business Partner contact layer as well as the CRM-specific extension where applicable.
Contact actions
| Action | What it does |
|---|---|
| Save | Creates or updates the Contact and returns to the Contact list / saved record path. |
| Close | Returns to the Contact list without using Save. |
- Account is required before Contact creation.
- Contact Name is required.
- Status is required.
- The selected Account determines the Business Partner under which the contact identity is created.
- When a pre-existing Business Partner contact is used by server-side flows, the service verifies that it belongs to the same Partner as the CRM Account.
- Account/Partner is not changed for an existing CRM Contact through normal edit.
Downstream impact
- Opportunity can link a CRM Contact belonging to the selected Account.
- Opportunity quick Call/Email/WhatsApp actions can use selected Contact communication details.
- Account/Contact context provides the person-level relationship behind a commercial Opportunity.
Common tasks
Contact task guide
| Task | Recommended steps |
|---|---|
| Add a new customer person | Create Contact → select Account → enter Contact Name/Status → add role and communication details → Save. |
| Record the main job context | Use Role, Designation and Department to explain why the person matters to the relationship. |
| Plan next follow-up | Maintain Next Contact Date and create a CRM Activity when a scheduled auditable follow-up is needed. |
| Correct customer assignment | Do not edit an existing Contact into another Account; correct the relationship using the appropriate customer/contact process. |
Troubleshooting
Contact issues
| Symptom | What to check |
|---|---|
| Contact will not save | Check Account, Contact Name and Status. |
| Account selector is disabled | This is intentional for an existing Contact. |
| Status list is unavailable | Check CRM_CONTACT_STATUS_CODE Value Set setup and active values. |
| Partner appears read-only | Partner is derived from the selected CRM Account/customer relationship. |
Related pages
Frequently asked questions
Can a Contact exist without an Account?
Not through the reviewed CRM Contact creation flow. Account is required.
Can I move a Contact to another Account?
Not through normal edit. The Account/Partner relationship is locked for an existing Contact.
Where does Contact Status come from?
The active screen loads it from Value Set CRM_CONTACT_STATUS_CODE.