Symptom
- Custom party fields (e.g., custom entries/fields in the parties tab or custom party roles) remain editable after a Lead is converted to an Opportunity or Account in SAP Cloud for Customer.
- Standard SAP behavior locks standard party fields upon lead conversion, but custom party fields are not locked.
Environment
SAP Cloud for Customer
Reproducing the Issue
- Navigate to SAP Cloud for Customer.
- Add custom party fields via Fine-Tuning → Leads → Maintain Involved Parties.
- Include custom fields and flag "Assign Party to UI" by attributing the Header Party Element
- Convert a Lead to an Opportunity or Account.
- Observe that the custom party fields remain editable, while standard fields are locked.
Cause
In SAP Cloud for Customer, parties (such as Contact, Employee Responsible, etc.) are involved in business documents like Leads, Opportunities, and Accounts. When you convert a Lead to an Opportunity (or Account, etc.), typically the lead itself becomes 'read-only' to preserve data integrity and audit trails. However, custom party fields may remain editable even after lead conversion.
The reason you can edit custom party fields after lead conversion is:
-
- Custom party roles are not part of the standard lead-to-transaction mapping. Standard parties and their fields often become locked upon conversion because they’re tightly managed by SAP and are usually referenced or copied (read-only for traceability). Custom party roles/fields, however, are not part of this tightly managed mapping. This allows flexibility for businesses to update supplemental or supporting role information, such as internal support staff, observers, or other stakeholders, even after the main lead has been converted.
- Business process flexibility. Some business processes require updates or clean-up of custom party information (for mapping purposes, reporting, or compliance) post-conversion, which would be impossible if those fields were locked down.
- SAP does not automatically restrict editability on custom-defined parties. Since these are not technically required for core lead processing or downstream processes, SAP allows them to remain open for adjustment.
Resolution
This is the current system design.
Keywords
lead conversion, custom party fields, editable fields, read-only fields, lead-to-opportunity, lead-to-account, maintain involved parties, fine-tuning, custom roles, lead header fields, converted lead, Assign Party to UI, party, closed, custom, header , KBA , LOD-CRM-LM , Lead Management , Problem
SAP Knowledge Base Article - Public