Skip to Content

role in dependancy object.

Dec 29, 2016 at 06:31 AM


avatar image

I have a CV, when i see where used list I could find two uses of it.

1. In another CV.

2. In a role.

when i see the table "SYS"."OBJECT_DEPENDENCIES" I couldn't find the role as a dependency object.

Does it mean anything.

Actually my aim here is to delete the CV, can I delete the CV without changing role.

Can anyone throw some light over this.

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

2 Answers

Florian Pfeffer
Dec 29, 2016 at 08:27 AM

The OBJECT_DEPENDENCIES view does not list dependencies to roles (this is so cause of the setup of the underlying OBJECTS view). So this is not an issue.

But you cannot delete the CV in a consistent way w/o adjusting the role too. When you delete the CV you will get an error for the role object that the CV is missing. So you have to first remove the CV from the role and then delete the CV to have a consistent implementation.


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

I tried to edit the question but got an error.

Can you please tell me the significance of DEPENDENCY_TYPE column in that table.


The only available (not complete) documentation for that column I know can be found here: SYS.OBJECT_DEPENDENCIES


Thank you so much for the reply Florian Pfeffer. I like your replies and I read them a lot.

Yeah, I ended up at the same spot in my search and questioning here.

i even saw a link where a similar question was mentioned, but not the solution.

I will keep searching for it. :)

Lars Breddemann
Jan 02, 2017 at 11:22 PM

Florian is right about the state of documentation of OBJECT_DEPENDENCIES.

In I provides some more information - based on what I could make out of the view's content.

For most practical matters of development/deployment dependency handling, DEPENDENCY_TYPE 1 and 2 are the most relevant ones (direct and indirect dependency).

For your question about roles: it's good to remember that OBJECT_DEPENDENCIES shows runtime dependencies, that means the dependent objects are not guaranteed to continue to work if the object they depend on gets changed.

For roles, that's different as if you change, e.g. a table the role does not change and does not stop to function properly. If you delete a table covered by a role, all that will happen is that the role will not be triggered anymore for this table (as it is not existent anymore).

However, upon activation of a role, it will be checked that all referenced objects exist at that point in time.

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

Thank you so much for the response Lars Breddemann.

I got a one more step close.

Most of the Stéphane MARIE replies in the thread you have given suits my situation.

Even I am trying to cleanse my application which contains 1150 odd number of objects(or artifacts).

Actually in a situation now i am doing manually each object. Thought I could get a clear cut difference in the usage by Dependency_type so that there will be less manual work required.

I have to still investigate about the direct and indirect dependencies to achieve my goal.


Hmm... well what Stephane wanted to build back then is a full dependency network of all objects.

To my knowledge, that is not directly possible. What I used in the past successfully a couple of times it to just go with the direct dependencies (type =1) from the view and build a graph based on that.

That way I can easily track indirect dependencies to some degree.

Looking back on the open question from Stephane's last comment, I'd guess that the usually in a table -> calc view -> calc view scenario, the dependency type 2 should be present between the table and the second calc. view.

However, if none of the table fields actually are used in the second calc. view (e.g. only some column from the middle calc view get projected and those didn't come from the table) then no indirect dependency should be maintained.


Hello Lars Breddemann,

I got an answer for the question i have been searching for(full dependency network of all objects)

This the the table which will be helpful in this case.


also to some extent if we search dependencies in reverse way(reversing base object and depend object in our search) in the OBJECT_DEPENDENCIES will gives better result.

One more info in this context was that the access to _SYS_REPO tables will not be there in future releases.

Can you give any point why this could happen.

Also i couldn't find any documentation on this _SYS_REPO tables.