Which views are available for creating Code List fields based on Value Help Views?

[#1]

Dear experts,

I am trying to create a custom field using the Key User Extensibility in S/4 HANA on premise. I am in the App "Custom Fields and Logic".

I click to create a new field, type the business content, label identifier, tooltip and select type "Code List based on CDS View" as shown here below:

When I open the search help for the Value Help View, many CDS views are available, some standard, some Z.

I don't understand what makes a view being listed in this search help. I took some Z ones appearing and replicated them exactly as they are and yet, my new CDS view don't appear in the list. I was believing this was driven by annotations in the view itself, but I start to think I am missing some piece of information here.

Please note: in my screenshot above, everything is left empty, but you can still call the search help for selecting the view, so the fact that the information is not present in it does not make any difference.

I am desperate for help: I spent a lot of time on this already and I am afraid I will not be able to sort it out on my own.

Thanks a lot in advance and have a good weekend!

Best regards,

Alberto

[georg_wilhelm · Accepted solution]

Hi Alberto,

the following types of CDS objects are supported as value help views:

1. All C1 released SAP Standard Views
2. C1 released Developer Extensibility Custom Entities
3. Key User Custom CDS Views

Best regards

Georg

[AlbertoR · Accepted solution]

Dear Georg,

Thanks a lot for your answer!

To be added that a release of category C1 can be done in ADT in Eclipse by opening the view, then navigating to Properties->API state:

[RajaGopalan]

I checked AI4ERP to determine what makes a CDS (Core Data Services) view appear in the Value Help View search help within the "Custom Fields and Logic" app in S/4 HANA.   There are some general guidelines based on standard practice:

1.Annotations: Ensure that the CDS view has the necessary annotations. Annotations such as `@ObjectModel.valueHelpDefinition: [ { entity : 'your_valuehelp_entity' } ]` might be required to enable the CDS view as a possible value help. This annotation signals that the CDS is suitable for value help functionality.

2.Interface Views: The CDS view might need to be an interface view or contain specific characteristics that allow it to be used in a user interface scenario.

3.Authorization: Make sure that the CDS view is not restricted by authorization checks that prevent it from being listed in certain contexts. It needs to have proper roles and authorizations to be visible in the UI components.

4.SAP Standards: Adhere to SAP standards and naming conventions for creating CDS views. Sometimes views do not appear if they deviate from expected standards or configurations.

5.Configuration: Check if there are configuration settings at a broader system level that impact which CDS views are available for selection. There might be administrative settings that either restrict or enable views for particular use cases.