3489783 - Troubleshooting Code List Restriction (FAQ)

In this knowledge-based article, you can analyze known issues related to the Code List Restriction (CLR) topic and resolve them.

Help Portal

SAP Cloud For Customer

Below are some references to documents about Default Value:

KBA 2584865 - Field Has A value Filled Already Then Default Value Does Not Work
KBA 2704064 - Defaulting Will Not Work As Expected If User Is Assigned With Multiple Business Roles
KBA 3065383 - Default Value Not Working For Code List Restriction With Business Role 
KBA 2566873 - Code List Restriction Functionality For A Default Value Will Work In Quick Create And List Modifications (Add row) 
KBA 2596029 - Code List Restriction Created At Later Date Takes Precedence And Defaulting Would Be Considered
KBA 2775193 - Defaulting Is Not Supported In Contacts Quick Create

Below are some references to documents about Code List Expected Behaviors:

KBA 3504495 - PDI Field Does Not Appear As Option In Code List for Code To restrict 

FAQ (Frequently asked questions) on Code list restriction:

1. Which field can be used as a control field? Some fields are not available as controlling field, which, creating a new code list restriction.
    Ans: Only business field (not all fields) exposed by application team or extension field of type code (list) or indicator can be used as a control field.

2. Which field can be used as a code to restrict field? Some fields are not available as code to restrict field which creating a new code list restriction.
    Ans: Only Code fields (list) exposed by application team or extension field of type can be used as code to restrict field while creating a code list restriction. If any Standard field is not exposed, please contact SAP.

3. Code list restriction is not working for a field with control field.
    Ans: If control field is not present in the screen, then code list restriction will not be applied.

4. Code to restrict field is showing wrong/incorrect values and not respecting the values which are maintained.
    Ans: First verify if the same code to restrict field is controlled by more than one control field then the values will be the intersection of all the code list restriction maintained or in other words it will be the common values of all code list restriction.

5. Any particular screen where CLR does not work?
    Ans:  Code list restriction does not work in Contacts advance search.

6. Does code list restriction work in offline mode?
   Ans: Yes, code list restriction works in offline mode.

7. Where Code list restriction default value works?
   Ans: Default value only works on quick create screen add row (list modification) and not on advance search or TI (thing inspector).

8. Default value is not working for a field in quick create with control field.
    Ans: Sometimes the default value does not work with control field when control field is changed due to missing round trip, so external round trip like pressing the ‘enter’ key is required to set the default value.

9. Where all code list restriction works?
    Ans: Code list restriction basically works on quick create, advance search and TI (thing inspector) screen.

10. Code list restriction in not working in Silverlight.
    Ans: Code list restriction works in HTML5 and RUI. We are not supporting in Silverlight.

11. In code list restriction quick create after selecting some business object the controlling field screen got changed and instead of business field and extension field, custom field is shown.
    Ans: When user selects a custom Business object (Custom BO)/ PDI created business object, then controlling field shows the custom field OVS (object value selector) in which all the Code/List or indicator fields are displayed.

12. In code list restriction, no default value is maintained, even then some default values are set in quick create.
    Ans: Check if some default values are set using BC (Business configuration) fine-tuning, or any default value is set by corresponding application team.

13. Some values in code list restriction are not restricted (unchecked), even then it is not shown in UI.
    Ans: Check if there is any context binding done in UI designer to restrict some values.

14. Some fields are not coming as code to restrict field while creating a new code list restriction even if it is code type.
     Ans: If the field is standard field (fields provided by SAP), then application team has to expose the field if they want to allow creating any code list restriction for that field. Only the field exposed by the corresponding application team will be visible. If it is a valid requirement, then please contact SAP.

15. In code list restriction TI → Default values tab, it is showing codes/technical name/garbage value.
     Ans: Just check if the value is restricted in restriction tab, if so then user has previously saved a default value which was restricted, so it is showing code values instead of description. So please maintain the correct default value which is not restricted.

16. In any TI (Thing inspector), the field is showing code value/garbage value instead of description for which code list restriction is maintained.
    Ans: This usually happens when a value is saved and later on a code list restriction is created for this field and the value is restricted. In this case, it is advisable to edit the TI and change the value to a valid one.

17. In code list restriction TI, one extra column is coming named ‘Type’.
    Ans: For code field of having List ID field (same field used in many work center view, example category field in activity BO), we are showing one extra column to handle List ID case so that the restriction in different work center view will work properly. 

18. Is CLR works in TI facet area?
    Ans: It works, if both code to restrict and control field are in facet area only. 


C4C V1 and CNS V2
Code List Restrictions

codelistrestriction;CLR;default value; NGAP; V2; CNS; , KBA , LOD-LE-RC-CLR , Code List Restriction , How To