3614981 - Code List Restriction Not Applied in the Advanced Search of an OWL View

After create a new custom field (type list) KUT or PDI it is expected that the restriction should happen in the advanced search of an OWL view. E.g. Accounts OWL.

SAP Cloud For Customer

1. Create a custom field in the Sales Data BO.
2. Create a new Code List Restriction (CLR) selection, the BO Sales Data.
3. Select the field created.
4. Create the restriction.
5. Add the field in the Advanced Search. E.g. Accounts OWL.
6. With the restriction enabled, the user can see all values, even those already restricted by the CLR.

The restriction is based on the BO selected. In this case, Sales Data.
For the Accounts OWL, in this case the field needs to be added in the Accounts OWL, and created via CLR to the same object Accounts OWL.

Create a CLR selecting the appropriate BO, in this case accounts.

The Sales Data BO is used in the creation of new objects in the system.

SAP Help Portal Configure Code List Restrictions 

Restriction Issue; BO Selection; Field Addition; Account Object; Field Type List (KUT, PDI); System Configuration; SAP Help Portal; Create New Custom Field; Sales Data Object; Code List Restriction Configuration; Object-Specific Restrictions; View Restrictions; Accounts OWL Configuration , KBA , AP-RC-UIF , C4C UI Framework , LOD-LE-RC-CLR , Code List Restriction , How To