Difference between catalog views and content views

[Former Member]

Hi All,

I wanted to know what is the difference between the views that are in catalog folder and the views that are in content folder( Attribute view, Analytic view and Calc View).

If we can build views from catalog folder, then why SAP has come with different views that are in content. I'm bit confused with this.

[Former Member]

Thank you everyone.....it helped me 🙂

Regards,

Pradeep

[srinivasan_vinayagam]

Hi Pradeep,

Catalog view customer specific different Views( Attribute, Analytic, CV) Scripts and so on.

Content View contains customer/SAP specific tables, activated views and so on.

Regards,

V Srinivasan

[Former Member]

Content is the placeholder for Designtime Information Models

Catalog is the placeholder for Runtime Objects.

Thanks.

[Former Member]

Hi Swarna,

Could you please give some kind of example what is Designtime Information Models & what are Runtime objects ?

A real time example

I am not a BW person

[Former Member]

Hi Pawan,

As mentioned by swarna, the objects in the content folder are design time objects (created in "project explorer")and these design time objects are later activated to create run time artifacts, you can see these run time artifacts in the "Catalog".

Design time artifacts can be seen as a defination for run time artifacts.

Creating design time objects helps in maintaining the source code, transportation of source code between different systems(in the form of delivery units) like from Dev to testing and from testing to production.

Examples of design time artifacts are files ending with .hdbprocedure, .attributeview, .xsodata or .hdbdd files, you usually create these files in project explorer and on committ these files are copied to repository i.e., under "content" folder. These files are later activated to create run time artifacts.

Examples for runtime artifacts would be the tables, procedures in the catalog.

Regards,

Vijay.