A KUT field or indicator has default value YES maintained, but in a certain view, the value defaults to NO.
SAP Cloud for Customer
Reproducing the Issue
Prerequisite, you have created a KUT field (or indicator) 'ABC' (ABC represents the name). This field has several extension scenarios active.
In our example, the field behaves differently when creating a visit directly (visit view) or when creating it from an account.
- Go to the Customers work centre.
- Go to the Accounts view.
- Open any Account.
- Go to Visits tab
- Click New.
RESULT: KUT indicator is on 'NO' by default.
- Go to the Visits, Visits planner or Home page view.
- Create a new visit
Result: the field is defaulted to ‘Yes’.
You expect the field to default to 'Yes' in all cases.
This default value Yes is over written by No due to extension scenario which has been applied on the field.
For example: Scenario -
Account - General Information to Activity - General Information
Account - Sales Data to Activity - General Information
This is expected system behaviour.
Please note that extension scenarios will extend the field with that they create the relevant connections when they are enabled. This will effect the behaviour of the field(s).
Help Portal: Extension Fields
KBA , BC-DWB-REP-EXT , Extensibility , How To