Skip to Content

Naming recommendations for SAP HANA

Aug 07, 2017 at 02:36 PM


avatar image

Hello SAP Community

We are discussing naming conventions for a SAP HANA project. Unfortunately I did not find any recommendation by SAP using search engines.
Except this old thread with broken links:


Are there naming conventions from SAP that we sould use:

  • in general (any scope within SAP HANA)
  • for any design- runtime objects (SAP HANA)?
  • Vairables

I did see that Microsoft abandoned Hungarian notation (Ungarische Notation) in favor of Clean code. This I like a lot and think it can be used for SAP Projects too.

Still my co-workers would like to use prefixes - are they recommended by SAP?

I did see CA_ for Calculation Views, etc. is there a list for all objects somewhere?

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

3 Answers

Jelena Perfiljeva
Aug 07, 2017 at 06:22 PM

I'm not sure it makes any difference with regards to naming conventions whether it's S/4HANA or not. Of course, there are new object types added but that may not change the overall strategy. It is a good opportunity though to review and update your internal naming conventions.

I'd suggest to check out the DSAG ABAP Guidelines (should be available online) for general guidance on the variable names. Our guidelines used to suggest using prefixes such as itab but you'd alo find similar guidance in ABAP literature years ago. After a revision 2-3 years ago, this is no longer required and was replaced simply with "descriptive name". Personally, I have no strong preference either way and as long as you don't use complete nonsense like "itab1" it's fine with me. (You should find a very long and heated debate on Hungarian notation on SCN few years ago, use Google.)

Regarding the object names - do what works best for your organization. E.g. we usually use a module as a prefix, like ZSD... It is so that we can easily identify which area the program belongs to and which person to ask about it. But this may not be helpful for other companies. In any case, make sure it's something descriptive and lends itself to easy searching. Personally, I don't find that using the object type (like RPT for a report) in the name is beneficial but again, that's just my preference.

Show 3 Share
10 |10000 characters needed characters left characters exceeded

I agree with that, specifically with the last sentence.

Why would it matter to me if I'm querying data from a sql-, cds-, analytic-, calculation-view or a table function (let alone a table)? What matters (to me) how the interface works. Do I need parameters or not? What does the data look like that I get back?

When I want to edit the object, I'm looking for the package location and it's name - the type really doesn't bother me at that point. If, on the other hand, the three additional characters can be used to make the name more telling about the meaning of the object, I'd rather have that.


Thanks for your feedback. I appreciate especially:

  • Jelena mentioned the review of ABAP Guidelines: prefixes where removed
  • Lars for clearly pointing to interface thinking and of course feedback from an SAP employee.

Found the old blog if anyone is interested:

157 comments, lots of reading there. :)

avatar image
Former Member Aug 07, 2017 at 05:01 PM

Hello Thorsten,

There are no recommendations for naming conventions in HANA. But convention is to use an object identifier like AV, CV or SP for procedures. The rest of the text is up to you. You could use CV<running number>_SV/GV(scripted or graphic)_<short description> or SP<running number>_READ/WRITE_<short description>. Its entirely up to how you want to identify from a view name.

10 |10000 characters needed characters left characters exceeded
Clemens Kopfer Aug 31, 2017 at 10:36 AM

For HANA-SDI there is a pretty good best practice guide which includes naming convention proposals.

Same principle, but with detailed proposals, as Benedict proposed --> using prefix (in CAPITALS).

10 |10000 characters needed characters left characters exceeded