Skip to Content
Author's profile photo Former Member

Naming Convention in Business Objects

    When you start to Business Objects Design from the origin, nobody usually is thinking of that the standard naming for reports , connections, universes , folders etc…  But if you have thousands of objects in your company , it is getting more hard to handle and search the objects. So I’m gonna try to give you some tips about how should be the naming convention of BO Applications.

1- Connections

Conn.pngAs you know, there are two different types of connection in Business objects which are Relational and OLAP connection. 

First of all, the main issue that I have faced with is writing the type of the objects as a prefix such as CON_EFASHION. You don’t have to identify the type of object in the name, it is obvious from the icon and the folder it is connection.  Even in BO Audit Database you can classify with the object type.  But, for the trace logs maybe it is good to identify but it is rare condition.

a. Relational Connection


DB or SCHEMA ( Preferable )




    In the Beginning, to understand which data source is being used for that connection, we should write the abbreviation of data source such as HANA, BWP and BIP etc…

    Besides, if datasources has more than one database or schema, it could be good to write the name of DB or SCHEMA. This condition depends on the structure of datasource.

    /wp-content/uploads/2015/02/relat_638264.jpgAfter we get the datasource information, then we should understand what kind of data that we get from the data source.  For that reason, we should classify the type of data. Depends the classification of your company, you should write the abbreviation of module or Department such as CRM, FI, HR etc…  Then we should give a number for each connection in a module.  At the end, we need some information about the data in the datasource so we should give a short explanation of the data.



    b. OLAP Connection



    Olap.jpgIn OLAP Connection, I will just explain for the BW Bex Queries. It is easy to define this. First the abbreviation of datasource, then the technical name of the Query, it is so easyIt is recommended that writing the description of the query in the description part.

Example:    HWP-ZQY_YQBI0001_Q001 

klasörler.jpgOn the other hand you can create folder for each datasource in the repository, Even if you have so many connections for each you can create sub-folders under the datasource folder and put the connections in the folder according to the module and datasource to organise them better.   

2- Universes

              a. Connection

    I have already explained the connection. Shortcut connection can remain the same name as original connection.

        b. Data Foundation



Naming Convention for Data Foundation is not so important to handle because it is obvious to which Business Layer use it and which connection is connected. But I am generally using this structure.


          c. Business Layer




BusinessLayer.jpgWhen you define a name for universe (business layer), you should consider that the name will be shown by end-users. So the name should be understandable for business users as well.

That’s why we need to define the good explanation of the universe. I also add the module name as a prefix to find the universe easily when you search it.

The main issue in this, ‘BL’ is written as a prefix for the name of universe. It is totally unnecessary. End-Users don’t understand what ‘BL’ is.


On the other hand, the dimensions and measures that will be used in universe also clearly understandable and some of them requires some description to end user should understand easily.

3- Reports




You should have different folders or sub-folders for each department or module in the repository. It is good to give a number for each report in a folder( module ) . Because the order of reports do not change when you add another reports in a folder. Besides,  You don’t have to write the “report” in the name of report such as “Balance Sheet Report”, It is better not to write unneccesary words. 

                                Example: 01-CRM : Daily Performance

                                Example: 01-FICA: Balance Sheet

Example: 02-FICA: Cash Flow

  This blog is not what you have to follow , it should give you a perspective to how you should make your naming convention, so according to the organization of company, it could change.

I hope this blog gives you some tips of how you should look at the naming convention in Business Objects.  If you have more idea about the subject , I will be glad to add to the blog. Feel  free to write your comment.


Assigned Tags

      1 Comment
      You must be Logged on to comment or reply to a post.
      Author's profile photo Mahboob Mohammed
      Mahboob Mohammed

      Thanks Arslan. This will come handy for sure.

      Mahboob Mohammed