You can create an opportunity without an account. However, after saving the opportunity, the system automatically adds an empty party with role Account to the Involved Parties facet.
SAP Cloud for Customer
Reproducing the Issue
- Go to the Business Configuration work center.
- Search for the Opportunities activity.
- Click in Involved Parties.
- Delete the checkbox Mandatory in the row Account.
- Go to the Sales work center.
- Go to the Opportunities view.
- Click New.
-> You will now see that the Account field is not mandatory.
- Maintain all other mandatory fields.
- Click Save and Open.
- Go to the Involved Parties facet.
RESULT: You will find an empty row with party Account.
The system always creates the initial account instance even when you remove the mandatory flag in BC.
This is because we have to remain compatible for other customers who rely on the fact that there is always a party instance existing no matter what are the settings in BC. There are various use cases where PDI implementations rely on such initial instances. Moreover, some UIs create initial instances, e.g. when Code List Restriction default values are used, etc.
Thus, there are various reasons why SAP decided to keep the initial instance. It is not causing any harm to the business processes.
This empty party role can manually be deleted by clicking on the bin icon next to the party role.
Moreover, this initial instance can also be deleted with an own small PDI implementation, for example the PDI could check for the initial account instance during before-save and delete it.
opportunity, account, party role, involved parties, , KBA , LOD-CRM-OPP , Opportunity Management , LOD-CRM-ACC , Account , How To