Skip to Content
0

HANA CDS Views Import failed after transport to next system

Jun 16, 2017 at 01:19 PM

151

avatar image
Former Member

Hello Everyone,

We are having a scenario where we need to have sub selects and nested selects as part of HANA CDS views. We are creating separate views for each sub select/nested select and using it as joins in main CDS Views within the same HDBDD file.

When HDBDD file is transported, if we have HANA CDS Views consuming views/tables which are already activated in the system then the import is successful. If we have a scenario where we are using other CDS views in the same HDBDD file and that dependent view (v_equi) is not activated yet in the system then the import is failed.

e.g.

First View: VIEW v_equi AS

SELECT FROM "EQUI" AS "EQUI"

INNER JOIN "MARA" AS "MARA"

ON "EQUI"."MANDT" = "MARA"."MANDT"

AND "EQUI"."MATNR" = "MARA"."MATNR" {

"EQUI"."EQUNR",

"EQUI"."INVNR",

WHEN "MARA"."MTART" = 'SOME Conditional logic'

THEN 'X'

ELSE ''

END AS "FILTER" }

WHERE "MARA"."MTART" in ('SOME conditional logic'); //Allowed material types

Second View: VIEW v_EQUI_FILTERED AS

SELECT FROM "v_equi" AS "EQUI" {

"EQUI"."EQUNR",

"EQUI"."INVNR",

} WHERE "EQUI"."FILTER" = 'X';

-

Would like to know if this is a standard behavior and how to overcome this transport failure issue .

-

Thanks & Regards

Santhosh

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

1 Answer

Thomas Jung
Jun 20, 2017 at 06:47 PM
0

How is v_equi created? Is it created via hdbview? How is the syntax in the HDBDD that references the V_EQUI view done? Do you have a USING statement in the HDBDD file?

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

Hello Thomas,

Thanks for the reply.

Both the views v_equi and v_EQUI_FILTERED are in the same HDBDD file .

When am transporting the hdbdd file to the next environment for the first time am getting the error, as the view v_equi which v_EQUI_FILTERED is referring is not active yet.

Currently we are following this approach.

Step 1: Comment v_EQUI_FILTERED code and activate the hdbdd file only with v_equi manually, it gets activated.

Step 2: Uncomment v_EQUI_FILTERED code and activate hdbdd file, it gets activated (as the view v_equi which it refers is already active).

Kindly suggest

0

In the same file? I've never seen a problem with dependencies between objects in the same file. I've only ever seen an issue when you get into complex relationships cross artifact.

You could of course enter a support ticket. Likely the solution will be to suggest moving to HDI. The dependency calculation in HDI is far superior to the old Repository Activation. I've done much more complex cross object dependencies then I would have ever attempted in the old Repository without any problem in HDI.

0
Former Member
Thomas Jung

Sure Thomas thanks. Will suggest to move towards HDI.

Thanks

Santhosh

0