Moving views from different packages

[#1]

Hi,

I have created a calculation view in HANA and the details are as follows:

Header 1	Header 2	Header 3
Calculation View	Calc1	Package1
Analytic view	AV1	Package 2
Attribute View	AttView1	Package3
Attribute View	AttView2	Package4
Attribute View	AttView3	Package3

Here the Calc1 is based on an Analytic View named AV1 which in turn uses the AttView1, AttView2 and AttView3.

Now as you can see, all these views are created in different package. All the Views are active and working fine as of now. Now, my aim is to move/copy all these views in to one single package named "MainPackage".

One way to do this is to recreate all these views using Copy From option in the new package and then connect all the attribute views (new ones in the MainPackage) to the  new analytic view (in the MainPackage) and then use this analytic view into the new calculation view (in the MainPackage). But this will require a lot of rework.  Is there a way to do it which will have minimum amount of rework?

Regards,

Piyush

[Ravi_Channe · Accepted solution]

Hi Piyush,

If you are on SP05, you can try 'refactoring' your objects to the MainPackage. It will move the objects to the required package (MainPackage) from the existing packages and recompile them.

You may have to start from Attrib views (base objects) first and move to Analytic and Calc views.

The refactoring option is available on the right click on the object.

Please refer to section 7.5.3 in HANA developer Guide.

Regards,

Ravi

[patrickbachmann · Accepted solution]

I have found the Refactoring is not helpful for myself because I want to see a history of the work I've done and the refactor seems to MOVE the objects (doesn't copy and leave original in tact).  So the way we handle this is by having a development package with a bunch of sub-packages by project.  Then unfortunately yes, once approved for production we manually copy to another package called production which has subfolders by functional area.  Then our delivery unit used for export only picks up our production packages and sub-packages.  I like the fact that refactor option recompiles your objects however we wanted to see a history of the original objects so we prefer the copy method.  If there was a refactor option that was COPY and REFACTOR rather than MOVE and REFACTOR then it would be great.

Not sure if that helps but that's how we handle this, for now at least.

-Patrick

[amit_agarwal21 · Accepted solution]

Refactoring will work, however if all the impacted objects are not present in your system ( case when you might have imported it from another system and all impacted objects are not yet there then it might fail ).

Subsequent to this I have another question that lets say if I move the view from one package to another package using refactoring then will my BO layer also acknowledge this change automatically or BO work ( at least universe level ) will have to be done again.

Pls confirm.

regards

Amit

[Ravi_Channe · Accepted solution]

Hi Amit,

If the dependent objects are not available, then I think the movement should work, but the objects might remain inactive. I haven't tried this specific scenario yet.

Regarding the BO layer, I think it will not recognize the change in the package. The BO layer will need the rework.

Regards,

Ravi