Showing results for 
Search instead for 
Did you mean: 

Gateway Entity and Property Names

0 Kudos

Hello Experts,

As per the following URL, it is recommended to name entities and entity properties using Upper Camel Case.

Creating High-Quality OData Services - SAP NetWeaver Gateway Foundation (SAP_GWFND) - SAP Library

UI developers in our team are recommending to use lower camel case names for properties and upper camel case names for entities to enable UI developers to distinguish between properties and entities.

Can you provide your feedback.

Can you please help us find more information on the following:

1. Why does SAP recommend Upper Camel Case to name entities and entity properties?

2. What are the advantages of doing so from a design, implementation as well as integration perspective?



Accepted Solutions (1)

Accepted Solutions (1)

Active Contributor
0 Kudos


"Naming Conventions" are just conventions as the name suggests. Their aim is better readability and usability by consumers. Beyond that, there will not be any specific reasons. Functionality/Performance will not be affected by naming conventions.

Within OData service, I do not find a specific use case to differentiate between an Entity and a Property. They are easily distinguishable if you know OData URL conventions. URI Conventions (OData Version 2.0) · OData - the Best Way to REST

But again, Frontend developers are actual consumers of your OData service. If they have a preference, there is nothing wrong in following it.



Answers (0)